How do we…
How do we decide the rules for remote working and personal devices under ISO 27001?
Add to board memoOpen the memo
The short answer
- Recommendation
- Decide first whether personal devices may reach company data. If not, block them at sign-in. If so, prefer browser or app-level controls over managing the whole device, set a baseline for managed devices, and make loss reporting, wipe and leaver steps work. Brief staff and sample.
- Reasoning
- Auditors ask which devices reach company data and how you know they meet your rules. The usual gaps are company email on unmanaged phones, devices out of compliance for months, loss reported late with no way to wipe and leavers who keep a laptop. The BYOD decision is a risk decision that top management should take on purpose, not drift into.
- Considerations
- The standard's text is paywalled. The controls are described from the pack's Library and public guides, which are secondary.
- NCSC's BYOD guidance is a UK source and advises a risk-based approach. Other regulators publish similar guidance.
- Monitoring personal devices touches privacy law and employment terms. Agree the approach with whoever advises on data protection.
- A fully remote organisation still needs the physical rules for homes and shared spaces. The question on a shared building covers that.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
- Loop back
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 20 steps.
Start
People work outside the office and some use their own devices
Remote working and device controls keep information safe when it leaves the building. The Library's mistakes are rules that assume a VPN nobody uses, personal devices with no controls reaching company data, and company email on unmanaged phones. The decision is what you allow, and on what terms.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
List who works remotely, from where, and what each group can reach
Include home, travel and shared spaces such as coworking sites, and separate staff from contractors. For each group note the systems and the classification of the information they reach. The rule you write should follow that picture, not a guess.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
- P15-A03 Classification Level Handling Rules MatrixHandling matrix
Decision
Will personal devices be allowed to reach company data?
NCSC advises starting from objectives, user needs and risks, and says no organisation can do all its functions securely on personal devices alone. Allowing them is a risk decision for top management, not a default. If staff already use them and nobody decided, answer yes and decide now.
- No: Block unmanaged devices at sign-in and say so in the rule
- Yes, or not known: Can people reach data in a browser or app without storing it locally?
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Block unmanaged devices at sign-in and say so in the rule
Use conditional access so only managed, compliant devices reach company data. State the rule in the remote working document and in the acceptable use policy, and tell staff what to do instead, such as the loan of a laptop.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Can people reach data in a browser or app without storing it locally?
Browser access and app-level controls keep company data off the personal device and need no management of the whole device. NCSC compares web access, virtual desktops, mobile device management and mobile application management. If staff need files stored locally, answer no.
- Yes: Use app controls: strong sign-in, no local download, device checks
- No: Enrol the device in management, or refuse it
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Use app controls: strong sign-in, no local download, device checks
Require multi-factor sign-in, block saving to the device where the data is sensitive, require a screen lock and a current operating system, and be able to remove company data alone. State what you cannot see on a personal device.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Enrol the device in management, or refuse it
NCSC warns that full management of a personal device makes it a corporate device in practice, with the privacy and cost consequences that brings. Tell staff plainly what you can see on the device and what you could wipe, and agree the terms before enrolment. The legal basis for that is a question for whoever advises on data protection. If staff will not accept the terms, they get a company device.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Do managed devices enforce encryption, lock, updates, malware cover?
Devices out of compliance for months with no action is the Library's named mistake. A report from device management shows the state. If you have not looked at the report this month, answer no.
- Yes: Can you lock or wipe a lost device, and do people report loss quickly?
- No, or not known: Set the baseline and block or chase non-compliant devices
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Set the baseline and block or chase non-compliant devices
Make the baseline automatic where you can. Give non-compliant devices a short deadline to fix, then restrict access, and track the exceptions with an owner and a date.
In the pack
- P02-A02 Security Exception & Waiver StandardWhen an exception is needed
Decision
Can you lock or wipe a lost device, and do people report loss quickly?
The Library's mistake is loss reported days later and no way to wipe a phone that has company email. For a personal device you may be able to remove only company data. If you cannot, answer no.
- Yes: Do staff handle Confidential information at home or on the move?
- No, or not known: Set a reporting rule and limit access until the device is dealt with
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Set a reporting rule and limit access until the device is dealt with
Tell staff who to call, any time, and what happens next: sessions revoked, device locked or company data wiped. Test it with one device. Include travel: a lost laptop abroad is the same problem.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Do staff handle Confidential information at home or on the move?
Rules for home networks, public places, screens and papers matter more as the classification rises. The pack's handling matrix has a row for remote and mobile working. If you have not asked, answer yes.
- Yes, or not known: Set simple rules for where and how Confidential work may be done
- No: Do leavers and movers lose access and return or wipe their devices?
In the pack
- P15-A03 Classification Level Handling Rules MatrixHandling matrix
- P15-A02 Information Classification & Handling PolicyHandling and labelling
Step
Set simple rules for where and how Confidential work may be done
Say how people connect to company systems and whether that way is actually used, since rules that assume a VPN nobody uses are a mistake the Library names. Cover screens in public places, calls, printing and paper at home, shared spaces and travel to places you decide are higher risk. Keep it to a page that people can follow, and put it in the briefing.
In the pack
- P15-A03 Classification Level Handling Rules MatrixHandling matrix
Decision
Do leavers and movers lose access and return or wipe their devices?
A leaver's account still active, or a company laptop never returned, shows how remote devices escape control. The leaver checklist includes device return and the wipe. If devices are not part of the leaver steps, answer no.
- Yes: Brief staff and keep their acknowledgement
- No, or not known: Add device return, wipe and data removal to leaver and mover steps
In the pack
- P13-A06 Leaver Access Removal ChecklistLeavers
Step
Add device return, wipe and data removal to leaver and mover steps
Tie the inventory of devices to the leaver checklist and chase the return. For personal devices, record that company data was removed and by whom.
In the pack
- P13-A06 Leaver Access Removal ChecklistRemoval checks
Step
Brief staff and keep their acknowledgement
The rules work only if people know them. Put them into the induction and the acknowledgement process. The Library lists acknowledgements as part of the evidence.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Check a sample of devices and sign-ins against the rule
Compare the device management report and the conditional access settings with the rule. Check a few leavers and a lost-device record. The auditor samples the same evidence.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Did the sample show a device or sign-in the rule does not allow?
Any unmanaged device with access, or a leaver's device not recovered, shows the rule is not yet applied. If you did not sample, answer yes.
- Yes, or not known: Close the route, fix the record and sample again
- No: Remote working and device rules decided, enforced and sampled
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Close the route, fix the record and sample again
Block or enrol the device, correct the leaver step that missed it and take a fresh sample.
- Then: Check a sample of devices and sign-ins against the rule (back to an earlier step)
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Outcome
Remote working and device rules decided, enforced and sampled
Keep the rule, the device and conditional access reports and the sample result. Do not say all devices are managed if personal ones reach company data through app controls only, and say plainly what you cannot see on them.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Practical checklist
- List who works remotely, from where, and what each group can reach.
- Decide whether personal devices may reach company data, with top management.
- Use app-level controls or enrolment for personal devices, and block the rest at sign-in.
- Enforce encryption, screen lock, updates and malware protection on managed devices.
- Set loss reporting and wipe, and rules for Confidential work at home or on the move.
- Add devices to the leaver and mover steps, brief staff and sample.
Evidence to have ready
- The remote working rule and the personal device rule, with acknowledgements.
- Device management compliance reports and conditional access settings.
- Loss reports and wipe records.
- Leaver records showing devices returned or company data removed.
Assumptions
- You have a device management or identity service that can report on devices and set sign-in conditions.
- Top management can decide whether personal devices are allowed.
- You know which staff and contractors need access from outside the office.
Not covered here
- Rolling out phishing-resistant sign-in. That is “How do we roll out phishing-resistant MFA, and in what order?”.
- Removing a leaver's access. That is “When must a leaver's access be removed, and what changes if they leave on bad terms?”.
- Physical controls for a shared building or rented office. That is “If we work from a shared building or a rented office, which physical controls do we still need under ISO 27001?”.
- Classifying information. That is “How do we classify information without everything ending up "Confidential"?”.
Related questions
- How do we roll out phishing-resistant MFA, and in what order?
- When must a leaver's access be removed, and what changes if they leave on bad terms?
- If we work from a shared building or a rented office, which physical controls do we still need under ISO 27001?
- How do we classify information without everything ending up "Confidential"?
- How do we decide where we need encryption and how we manage keys and certificates under ISO 27001?