Cloud & platform

SBOM

Software Bill of Materials

A machine-readable inventory of the components, versions and licences inside a piece of software, typically in SPDX or CycloneDX format.

An SBOM lists every package in an artefact with identifiers such as a purl (pkg:npm/lodash@4.17.21) and, ideally, hashes and dependency relationships. The two dominant formats are SPDX (Linux Foundation, ISO/IEC 5962) and CycloneDX (OWASP). Tools like Syft generate them from images or lockfiles at build time.

Its real use is answering "are we affected?" in minutes when the next Log4Shell lands: query stored SBOMs for the component instead of rescanning everything. US federal procurement (EO 14028) pushed it into the mainstream.

Pitfalls: SBOMs generated from manifests miss vendored or statically linked code; an SBOM nobody indexes is useless; and presence of a vulnerable component is not exploitability, which is what VEX statements address. The same inventory idea applied to cryptography is a CBOM.

Learn it properly

Also used in

Related terms