5.4.2 Information security objectives and planning to achieve them
The requirements of ISO/IEC 27001 for setting information security objectives and planning to achieve them apply to the PIMS, with those objectives now reaching privacy outcomes under the extended interpretation.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Monitoring results against the privacy objectives · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Objective register including privacy objectives with measures and owners · Policy repository / GRC workspace
- Plans showing what will be done, by whom, by when and how evaluated · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Objective set carried over from the ISMS with no privacy objective added
- Privacy objectives expressed as compliance with the law, which is not measurable
- Objectives set but never monitored
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.4.1 Actions to address risks and opportunities · 5.5.1 Resources