Bring Your Own Device policies are common in SMEs where providing every employee with a company device is cost-prohibitive. They create a complex security environment where corporate credentials exist on a device the organisation does not control, running software it has not vetted, on networks it cannot monitor. With the right controls in place, BYOD is workable; without them, it is a significant credential security risk.
BYOD Credential Risks by Category
| Risk | How it manifests | Control |
|---|---|---|
| Browser autofill spillover | Work credentials saved in personal browser profile, accessible to family members | Mandate company password manager for all work credentials |
| Retained access after leaving | Employee still has work credentials on personal device months after departure | Revoke password manager access on last day; change shared credentials |
| Personal device malware | Malware capturing keystrokes or clipboard on a personal device used for work | MDM with malware detection; require up-to-date OS; block side-loaded apps |
| Weak screen lock | Physical device access gives access to work apps | Policy and/or MDM requiring strong PIN or biometric |
| iCloud/Google backup of credentials | Work credentials backed up to personal cloud account outside company control | Configure password manager to prevent backup; use business app not personal |
The Minimum BYOD Policy Requirements
- All work credentials accessed exclusively through the company password manager app, not the personal browser or personal password manager
- Screen lock with PIN of at least 6 digits or biometric, auto-lock within 5 minutes
- MFA enabled on all work accounts accessed from the personal device
- Disk encryption enabled (standard on iOS; Settings → Security on Android)
- Written agreement at onboarding that the company may require remote wipe of corporate data on departure
When the Employee Leaves or the Device Changes Hands
One of the most significant credential risks in any BYOD arrangement arises at the moment an employee leaves the organisation or stops using a particular device for work. Unlike a company-owned laptop, you cannot physically collect a personal phone or tablet, wipe it remotely without consent, or compel the employee to hand it over. Your ability to act is constrained from the outset.
What you can require under a well-drafted BYOD policy:
- Revocation of all work account access through your identity provider or MDM platform before or on the employee's final day.
- Removal of any corporate applications, certificates or VPN profiles you have pushed to the device.
- Signed acknowledgement that the employee will delete locally cached work data, including email attachments and downloaded files.
- Return of any hardware tokens or physical security keys issued separately.
What you generally cannot require without explicit prior agreement:
- A full remote wipe of the device, which would erase personal data and may expose you to liability under UK data protection law.
- Access to personal accounts or applications stored alongside work ones.
- Inspection of personal files as part of an offboarding audit.
Device resale or replacement introduces a separate risk. If an employee sells or trades in a device that was used for work, locally stored credentials, session tokens or cached passwords could persist even after a factory reset on some operating systems. Your policy should require employees to notify IT before disposing of any device that accessed corporate systems, so that server-side sessions can be terminated and access logs reviewed.
The practical lesson for SMEs is that offboarding procedures must be designed before an employee is ever enrolled in BYOD, not improvised when they hand in their notice. Centralised identity management, with the ability to revoke individual device sessions instantly, is the most reliable control available.