SDG data protection blog

Laws & regulationIT security

SBOM under the CRA: Software Bill of Materials under the Cyber Resilience Act

05 November 2026 by Sebastian Baier · Reading time approx. 9 minutes

The Cyber Resilience Act requires manufacturers of products with digital elements to identify and document the components contained in their products, including by drawing up a software bill of materials (SBOM) in a commonly used and machine-readable format covering at the very least the top-level dependencies (Annex I Part II point 1 of Regulation (EU) 2024/2847). The SBOM forms part of the technical documentation. Manufacturers do not have to make it public, but must provide it upon a reasoned request from the market surveillance authority. The requirement applies from 11 December 2027.

This article explains what the SBOM must achieve, which formats have become established and how to build an SBOM process that holds up throughout the entire support period. An overview of the CRA can be found on the page Cyber Resilience Act consulting.

What is an SBOM?

Under Art. 3 point 39 CRA, a software bill of materials (SBOM) is a formal record containing details and supply chain relationships of components included in the software elements of a product. Put simply: a machine-readable list of all the libraries, frameworks and modules your software consists of, with version and origin.

The benefit lies in vulnerability handling. If a vulnerability becomes known in a widely used open-source library, the SBOM shows within minutes which of your products and versions are affected. Without an SBOM, the search only begins when the clock is actually already running, for example for reporting an actively exploited vulnerability within 24 hours under Art. 14 CRA.

What the CRA requires

Reference Content
Annex I Part II point 1 identify and document vulnerabilities and components, including by drawing up an SBOM in a commonly used and machine-readable format covering at the very least the top-level dependencies
Annex VII point 2(b) the technical documentation describes the vulnerability handling processes, including the SBOM, alongside the coordinated vulnerability disclosure policy, the contact address and the secure distribution of updates
Annex VII point 8 the SBOM itself must be provided to the market surveillance authority upon a reasoned request, insofar as the authority needs it to check compliance with the essential cybersecurity requirements
Annex II point 9 if the manufacturer makes the SBOM available to users, it must indicate where it can be accessed
Art. 13(24) the Commission may specify the format and elements of the SBOM by means of implementing acts

Timing: the essential cybersecurity requirements of Annex I apply from 11 December 2027 to products placed on the market from that date. The reporting obligations under Art. 14 already apply from 11 September 2026, including for existing products. An SBOM is not mandatory for this, but it makes reporting on time considerably easier. Details in the article CRA reporting obligations.

Depth: the legal minimum is the top-level dependencies, that is the components your product integrates directly. Vulnerabilities, however, are often found in transitive dependencies, that is in libraries that your direct dependencies bring along themselves. For effective vulnerability handling it is therefore worthwhile recording the dependencies as deeply as your tools allow.

Who may see the SBOM

Recipient Obligation under the CRA
The public no obligation to make it public
Customers and users no obligation to hand it over; possible on a voluntary or contractual basis, in which case indicating where it can be accessed (Annex II point 9)
Market surveillance authority to be provided upon a reasoned request (Annex VII point 8); in Germany, the BSI (Federal Office for Information Security) is to become the market surveillance authority

The recitals of the CRA emphasise the protection of confidentiality: authorities should only exchange information about dependencies with each other in anonymised and aggregated form.

In practice, customers increasingly require SBOMs contractually, in particular regulated companies that have to manage their supply chain under NIS2. See NIS2 and the supply chain. Determine under which conditions you pass on SBOMs, for example under a non-disclosure agreement.

Formats and technical guidelines

The CRA does not prescribe a specific format and mentions neither CycloneDX nor SPDX; it only requires a "commonly used and machine-readable" format. In market practice, two open standards have become established:

Format Origin Typical use
CycloneDX OWASP project, standardised by Ecma International as ECMA-424 strongly focused on security and vulnerability management
SPDX Linux Foundation, standardised in version 2.2.1 as ISO/IEC 5962:2021 originally from licence management, now widely used

Both formats are supported by common build and analysis tools. More important than the choice of format is that the SBOM is generated automatically, completely and for each product version.

