Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Software Bill of Materials (SBOM)?

A software bill of materials (SBOM) is a formal, machine-readable inventory of all the components, libraries, and dependencies that make up a piece of software, including their versions.

Illustration for the cybersecurity term Software Bill of Materials (SBOM)
Home / Blog / Cybersecurity Terms / What Is a Software Bill of Materials (SBOM)?
17 November 2026

What Is a Software Bill of Materials (SBOM)?

What Is a Software Bill of Materials (SBOM)?

A software bill of materials (SBOM) is a detailed, machine-readable list of every component that makes up a piece of software: open-source libraries, commercial modules, frameworks, and their transitive dependencies, together with version numbers, suppliers, and licence information. It works like the ingredients label on food packaging, telling you exactly what is inside.

Modern applications are assembled more than they are written. A typical application can contain hundreds of open-source packages, many of which pull in further packages of their own. Without an SBOM, it is surprisingly difficult to answer a simple question: are we using the vulnerable library everyone is talking about?

Why SBOMs Matter

The Log4Shell vulnerability (CVE-2021-44228), disclosed in December 2021, made the problem painfully clear. The flaw sat in Log4j, a Java logging library embedded deep inside thousands of products. Many organisations spent weeks working out which of their systems and suppliers’ products were affected, because nobody had a reliable inventory of components. Organisations with SBOMs could search them and answer within hours.

SBOMs also support the wider fight against supply chain attacks, such as the backdoor discovered in the XZ Utils compression library in March 2024, by making it easier to see exactly which component versions are present.

What an SBOM Contains

In 2021, the US National Telecommunications and Information Administration (NTIA) published the minimum elements an SBOM should include:

Richer SBOMs may also include licences, cryptographic hashes, and known vulnerability references.

SBOM Formats

Two formats dominate:

FormatMaintained byNotes
SPDXLinux FoundationPublished as ISO/IEC 5962:2021, strong on licence compliance
CycloneDXOWASPSecurity-focused, standardised as ECMA-424, supports VEX and services

Both can be produced in JSON or XML and are supported by most build and scanning tools.

Using SBOMs in Practice

SBOMs are most useful when generated automatically and kept up to date:

  1. Generate an SBOM during every build using software composition analysis or dedicated tools, rather than writing one by hand.
  2. Store SBOMs centrally alongside release artefacts, for both in-house software and products bought from suppliers.
  3. Monitor components continuously against vulnerability databases, so newly disclosed flaws are matched to affected products immediately, feeding your vulnerability management process.
  4. Assess exploitability using VEX (Vulnerability Exploitability eXchange) statements, which tell customers whether a listed vulnerability actually affects the product.
  5. Request SBOMs from suppliers as part of procurement and contracts.

Regulation and Policy

Governments increasingly expect SBOMs. US Executive Order 14028 on improving the nation’s cybersecurity, issued in May 2021, made SBOMs a requirement for software sold to US federal agencies. The EU Cyber Resilience Act, which entered into force in December 2024, requires manufacturers of products with digital elements to draw up an SBOM, with its main obligations applying from December 2027. UK organisations selling into the EU will need to comply, and the NCSC encourages SBOM adoption as part of good supply chain security practice. Medical device regulators have also begun requiring SBOMs.

Limitations

An SBOM is an inventory, not a security guarantee. It only lists what is known, and quality varies widely between tools. It does not show whether a vulnerable function is actually reachable, which is why VEX and context matter. SBOMs must also be maintained, because an inventory that describes last year’s release is of little use during an incident.

Integrating SBOM generation into secure software development pipelines turns it from a compliance document into a practical tool.

At Privia Security, our Web Application Security Services include review of third-party components and dependencies, helping you understand the supply chain risk inside your software.

FAQ – Frequently Asked Questions

Who Needs an SBOM?

Any organisation that develops, sells, or relies on software benefits from SBOMs. Software vendors increasingly need them to meet customer and regulatory requirements, such as the EU Cyber Resilience Act and US federal procurement rules. Buyers use them to understand supplier risk and to respond quickly when a widely used component turns out to be vulnerable.

What Is the Difference Between SPDX and CycloneDX?

Both are standard SBOM formats. SPDX, maintained by the Linux Foundation and published as an ISO standard, has deep roots in licence compliance. CycloneDX, maintained by OWASP, was designed with security use cases in mind and supports features such as VEX. Most tools can produce and consume both formats.

What Is VEX?

VEX, or Vulnerability Exploitability eXchange, is a companion document to an SBOM that states whether specific vulnerabilities in listed components actually affect a product. For example, a vendor may confirm that a vulnerable function is never called. VEX helps customers focus on real risks instead of chasing every vulnerability that appears in a scan.

Related Terms

You May Be Interested In These

What Is BACnet Security?

Cybersecurity Terms

17 November 2026

What Is BACnet Security?

Read More
What Is Metasploit?

Cybersecurity Terms

17 November 2026

What Is Metasploit?

Read More