A.5.2 Information security roles and responsibilities
Name who owns what in security and make the allocation explicit and traceable.
9
artefacts
1
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
- Access control assignment logs showing role assignments · Identity provider / directory
periodic reviewEvidence produced at each review
- Signed responsibility acceptance forms · Document repository
governing documentDocuments that govern the control
- Organizational chart with security function highlighted · Policy repository / GRC workspace
- Job description for Information Security Manager · Policy repository / GRC workspace
- Security role description document · Policy repository / GRC workspace
- RACI matrix for information security processes · Policy repository / GRC workspace
- Responsibility register linking assets to owners · Policy repository / GRC workspace
- Delegated authority letters for security decisions · Document repository
- Policy amendment records documenting delegation · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Roles not updated after staff changes
- No documented acceptance of responsibilities
- Unclear separation between ownership and operational duties
- Delegated authority not reflected in policy documents
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 sheetA.5.1 Policies for information security · A.5.3 Segregation of duties