PS.3.2 Software Bill of Materials
Produce a software bill of materials for each release in a machine readable format. Make it available to customers and use it internally to triage component vulnerabilities.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- SBOM generation in the build pipeline · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- SBOM publication or delivery process · Document repository
- Internal SBOM index for vulnerability lookups · Policy repository / GRC workspace
- SBOM format choice document (e.g. CycloneDX, SPDX) · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- SBOM generated but never consumed for vulnerability triage
- no SBOM provided for legacy releases still under support
- SBOM does not include transitive dependencies
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 sheetPS.3.1 Archive and Protect Released Software · PW.1.1 Design Software to Meet Security Requirements