Back to DashboardStrategyPhase 1 · Discovery & Inventoryintermediate30 min

Software Bill of Materials (SBOM)

Inventory software components within a stated scope, with versions, supplier or producer details, and dependency relationships.

Why this matters: An SBOM can help teams investigate dependencies for vulnerability, licensing, and migration work. Its coverage depends on how it is generated and maintained, and downstream disciplines combine it with other evidence.

Start here: Pick a sample component in the SBOM Format Explorer: the same package is shown as a CycloneDX entry and an SPDX package side by side, with the nine minimum elements mapped to each format's fields.

For your role

Executive / Business Leader
SPDX against CycloneDX mapped onto the NTIA minimum elements, then the Generation Tool Picker: the software inventory that vulnerability management, licensing and the CBOM all build on.
GRC / Risk & Compliance
The NTIA minimum-elements mapping is the check for whether a supplier's SBOM is usable; the tool picker matches build artifact types to generators and formats.
Developer / Engineer
Match your build artifact type to a generator and format in Step 2: the SBOM is what the CBOM and VEX triage read, so it has to come out of the build, not a spreadsheet.
Security Architect
SPDX or CycloneDX, and which generator per artifact type: the two decisions that make the dependency graph reusable downstream.
IT Ops / DevOps
Pick the generator per artifact type and keep the SBOM regenerated per build: it is the inventory that vulnerability triage with VEX closes the loop on.
Practice in the Simulation

Why an SBOM, and what it isn't

● standardA Software Bill of Materials (SBOM) is a machine-readable inventory of software components within a product's stated scope, with information such as names, versions, suppliers or producers, and dependency relationships. Coverage depends on how the SBOM is generated and maintained; it should not be assumed to include every dependency. It helps answer what is in this build?

◆ practitionerIt does not answer what cryptography is inside it? — that is the CBOM module's job, one layer up. An SBOM lists software components. A CBOM records cryptographic assets and related properties; discovery can also require scanners, certificate and key inventories, runtime observation, and manual investigation.

SPDX vs CycloneDX — general BOM formats

● standardSPDX is an international open standard (ISO/IEC 5962:2021 for v2.x; released v3.0.1). CycloneDX is an OWASP community specification; CycloneDX 1.6 was published as ECMA-424 and v1.7 is the 2nd edition. Both formats represent software components and relationships, but use different schemas and field models. Compare the versions and downstream tool support your workflow requires instead of assuming one is universally more complete.

◆ practitionerGeneral software inventory does not establish a complete cryptographic asset inventory. CycloneDX includes a cryptographic-asset model; the extension and the SPDX-vs-CycloneDX trade-off for a crypto inventory specifically are covered in the CBOM module. CycloneDX's own cross-tool algorithm/curve naming registry is covered in the CycloneDX Cryptography Registry module.

NTIA's minimum elements

● standardNTIA's 2021 Minimum Elements for a Software Bill of Materials defines seven data fields: Supplier Name, Component Name, Version of the Component, Other Unique Identifiers, Dependency Relationship, Author of SBOM Data, and Timestamp. NTIA's framing applies the first five fields to components; author and timestamp are metadata about the SBOM itself.

● standardCISA finalized a successor on 29 July 2026 — the 2026 Minimum Elements for a Software Bill of Materials, v2.1 — co-authored with NSA, FBI, and 15 international partner cyber agencies. It revises or replaces several 2021 fields and adds ten new elements; it is not a strict superset. See the next section for what changed and why.

What changed in the 2026 update

● standardThe seven elements above remained the baseline for about five years while SBOM tooling matured well past what they were designed for. The 2026 update adds ten new required elements: seven at the document level (SBOM Author Signature, SBOM Data Format Name, SBOM Data Format Version, SBOM Tool Name, SBOM Tool Version, SBOM Version, and SBOM Generation Context) and three per component (Component Hash Algorithm, Component Hash Value, and Component License). Existing elements are revised rather than carried over unchanged: Appendix B replaces Supplier Name with Component Producer, Other Unique Identifiers with Component Identifiers, Author of SBOM Data with SBOM Author, and Version of the Component with Component Version, and removes the Access Control element. Check anything built against the 2021 baseline against Appendix B.

