SBOMs under the CRA: where the obligation actually sits

The Cyber Resilience Act mentions the software bill of materials in three separate places, and they are routinely run together. They are different provisions doing different work, so they are set out here one at a time, verbatim.

1. The duty to draw one up — Annex I, Part II, point (1)

This is the operative obligation, and the only place the Regulation says “top-level dependencies”. It sits in the essential cybersecurity requirements on vulnerability handling, not in the technical documentation annex.

“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, consolidated text 02024R2847-20241120, Annex I, Part II, point (1).

Article 13(24) confirms which provision is the operative one: it empowers the Commission to specify, by implementing act, “the format and elements of the software bill of materials referred to in Part II, point (1), of Annex I”. The format rules, when they arrive, will attach to Annex I — not to Annex VII.

Selling the same device in the United States? FDA's premarket cybersecurity guidance asks for two per-component values the CRA does not — the level of support and the end-of-support date — and neither is among the NTIA minimum elements either: FDA SBOM end-of-support addendum: template and example.

2. The documentation item — Annex VII, point 8

This is the technical-documentation entry. It is conditional and reactive: the SBOM goes into the file further to a reasoned request from a market surveillance authority.

“where applicable, the software bill of materials, 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 set out in Annex I.”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 8.

So Annex VII point 8 is not the source of a general duty to publish an SBOM, and it does not mention top-level dependencies. Anything that attributes the top-level-dependencies requirement to Annex VII point 8 has conflated it with Annex I Part II(1) above.

3. The third mention — Annex VII, point 2(b)

The SBOM appears once more, as one element of the vulnerability-handling process information that the technical documentation has to describe. It is a third, separate mention and it does not fold into either of the first two.

“necessary information and specifications of the vulnerability handling processes put in place by the manufacturer, including the software bill of materials, the coordinated vulnerability disclosure policy, evidence of the provision of a contact address for the reporting of the vulnerabilities and a description of the technical solutions chosen for the secure distribution of updates;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 2(b).

What formats

The Regulation itself says only “a commonly used and machine-readable format”. The most specific public guidance in circulation is the German BSI's TR-03183-2 v2.1.0 (2025-08-20), which sets a version floor of CycloneDX 1.6 or higher and SPDX 3.0.1 or higher.

ceproof emits CycloneDX 1.6, which meets that floor, and SPDX 2.3, which does not. SPDX 3.0.1 is a different data model rather than a version bump, and support for it is on the backlog — not shipped, and with no date. Saying so is cheaper than being caught by a reader who checks.

What ceproof emits

Both SBOM formats are in the free tier: no license key, no account, no network calls. Below is a complete, real sbom.cyclonedx.json as the CLI wrote it — a minimal one-dependency project, so it fits on the page — not a hand-written example.

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:2ae9b47a-16b5-4a93-8233-010443887c56",
  "version": 1,
  "metadata": {
    "timestamp": "2026-10-25T03:44:38.394Z",
    "tools": [
      {
        "vendor": "ceproof",
        "name": "ceproof",
        "version": "0.3.3"
      }
    ],
    "component": {
      "type": "application",
      "name": "example-product-agent"
    }
  },
  "components": [
    {
      "type": "library",
      "name": "semver",
      "version": "7.8.5",
      "purl": "pkg:npm/semver@7.8.5",
      "licenses": [
        {
          "license": {
            "id": "ISC"
          }
        }
      ]
    }
  ]
}

Licence data comes from the resolved dependency tree and is reported as what it is: where a licence cannot be determined, the component is marked unknown rather than guessed at. The effect on the pack is that Annex VII point 8 can be derived — a real list of components with real licence data — while the vulnerability-handling specification at point 2(b) stays partial, because the SBOM is only one of the things that item asks for.

Note: on the CRA profile ceproof builds the SBOM from your repository's own manifests and lockfiles, and takes no SBOM as input — --sbom is refused there with a usage error rather than quietly ignored. Importing an SBOM you already have is FDA-profile only: ceproof scan --profile fda --sbom firmware.cdx.json reads CycloneDX JSON (spec 1.4, 1.5 or 1.6), repeatable for more than one file, and in the GitHub Action the same two inputs are fda: true and fda-sbom:. SPDX import is not implemented, and a component list typed by hand is not accepted on either profile.

All 21 items in the technical file and the DoC →

Draft yours from your own repository

ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.

Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.