9.1 Monitoring, measurement, analysis and evaluation
The organization shall decide: what is to be monitored and measured, the privacy processes and controls among them; which methods of monitoring, measuring, analysing and evaluating apply, so that results are valid; when monitoring and measuring take place and who carries them out; and when the results are analysed and evaluated and by whom. It shall assess privacy performance and how effective the PIMS is, and keep suitable documented evidence of the results. The Robere correspondence table notes an editorial change in how the text describes who monitors and evaluates.
Source: ISO/IEC 27701:2025, 9.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 27701:2025 in the compliance library.
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
- Results of measurement of privacy performance and PIMS effectiveness · Data governance / DLP tooling
- Analysis and evaluation records · Document repository
governing documentDocuments that govern the control
- Monitoring and measurement plan naming what, how, when and who · Policy repository / GRC workspace
First move
Common gaps auditors find
- Measures limited to security metrics with nothing on the processing of PII or requests from individuals
- Results collected but never evaluated
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