5.2.4 Information security management system
The organization must establish, implement, maintain and continually improve a privacy information management system that satisfies the management system clauses of ISO/IEC 27001 as extended by the PIMS-specific requirem
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
- Evidence of operation across a full management cycle · Document repository
- Improvement record specific to the privacy extension · Data governance / DLP tooling
governing documentDocuments that govern the control
- PIMS documentation showing the ISO/IEC 27001 clauses and the PIMS extensions together · 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
- PIMS asserted as an ISMS with a privacy annex bolted on, with no evidence the management clauses were re run
- Continual improvement evidenced only for security topics
- Extensions documented but never operated
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.2.3 Determining the scope of the information security management system · 5.3.1 Leadership and commitment