Basics

What is an SBOM? A plain-English explanation

By SBOMBox SBOM experts · · Updated · 5 min read

Short answer: an SBOM, or software bill of materials, is a machine-readable list of every component inside a piece of software: each library and package, its version, who supplies it and how the pieces depend on each other. Think of it as the ingredients label for software. When a new vulnerability is announced, an SBOM tells you in minutes whether you are affected.

SBOM meaning

SBOM stands for software bill of materials. The term comes from manufacturing, where a bill of materials lists every part needed to build a product. Modern applications are mostly assembled from open-source and third-party code, often hundreds of packages deep, so software needs the same kind of parts list. Other parts lists exist for hardware, cryptography and AI models; see the types of bill of materials.

What is in an SBOM?

Typical SBOM fields
FieldExampleWhy it matters
Component namelog4j-coreIdentifies the part
Version2.14.1Vulnerabilities affect specific versions
SupplierApache Software FoundationTells you who to ask for a fix
Unique identifierpkg:maven/org.apache.logging.log4j/log4j-core@2.14.1A package URL (purl) lets tools match vulnerabilities exactly
HashSHA-256 of the fileProves the component is the one listed
LicenceApache-2.0Supports open-source licence compliance
Dependency relationshipsapp → spring-boot → log4j-coreShows transitive dependencies, where most risk hides
Author and timestampCI pipeline, 2026-11-17Shows who made the SBOM and when

Regulators define the minimum set slightly differently. The SBOM minimum elements guide compares the CISA 2026 list, NTIA and BSI TR-03183-2 field by field, and the minimum elements checker tests your file against each.

SBOM formats: CycloneDX and SPDX

Two formats dominate, and both are open standards. CycloneDX comes from OWASP and is standardised as ECMA-424; it is security-focused and also covers VEX, services, cryptography and ML models. SPDX comes from the Linux Foundation and is the international standard ISO/IEC 5962:2021; it grew out of licence compliance. Both work in JSON. Which to pick is covered in CycloneDX or SPDX?, and a full file is annotated line by line in our SBOM example.

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "components": [
    {
      "type": "library",
      "name": "log4j-core",
      "version": "2.14.1",
      "purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1",
      "licenses": [{ "license": { "id": "Apache-2.0" } }]
    }
  ]
}

Why SBOMs matter in cyber security

In December 2021 the Log4Shell vulnerability hit a logging library used in a vast number of products. Teams with SBOMs searched them and knew within hours which products were affected. Teams without them spent weeks reading build files. That gap is why SBOMs became a security baseline. Read the Log4Shell lesson for the full story.

Who requires an SBOM?

SBOM requirements at a glance
RuleWhoSince
EU Cyber Resilience ActManufacturers of products with digital elements sold in the EU11 December 2027
US federal contractsSoftware suppliers to US agencies, case by case under OMB M-26-052026
FDA section 524BMakers of cyber devices (medical)2023
Germany BSI TR-03183-2Benchmark for SBOM content; referenced for CRA readinessCurrent version

See CRA SBOM requirements and SBOM regulations by country for the detail, or answer five questions in do I need an SBOM?.

How to generate an SBOM

You never write an SBOM by hand. A generator reads your lock files, build output or container image and writes the file. Generate it in CI for every release, from the artifact you actually ship.

sbombox login
sbombox init
sbombox generate

An SBOM is the start, not the finish

A file saved in a build folder helps nobody. The value comes from checking it is complete, storing one per release, and matching it against new vulnerabilities every day. Generating an SBOM is not the same as being ready. To see how good an SBOM you already have is, drop it into the free SBOM checker: no account, nothing stored.

Frequently asked questions

What does SBOM stand for?

Software bill of materials: a list of every component, library and dependency in a piece of software, with versions and suppliers.

What is an SBOM in cyber security?

A security tool for knowing what you run. When a new vulnerability is published, you match it against your SBOMs to find every affected product and version within minutes.

What format is an SBOM?

Usually CycloneDX or SPDX, in JSON or XML. Both are open standards and machine-readable; SPDX is ISO/IEC 5962:2021 and CycloneDX is ECMA-424.

Is an SBOM mandatory?

In the EU, yes for products with digital elements under the Cyber Resilience Act, from 11 December 2027. In the US, the FDA requires one for cyber devices and federal agencies may require one in contracts. Elsewhere, customers increasingly ask for one.

What is the difference between an SBOM and SCA?

Software composition analysis (SCA) is the process of scanning code for open-source components and their risks. An SBOM is the standard file that records the result. See SBOM vs vulnerability scan.

How often should an SBOM be updated?

Every release, and whenever dependencies change. See how often to update your SBOM.