Core Concepts

Cyber Resilience Act, SBOM and BSI TR-03183-2

What the EU Cyber Resilience Act requires about the components of your product, what the BSI TR-03183-2 guideline adds, and which part of it Deptools covers.

The EU Cyber Resilience Act (CRA) makes a Software Bill of Materials (SBOM) mandatory for most products with digital elements sold in the European Union. This page explains what the regulation requires about the components of your product, and what the German BSI guideline TR-03183-2 adds to it. It then maps those requirements to the SBOM that Deptools produces, and lists what stays your responsibility as a manufacturer.

This page describes the regulation and the guideline. It is not legal advice. The official texts it relies on are listed at the end of the page, with the articles and sections used.

What the Cyber Resilience Act is

The Cyber Resilience Act is Regulation (EU) 2024/2847. It sets cybersecurity requirements for products with digital elements, hardware and software, made available on the EU market in the course of a commercial activity.

Most of its obligations fall on the manufacturer: the company that develops a product, or has it developed, and markets it under its own name or trademark. Selling it, monetizing it or giving it away free of charge makes no difference.

DateWhat applies
10 December 2024The regulation enters into force
11 June 2026The rules on the notification of conformity assessment bodies (Chapter IV)
11 September 2026The reporting of actively exploited vulnerabilities and severe incidents (Article 14), for every product on the market, including those placed on it before 2027
11 December 2027Every other obligation, the SBOM included

The reporting obligation already applies. For an actively exploited vulnerability in your product, you send an early warning within 24 hours of becoming aware of it, a notification within 72 hours, and a final report no later than 14 days after a fix or a mitigation is available. A severe incident follows the same first two deadlines, with a final report within one month. The reports go at the same time to the CSIRT designated as coordinator in your Member State and to ENISA, through the single reporting platform run by ENISA.

A failure to meet the essential requirements of Annex I, or the obligations of Articles 13 and 14, can be fined up to EUR 15 million or 2.5% of the worldwide annual turnover, whichever is higher.

Open source has its own rules. The regulation applies only in the course of a commercial activity, and free and open source software that its manufacturer does not monetize is not one. An open-source software steward, such as a foundation that supports open source intended for commercial use, has lighter obligations: a documented cybersecurity policy and cooperation with the authorities. It cannot be fined. A company that ships open source components inside its own product is the manufacturer of that product, whatever the licenses of the components.

What it requires for the components of your product

Annex I, Part II, point (1) requires the manufacturer to identify and document the vulnerabilities and the components of the product, including by drawing up an SBOM. The SBOM must be in a commonly used, machine readable format, and cover at least the top-level dependencies of the product.

The regulation defines the SBOM as a formal record of the components of the software and of the supply chain relationships between them (Article 3). Four more rules shape what you do with it:

  • The SBOM is part of the technical documentation (Annex VII). You keep it for at least 10 years after the product is placed on the market, or for the support period if that is longer (Article 13(13)).
  • A market surveillance authority can ask for it, with a reasoned request (Annex VII, point 8).
  • You do not have to publish it. The regulation says so in recital 77. If you choose to give it to your users, the user information says where to find it (Annex II, point 9).
  • You remain responsible for the components you integrate. Article 13(5) requires due diligence on components sourced from third parties, free and open source ones included.

Top-level dependencies are the minimum. In most projects the transitive dependencies far outnumber the direct ones, so an SBOM limited to direct dependencies leaves most of the packages you ship out of any vulnerability check.

The SBOM is the first of eight vulnerability handling requirements in the same part of Annex I. The other seven ask you to fix vulnerabilities without delay with security updates, to test the security of the product regularly, to disclose fixed vulnerabilities, to have a coordinated vulnerability disclosure policy and a contact address for reports, and to distribute security updates securely, without delay and free of charge.

The regulation does not name an SBOM format. Article 13(24) allows the Commission to specify the format and the elements of the SBOM by an implementing act.

Where BSI TR-03183-2 fits

The German Federal Office for Information Security (BSI) publishes the technical guideline TR-03183, Cyber Resilience Requirements for Manufacturers and Products, to prepare manufacturers for the CRA. Part 2 covers the SBOM. Its current version is 2.1.0, of 20 August 2025.

The guideline is not binding, and following it does not give a presumption of conformity with the CRA. The BSI states that harmonized European standards will replace it as soon as they are available. Until then, it is the most detailed public specification of what a CRA SBOM should contain, and a customer may make it a contractual requirement.

What Part 2 requires, in short:

  • Format. JSON or XML, valid against CycloneDX 1.6 or later, or SPDX 3.0.1 or later. Official releases of the specifications only.
  • Depth. Dependencies resolved recursively for every component in the scope of delivery, down to and including the first component outside that scope. This goes far beyond the top-level minimum of the CRA.
  • Source of the data. The SBOM contains the information available during the build.
  • One SBOM per version. Each version of the software gets its own SBOM. A new SBOM for the same version is issued only to add information or to fix an error.
  • No vulnerabilities. The SBOM must not contain vulnerability information. A software version does not change, so its SBOM is static, while the vulnerabilities known for it change over time. They belong in a separate security advisory, such as CSAF or VEX, see Where the CVEs go.
  • Data fields. A required list for the SBOM itself and for each component, mapped to the Deptools file further down.

