GS-10 Define and implement DevOps security strategy
Mandate security controls as part of the organisation's DevOps engineering and operating standard, defining security objectives, control requirements and tooling specifications.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), GS-10. 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
none for this control
governing documentDocuments that govern the control
- DevOps engineering standard containing the mandated security controls · Policy repository / GRC workspace
- Defined security objectives and control requirements for pipelines · Policy repository / GRC workspace
- Approved tooling specification · Document repository
- Conformance reporting across delivery teams · Document repository
First move
Common gaps auditors find
- security expectations communicated informally rather than in the standard
- standard published with no conformance measurement
- each team selecting its own security tooling with no baseline
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 sheetGS-9 Define and implement endpoint security strategy · IM-1 Use centralized identity and authentication system