EvidenceSheet
ISO/IEC 27001:2022 · Technological controls

A.8.1 User end point devices

Information that sits on, is handled by or can be reached through user endpoint devices is to be protected. Purpose (stated in ISO/IEC 27002:2022): shields information from the risks that endpoint devices bring. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.1.

Source: ISO/IEC 27001:2022, A.8.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

5
artefacts
2
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Device management (MDM or endpoint management) reports showing enrolment, encryption, patch level, firewall and anti-malware status · Vulnerability scanner / patch tooling
  • Configuration evidence for software installation restrictions, removable media or port controls and blocking of local storage for highly sensitive information · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • User acknowledgement of endpoint responsibilities and, for BYOD, of data ownership and remote wipe terms · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

  • Statement of Applicability entry for control A.8.1, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
  • The topic-specific endpoint policy covering classification limits, registration, software restrictions, updates, network connection rules, encryption, malware protection, remote wipe, backup and port control · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

A.7.14 Secure disposal or re-use of equipment · A.8.2 Privileged access rights