BYOD (Bring Your Own Device)

BYOD adoption is usually driven by cost and convenience — an organization doesn't have to buy and provision a device for every employee, and employees often prefer using hardware they already know — but it inverts the usual IT relationship: the device exists first, and management gets layered on afterward, if it gets layered on at all.

The core tension is that a personal device mixes personal and corporate data on the same hardware, which is why BYOD management usually looks different from full corporate-device management: containerization (separating a managed work profile from the rest of the phone) and conditional access (require a passcode and encryption before corporate email connects, without controlling the whole device) are common middle grounds.

Policy has to answer specific, sometimes uncomfortable questions before rollout — can IT remote-wipe a personal device, what happens to that access when the employee leaves, does the policy even apply to contractors — because a BYOD program with no written answer to those questions tends to improvise the answer during an actual incident instead.