5.6.3 Information security risk treatment
The requirement of ISO/IEC 27001 to implement the risk treatment plan applies to the PIMS, so the privacy controls chosen during treatment must actually be implemented and their implementation evidenced.
3
artefacts
0
held by a system
2
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence of implementation for the privacy controls selected · Data governance / DLP tooling
- Residual risk acceptance records · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Risk treatment plan with implementation status per control · 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
- Treatment plan closed on the basis that a control was purchased rather than operating
- Privacy controls in the Statement of Applicability with no implementation evidence
- Residual risk accepted by someone without the authority to accept it
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.2 Information security risk assessment · 5.7.1 Monitoring, measurement, analysis and evaluation