8. Corporate Device Management¶
Once a mobile device belongs to or is used for an organization, there are a few standard models for who owns what, and who controls what.
| Model | Who owns the device | Personal use allowed? |
|---|---|---|
| COBO (Corporately Owned, Business Only) | The organization | No — work only |
| COPE (Corporately Owned, Personally Enabled) | The organization | Yes, alongside work use |
| BYOD (Bring Your Own Device) | The employee/student | Yes — it's their personal device |
Why this matters beyond the label¶
- COBO/COPE devices can be fully controlled by MDM without much controversy — the organization owns the hardware.
- BYOD is where things get complicated: the organization needs some control (to protect its data) on a device it doesn't own, which raises real questions about privacy, what an MDM profile can see, and what happens to personal data if the device is wiped.
Containerization is the usual answer to the BYOD problem: MDM creates a separate, encrypted "work" space on the personal device, so a remote wipe can erase just that container — emails, work apps, work files — without touching personal photos or apps.
Try it
A school is deciding whether students use school-owned tablets (COPE) or their own personal devices (BYOD) for the MUD lab. List one real advantage and one real downside of each approach for this specific situation.
Tip
Before enrolling a personal device in any MDM system, it's worth actually reading what the enrollment screen says the organization can see and do — containerization limits it, but the exact boundary varies by MDM product.
Watch along
From the CompTIA A+ 220-1201 Full Course: Corporate device management (49:22)