Colour theme
Book a consultation

Nine checks before a phone handles work data

Review ownership, support, locking, work apps, access, data removal, reporting, backups and departure handling before using a phone for business.

Application icons displayed on a smartphone screen against a black background

A phone that can open work email may also store attachments, contacts and signed-in sessions. Before you allow that access, decide how the work data is protected and who acts when the phone is lost or changes hands.

Run through these nine checks on a test phone with the apps staff will use, and with made-up sample data.

1. Agree on ownership and permitted work

Record whether the phone belongs to the organization or the employee. Write down which tasks and information staff may handle on it.

The Cyber Centre’s mobile deployment guidance explains ownership options. For a personal phone, agree what the business can see and control before enrolment, and check the privacy implications. With Intune app protection, for example, the business can manage its work apps without enrolling the whole phone.

2. Confirm support and updates

Check the manufacturer’s support status, operating-system version and update process. Include the apps required for work.

Decide what happens when a phone stops getting updates. Its email app may keep working long after the security fixes for its operating system have stopped.

3. Test locking and account access

Require a PIN or passcode, with fingerprint or face unlock if you like, and a short auto-lock. The phone’s lock and the work account’s sign-in are separate controls, so check multi-factor authentication and account recovery too.

Turn off lock-screen message previews if they could show work information. Don’t share the unlock code to make a handoff easier.

4. Choose the apps and storage locations

Choose the apps needed for the task and install them from the official app store or your company portal. Review requested permissions and cloud connections.

Test whether attachments and files can move into personal storage. Keep work files in the work location, such as OneDrive for Business, and note any exception you agree to.

5. Check connection and remote-access rules

Decide which networks staff may use for work. The phone’s own mobile data is often a safer choice than public Wi-Fi. Test the VPN or app access if the task needs it.

A VPN protects the connection, but it can’t spot a fake website or remove malware from the phone.

6. Understand management and removal limits

Check which device or app controls your management platform supports. Know the difference between a factory reset, retiring the phone from management and removing only the work-app data.

Microsoft’s selective-wipe documentation shows that a selective wipe only reaches apps covered by your policies. A wipe also waits until the phone next connects, and it can’t reach a copy already saved somewhere else.

7. Make reporting usable

Tell staff how to report a lost phone, an unexpected sign-in prompt or a suspicious text.

Make sure they have a number to call when they can’t use work email. Don’t require staff to retrieve a missing phone themselves.

8. Verify work-data recovery

Find out what’s stored only on the phone, such as site photos or notes, and what’s already in a managed service. Check how the phone-only information is backed up.

Test that it can be recovered without putting business information in a personal iCloud or Google account. Include records created while the device was offline.

9. Test departure and reassignment

With a test account, practise removing access and wiping the work data. Hand over any shared records, and remove the phone’s number from accounts that use it for recovery or sign-in codes.

Note the result before the phone goes to someone else. Repeat the checks when the apps, the owner or the work changes.


Featured Image Credit