What evidence do auditors commonly ask for on 8.2 Privacy risk assessment?

Schedule of privacy risk assessments and evidence of each performance; Assessments triggered by significant change such as new processing, new systems or new jurisdictions; Documented results.

What is the most common gap auditors find on 8.2?

Assessment performed once at certification

ISO/IEC 27701:2025 · Operation

`8.2` Privacy risk assessment

The organization shall carry out privacy risk assessments on a planned schedule and also whenever a significant change is planned or takes place, applying the criteria set under 6.1.2, and shall keep documented evidence of what each assessment found.

Source: ISO/IEC 27701:2025, 8.2. 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

Document repository

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

Documented results · Document repository

governing documentDocuments that govern the control

Schedule of privacy risk assessments and evidence of each performance · Policy repository / GRC workspace
Assessments triggered by significant change such as new processing, new systems or new jurisdictions · Document repository

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

Assessment performed once at certification
Significant changes to processing introduced without a re-assessment

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

8.1 Operational planning and control · 8.3 Privacy risk treatment