What evidence do auditors commonly ask for on PS.3.2 Software Bill of Materials?

SBOM generation in the build pipeline; SBOM publication or delivery process; Internal SBOM index for vulnerability lookups; SBOM format choice document (e.g. CycloneDX, SPDX).

What is the most common gap auditors find on PS.3.2?

SBOM generated but never consumed for vulnerability triage

NIST SP 800-218 (SSDF) · Protect the Software

`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.

Source: NIST SP 800-218 (SSDF), PS.3.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 NIST SP 800-218 (SSDF) 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

SBOM generation in the build pipeline · Policy repository / GRC workspace
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

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

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 sheet

PS.3.1 Archive and Protect Released Software · PW.1.1 Design Software to Meet Security Requirements