Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Protect information on user devices (laptops, phones, tablets), including personal devices if allowed.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Teams should translate endpoint protection into day-to-day device governance for laptops, phones, tablets, and any permitted BYOD use. In practice, policy wording alone is not control operation; the real focus is on enrollment, configuration, monitoring, reporting, and recovery evidence. Reviewers usually look for clear accountability between IT, security, HR, and users, especially where personal devices, lost devices, and remote wipe decisions create different risk paths.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Managed devices exist, but encryption, screen lock, update baselines, or MDM enrollment are not consistently enforced, leaving device protection dependent on user choice.
BYOD is allowed in practice, yet containerization, separation of corporate data, and offboarding wipe steps are undocumented or not evidenced for current users.
Lost or stolen device handling is vague; tickets, notifications, and wipe approvals cannot be traced across IT, managers, and affected users.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Maintain one device register covering issued and permitted personal devices, with ownership, OS version, encryption status, and MDM enrollment recorded by IT asset owners. Define who approves exceptions for legacy devices and how those exceptions are time-limited, risk-assessed, and reviewed. Link the register to onboarding and offboarding so returned assets and remote wipe actions can be confirmed promptly.
Use a standard build or baseline profile for each platform that turns on disk encryption, passcode length, auto-lock, secure backup, and update enforcement. The endpoint administrator should review compliance dashboards weekly, close drift tickets, and document any remediation delays caused by business applications, travel, or device compatibility constraints.
Set a clear user reporting path for loss, theft, malware suspicion, jailbreak/root detection, and unauthorized sharing. Service desk staff should capture incident time, device identifier, location, and containment steps, then security should decide whether to isolate the device, revoke tokens, or trigger wipe. Keep evidence of approvals and user acknowledgements.
For BYOD, require managed app containers or equivalent separation, and prohibit storage of sensitive records outside approved apps unless the risk owner accepts the exposure. The accountable manager should ensure exit checklists include removal of corporate credentials, mailbox access, and managed app data, with a final confirmation stored in the leaver record.
What an auditor will ask to see
MDM compliance report showing encryption, PIN, patch, and enrollment status by device.
Lost device incident ticket with notification time, containment decision, and remote wipe approval.
BYOD acceptance record with container requirement, user acknowledgement, and exception expiry.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.1. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.