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

Dynamic testing tool and the environment it runs against; Gate configuration and threshold; Finding remediation records; Coverage across externally reachable applications.

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

dynamic testing run manually before major releases only

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

`DS-5` Integrate dynamic application security testing into DevOps pipeline

Integrate dynamic application security testing into the delivery workflow as a gating control, so results can prevent vulnerable builds reaching production.

Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-5. 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 remediation records · Document repository

governing documentDocuments that govern the control

Dynamic testing tool and the environment it runs against · Policy repository / GRC workspace
Gate configuration and threshold · Policy repository / GRC workspace
Coverage across externally reachable applications · Document repository

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

dynamic testing run manually before major releases only
tests point at a stub environment unrepresentative of production
authenticated paths never tested

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-4 Integrate static application security testing into DevOps pipeline · DS-6 Enforce security of workload throughout DevOps lifecycle