DS-7 Enable logging and monitoring in DevOps
Extend logging and monitoring to non-production environments and to the delivery workflow itself, because compromise of those environments carries risk into production.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-7. 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
- Log collection from build systems and non-production environments · SIEM / log platform
- Detection rules covering pipeline activity such as unexpected credential use · Identity provider / directory
- Alert routing for pipeline events · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Retention applied to these logs · Policy repository / GRC workspace
First move
Common gaps auditors find
- monitoring scoped to production only
- build system logs kept locally and never collected
- no detection rules written for pipeline abuse
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-6 Enforce security of workload throughout DevOps lifecycle · ES-1 Use Endpoint Detection and Response (EDR)