# CRA SBOM requirements: what the Cyber Resilience Act asks for

URL: https://sbombox.com/blog/cra-sbom-requirements
By SBOMBox SBOM experts. Published 2026-11-11, updated 2026-11-13

> The Cyber Resilience Act requires an SBOM for every product with digital elements. What it must cover, the format, who sees it, deadlines and how to prepare.

Short answer: under the EU Cyber Resilience Act, manufacturers must draw up an SBOM for each product with digital elements, in a commonly used and machine-readable format, covering at the very least the top-level dependencies. It goes in your technical documentation; you do not have to publish it, but market surveillance authorities can ask for it. The duty applies from 11 December 2027.

## Where the CRA SBOM requirement comes from

Annex I, Part II of the CRA sets the vulnerability-handling requirements. The first of them reads (all 21 requirements are in our [Annex I checklist](https://sbombox.com/blog/cra-annex-i-essential-requirements)):

> 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;
>
> — Regulation (EU) 2024/2847, Annex I, Part II, point (1). [Official text on EUR-Lex](https://eur-lex.europa.eu/eli/reg/2024/2847/oj)

Three other provisions shape it. Article 13(24) lets the Commission specify the format and elements of the SBOM by implementing act. Recital 77 explains the purpose: manufacturers should identify and document the components in their products, including by drawing up an SBOM, to help everyone who uses or buys them understand the supply chain. And the SBOM forms part of the technical documentation described in Annex VII. See our [CRA technical documentation checklist](https://sbombox.com/blog/cra-technical-documentation-checklist).

## What the CRA SBOM must cover

- Format: 'commonly used and machine-readable'. In practice that means CycloneDX or SPDX in JSON or XML. The CRA does not name one; see [CycloneDX or SPDX?](https://sbombox.com/blog/cyclonedx-vs-spdx-which-to-pick).
- Depth: at least the top-level dependencies. That is a floor, not a target: transitive dependencies are where most exploited vulnerabilities sit, so include them wherever your tools can.
- Scope: every product with digital elements you place on the EU market, and each version you support.
- Fields: the CRA does not list them. The Commission can specify the format and elements by implementing act. Until then, Germany's [BSI TR-03183-2](https://sbombox.com/blog/bsi-tr-03183-2-sbom-requirements) is the most detailed benchmark, and CISA's [2026 minimum elements](https://sbombox.com/blog/sbom-minimum-elements) are a good cross-check.

**CRA SBOM requirement at a glance**

| Question | Answer |
| --- | --- |
| Who must produce it? | The manufacturer of each product with digital elements placed on the EU market |
| Format? | Commonly used and machine-readable: in practice CycloneDX or SPDX, in JSON or XML |
| How deep? | At least top-level dependencies; full transitive coverage is good practice |
| Which fields? | Not listed in the CRA; BSI TR-03183-2 is the usual benchmark |
| Must it be published? | No. It sits in the technical documentation and goes to market surveillance authorities on request |
| From when? | 11 December 2027, with reporting duties from 11 September 2026 |
| For how long? | Each version's SBOM for the support period, with documentation kept for ten years or the support period, whichever is longer |

## Who sees your SBOM

The CRA does not require you to publish your SBOM. It must be in your technical documentation and provided to market surveillance authorities on a reasoned request. You may choose to share it with customers, for example under NDA or alongside VEX statements, and many enterprise buyers will ask.

## CRA SBOM deadlines

- 10 December 2024: the CRA entered into force.
- 11 September 2026: reporting of actively exploited vulnerabilities and severe incidents began, through [ENISA's Single Reporting Platform](https://sbombox.com/blog/enisa-cra-single-reporting-platform). You need component inventories to report fast, even though the SBOM duty itself comes later.
- 11 December 2027: all other obligations apply, including the SBOM, conformity assessment and CE marking.

## What the SBOM is for under the CRA

The CRA treats the SBOM as a working tool, not a filing. It underpins the other Annex I, Part II duties: addressing vulnerabilities without delay, regular testing, sharing information about fixed vulnerabilities, coordinated disclosure and secure updates. An SBOM generated once and left in a build artifact does none of that. [Generating an SBOM is not the same as being ready](https://sbombox.com/blog/sbom-is-not-readiness).

## Open source and SaaS

- Non-commercial open-source projects are outside the CRA; open-source stewards have lighter duties. See [the CRA and open source](https://sbombox.com/blog/cra-and-open-source).
- Pure SaaS is generally out of scope, but downloadable clients and remote data processing for a product are in. See [does SaaS need an SBOM under the CRA?](https://sbombox.com/blog/sbom-for-saas-cra).

## Getting CRA SBOM-ready

- Generate an SBOM for every release in CI, from the artifact you actually ship.
- Include exact versions, package URLs, hashes, licences and the dependency graph, not only top-level components.
- Score each SBOM against a CRA profile and BSI TR-03183-2. The [free SBOM checker](https://sbombox.com/audit) does both.
- Store SBOMs per release for the product's support period, and monitor them for new vulnerabilities.
- Record VEX decisions so you can show why each vulnerability was or was not addressed.

The [CRA workspace](https://sbombox.com/cra) in SBOMBox keeps the SBOM, vulnerability and VEX evidence for each release together.

## Frequently asked questions

### Does the Cyber Resilience Act require an SBOM?

Yes. Annex I, Part II, point (1) requires manufacturers to draw 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 product.

### Do I have to publish my SBOM under the CRA?

No. The SBOM belongs in your technical documentation. You must provide it to market surveillance authorities on a reasoned request, but you do not have to make it public.

### Which SBOM format does the CRA require?

None by name. It must be commonly used and machine-readable, which in practice means CycloneDX or SPDX. The Commission may specify a format later by implementing act.

### Does the CRA SBOM need transitive dependencies?

The legal minimum is top-level dependencies. Most guidance, including BSI TR-03183-2 and CISA's 2026 minimum elements, expects full coverage, and transitive dependencies are where most exploited vulnerabilities are found.

### When does the CRA SBOM requirement apply?

From 11 December 2027, together with the other essential requirements. Vulnerability reporting has applied since 11 September 2026, and in practice you need component inventories to meet it.

This is general information, not legal advice. Confirm how the rules apply to your products with counsel.