SBOMs are generated with the most recent version of the guideline. The version before it remains accepted for six months after a new one is published, and an SBOM that complies when it is delivered stays compliant afterwards.

Which format to deliver

Deptools exports two formats. For the CRA and TR-03183-2, deliver CycloneDX 1.7.

FormatMeets the TR-03183-2 formatUse it for
CycloneDX 1.7Yes, the guideline asks for 1.6 or laterThe CRA, TR-03183-2, security tools such as Dependency-Track
SPDX 2.3No, the guideline asks for SPDX 3.0.1 or laterLicense review and procurement, tools that do not read SPDX 3

Both formats are commonly used and machine readable, as the CRA asks. Only CycloneDX also meets the format rule of the guideline.

What the Deptools SBOM covers

Deptools builds the SBOM from the analysis of your build files and lockfiles. It lists the full dependency graph, direct and transitive, with one entry per package and one relationship per dependency. The file passes the official JSON schema of its format, and contains no CVE and no score.

The tables below map each requirement of TR-03183-2 to the CycloneDX file:

  • Yes: the field is in the file, on every package when it is a field of each package.
  • Partly: the field is in the file for some packages only, or holds only part of what the guideline asks.
  • With your CI: Deptools writes the field when your pipeline provides the value.
  • With your settings: the field holds what the guideline asks once you set its value in the settings of your organization.
  • No: the field is not in the file.

The SBOM itself

RequirementIn the fileDetail
Format and versionYesCycloneDX 1.7, JSON
No vulnerability informationYesNo CVE and no score, in either format
Creator of the SBOMWith your settingsDeptools, by URL, in every file. The guideline expects the entity responsible for the SBOM, which is you, preferably with an email address. The public contact of your organization provides it once you set it
TimestampYesThe creation date, in UTC
SBOM URIYesA urn:uuid: serial number, unique to each file
One SBOM per versionWith your CIEach analysis has its own SBOM, with the commit and the product version your pipeline declares. Your CI keeps one file per release

The main component, your product

RequirementIn the fileDetail
NameYesThe name your build files declare, with its group. Otherwise the repository and subfolder of the project, or the project name for a CI upload project
VersionWith your CIThe product version declared by your pipeline. Otherwise the version your build files declare, often a development version such as 2.4.1-SNAPSHOT on a branch
CreatorPartlyThe repository of a project linked to GitHub, the public contact of your organization once you set it, and the authors your build files name (Maven developers, npm author, Composer authors). A CI upload project has a creator only through that contact and those authors
Other unique identifiersPartlyA pkg:github purl at the scanned commit, for a project linked to GitHub. None for a CI upload project, which has no public identifier to point to
LicensesPartlyThe licenses your build files declare: licenses in a POM or in build.sbt, license in package.json or composer.json. Deptools does not read the license of a Gradle project, and never uses the license of the repository. A name that is not an SPDX identifier gets a LicenseRef-deptools- identifier built from that name
Filename, executable, archive and structured propertiesPartlyDeptools never sees the file you ship, so it writes the file name only where the build tool fixes it: a Maven jar, war or ear, or an npm package that is not private, when the SBOM carries the version your build files declare. Absent for other Maven packagings, Gradle, sbt and Composer
Hash value (SHA-512) of the deployable componentNoDeptools never sees the file you ship

Each dependency

RequirementIn the fileDetail
Name and versionYesAs resolved by the analysis
Other unique identifiersYesA purl on every package
Dependencies, and their completenessYesThe direct dependencies of each package, and a completeness statement for each list (compositions)
Executable, archive and structured propertiesYesThe properties of the BSI taxonomy. A .jar, an npm tarball or a Composer archive is a structured archive and does not run on its own
Original licensesYesThe licenses each package declares, marked as declared. A license outside the SPDX list gets its ScanCode LicenseDB identifier (LicenseRef-scancode-) when Deptools identifies it, a LicenseRef-deptools- identifier otherwise
Distribution licensesPartlyThe declared license, when a package declares a single identified license or expression, OR included. Nothing when the analysis has several licenses and no operator between them: a Maven POM that lists several, an npm dependency whose expression the analysis records as separate licenses, or a package that names several licenses without saying how they combine. Nothing for a license Deptools could not identify
CreatorPartlyThe source repository, or the registry page of the package. Absent for an unresolved package that declares no repository
Source code URIPartlyThe source repository, not the exact tag or commit of the version
Filename, and URI of the deployable formPartlyThe npm tarball and the .jar on Maven Central. Absent for Composer, for other Maven repositories and for unresolved packages. A Maven Central package without a .jar, such as a Maven BOM, names a .jar that does not exist until Deptools checks it, after the analysis. After the check, it has none
Hash value (SHA-512) of the deployable componentPartlyThe SHA-512 of the npm tarball and of the .jar on Maven Central. A Maven Central version may only get it at the next scan. None for an old npm version that has only a SHA-1, for other Maven repositories, for Composer and for unresolved packages. A Composer archive is not the same file from one download to the next
Effective license (optional)NoDeptools does no legal review of its own

