SBOM for hardware manufacturers — CycloneDX vs SPDX practical guide
Practical SBOM guide for hardware manufacturers: the CRA Annex I requirement, CycloneDX vs SPDX and their versions, generation tooling, VEX and per-release upkeep.
By Vladimír VicianUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A Software Bill of Materials (SBOM) is a machine-readable inventory of the software components in a product. For in-scope products, CRA Annex I Part II point (1) makes it an obligation once the main product duties apply. Check the Article 2 scope and the Article 69 transition before applying every duty to every digital product or legacy unit.
This guide covers what an SBOM is, what the CRA says about it, the two formats (CycloneDX and SPDX) and how to choose between them, the tooling for generating SBOMs from hardware build pipelines, VEX, and how to maintain SBOMs through the product lifecycle.
What an SBOM is — and is not
An SBOM lists the software components in a product. For each component it records:
- Name — the component name (for example
openssl,mbedtls,freertos) - Version — the specific version included (for example
3.0.13) - Supplier — the upstream project or the vendor that supplied the code or binary
- Unique identifier — a Package URL (
pkg:generic/openssl@3.0.13), an SPDX identifier or a CPE - Hash — a cryptographic hash of the binary or source artefact
- Licence — an SPDX licence identifier (
Apache-2.0,BSD-3-Clause,GPL-3.0-or-later) - Source or download location — where the component came from
- Dependencies — which components depend on which
Vulnerability status is deliberately not on that list. It changes while the shipped software stays the same, so it belongs in a separate document (see the VEX section below).
What an SBOM is not:
- A vulnerability scan result — the SBOM is the input to vulnerability monitoring, not the output
- A licence compliance report — the SBOM contains licence metadata, but the compliance assessment is a separate activity
- A quality metric — the SBOM describes components, not how well they are written
- An inventory of every line of code — the granularity is the component, not the file
What the CRA says about SBOMs
The requirement is Annex I Part II point (1) of Regulation (EU) 2024/2847. Manufacturers of products with digital elements shall:
"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;"
Other points of Part II depend on that inventory:
- Point (2) — address and remediate vulnerabilities without delay, including by providing security updates. You need to know which components are affected.
- Point (3) — apply effective and regular tests and reviews of the security of the product. You need to know what to test.
- Point (4) — once a security update is available, share and publicly disclose information about fixed vulnerabilities, including information that lets users identify the affected product.
- Point (7) — provide mechanisms to securely distribute updates so that vulnerabilities are fixed or mitigated in a timely manner.
Five other provisions decide who sees the SBOM, how long you keep it and how it may be specified further:
- Annex VII lists the SBOM in the technical documentation: in point 2(b) as part of the description of the vulnerability handling processes, and in point 8, where applicable, further to a reasoned request from a market surveillance authority that needs it to check compliance with Annex I.
- Recital 77 states that manufacturers should not be obliged to make the SBOM public.
- Article 31(2) requires the technical documentation to be drawn up before the product is placed on the market and continuously updated, where appropriate, at least during the support period.
- Article 13(13) requires the technical documentation to be kept for at least 10 years after the product has been placed on the market or for the support period, whichever is longer.
- Article 13(24) allows the Commission to specify the format and elements of the SBOM by implementing act. As of 21 November 2026 we are not aware of such an act; check EUR-Lex before you fix your format.
Guidance that fills in the detail
The CRA text stops at "commonly used and machine-readable" and "top-level dependencies". Three public documents go further. None of them is EU law, but recipients and authorities may refer to them.
- BSI TR-03183-2, version 2.1.0 (20 August 2025), a technical guideline from Germany's Federal Office for Information Security. An SBOM that conforms to it must be JSON or XML in CycloneDX 1.6 or higher or SPDX 3.0.1 or higher, must be generated separately for each software version, must resolve dependencies recursively, and must not contain vulnerability information.
- ENISA Technical Advisory for Software Bill of Materials (October 2026). It describes an SBOM lifecycle of generation, validation, signing, storage, consumption and continuous maintenance, compares SPDX 3.0.1 with CycloneDX 1.7, and maps the BSI data fields to the CISA minimum elements. It states that its recommendations are non-mandatory and that it is not a legal interpretation of the CRA.
- CISA 2026 Minimum Elements for an SBOM (published 29 July 2026), which updates and replaces the 2021 NTIA minimum elements.
CycloneDX vs SPDX — practical comparison
Both are candidate formats. A format name alone proves nothing: check the version, the dependency coverage, what your recipients require and what your tools actually emit.
| Dimension | CycloneDX | SPDX |
|---|---|---|
| Governance | OWASP Foundation project, standardised by Ecma International | Linux Foundation project |
| Standardisation | ECMA-424; the 2nd edition (December 2025) defines CycloneDX 1.7 | SPDX 2.2.1 is ISO/IEC 5962:2021; the current release, SPDX 3.0.1, is not that ISO edition |
| Focus | Security and vulnerability tracking | Licensing, provenance and dependencies; SPDX 3 adds a security profile |
| Serialisation | JSON, XML, Protocol Buffers | SPDX 2.x: JSON and tag-value, among others; SPDX 3.0: JSON-LD |
| Vulnerability data | Optional vulnerabilities array with analysis states (VEX) | External documents; SPDX 3 security profile — check consumer support |
| Licence expression | SPDX licence identifiers | Native SPDX licence expressions |
| Signature | Embedded JSON signature (JSF) | External signature or attestation |
| Native embedded tooling | Buildroot utils/generate-cyclonedx; per-ecosystem CycloneDX generators | Yocto create-spdx, Zephyr west spdx, ESP-IDF idf.py sbom-create |
| Scanners | Syft, Trivy | Syft, Trivy |
Choose the format your recipient and your pinned toolchain can consume, then check the version. If you provide both formats, validate the conversion and record which relationships or assertions were lost. This article does not establish that one format is better for all embedded products.
CycloneDX SBOM — a synthetic structural example
All names and versions below are fictional. This is a schema example, not scanner output, a real firmware inventory or evidence of CRA coverage. It is valid against the CycloneDX 1.7 JSON schema.
{
"bomFormat": "CycloneDX",
"specVersion": "1.7",
"version": 1,
"metadata": {
"component": {
"type": "device",
"bom-ref": "demo-device",
"name": "ExampleSensor",
"version": "demo-1"
}
},
"components": [
{
"type": "library",
"bom-ref": "example-library",
"name": "example-library",
"version": "demo-1",
"purl": "pkg:generic/example-library@demo-1"
}
],
"dependencies": [
{
"ref": "demo-device",
"dependsOn": [
"example-library"
]
},
{
"ref": "example-library",
"dependsOn": []
}
]
}
A real release needs actual component identities, versions, dependencies and a link to the firmware artefact it describes. How to validate an SBOM beyond the JSON schema shows what a schema pass does not tell you.
Tooling for generating SBOMs
| Tool | Type | Use |
|---|---|---|
| Syft | Open source CLI | Scans container images, directories, files and archives, including an extracted root filesystem; CycloneDX and SPDX output |
| Trivy | Open source CLI | SBOM plus vulnerability scan; CycloneDX and SPDX output |
| CycloneDX generators | Build-system integration | cyclonedx-py, cyclonedx-node-npm, cyclonedx-gomod, cargo-cyclonedx and others; default spec versions differ per tool |
| FOSSology | Open source web app | Licence compliance scanning and review |
| ScanCode Toolkit | Open source CLI | Licence and copyright scanning |
| REUSE Tool | Open source CLI | Licence metadata at source-file level |
| Commercial SCA platforms | Commercial | Continuous monitoring; check which formats and versions they ingest |
For embedded firmware specifically:
- Yocto/OpenEmbedded has had the
create-spdxclass since release 3.4 (honister). In the 5.0 (scarthgap) series the class produces SPDX 2.2; in release 6.0 it produces SPDX 3.0. See the Yocto SPDX tutorial. - Buildroot generates CycloneDX from its package metadata with
make show-info | utils/generate-cyclonedx.make legal-infois a different export: it collects legally relevant material, such as package sources and licence information, for licence compliance. - ESP-IDF (Espressif) generates SBOMs with
idf.py sbom-create, based on theesp-idf-sbomtool. The default is SPDX 2.2 tag/value; SPDX 2.2 JSON, SPDX 3.0 JSON-LD and CycloneDX 1.6 JSON are options. - Zephyr generates SPDX with
west spdx; SPDX 2.3 is its default.
For closed-source firmware blobs (radio chipset firmware, modem firmware), ask the supplier for a component-level SBOM or, failing that, for version and security-advisory information. Record the blob with its hash either way.
Pin the version of every generator and scanner in your pipeline and verify release signatures or checksums. In March 2026 a malicious Trivy release (v0.69.4) and repointed trivy-action tags were published with compromised credentials (GitHub advisory GHSA-69fq-xp46-6x23).
VEX — recording what is actually exploitable
A scanner that matches SBOM components against vulnerability databases reports every known vulnerability in every listed version. Some of those vulnerabilities cannot be exploited in your product, for example because the affected code is not built in.
VEX — Vulnerability Exploitability eXchange — records your analysis of each match: which vulnerability, which product version, what status, and why. Three formats can carry it, and their vocabularies differ:
| Format | Where the statement lives | Status values |
|---|---|---|
| CycloneDX | vulnerabilities[].analysis in a BOM document | resolved, resolved_with_pedigree, exploitable, in_triage, false_positive, not_affected |
| CSAF (VEX profile) | Stand-alone CSAF document | Product status known_affected, known_not_affected, fixed, under_investigation |
| OpenVEX | Stand-alone document | not_affected, affected, fixed, under_investigation |
Do not copy a status name from one format into another: fixed, for example, is not a CycloneDX state and fails schema validation.
Keep VEX separate from the SBOM. The SBOM for a release does not change; the vulnerability analysis does. BSI TR-03183-2 goes as far as requiring that an SBOM contain no vulnerability information, and recommends CSAF, including its VEX profile, for distributing it. In CycloneDX the same separation is possible, because a BOM document that carries only the vulnerabilities array and the components it refers to is valid on its own. The CycloneDX VEX example for embedded firmware works through one.
A not_affected statement needs evidence for that product and release. Without it, VEX becomes a way to hide scanner findings.
SBOM maintenance lifecycle
An SBOM is not a one-time deliverable. For each product release:
- Generate — at the end of the build pipeline, automatically
- Validate — against the schema of the chosen format version, then for identities and coverage
- Sign — so recipients can verify where it came from
- Store — with the firmware binary and the technical documentation, under version control
- Distribute — to the notified body with the technical documentation where a third-party assessment applies, to a market surveillance authority on reasoned request, and to customers where a contract requires it
- Monitor — match it continuously against vulnerability sources such as the European vulnerability database, NVD, OSV and supplier advisories
- Update — issue a new SBOM with each release that changes any component, and keep the earlier ones for the retention period
The ENISA Technical Advisory describes the same sequence: generation, validation, signing, storage, consumption, and continuous maintenance and updates.
Where Cenitia matches an uploaded SBOM against public advisories, it covers only components that carry npm, PyPI, crates.io or Go package URLs, using OSV advisory data. All other component types, which includes most firmware, operating-system and C or C++ components, are counted as unknown and are not assessed.
Common SBOM mistakes
- No SBOM at all. For in-scope products placed on the market from 11 December 2027 this is a non-conformity with Annex I Part II.
- One SBOM generated at first release and never updated. Article 31(2) requires the technical documentation to be continuously updated where appropriate, at least during the support period. An SBOM that no longer matches the shipped firmware cannot support vulnerability handling.
- Only the manufacturer's own applications listed. The CRA does not define "top-level dependencies", but an inventory without the kernel, C library, RTOS, radio stack and bootloader cannot tell you whether a new vulnerability affects the device.
- Missing closed-source firmware blobs. Wi-Fi, modem and GPU firmware are software in the product. List them with supplier, version or build identifier and hash, even when their contents are opaque.
- Unsigned SBOM. Signing is not a CRA requirement, but without it a recipient cannot verify that the SBOM came from you unaltered.
- Scanner output passed on without analysis. Matches against an SBOM include vulnerabilities that are not exploitable in the product. Without a recorded analysis, every recipient has to repeat the triage.
- Vulnerability data embedded in the SBOM. It goes stale while the SBOM stays valid, and it conflicts with BSI TR-03183-2.
- No retention plan. Article 13(13) requires the technical documentation to be kept for at least 10 years after the product has been placed on the market or for the support period, whichever is longer. Earlier SBOMs are also what lets you check older firmware in the field against new vulnerabilities.
- SBOM stored on a developer's laptop instead of in version control. Losing earlier SBOMs means losing part of the technical documentation.
Review the supported scope and workflow
Related from the Library
- CRA Annex I explained — the Annex I Part II point (1) requirement in context
- Technical File 101 — where the SBOM sits in the documentation
- SBOM update frequency under the CRA — per-release maintenance and retention
- SBOM tooling for embedded systems compared — the tools above in more detail
- CRA timeline and reporting obligations — Article 14 reporting, which has applied since 11 September 2026
Further reading
- CycloneDX specification overview — current version 1.7, published as ECMA-424
- SPDX specifications — current release 3.0.1; SPDX 2.2.1 is ISO/IEC 5962:2021
- BSI TR-03183-2, version 2.1.0 — German technical guideline on SBOM content and format
- ENISA Technical Advisory for Software Bill of Materials — non-mandatory guidance, October 2026
- CISA 2026 Minimum Elements for an SBOM and the 2021 NTIA minimum elements it replaces
- OASIS CSAF 2.0 specification — the VEX profile is section 4.5
- OpenVEX specification
- Syft output formats — supported CycloneDX and SPDX versions
- Trivy documentation — SBOM and vulnerability scanning
FAQ
Frequently asked questions
What is an SBOM?
A software bill of materials is a machine-readable inventory of the software components in a product. For each component it records a name, version, supplier and identifier, and it records how the components depend on each other. It is the input to vulnerability handling, not a vulnerability report and not a licence audit. CycloneDX and SPDX are the two widely used formats.
Is an SBOM mandatory under the Cyber Resilience Act?
Yes, for products in scope. 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 products. The requirement applies with the main CRA obligations to products placed on the market from 11 December 2027; check the scope in Article 2 and the transition in Article 69. The SBOM is part of the technical documentation listed in Annex VII. Recital 77 states that manufacturers should not be obliged to make it public.
CycloneDX or SPDX — which one should I use?
The CRA names neither. Choose the format and the version that your build tooling emits natively and that your recipients can ingest. Germany's BSI TR-03183-2 (version 2.1.0), a technical guideline and not EU law, accepts CycloneDX 1.6 or higher and SPDX 3.0.1 or higher, in JSON or XML. Yocto's create-spdx class emits SPDX; Buildroot, Syft and Trivy can emit CycloneDX. If you convert between formats, validate the result and check which relationships and fields were lost.
Do I need SBOMs for closed-source firmware components?
Closed-source components that ship in the product, such as radio firmware, vendor SDK binaries and bootloaders, belong in the inventory. Record at least a name, a version or build identifier, the supplier and a hash, and ask the supplier for component and vulnerability information under your supply contract. Article 13(5) of the CRA requires due diligence on integrated third-party components. It does not by itself oblige every upstream supplier to hand over an SBOM, so record what is missing and how you monitor that gap.
How granular must the SBOM be?
The legal floor is the wording of Annex I Part II point (1): at the very least the top-level dependencies of the products. The CRA does not define that term. BSI TR-03183-2 describes a top-level SBOM as one that fully describes the components the primary component directly depends on, and for conformity with the guideline itself it asks for recursive dependency resolution. For firmware, an inventory that omits the operating system, libraries, bootloader and vendor binaries cannot tell you whether a new vulnerability affects the device, so documenting transitive dependencies is the practical choice.
How often does an SBOM need to be updated?
The CRA sets no interval. Keep one SBOM per released firmware version and generate a new one whenever the included software changes. Article 31(2) requires the technical documentation, which includes the SBOM, to be continuously updated where appropriate, at least during the support period. Article 13(13) requires it to be kept for at least 10 years after the product has been placed on the market or for the support period, whichever is longer. Keep the SBOMs of earlier releases; do not overwrite them.
What is VEX and how does it relate to SBOM?
VEX (Vulnerability Exploitability eXchange) is a machine-readable statement of whether a specific vulnerability affects a specific product version, with a justification. The SBOM lists components, a scanner matches them against known vulnerabilities, and VEX records your analysis of each match. CSAF, CycloneDX and OpenVEX can all carry VEX, each with its own status vocabulary. BSI TR-03183-2 requires vulnerability information to be kept out of the SBOM and recommends CSAF, including its VEX profile, for distributing it.
Who should I share the SBOM with?
The CRA requires it in two situations. The SBOM is part of the technical documentation, which a notified body examines where a third-party conformity assessment applies. Annex VII point 8 provides for supplying it to a market surveillance authority on a reasoned request, where the authority needs it to check compliance with Annex I. Sharing it with customers or researchers, or publishing it, is a contractual or voluntary choice. If you make it available to users, Annex II point 9 requires you to tell them where it can be accessed.
Continue reading
Related guides
reference
SBOM for legacy embedded firmware: building one from binaries when source is gone
Build an SBOM for legacy firmware from binaries: Binwalk extraction, Syft and Trivy scans, EMBA, a residual-risk register, and what the CRA asks of legacy units.
14 min read
reference
SBOM tooling for embedded systems: Syft, Trivy, Yocto SPDX and CycloneDX-generators compared
SBOM tools for embedded development compared: Yocto create-spdx, Buildroot, CycloneDX generators, Syft, Trivy, Binwalk and EMBA, with their limits and versions.
14 min read
guide
SBOM update frequency under CRA: release-based maintenance and historic retention
How often an SBOM must be updated under the CRA: Annex I Part II point (1), Article 31(2), one SBOM per release, retention of earlier SBOMs and continuous monitoring.
11 min read
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.