5.6.2 Information security risk assessment
The requirement of ISO/IEC 27001 to perform risk assessments at planned intervals or on significant change applies to the PIMS, so privacy risk assessment is a recurring operation rather than a one time planning exercise
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
- Schedule of risk assessments with evidence of execution · Policy repository / GRC workspace
- Retained assessment results including privacy risk · Data governance / DLP tooling
governing documentDocuments that govern the control
- Trigger definition for significant change · 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
- Assessment run once at implementation and never repeated
- Significant change undefined, so the trigger never fires when a new processing activity starts
- Results not retained, so no trend is visible
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.1 Operational planning and control · 5.6.3 Information security risk treatment