A customer sends you a supplier form. One line asks for a software bill of materials, an SBOM, for each product you deliver. Soon the EU Cyber Resilience Act (CRA) asks for one too. What exactly must it contain, and who gets to see it?
The CRA’s own words on SBOMs are short. This note goes through each one, with the exact article, and adds what customers already ask for.
The short answer
- What: a record of the components in your product’s software, in a commonly used, machine-readable format, covering at least the top-level dependencies (Annex I, Part II, point 1).
- Where it goes: into your technical documentation (Annex VII, point 2(b)).
- Who sees it: a market surveillance authority can ask for it with a reasoned request (Annex VII, point 8). You do not have to make it public (recital 77).
- From when: for products that you place on the market from 11 December 2027 (Article 71(2)). Older products need it only after a substantial modification (Article 69(2)).
What the Cyber Resilience Act says about the SBOM
First, the definition.
Article 3(39)
‘software bill of materials’ means a formal record containing details and supply chain relationships of components included in the software elements of a product with digital elements;
So the SBOM is about the software in your product: the components, their details, and how they relate. For a hardware device, that means the firmware and any other software it runs.
Then the duty itself. It is the first of the vulnerability handling requirements.
Annex I, Part II, point 1
Manufacturers of products with digital elements shall: (1) identify and document vulnerabilities and components contained in products with digital elements, 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;
Three words carry the weight here: “commonly used”, “machine-readable” and “top-level”.
“Top-level dependencies”: the minimum
The CRA asks for “at the very least the top-level dependencies” (Annex I, Part II, point 1). It does not define the term. The Commission may set the format and the elements of the SBOM later, in an implementing act (Article 13(24)).
Until then, a careful start is this: list every component that your own software includes directly, with its name, its version and its supplier. Those are the first level. Where you can, go deeper and list the components inside them, because a flaw in a deeper component can reach your product too. “At the very least” sets a floor, not a target.
Which SBOM format?
The CRA names no format. It asks for one that is “commonly used and machine-readable” (Annex I, Part II, point 1). Two open standards are in wide use:
- SPDX, an international standard as ISO/IEC 5962:2021; the current version is 3.0.
- CycloneDX, published by Ecma International as ECMA-424; the 2nd edition of December 2025 covers CycloneDX 1.7.
Pick one that your customers and your tools can read. If the Commission later specifies a format under Article 13(24), you will follow that.
Who sees your SBOM
Your technical documentation. The SBOM is part of it, as one of the specifications of your vulnerability handling processes (Annex VII, point 2(b)).
A market surveillance authority, on request. The technical documentation includes, where applicable, the SBOM “further to a reasoned request from a market surveillance authority provided that it is necessary in order for that authority to be able to check compliance with the essential cybersecurity requirements” (Annex VII, point 8).
Not the public, unless you choose. The recitals say that manufacturers “should not be obliged to make the SBOM public” (recital 77). If you decide to give it to users, your user information must say where they can find it (Annex II, point 9).
What customers already ask for
The law sets a floor. Your customers can ask for more, and some do already. Honeywell’s page for its suppliers on the CRA, read on 19 October 2026, lists this request: “A machine-readable SBOM for each product or component supplied to Honeywell, covering at minimum all top-level dependencies and known vulnerabilities at the time of delivery” (Honeywell). Note the last part: the customer wants the known vulnerabilities too, not only the list of parts.
This follows from the CRA too. A manufacturer must use due diligence when it builds in components from third parties (Article 13(5)). So your OEM customers ask you for evidence, such as the SBOM in Honeywell’s list. Our note We only make a module explains why component suppliers get these questions.
Why the SBOM matters for the 24-hour clock
The SBOM is not only a document for an authority. Its purpose, in the CRA’s own recitals, is to help manufacturers and users “to track known newly emerged vulnerabilities and cybersecurity risks” (recital 77).
Since 11 September 2026, you must send an early warning within 24 hours after you become aware of an actively exploited vulnerability in your product (Article 14(1) and (2)(a); Article 71(2)). When attackers start to use a flaw in a common library, the first question is which of your products and versions contain it. With an SBOM for each version, that answer takes minutes. Without one, it can take most of the 24 hours. The steps of that clock are in our note on the CRA’s 24-hour clock.
A practical start
- One SBOM for each version you ship. A version with a new library is a new list.
- Make it from the build, not by hand. Generate it each time you build the firmware, so it matches what you actually ship.
- Choose SPDX or CycloneDX, and keep the same format across products.
- Keep it with your technical documentation, ready for a reasoned request (Annex VII, points 2(b) and 8).
- Check it every day against lists of vulnerabilities that attackers actively use, so you know quickly when the 24-hour clock may start.
Where Relvault fits
Relvault prepares this for small device makers: an SBOM for each version, the daily check against exploited-vulnerability lists, the report drafts and the answers to customer questionnaires. Your engineers check each item, and your company signs and files. See how it works and the prices.
Selling a product that is already on the market? Read what the CRA asks of products already on the market.
Common questions
Does the CRA require an SBOM?
Yes. Manufacturers must draw up an SBOM in a commonly used and machine-readable format, covering at least the top-level dependencies (Annex I, Part II, point 1). This applies to products placed on the market from 11 December 2027 (Article 71(2)).
Do I have to publish my SBOM?
No. The recitals say that manufacturers should not be obliged to make the SBOM public (recital 77). An authority can ask for it with a reasoned request (Annex VII, point 8). If you choose to share it with users, your user information must say where (Annex II, point 9).
Which SBOM format does the CRA require?
The CRA names no format. It asks for a “commonly used and machine-readable” one (Annex I, Part II, point 1). The Commission may specify the format and elements later in an implementing act (Article 13(24)).
Does the SBOM cover hardware components?
The CRA defines the SBOM as a record of “components included in the software elements” of the product (Article 3(39)). So it covers the software, including the firmware of a hardware device.
Do I need SBOMs for products I already sell?
For products placed on the market before 11 December 2027, the CRA requirements apply only after a substantial modification (Article 69(2)). The reporting duty applies to them already (Article 69(3)), and an SBOM makes that duty much easier.
Sources
- Regulation (EU) 2024/2847, the Cyber Resilience Act, official text on EUR-Lex. This note uses Articles 3(39), 13(5), 13(24), 14(1) and (2), 69(2) and (3), and 71(2); Annex I, Part II, point 1; Annex II, point 9; Annex VII, points 2(b) and 8; and recital 77.
- Honeywell, EU Cyber Resilience Act page for suppliers, read 19 October 2026.
- SPDX, specifications (ISO/IEC 5962:2021), read 19 October 2026.
- Ecma International, ECMA-424, CycloneDX Bill of Materials specification, 2nd edition, December 2025.