TMA-ANDROID-WORK-PROFILE
Ensure corporate data on personally owned devices is isolated in a managed work profile
Description
A work profile (Android Enterprise) separates corporate apps and data into an encrypted, separately managed user so the organisation can enforce policy and wipe work data without touching personal data, and blocks data flow between profiles.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
On device: Settings > Passwords & accounts shows separate Personal and Work tabs and the launcher shows badged work apps; Settings > Security & privacy > Device admin apps lists the organisation's EMM (e.g. Android Device Policy). Optional read-only adb: adb shell pm list users shows a managed profile. EMM console: device enrolled as Work profile (personally owned) or Fully managed (company owned) and compliant, with crossProfilePolicies blocking copy/paste and data sharing from work to personal.
How it is fixed
Fix method: Guidance or infrastructure patch
Enroll the device through the EMM as an Android Enterprise work profile (BYOD) or fully managed device (company owned) and deploy corporate apps only into the work profile; set crossProfilePolicies to block copy/paste and data sharing from work to personal.
Properties
- Operating systems
- Any
- Tags
- androidandroid-enterprisework-profilebyod
- Reference
- CIS Google Android Benchmark - Work profile / Android Enterprise management (verify section number for your release)