5.7.1 Monitoring, measurement, analysis and evaluation
The monitoring, measurement, analysis and evaluation requirements of ISO/IEC 27001 apply to the PIMS, so the organization must determine what privacy performance is measured, by what valid method, when and by whom, and m
3
artefacts
0
held by a system
0
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Measurement set covering privacy performance with method, frequency and owner · Policy repository / GRC workspace
- Retained results · Document repository
- Evaluation of PIMS effectiveness drawn from those results · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Privacy measured by counting requests received rather than by whether obligations were met on time
- Measurement collected and never analysed
- Method changed between periods, destroying the trend
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 sheet5.6.3 Information security risk treatment · 5.7.2 Internal audit