From 11 December 2027, every product that falls under the Cyber Resilience Act and is placed on the market from that day needs a software bill of materials, SBOM for short (Annex I, Part II, point 1 CRA). For older products this applies as soon as you substantially modify them after that date (Art. 69(2)). For devices and machines, every single unit delivered counts (draft Commission guidance, para. 11).
The first part of this article is written for management: what an SBOM is, why you need it, how much effort it takes and what to arrange. Formats, tools and commands are in the final part “For your developers”. The overview of all obligations is in Cyber Resilience Act: what the regulation means for manufacturers.
What is an SBOM?
An SBOM, short for software bill of materials, is the ingredient list of your software. It lists which third-party building blocks are inside your product, such as libraries for networking, encryption or the user interface, in which version and what they depend on. The CRA defines it as a formal record of the components and their supply chain relationships (Art. 3(39) CRA).
Why this matters shows when something goes wrong. If a vulnerability becomes known in a widely used library, you need to know quickly whether your product contains it. With an up-to-date bill of materials, a simple lookup is enough.
What the CRA requires from an SBOM
- Scope: at least the top-level dependencies, meaning the building blocks your software includes directly (Annex I, Part II, point 1). For finding vulnerabilities a deeper list pays off, because indirectly included libraries can have vulnerabilities too.
- Format: free choice, as long as it is commonly used and machine-readable. The Commission may still lay down the format and mandatory elements (Art. 13(24)); check before the cut-off date whether it has done so.
- Publication: not required (Recital 77). The SBOM belongs in the technical documentation, and the market surveillance authority, the state body supervising products, receives it upon a reasoned request (Annex VII, points 2 and 8).
The SBOM belongs in the technical documentation. You do not have to publish it.
How much effort an SBOM takes
The effort depends mainly on how your software is built. It comes in two parts:
- Once: your developers set up generation in the build, the process that turns the source code into your deliverable software. If your software gets its building blocks through a package manager, as many web, desktop and mobile applications do, free tools read out the list largely automatically. Firmware and control software need more manual work.
- Ongoing: after that, the SBOM is produced with every version by itself. The work lies in checking for new vulnerabilities: assessing hits and deciding whether and when an update comes. The CRA does not say how often to check; it requires regular testing and fixing vulnerabilities without delay (Annex I, Part II, points 2 and 3).
What you should arrange
Our recommendation:
- Decide which products and variants need an SBOM. Variants with a different build or feature set count as separate products under the draft Commission guidance (paras. 13 and 14).
- Ask your developers or a service provider to generate the SBOM automatically for every delivered version and store it with that version.
- Decide how often the SBOM is checked for new vulnerabilities, who assesses the hits and who decides on updates.
- Clarify who in your company reports an actively exploited vulnerability. From the moment you become aware, you have 24 hours (Art. 14(2)).
How reporting works and who should handle it is explained in CRA reporting obligations and deadlines to 2027.
If you do not want to build this in-house, we take over the technical part. What the service covers is on the page SBOM and vulnerability service for the CRA.
SBOM for controllers and firmware
The same obligation applies to software in machines and devices, but the bill of materials is often harder to obtain there. A finished firmware image does not reveal its components by itself; the BSI guideline TR-03183-2 treats it as a file that cannot be broken down into its components. Libraries compiled firmly into the software still count as components (sections 3.2.7 and 8.1.6).
The SBOM is most reliable when it is produced where the firmware is built, from source code and build data. Where there is no package manager, your developers record included libraries by hand with name, version and origin. If you find a vulnerability in a bought-in part, such as the operating system of a controller, report it to its manufacturer (Art. 13(6)).
For your developers: create an SBOM with CycloneDX and SPDX
SBOM formats: CycloneDX and SPDX
There are two standardised formats for SBOMs. Use the format your build produces without detours; the free generators Syft, cdxgen and Trivy write both.
CycloneDX is standardised as Ecma standard ECMA-424; the second edition of December 2025 corresponds to CycloneDX 1.7. The format can also carry VEX information, the statement whether a known vulnerability actually affects your product. The CycloneDX project provides plugins for Maven, Gradle, npm and Python, all under Apache-2.0.
SPDX is standardised as ISO/IEC 5962:2021; this standard corresponds to SPDX 2.2.1. For Python there are the SPDX tools of the project.
BSI TR-03183-2: more than the CRA minimum
In Germany, the BSI Technical Guideline TR-03183-2 describes what an SBOM should contain. The current version is 2.1.0 of 20 August 2025; the previous version 2.0.0 could only be used for six months after that, until about February 2026 (section 7). It requires JSON or XML valid under CycloneDX 1.6 or later or SPDX 3.0.1 or later (section 4).
Mandatory data under TR-03183-2:
- For the SBOM: creator with email address, or a URL instead, and a timestamp (section 5.2.1).
- Per component: creator, name, version, filename, dependencies with a statement of completeness, distribution licences, SHA-512 hash of the deployable component and the properties executable, archive and structured (section 5.2.2).
- Depth: recursively at least down to the first component outside the scope of delivery (section 5.1).
The TR is a national guideline. A format binding for the CRA can only come from a Commission implementing act (Art. 13(24)).
Creating an SBOM in five steps
- 1. Define the scope of delivery: desktop build, mobile app, firmware or container image. Each variant gets its own SBOM.
- 2. Choose a tool: Syft by Anchore, cdxgen or Trivy by Aqua, all under Apache-2.0; for Maven, Gradle, npm and Python the CycloneDX plugins.
- 3. Build it in: the SBOM is generated automatically with every release build and stored with the release.
- 4. Check completeness: review the first SBOM by hand. Add components that came in without a package manager, such as copied source code, precompiled files or statically linked libraries.
- 5. Check and repeat: before the release and continuously afterwards against vulnerability databases, for as long as the product is in its support period.
Checking the SBOM against vulnerability databases
Products must be placed on the market without known exploitable vulnerabilities (Annex I, Part I, point 2). Under the draft Commission guidance, a vulnerability is known if it is listed in the European Vulnerability Database EUVD or another known database, or is otherwise known to the manufacturer (paras. 233 and 234).
Databases:
- OSV.dev bundles open-source vulnerability databases in the common OSV format.
- The NVD, the National Vulnerability Database of the US NIST.
- The EUVD of ENISA, launched on 13 May 2025 on the basis of the NIS2 Directive.
Free tools, all under Apache-2.0:
- Grype by Anchore reads an SBOM directly: grype sbom:./sbom.json.
- Trivy checks existing SBOMs with trivy sbom.
- OSV-Scanner by Google checks against OSV.dev.
- Dependency-Track collects SBOMs of many products and versions and checks them continuously.
Not every hit requires a patch. According to the FAQ of the Commission services, which are not binding, the remedy depends on the risk: a patch, a workaround or a note in the documentation (FAQ 4.3.1). If a vulnerability does not affect your product, record that in a VEX document, for example with CSAF 2.0 or CycloneDX VEX.
What such a check looks like on a small scale is shown by our website check on a website: it reads out the Angular, AngularJS or PHP version and checks it against OSV.dev: Start the website check.
Note: this article describes the SBOM requirement under the regulation as of 16 November 2026. It is not legal advice. Which components belong in your SBOM and whether your product meets the requirements is for you as the manufacturer to assess; you issue the EU declaration of conformity yourself.
SBOM and vulnerability monitoring as a service
If you do not want to build the SBOM yourself and check it continuously, we take over the technical part: we create the SBOM of your product, compare it every month with public vulnerability databases and send you a short report with an update recommendation. We set the monthly rhythm; the CRA does not require a particular one. What we need from you, whether source code, build or firmware image, we clarify beforehand.
The service is in preparation. Those who sign up hear first when it launches and what it costs: waiting list for the SBOM and vulnerability service.