5.7.3 Management review
The management review requirements of ISO/IEC 27001 apply to the PIMS, so top management must review the privacy extension at planned intervals against the same defined input set and record the resulting decisions.
3
artefacts
0
held by a system
2
at each review
hard
to go live
Data governance / DLP tooling
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
- Review records showing privacy inputs presented and privacy decisions taken · Data governance / DLP tooling
- Attendance evidencing top management · HR system / LMS
governing documentDocuments that govern the control
- Actions arising tracked to closure · Policy repository / GRC workspace
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 noted as an agenda item with no input data behind it
- Review conducted by the privacy function reporting to itself
- Decisions recorded without owners or dates
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.7.2 Internal audit · 5.8.1 Nonconformity and corrective action