Definition: Software Bill of Materials (SBOM)
A Software Bill of Materials (SBOM) is a formal, machine-readable inventory listing every component, library, and dependency that makes up a piece of software, so a buyer or operator can tell exactly what is running inside it.
Core characteristics of Software Bill of Materials (SBOM)
An SBOM is generated from the actual build, not written from memory, and it answers one question fast: which products contain a given library.
- Lists direct and transitive open-source and commercial dependencies
- Records version numbers, licenses, and known identifiers for each component
- Is structured for automated parsing, not just human review
- Updates whenever a new build changes the dependency tree
Software Bill of Materials (SBOM) vs. AI Bill of Materials (AI-BOM)
An SBOM and an AI Bill of Materials (AI-BOM) are related but distinct records. An SBOM covers the general software supply chain: code libraries, open-source packages, licenses, and the CVEs tied to them, for any application. An AI-BOM is the AI-specific analog, extending that idea to training datasets, model weights, and training provenance. A company shipping both conventional software and AI features typically needs both records, not one in place of the other.
Importance of Software Bill of Materials (SBOM) in enterprise AI
Modern software is assembled from hundreds of open-source packages, and a single vulnerable library can sit buried four or five dependencies deep. Gartner projected that by 2025, 60% of enterprise software buyers would mandate SBOM disclosure from suppliers during procurement, up from under 20% in 2022, turning the SBOM from a security nice-to-have into a contractual gate.
Methods and procedures for Software Bill of Materials (SBOM)
Producing a usable SBOM combines build-time tooling with a format every downstream system can read.
Software composition analysis and dependency scanning
The starting point is scanning the build artifact or source tree to extract every dependency it pulls in, rather than relying on a manually maintained list.
- Resolve the full dependency tree, including transitive dependencies
- Match each component against known vulnerability databases
- Flag unlicensed or incompatible open-source licenses
Standardized SBOM formats (SPDX, CycloneDX)
Most organizations adopt one of two established formats rather than a custom spreadsheet. SPDX, maintained by the Linux Foundation, and CycloneDX, maintained by OWASP, both encode component names, versions, licenses, and relationships so security and procurement systems on both sides of a deal can parse them without manual translation.
Automated generation in CI/CD pipelines
Hand-maintained SBOMs go stale the moment a dependency is bumped. Mature teams generate the SBOM as a build artifact inside the CI/CD pipeline, so every release ships with a current record automatically.
Important KPIs for Software Bill of Materials (SBOM)
Running an SBOM program well requires tracking coverage, speed, and quality together.
Coverage and completeness metrics
- Production applications with a current SBOM: target >95%
- Components with a resolved license: target >98%
- Time to generate an SBOM for a new release: under 1 build cycle
- Third-party vendors with a supplied SBOM at intake: target >80%
Strategic risk-management metrics
An SBOM should cut the time needed to answer “which products use this library” once a new vulnerability is disclosed. IDC found mature software supply-chain inventories patch affected systems up to 50% faster than manual tracking.
Audit and freshness metrics
An SBOM nobody regenerated since the last release is already out of date. Freshness is best tracked as build-to-build drift, with anything older than one release cycle flagged before it reaches a customer or auditor.
Risk factors and controls for Software Bill of Materials (SBOM)
SBOM programs face a mix of process gaps and the pressures that come with sudden regulatory attention.
Incomplete or outdated inventories
An SBOM that misses transitive dependencies or was generated from an old build gives a false sense of coverage.
- Build scripts that pull dependencies outside the scanned pipeline
- Vendored or copy-pasted code that scanners cannot detect
- Legacy applications never scanned since their original release
Vulnerability and license exposure
Even a complete SBOM only helps if someone acts on it. It surfaces known CVEs and incompatible open-source licenses so security and legal teams can act before a customer or auditor finds them first.
Regulatory non-compliance exposure
The Cyber Resilience Act (CRA) requires manufacturers of products with digital elements to maintain an SBOM covering at least top-level dependencies. Without one, assembling it under enforcement pressure becomes a rushed exercise instead of routine documentation.
Practical example
A 70-person industrial control-software vendor in Bavaria supplies machine-monitoring software to automotive-parts manufacturers across the EU. When its largest customer’s procurement team began requiring an SBOM for contract renewal, citing both ISO 27001 certification and incoming CRA obligations, the vendor had no automated way to produce one. Adding software composition analysis to its build pipeline and generating a CycloneDX SBOM for every release took about three weeks.
- Standardized SBOM attached automatically to every release
- Faster response when a customer asks about a newly disclosed CVE
- Cleaner vendor due-diligence process during contract renewals
- Documented license inventory ready for legal review
Current developments and effects
SBOM practice is shifting from a security-team habit to a baseline procurement and regulatory expectation.
Regulatory mandates expanding
Governments on both sides of the Atlantic are turning SBOM disclosure into a legal requirement.
- The EU Cyber Resilience Act phases in SBOM-related obligations through 2027
- NIS2 widens security and incident-reporting duties for a larger set of EU companies
- US federal procurement rules under Executive Order 14028 already require SBOMs from software vendors selling to government agencies
Convergence with AI supply-chain security
As vendors ship products combining conventional code with AI features, SBOM and AI-BOM tooling are converging on shared formats and pipelines.
Vendor tooling maturing
Open-source and commercial scanning tools now generate SBOMs automatically as a build byproduct, cutting the manual effort that made early programs slow to start.
Conclusion
A Software Bill of Materials turns a product’s hidden dependency tree into a documented, queryable record. As the Cyber Resilience Act’s obligations take fuller effect and procurement teams treat an SBOM as a condition of doing business, having one ready stops being optional. Vendors that automate generation inside their build pipeline avoid scrambling to reconstruct a product’s composition under contract or audit pressure. Treating it as a routine release artifact, not a one-off exercise, keeps a vendor ready for the next customer request or disclosed vulnerability.
Frequently Asked Questions
What is a Software Bill of Materials?
A formal, machine-readable inventory of every component, library, and dependency inside a piece of software, giving a traceable record of what it is built from.
How is an SBOM different from an AI Bill of Materials?
An SBOM covers the general software supply chain: code libraries, licenses, and the CVEs tied to them. An AI Bill of Materials is the AI-specific version, covering datasets, model weights, and training provenance instead.
Does the EU Cyber Resilience Act require an SBOM?
Yes. Manufacturers of products with digital elements must maintain an SBOM covering top-level dependencies, with the CRA’s full obligations applying from December 2027 after an earlier reporting duty starting September 2026.
Is building an SBOM worth it for a mid-sized software vendor?
Yes, especially for any vendor selling to enterprise customers who run their own AI vendor risk management or third-party risk process, since a missing SBOM increasingly stalls a deal at the procurement stage.
What does it cost to set up SBOM generation?
Most of the cost is upfront: adding scanning to the build pipeline and clearing an initial backlog of unlicensed components. Once automated, each release adds negligible ongoing cost.
Do we need our own IT team to maintain an SBOM process?
Not necessarily. Many vendors integrate an off-the-shelf scanning tool into their CI/CD pipeline with help from an external security consultant, then let generation run with only occasional internal review afterward.