◆ practitionerGenerator features and output change by release, ecosystem, lock file, and configuration. A supported format does not guarantee that every value is present or that an SBOM meets a particular contract or regulatory requirement. The workshop links tool documentation and shows what to inspect; check your generated artifact against the applicable CISA guidance and requirements.

VEX closes the vulnerability-triage gap

● standardAn SBOM lists components; it does not determine whether a vulnerable code path is reachable in a particular product. VEX (Vulnerability Exploitability eXchange) — Profile 5 of OASIS CSAF 2.0 — closes that gap with a machine-readable product status and supporting rationale for a vulnerability. CSAF's VEX profile includes statuses such as known affected, known not affected, fixed, or under investigation. A VEX statement supports triage; it does not prove by itself that a vulnerability is or is not exploitable.

◆ practitionerProduct status and justification can help teams prioritize investigation. Validate the statement against the product version and evidence available to your organization.

U.S. procurement guidance & EU CRA

● standardExecutive Order 14028 directed federal software supply-chain security work, including the original NTIA minimum-elements effort. For federal procurement, OMB M-22-18 says agencies may require an SBOM in solicitations based on software criticality or agency determination; this is not a blanket rule that every federal software vendor must provide one. The EU Cyber Resilience Act (Regulation EU 2024/2847) requires manufacturers of in-scope products with digital elements to document components and vulnerabilities, including an SBOM in a commonly used machine-readable format covering at least top-level dependencies. Its general application date is 11 December 2027, with earlier dates for specified provisions.

◆ practitionerThese are general software supply-chain requirements, not PQC-specific mandates. A PQC discovery effort can use a relevant SBOM as one input, while checking its scope and cross-referencing it with other evidence.

Bridge: from SBOM to CBOM

◆ practitionerIn this module's staged model, an SBOM is a discovery input, not the CBOM output. A crypto-discovery effort can cross-reference its component and dependency information rather than assume it already describes cryptographic assets. US policy draws the same distinction: CISA's July 2026 guidance defines minimum SBOM elements, while Executive Order 14412 (22 Jun 2026) directs CISA to publish separate guidance on minimum CBOM elements by 19 March 2027.

◆ practitionerTwo different next steps, two different modules:

  • Need to know what cryptographic algorithms, keys, and certificates a component uses? That's the CBOM module.
  • Need to resolve the same mechanism named differently across an HSM, a certificate, and a library string? That's the CycloneDX Cryptography Registry module.

Check your understanding

17 questions on Software Bill of Materials (SBOM), each with its answer and the reason.

Take the quiz

Next step

Produce the artifact: Management Tools Audit

This module belongs to phase 1 (Discovery & Inventory); Management Tools Audit produces a deliverable of that phase in the Command Center.

Production Tool Capabilities & Verification Checklist

Capabilities to require in your production tools:

  • SPDX 3.0 / CycloneDX 1.6 Software Bill of Materials (SBOM) tracking transitive cryptographic library dependencies (`openssl`, `libcrypto`, `bouncycastle`, `wolfssl`, `rustls`, `go/crypto`).
  • Automated End-of-Life (EoL) and CVE correlation (e.g., flagging `OpenSSL 1.1.1` EoL or libraries lacking PQC support) via Package URL (`purl`) and CPE matching.
  • Cryptographic signing and verification of SBOM artifacts using `ML-DSA` / Sigstore Cosign.

How to evaluate in your environment

Scan container images and application lockfiles to produce an SBOM, resolve `purl` entries against the PQC product catalog, and verify EoL/CVE flags.

Production evidence to collect

Signed SBOM artifact, transitive crypto-library dependency tree, and EoL/CVE remediation ticket log.

Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.

Record evidence for your environment

Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.

SPDX 3.0 / CycloneDX 1.6 Software Bill of Materials (SBOM) tracking transitive cryptographic library dependencies (`openssl`, `libcrypto`, `bouncycastle`, `wolfssl`, `rustls`, `go/crypto`).
Automated End-of-Life (EoL) and CVE correlation (e.g., flagging `OpenSSL 1.1.1` EoL or libraries lacking PQC support) via Package URL (`purl`) and CPE matching.
Cryptographic signing and verification of SBOM artifacts using `ML-DSA` / Sigstore Cosign.

Evidence missing. 0 of 3 requirements have a reference or scope rationale.

Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.