Software Bill of Materials (SBOM)

A software bill of materials (SBOM) is a list of every component, library and dependency inside a piece of software, like an ingredients label. It helps buyers and developers find out quickly whether they're affected by a new vulnerability.

IntermediateCategory: Cloud and software supply chain

Also called: SBOM, software inventory, SPDX, CycloneDX

What is an SBOM?

Modern software is assembled more than written. A typical application includes hundreds of open-source libraries and commercial components, which in turn depend on others. NIST defines a software bill of materials as a formal record of those components and their supply chain relationships.

The comparison usually made is a food ingredients label: if a recall is announced for one ingredient, you can check every product's label to see which contain it.

Why SBOMs matter

When the Log4Shell vulnerability in the widely used Log4j library was disclosed in December 2021, organizations around the world spent weeks trying to work out which of their software contained it. Software makers often didn't know either, because Log4j was buried several layers deep in their dependencies. With accurate SBOMs, that question could have been answered in minutes.

The US government pushed SBOM adoption through the 2021 Executive Order on Improving the Nation's Cybersecurity, and CISA leads ongoing SBOM work with industry.

What an SBOM contains

Minimum elements include, for each component:

  • Supplier name
  • Component name and version
  • Unique identifiers
  • Its relationship to other components (what depends on what)
  • Who created the SBOM and when

The two most common formats are SPDX and CycloneDX, both machine-readable so tools can check them automatically against vulnerability databases.

How businesses use SBOMs

  • Software makers generate SBOMs automatically in their build pipelines and use them to track and fix vulnerable open-source components.
  • Buyers ask key vendors for SBOMs, or at least ask whether they produce them, as part of third-party risk management. When a new flaw hits the news, they can check exposure quickly.
  • Regulated industries increasingly require them; for example, the FDA expects SBOMs for internet-connected medical devices.

An SBOM is only useful if it's accurate, kept current and actually checked against new vulnerabilities.

Related terms

Sources

  1. Software Bill of Materials (glossary) (NIST)
  2. Software Bill of Materials (SBOM) (CISA)

Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.