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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), GS-1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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