5.8.2 Continual improvement
The continual improvement requirement of ISO/IEC 27001 applies to the PIMS, so the organization must keep improving the suitability, adequacy and effectiveness of the privacy extension and not only correct it when it fai
3
artefacts
0
held by a system
2
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
- Improvement backlog with privacy items traceable to measurement, audit or review · Data governance / DLP tooling
- Evidence of improvements delivered across cycles · Document repository
governing documentDocuments that govern the control
- Link from regulatory and business change into the improvement determination · 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
- Improvement register that only ever contains corrective actions
- Regulatory developments tracked by legal but never entering the improvement process
- Backlog that accumulates and never closes
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