5.3.3 Organizational roles, responsibilities and authorities
Organizational roles, responsibilities and authorities must be assigned and communicated as ISO/IEC 27001 requires, now covering the privacy responsibilities that the extended interpretation brings into the management sy
3
artefacts
0
held by a system
1
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
- Evidence of communication to the holders · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Responsibility assignment covering privacy roles and their authority · Policy repository / GRC workspace
- Reporting line from the privacy role into top management · 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
- Privacy responsibility assigned without the authority to stop a processing activity
- Roles assigned to a function rather than a person, so nobody answers for them
- No deputy, leaving the privacy function unavailable during absence
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.3.2 Policy · 5.4.1 Actions to address risks and opportunities