BYOD & Device Isolation
Mobile Enterprise & MDM Security · Mobile Advanced Security track
9 min read
In this module
The BYOD Challenge
Bring Your Own Device (BYOD) sits on a tension you can't engineer away. Employees want their phones at work — familiar, always nearby, often nicer than what corporate IT issues. Organisations want their data protected on those phones. Nobody wants their boss reading their iMessages, looking at their photos, or watching what they bank with.
The way out is isolation. Technical mechanisms that wall corporate data off from personal data, so the organisation can manage what it owns without rummaging through what it doesn't.
Android Work Profile
Android's Work Profile is the workhorse for BYOD isolation. It carves a separate encrypted container into the device with its own storage, apps, contacts, and accounts.
Under the hood, a work profile is a second Android user. Install the same app on both sides and you get two copies with different Linux UIDs (user ID × 100000 + app ID), different data directories and different keys. The UIDs below are illustrative.
If no separate work passcode is set, the work profile's credential-encrypted storage is unlocked by the device credential instead.
Isolation Properties
Isolation here lives at the OS level, and it's serious:
- Separate storage: Work apps cannot access personal files, and personal apps cannot access work files. The filesystem is cryptographically separated.
- Separate contacts: Work contacts appear in a separate section. Personal apps cannot query work contacts, and work apps cannot access personal contacts (unless explicitly configured).
- Separate clipboard: Copy-paste between work and personal apps is blocked by default (configurable by MDM policy).
- Separate accounts: Work profile has its own Google account and app installations. The Play Store shows a "Work" tab with enterprise-approved apps.
- Independent encryption: The work profile has its own encryption, which can be configured with a separate work passcode.
MDM Control Boundaries
The MDM can enforce policies only within the work profile:
- Install and remove work apps.
- Configure work email, VPN, and WiFi for work apps.
- Enforce passcode requirements for the work profile.
- Wipe the work profile (selective wipe) without affecting personal data.
- Restrict copy-paste, screenshot, and sharing between work and personal.
What the MDM cannot do: read personal messages, peek at photos, browse history, install apps on the personal side, or track location (barring a separately granted permission).
User Experience
Work apps wear a tiny briefcase badge to set them apart. Users can pause the work profile entirely outside working hours, killing every work app and notification at once. Small thing, big morale impact.
The Android Work Profile provides a contractual and technical privacy guarantee to the employee. The MDM documentation and the Android setup flow explicitly state that the organisation cannot see personal data. This guarantee is enforced at the OS level through Linux kernel UID separation, SELinux policies, and encrypted storage boundaries. Reading personal data directly would take a kernel exploit. It isn't absolute, though: on company-owned devices the admin sees more device-wide information, and policy choices such as cross-profile clipboard or sharing rules, or an accessibility service the user grants across profiles, can still leak data from one side to the other. This privacy guarantee is what makes BYOD programmes acceptable to employees.
iOS User Enrolment
Apple's BYOD answer is User Enrolment, shipped in iOS 13. Where supervised enrolment hands the MDM a fistful of device-wide power, User Enrolment is built to manage corporate data and nothing else.
How It Works
User Enrolment plants a Managed Apple Account (called a managed Apple ID until Apple renamed it in 2024) on the device next to the user's personal one. Managed apps and data anchor to the managed account; personal apps and data stay with the personal Apple Account.
Separation is enforced per-app:
- Managed apps live in a separate container, encrypted with a key tied to the managed account.
- Managed apps can't hand documents to personal apps: managed open-in rules block it. Since iOS 15 the MDM can also set the
requireManagedPasteboardrestriction, which makes copy and paste follow the same rules. - The MDM installs and removes managed apps, pushes configuration profiles for managed accounts, and selectively wipes managed data.
Limitations Compared to Android Work Profile
iOS User Enrolment isolates less than Android Work Profile:
- No visual "work container". Managed and personal apps share the same home screen grid.
- The MDM can't enumerate the user's personal apps. It only sees the managed ones.
- The MDM can insist that a passcode exists, but only a basic one: in practice a six-digit, non-simple PIN. It can't push complexity rules, and it gets no unlock token to clear the passcode.
- User Enrolment can't be mandated via ADE. The user has to opt in voluntarily.
Samsung Knox
Samsung Knox piles hardware-backed extras on top of Android Enterprise, all Samsung-specific. Government and defence shops lean on it heavily where stock Android Enterprise isn't enough.
TIMA (TrustZone-based Integrity Measurement Architecture)
TIMA lives in the ARM TrustZone Secure World and watches integrity from a vantage point Android can't reach:
- Kernel integrity: TIMA periodically measures the kernel code and data, comparing against a known-good baseline. If tampering is detected, Knox triggers a remediation action (container lock, device wipe).
- SE for Android policy monitoring: TIMA verifies that SELinux policies have not been modified by a compromised kernel.
- Boot attestation: Knox verifies the integrity of the boot chain (bootloader, kernel, system image) using hardware-rooted trust. If any component has been tampered with, a hardware e-fuse is permanently set, recording the integrity violation.
Knox Container
Knox Container (now folded into Samsung's Separated Apps feature) layers extra isolation on top of the standard Work Profile:
- Defence-grade encryption: Container data is encrypted with a key derived from both the user's credentials and a hardware-bound key in the TrustZone.
- Per-app VPN: Traffic from apps inside the container can be routed through a dedicated VPN, while personal app traffic uses the normal network path.
- Common Criteria certification: Samsung Knox has achieved Common Criteria certification, which is required for certain government deployments.
App-Level Containerisation
When platform-level isolation isn't enough — or isn't available — organisations move to app-level containerisation. Wrap enterprise apps with an SDK or binary wrapper, bolt security controls on from the outside.
App Wrapping
App wrapping drapes a security layer over an existing app binary, no source-code edits required. The wrapper hooks system API calls and enforces policy on its way through:
- Data-at-rest encryption for the app's local storage.
- Certificate pinning for network connections.
- Copy-paste restrictions.
- Screenshot prevention.
- Authentication requirements (PIN, biometric) before app launch.
- Jailbreak/root detection with app self-destruction.
Citrix (Secure Hub), MobileIron (now Ivanti), and Microsoft (Intune App Protection Policies) all sell flavours of this.
SDK Integration
For in-house apps, integrating an MDM vendor's SDK reaches further than wrapping ever can. The SDK exposes APIs for:
- Secure local storage with hardware-backed encryption.
- Managed networking (per-app VPN, proxy configuration).
- Data loss prevention (DLP) policies enforced at the API level.
- Remote wipe of the app's data container.
Try matching each of these people to an enrolment model and a wipe policy, and note what the organisation can see on their phone. There's more than one defensible answer for some of them.
- A six-month contractor with their own Android phone who needs Outlook and Teams.
- An executive carrying a company-bought iPhone that holds board papers.
- A field engineer sharing a rugged Android handset with the next shift, running one inspection app.
Show one reasonable answer
- App protection policies with no device enrolment at all, or a Work Profile if the contractor accepts one. Either way the only wipe on the table is selective, and the organisation sees nothing outside the managed apps. Anything heavier is hard to justify for a short contract.
- Company-owned, so supervised full management through Automated Device Enrolment is fair game: full wipe, device-wide restrictions, managed open-in for the board papers. The privacy note should say plainly that this phone isn't a personal device, and the executive keeps personal life on a second one.
- A fully managed dedicated device in kiosk (lock task) mode, locked to the inspection app. Full wipe is fine because nobody's personal data should be on it, and there's no privacy note to write beyond "this device belongs to the company".
Data Loss Prevention (DLP)
DLP policies stop corporate data from wandering out of the managed bubble.
Copy-Paste Restrictions
MDM can block clipboard sharing across the managed/unmanaged boundary. Android Work Profile enforces this at the OS level. iOS 15 and later can too, through the requireManagedPasteboard restriction, which makes copy and paste obey the managed open-in rules. Anything finer, such as allowing paste only into specific apps, still needs an app protection policy like Intune's, which covers only apps built with the Intune SDK or wrapped.
Screenshot Prevention
Android exposes FLAG_SECURE on activities, which kills screenshots and screen recording. MDM policy can force this for managed apps. iOS has no per-app equivalent for MDM to force. What it does have is a device-wide restriction (allowScreenShot, which also covers screen recording), and switching that off on someone's personal phone is a heavy hand.
Managed Open-In
Both iOS and Android support managed open-in restrictions. Files from managed apps can only open in other managed apps. The user can't take a corporate document, hand it to a personal cloud storage app, and upload it into the wild.
BYOD isolation ranges from full device management (maximum security, minimum privacy) through platform-level containers (Work Profile, User Enrolment - balanced security and privacy) to app-level wrapping (minimum device impact, security limited to wrapped apps). The choice depends on the organisation's risk tolerance, the sensitivity of the data, and the employees' privacy expectations. Stronger isolation increases security but also increases friction and may reduce BYOD adoption rates.