DS-2 Ensure software supply chain security
Maintain inventory of open source and third party components in code using Software Composition Analysis tools.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DS-2. 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
- SCA scan results · Vulnerability scanner / patch tooling
- License compliance report · Document repository
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- SBOM per application · Document repository
- Vulnerable dependency tracker · Document repository
First move
Common gaps auditors find
- No SBOM produced
- SCA not in pipeline
- Vulnerable dependencies unaddressed
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-1 Conduct threat modeling · DS-3 Secure DevOps infrastructure