An SBOM — software bill of materials — is a formal, machine-readable inventory of every component inside a piece of software: each library and dependency, its exact version, who built it, and how the parts relate. It is the ingredients list on a food packet, but complete, structured, and generated automatically from the build rather than typed by hand.
Modern software is mostly assembled. A single application can pull in hundreds of open-source packages, each with its own maintainers and its own dependencies. When a vulnerability is announced in one of them, the first question every team asks is the same: are we affected? Without an SBOM, answering that means grepping repositories and guessing. With one, it is a lookup.
What an SBOM contains
The US National Telecommunications and Information Administration (NTIA) published a widely adopted minimum-elements list. At floor level, an SBOM records:
| Element | What it pins down |
|---|---|
| Supplier | Who built or maintains the component |
| Component name & version | The exact library and release, not a range |
| Unique identifiers | Stable IDs such as PURL or CPE so tools can match it to vulnerability databases |
| Dependency relationships | Which components depend on which — the tree, not just the bag |
| Author of the SBOM | Who generated this document |
| Timestamp | When it was generated — inventories go stale |
That is the floor. Good SBOMs also record hashes, license expressions, and build provenance.
Why SBOMs suddenly matter
Three incidents taught the industry that you cannot defend software whose ingredients you do not know:
- SolarWinds (December 2020). Attackers trojanized the build pipeline of the Orion network-monitoring product. Roughly 18,000 organizations installed the tainted update — among them parts of the US Treasury. Knowing your dependency on Orion was suddenly critical information.
- Log4Shell (December 2021, CVE-2021-44228). A remote-code-execution flaw in log4j, a logging library buried inside thousands of products. Teams spent weeks not fixing the bug but simply finding out where log4j was used. That is an inventory problem.
- XZ Utils backdoor (March 2024, CVE-2024-3094). A multi-year social-engineering campaign planted a backdoor in a compression library that ships in nearly every Linux distribution. It was caught by a slow SSH login, not by a scanner.
Regulators followed the incidents. Executive Order 14028 pushed software bill of materials requirements onto suppliers to the US federal government; the FDA requires SBOMs for new medical-device submissions; and the EU Cyber Resilience Act phases in component-transparency obligations from 2027. Buyers and insurers now routinely ask for an SBOM before signing.
SPDX vs CycloneDX: the two main formats
| SPDX | CycloneDX | |
|---|---|---|
| Home | Linux Foundation | OWASP |
| Status | ISO/IEC 5962:2021 standard | OWASP standard, ECMA-424 |
| Roots | License compliance | Application security |
| Typical output | JSON, RDF, tag-value, spreadsheets | JSON or XML |
Either is a good choice. Pick the format your consumers ask for; what matters is that the inventory exists, is current, and is machine-readable.
How to generate an SBOM
Generation should be automated from the source or the built artifact — a hand-maintained list rots within one release cycle. Common free tools:
syft dir:. -o cyclonedx-json > sbom.json — Anchore Syft scans a directory or container image and emits SPDX or CycloneDX.
trivy fs --format cyclonedx -o sbom.json . — Trivy inventories components and can also match them to known CVEs.
cdxgen -o sbom.json — OWASP cdxgen supports dozens of ecosystems out of the box.
For Python projects specifically, the CycloneDX team maintains a dedicated generator: pip install cyclonedx-bom, then cyclonedx-py requirements requirements.txt -o sbom.json (or point it at Poetry or PDM metadata). Pair it with pip-audit to check the same dependency tree against known vulnerabilities.
SBOM automation in CI
An SBOM earns its keep when it is generated per release and diffed against the previous one. A practical minimum:
- Generate the SBOM in CI — on GitHub Actions,
anchore/sbom-action@v0does it in one step. - Publish it next to the release artifact, so users and responders never have to ask.
- Diff each release against the last. A new dependency appearing in the diff is a review moment, not a surprise later.
- Feed it to a monitoring tool (OWASP Dependency-Track, Grype, or the ecosystem equivalents) so a new CVE is matched against your inventory automatically.
That last step closes the loop the incidents opened: when the next Log4Shell drops, the affected-component list is a query, not a scavenger hunt.
SBOM — common questions
What does SBOM stand for?
Software bill of materials. The term borrows from manufacturing, where a bill of materials lists every part in a product. An SBOM does the same for a software release.
What is an SBOM in cybersecurity?
It is the inventory that vulnerability response starts from. When a CVE is published, security teams match it against SBOM components to find affected products and versions — instead of grepping source code under pressure.
Does an SBOM list vulnerabilities?
No. It lists components. Vulnerability matching is a second step that compares those components against advisories — tools like Dependency-Track, Grype or pip-audit automate it.
Is an SBOM legally required?
It depends on your jurisdiction and customers. US federal software suppliers, medical-device makers submitting to the FDA, and (from 2027) products in scope of the EU Cyber Resilience Act all face SBOM obligations. Even where none apply, enterprise buyers and insurers increasingly request one.
See also: the SBOM glossary entry for the one-line definition, the free client-side tools for hashing and inspecting the artifacts you ship, and the security checklist for the surrounding account-security basics.