Depth and source of the data

RequirementIn the fileDetail
Recursive resolutionYesThe full transitive graph of the scopes your project analyzes
Several versions of one packageYesEach version is its own entry
Scope of deliveryYesEach package is marked from the scope its direct dependency is declared in: shipped, provided by the environment at run time (isExternal), or not used at run time (excluded). The marking follows your build files, not your packaging, see Dependencies your product does not ship
Runtime and interpreterPartlyPHP, Node.js or OpenJRE, with the lowest version your build files require, provided by the environment (isExternal). PHP platform packages are listed on the PHP component. Some projects get none, for example an sbt project, an Android build, or a requirement with no lowest version such as *, see The runtime your product needs
Information available during the buildPartlyDeptools reads your build files and does not run your build. With a lockfile, the graph matches what you install

This coverage changes as Deptools improves. The fields of the file are described one by one in Export reports and SBOMs.

Where the CVEs go

The SBOM lists no CVE because the guideline forbids it, not because Deptools ignores them. Every analysis checks each package of the graph, direct and transitive, against the OSV database of known CVEs. The result is available in four places:

  • The dashboard. The Security tab lists the CVEs of every dependency, with their severity and the version that fixes them. They set the Security score of each package, see The health score.
  • The CSV report. The Security preset exports, for each package, the count of CVEs per severity, the identifier of each CVE and the version that fixes them all. See Export reports and SBOMs.
  • The Graph JSON. Each package of the file carries its CVEs, for your own scripts. See Export reports and SBOMs.
  • Your CI. The status of a scan gives the count of CVEs per severity, and a quality gate can fail the build above a severity you choose. See Scan from GitHub Actions.

These are the CVEs known on the day of the analysis. Scan again to check a version against the CVEs published since.

A CVE in a dependency does not always mean your product is affected. Your code may never call the vulnerable function, or may use the package in a way that avoids the flaw. A VEX document (Vulnerability Exploitability eXchange) records that decision for each CVE: affected, not affected and why, fixed, or under investigation. A CSAF document (Common Security Advisory Framework, an OASIS standard) is the advisory you publish for your users, and VEX is one of its profiles. TR-03183-2 gives both as examples of how to exchange vulnerability information.

Deptools does not produce VEX or CSAF documents. These open source tools do, from the SBOM that Deptools gives you:

  • OWASP Dependency-Track imports a CycloneDX SBOM, matches its packages against vulnerability databases, lets you record an analysis decision for each finding, and exports those decisions as a CycloneDX VEX document. See Exchanging VEX documents.
  • Secvisogram, an editor developed by the BSI, writes CSAF advisories in the browser. The OASIS CSAF project lists it with the other CSAF open source tools, such as validators and the software to publish your advisories.

What stays your responsibility

An SBOM is one obligation among several. Deptools helps with some of the others, and some are yours alone.

Components Deptools does not see. Deptools reads the dependencies declared in the build files of the ecosystems it supports. Code copied into your repository, native libraries, the operating system of a container image and the dependencies of other ecosystems are not in its SBOM. If your product ships them, your SBOM has to list them too.

Vulnerability handling. The CRA requires you to handle the vulnerabilities of your product for its whole support period, at least five years in most cases. Deptools lists the CVEs of every dependency at every analysis, as described in Where the CVEs go. Whether a CVE affects your product depends on how your code uses the vulnerable package. That analysis is yours, and so are the VEX and CSAF documents that record it, the security updates and the disclosure policy.

Reporting. Reporting an actively exploited vulnerability or a severe incident to your CSIRT and to ENISA is the manufacturer's duty. No tool reports for you.

Keeping the record. The SBOM of every release belongs in your technical documentation for at least 10 years. Deptools keeps the completed analyses of a project, as Track scores over time explains, but your own archive is the record the regulation asks for. Keep the file your CI downloads with each release.

Keep an SBOM for every release

Each scan produces an analysis, and each analysis has its SBOM. To keep one SBOM per release:

  1. Scan from your pipeline, on the build of each release.
  2. Declare the product version, so the SBOM names your product with it. Each guide below explains how.
  3. Keep the downloaded SBOM as an artifact of the build, then archive it with your release.

The guides cover each pipeline:

For a scan that already ran, the SBOM button of the History tab downloads its SBOM, see Track scores over time.

Sources

Last reviewed in November 2026.