GS-1 Align organization roles, responsibilities and accountabilities
Define and document cloud security roles, responsibilities, and accountabilities at strategic and operational levels with senior leadership endorsement.
4
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
- Executive sponsor sign-off · Document repository
governing documentDocuments that govern the control
- Cloud security RACI · Policy repository / GRC workspace
- Roles and responsibilities document · Policy repository / GRC workspace
- Communication artefacts · 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
- RACI absent
- Operations and security responsibilities unclear
- No exec sponsor
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 sheetES-3 Ensure anti-malware software and signatures are updated · GS-2 Define and implement enterprise segmentation/separation of duties strategy