5.5.4 Communication
The communication requirements of ISO/IEC 27001 apply to the PIMS, so the organization must determine what privacy relevant communication is needed internally and externally, when, with whom, how and by whom.
3
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Communication plan covering privacy topics and audiences · Policy repository / GRC workspace
- Named authority for external privacy communication including with supervisory authorities · Policy repository / GRC workspace
- Evidence the plan has been exercised or used · 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
- No named channel to the supervisory authority until a breach forces one
- Communication plan covers security incidents only
- Communication with individuals conflated with marketing channels
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