DS-3 Secure DevOps infrastructure
Secure the DevOps infrastructure and pipeline across build, test and production stages, including the repositories that hold source code, packages and images.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-3. 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
- Branch protection and required review settings · Source control / CI pipeline
- Build agent hardening and isolation configuration · Source control / CI pipeline
- Audit logging of pipeline configuration changes · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Access control on source and artefact repositories · Policy repository / GRC workspace
First move
Common gaps auditors find
- pipeline permissions broader than production permissions
- shared build agents across trust boundaries
- pipeline definitions editable without review
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-2 Ensure software supply chain security · DS-4 Integrate static application security testing into DevOps pipeline