What evidence do auditors commonly ask for on DS-1 Conduct threat modeling?

Threat models for in-scope applications with dates; Identified threats mapped to mitigating controls; Coverage of build artefacts and pipeline in the model; Trigger conditions requiring a model refresh.

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

threat model produced once at design and never revisited

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

`DS-1` Conduct threat modeling

Perform threat modelling to identify potential threats and enumerate mitigating controls, covering both the running application and the artefacts and pipeline that produce it.

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

none for this control

governing documentDocuments that govern the control

Threat models for in-scope applications with dates · Policy repository / GRC workspace
Identified threats mapped to mitigating controls · Document repository
Coverage of build artefacts and pipeline in the model · Policy repository / GRC workspace
Trigger conditions requiring a model refresh · 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

threat model produced once at design and never revisited
model covers the application but not the pipeline that deploys it
threats enumerated with no owner for the mitigations

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

DP-8 Ensure security of key and certificate repository · DS-2 Ensure software supply chain security