What evidence do auditors commonly ask for on A.3.22 User endpoint devices?

Endpoint and mobile device rules addressing PII specifically; Technical protections on devices that access PII, such as encryption, remote wipe and access control; Evidence the rules reach personal devices where these are permitted.

What is the most common gap auditors find on A.3.22?

Mobile rules that address device loss but not PII stored in applications and caches

ISO/IEC 27701:2025 · Annex A Table A.3 information security controls with PII-specific guidance

`A.3.22` User endpoint devices

The organization shall make sure PII is not put at risk through mobile phones, laptops and other endpoint devices, by means of the rules, safeguards and handling expectations it sets for any endpoint that reaches or holds PII.

Source: ISO/IEC 27701:2025, A.3.22. 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 27701:2025 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

Evidence the rules reach personal devices where these are permitted · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

Endpoint and mobile device rules addressing PII specifically · Policy repository / GRC workspace
Technical protections on devices that access PII, such as encryption, remote wipe and access control · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Mobile rules that address device loss but not PII stored in applications and caches
Bring-your-own-device permitted with no control over PII on the device

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.3.21 Secure disposal or re-use of equipment · A.3.23 Secure authentication