DS-6 Enforce security of workload throughout DevOps lifecycle
Integrate security controls into CI/CD pipelines including SAST, secret scanning, and IaC scanning with pipeline failure on critical findings.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-6. 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
- Pipeline security configuration · Source control / CI pipeline
- SAST scan results · Vulnerability scanner / patch tooling
- Secret scanning alerts · Vulnerability scanner / patch tooling
- IaC scan reports · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Security gates as warnings only
- Secrets in repos not blocked
- IaC misconfigurations deployed
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 sheetDS-5 Integrate dynamic application security testing into DevOps pipeline · DS-7 Enable logging and monitoring in DevOps