What is an SBOM? Software bill of materials explained

Hephaestus Technology6 min read

What is an SBOM? A software bill of materials is a machine-readable inventory of the components inside a piece of software, which CISA describes as "a list of ingredients that make up software components". It lets you answer, in minutes rather than days, whether a newly published vulnerability affects your product. Under the EU's Cyber Resilience Act, manufacturers of products with digital elements must draw one up, covering at least top-level dependencies.

Key takeaways

  • An SBOM is a machine-readable list of the software components, versions and suppliers in a product.
  • The Cyber Resilience Act requires an SBOM in a commonly used, machine-readable format, covering at least top-level dependencies.
  • You do not have to publish your SBOM under the CRA, but market surveillance authorities can request it.
  • SPDX (ISO/IEC 5962:2021) and CycloneDX (ECMA-424) are the two main formats.
  • Generate SBOMs automatically in your build pipeline for every release, including firmware.

What does an SBOM contain?

An SBOM records each component in your software and how they relate. The US NTIA's 2021 minimum elements described it as a "formal record containing the details and supply chain relationships" of software components, and its report set a baseline of seven data fields: supplier name, component name, version, other unique identifiers, dependency relationship, author of the SBOM data and a timestamp.

That baseline has since been updated. On 29 July 2026, CISA, the NSA, the FBI and international partners published the 2026 Minimum Elements for a Software Bill of Materials, adding requirements for component hashes, licences, the name of the SBOM tool and the context in which the SBOM was generated, with an "emphasis on machine-processable SBOM formats".

A simple entry for a firmware image might list:

Field Example
Component mbedtls
Version 3.x.y
Supplier the upstream project
Identifier a package URL or CPE
Hash SHA-256 of the component
Licence Apache-2.0
Relationship dependency of the network stack

Why does an SBOM matter?

Because you cannot fix what you do not know you ship. When a vulnerability is disclosed in a widely used library, the first question is "are we affected?". Without an inventory, teams search source trees and ask former contractors. With one, they query a file.

CISA calls the SBOM "a key building block in software security and software supply chain risk management" (CISA). It also supports licence compliance, due diligence during fundraising or acquisition, and procurement, where larger customers increasingly ask suppliers for one. It belongs on any software handover checklist when a development partner finishes a project.

What does the Cyber Resilience Act require?

The CRA makes the SBOM a legal requirement for manufacturers. Annex I Part II, point 1, of Regulation (EU) 2024/2847 requires manufacturers to "identify and document vulnerabilities and components contained in products with digital elements", including by drawing up an SBOM "in a commonly used and machine-readable format" covering at least "the top-level dependencies of the products".

Four details matter:

  1. Top-level dependencies are the floor. Going deeper into transitive dependencies is good practice, but the legal minimum is the direct ones.
  2. It is part of the technical documentation. Annex VII lists the SBOM among the documents describing your vulnerability handling, and says you provide it to a market surveillance authority on reasoned request.
  3. It does not have to be public. Recital 77 says manufacturers need not make the SBOM public.
  4. Timing. The SBOM requirement applies to products placed on the market from 11 December 2027, under Article 71. The CRA's reporting duty, which has applied since 11 September 2026, is much easier to meet when you already know what you ship.

The SBOM also feeds other duties. Article 13(5) requires due diligence on third-party components, and Article 13(6) requires you to report vulnerabilities you find in a component to its maintainer. For the full list, see our Cyber Resilience Act checklist.

Which SBOM format should you use?

Use SPDX or CycloneDX; both are open, widely supported and meet the "commonly used and machine-readable" test in practice.

SPDX CycloneDX
Standard ISO/IEC 5962:2021 (SPDX) ECMA-424 (CycloneDX)
Hosted by Linux Foundation OWASP and Ecma International
Named in NTIA 2021 minimum elements Yes (NTIA) Yes (NTIA)

If a customer or authority specifies a format, use it. Otherwise, pick the one your build tools generate natively and stick with it.

How do you create an SBOM in practice?

Automate it. A manual spreadsheet goes stale with the next release.

  1. Choose a generator that reads your package manager lock files or scans built artefacts. Most language ecosystems and container tools have one.
  2. Run it in CI on every release build, so the SBOM matches the exact binary or image you ship.
  3. Handle embedded code separately. Firmware often includes vendored C libraries, a real-time operating system and chip vendor SDKs that no package manager knows about. List these explicitly in a manifest the generator can read.
  4. Store SBOMs with releases, versioned and signed, so you can answer questions about products shipped years ago during the support period.
  5. Feed them to a vulnerability scanner that matches components against public advisories and alerts you to new issues.
  6. Add VEX where useful. CISA describes a VEX as "a form of a security advisory that indicates whether a product or products are affected" by a known vulnerability (CISA). It lets you tell customers a flagged library is present but not exploitable in your configuration.

What does it cost, and what are the pitfalls?

For most software teams, the tooling cost is low: open-source generators exist for the main ecosystems, and the effort is in wiring them into the build and keeping them accurate. The cost rises for embedded and hardware products, where components are compiled in and must be tracked by hand, and for legacy code with no package management.

Common pitfalls:

  • Generating once. An SBOM from the first release is wrong by the second.
  • Scanning source, shipping something else. Build flags and vendored code mean the source tree and the binary differ. Generate from the build.
  • Ignoring firmware and SDKs. For devices, the riskiest components are often the ones a package manager does not see.
  • No owner. Someone must act on what the scanner reports, or the SBOM is decoration.
  • Treating it as the whole job. The SBOM supports vulnerability handling; it does not replace patching, testing and secure update delivery.

Frequently asked questions

Is an SBOM mandatory in the EU?

Yes, for manufacturers of products with digital elements under the Cyber Resilience Act, for products placed on the market from 11 December 2027. It must be machine-readable, in a commonly used format, and cover at least top-level dependencies.

Do I have to share my SBOM with customers?

The CRA does not require you to publish it; you must provide it to market surveillance authorities on reasoned request. Many manufacturers share SBOMs with business customers under contract, because procurement teams increasingly ask for them.

What is the difference between SPDX and CycloneDX?

Both are open, machine-readable SBOM formats. SPDX is an ISO/IEC standard hosted by the Linux Foundation, and CycloneDX is an Ecma standard developed with OWASP. Many SBOM tools can produce either, so the choice usually follows your tooling and customers.

How often should an SBOM be updated?

For every release. Generating the SBOM automatically in the build pipeline keeps it aligned with what you actually ship, including patches and security updates.

Does an SBOM need to include open-source components?

Yes. Open-source libraries are usually most of a modern product's code and are a common source of vulnerabilities. The CRA also requires due diligence on third-party components, including open-source ones.

Building a connected product and want a second opinion on its security plan? Book a free 30-minute call with our team.

Cover photo by Christina Morillo on Pexels.

Hephaestus Technology

We help founders and businesses validate, build and launch products across software, AI and hardware, from offices in Ho Chi Minh City, Dublin and Delaware. See how we work.

Tell us what
you're building.

A free 30-minute call. You'll get an honest view of the idea, the risks we see and what we'd do first, whether or not we end up working together.