Practical example: the AusweisApp of the German federal government (the official eID app) shows what an SBOM looks like. On its download page, under „Weiterführende Informationen“ (further information), an SBOM for the current version is available for download, in November 2026 for version 2.6.2 in SPDX 2.3 format. It lists the product and its dependencies, such as Qt modules and OpenSSL, with version, supplier and licence, as well as identifiers for vulnerability matching (CPE or package URL). According to the file, it was generated with a tool for the CMake build and belongs to exactly one version, which is also what makes sense for your SBOM process.

Guidance is provided by the BSI Technical Guideline TR-03183-2 on SBOMs, currently in version 2.1.0 of 3 September 2025. It describes formal and technical requirements for SBOMs, such as mandatory fields for the SBOM and for each component, and contains a mapping of the data fields to CycloneDX and SPDX. The guideline is not binding, but it offers concrete guidance for implementation. Whether the Commission will specify a binding format under Art. 13(24) remains to be seen; keep an eye on developments.

How to build the SBOM process

  1. Record products and versions Which products with digital elements do you offer, and which versions are in the field? Do not forget existing products; they are covered by the reporting obligations.
  2. Choose tool and format CycloneDX or SPDX, to suit your build environment and your customers' requirements.
  3. Generate the SBOM in the build Automatically with every release, not once by hand. Every version delivered gets its own SBOM.
  4. Include purchased components Contractually oblige suppliers of software, firmware or modules to provide SBOM data and security updates throughout your own support period.
  5. Store with versioning Keep SBOMs for as long as the technical documentation must be kept, that is at least ten years or for the support period, whichever is longer.
  6. Match continuously Regularly match SBOMs against vulnerability information and assess the hits.
  7. Link with remediation and reporting Who decides on updates, who checks whether a report under Art. 14 is necessary? See CRA: obligations for manufacturers.
  8. Regulate disclosure Define conditions for customers and the procedure for requests from authorities.

Typical mistakes

Mistake Consequence
SBOM created once in the project instead of continuously in the build out of date after the next release
one SBOM for all versions affected versions cannot be determined in an emergency
only your own components, purchased modules missing gaps exactly where you have no source code
SBOM without vulnerability matching a document with no security benefit
no rule on disclosure case-by-case decisions and confidentiality risks

How SDG supports you

We advise manufacturers and support implementation. We do not inspect or test products ourselves.

  • Gap analysis against Annex I, including the SBOM process and vulnerability handling
  • Process design: roles, procedures and documentation for SBOM, vulnerability handling and reporting
  • Supplier requirements: clauses on SBOM deliveries and security updates
  • Linking with ISO 27001 and NIS2, if you are regulated yourself
  • Training for the teams involved: training

Frequently asked questions about the SBOM under the CRA

What is an SBOM?

Under Art. 3 point 39 CRA, a software bill of materials is a formal record containing details and supply chain relationships of components included in the software elements of a product. In practice, it is a machine-readable list of all libraries and modules with version and origin.

Is an SBOM mandatory under the CRA?

Yes. Annex I Part II point 1 requires an SBOM in a commonly used and machine-readable format covering at the very least the top-level dependencies. The requirement applies to products placed on the market from 11 December 2027.

Do I have to make the SBOM public or hand it over to customers?

No. The CRA does not provide for an obligation to make it public and does not require it to be handed over to customers. The SBOM forms part of the technical documentation and must be provided to the market surveillance authority upon a reasoned request. Passing it on to customers is possible on a voluntary or contractual basis.

Which format do I need for the SBOM?

The CRA requires a commonly used and machine-readable format without specifying it. In practice, CycloneDX and SPDX have become established. The BSI Technical Guideline TR-03183-2 describes requirements for SBOMs and maps the data fields to both formats.

Are the direct dependencies enough?

Legally, the minimum is the top level of dependencies. Many vulnerabilities, however, are found in transitive dependencies. For effective vulnerability handling it is advisable to record them in greater depth.

For how long must I keep SBOMs?

As part of the technical documentation, for at least ten years after the product has been placed on the market or for the support period, whichever is longer. Every version delivered should have its own SBOM.

What does an SBOM look like in practice?

A publicly accessible example is the AusweisApp of the German federal government. Its download page provides an SBOM for the current version in SPDX format. It lists the product and its dependencies with version, supplier, licence and identifiers for vulnerability matching.


Sources: Regulation (EU) 2024/2847 (Cyber Resilience Act), BSI TR-03183, AusweisApp: download and SBOM

Note: This article provides general information and does not replace legal advice in individual cases.