What evidence do auditors commonly ask for on DS-4 Integrate static application security testing into DevOps pipeline?

Static analysis tool integrated in the pipeline; Gate thresholds and the action taken when exceeded; Finding triage and suppression records with justification; Coverage across repositories in scope.

What is the most common gap auditors find on DS-4?

scanning runs but never blocks a build

Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) · DevOps Security

`DS-4` Integrate static application security testing into DevOps pipeline

Integrate static application security testing into the delivery workflow as a gating control, so results can block vulnerable code from being committed, built or deployed.

Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-4. 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.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Finding triage and suppression records with justification · SIEM / log platform

governing documentDocuments that govern the control

Static analysis tool integrated in the pipeline · Policy repository / GRC workspace
Gate thresholds and the action taken when exceeded · Policy repository / GRC workspace
Coverage across repositories in scope · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

scanning runs but never blocks a build
findings suppressed in bulk to clear the backlog
only the main repository scanned

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 sheet

DS-3 Secure DevOps infrastructure · DS-5 Integrate dynamic application security testing into DevOps pipeline