What is an SBOM? Obligations under the Cyber Resilience Act
As of 3 min read
The Cyber Resilience Act requires manufacturers to draw up a software bill of materials (SBOM). What exactly is mandatory is set out in a few sentences of the Regulation – much of what is often said about it is not in there. This guide separates the two.
What is an SBOM?
SBOM stands for software bill of materials. It is a machine-readable list of the components in a software product, similar to a list of ingredients. If a vulnerability becomes known in a component, it shows which products may be affected.
Art. 3(39) defines the software bill of materials as “a formal record containing details and supply chain relationships of components included in the software elements of a product with digital elements”.
Source: Art. 3(39) CRA
Example: what an SBOM looks like
The example is a heavily shortened file in the CycloneDX format with a single component. A real SBOM lists all the components covered. The package URL (purl) allows a component to be matched unambiguously against vulnerability databases.
{
"bomFormat": "CycloneDX",
"specVersion": "1.6",
"version": 1,
"metadata": {
"component": { "type": "application", "name": "My product", "version": "2.0.0" }
},
"components": [
{
"type": "library",
"name": "lodash",
"version": "4.17.21",
"purl": "pkg:npm/lodash@4.17.21",
"licenses": [{ "license": { "id": "MIT" } }]
}
]
}Source: CycloneDX specification (GitHub) · Annex I Part II(1) CRA
The obligation: Annex I, Part II, point 1
Manufacturers must identify and document vulnerabilities and components contained in their products, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products.
It follows that:
- The minimum scope is the top-level dependencies. The wording does not prescribe a complete, transitive bill of materials – but one helps to find vulnerabilities in deeper dependencies.
- The Regulation does not prescribe a specific format, only a “commonly used and machine-readable” one.
- The SBOM is part of vulnerability handling and therefore tied to the obligations of Annex I, Part II: address vulnerabilities without delay, test security regularly, disclose fixed vulnerabilities.
When integrating third-party components, Art. 13(5) also requires due diligence so that they do not compromise the cybersecurity of the product – including for free and open-source software.
Source: Annex I, Part II CRA · Art. 13(5) CRA
From when
The requirements of Annex I apply together with the Regulation as a whole from 11 December 2027 (Art. 71(2)). For the reporting obligations, which have applied since 11 September 2026, an SBOM is not mandatory – but it is the fastest way to see whether an actively exploited vulnerability affects your own product.
Source: Art. 71(2) CRA
Do I have to publish the SBOM?
No. Recital 77 states that manufacturers should not be obliged to make the software bill of materials public. If you decide to make it available to users, the information for users under Annex II, point 9 must state where it can be accessed.
Source: Recital 77 CRA · Annex II, point 9 CRA
Which format?
The Commission may specify the format and elements of the SBOM by means of an implementing act (Art. 13(24)). The Commission’s implementation overview (as of 27 July 2026) does not list such an act.
In practice, CycloneDX and SPDX are widespread. In its Technical Guideline TR-03183-2 (version 2.1.0), the German Federal Office for Information Security (BSI) describes formal and technical requirements for SBOMs and maps its data fields to both formats. The guideline is expressly not binding and does not give rise to a presumption of conformity – but it is a good guide to which details are useful per component.
Source: Art. 13(24) CRA · Commission: implementation of the Cyber Resilience Act · BSI TR-03183
In practice
- Generate one SBOM per product and version – ideally automatically in the build, so that it matches the delivered state.
- Continuously match the SBOM against vulnerability databases; an SBOM that only sits in an archive does not serve the purpose of vulnerability handling.
- For every vulnerability found, record whether the product is affected – and why not, if it is not.
- Keep the SBOM with the technical documentation.
Source: Annex I, Part II, points 1–3 CRA
Related guides
- Product and evidenceGenerate an SBOM in CI/CD: Syft, Trivy, cdxgen5 min read
- Product and evidenceTechnical documentation under the Cyber Resilience Act7 min read
- Reporting obligationsCyber Resilience Act: reporting under Art. 14, step by step7 min read
- Product and evidenceSupport period under the Cyber Resilience Act: at least five years?3 min read
- Reporting obligationsPHP2Shell and the Cyber Resilience Act: what manufacturers must do now6 min read
- Product and evidenceAnnex I CRA: the essential cybersecurity requirements10 min read
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 3(39), Art. 13, 71, Annexes I, II, VII, Recital 77 (EUR-Lex, Official Journal)
- BSI: Technical Guideline TR-03183 (Part 2: SBOM, version 2.1.0)
- Commission: implementation of the Cyber Resilience Act, as of 27 July 2026
First published 19 Oct 2026, last updated 4 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.