CycloneDX and SPDX are the two Software Bill of Materials (SBOM) data formats that regulators and standards bodies most commonly name by name, and both now carry third-party standards-body recognition: CycloneDX as ECMA-424 through Ecma International, SPDX as ISO/IEC 5962:2021. CycloneDX describes itself on its own site as "a full-stack Bill of Materials (BOM) standard that provides advanced supply chain capabilities for cyber risk reduction," and is maintained as an OWASP Flagship Project jointly with an Ecma International technical committee. SPDX describes itself as "an open standard for communicating software bill of material information, including provenance, license, security, and other related information," run as "an open source project hosted by the Linux Foundation." Neither format is legally mandated by name in the CRA or the CISA-led Minimum Elements document — both are simply named as acceptable, widely-used choices — so the practical question for a device maker is usually which one a given customer, tool or compliance workflow expects, not which one is "correct."
Key takeaways
- SPDX is the older of the two.
- SPDX's strength remains precise license and provenance metadata per component — useful for legal/compliance review of open-source usage.
- As of 2026-11-10, the latest releases are CycloneDX 1.7 and SPDX 3.0.1, and the one regulator text that names minimum versions is Germany's BSI TR-03183-2.
- The two formats store the same facts in different shapes.
Where each format came from
SPDX is the older of the two. Specification development began in February 2010 inside a Linux Foundation work-group, split across technical, legal and outreach sub-groups; the first version (1.0) launched in August 2011, focused on package-level license documentation. The format's license-compliance roots run deep — SPDX's own license list and license-expression syntax remain one of its most widely used parts outside pure SBOM use cases. SPDX reached ISO/IEC 5962:2021 status in August 2021, formally making it "the international open standard for security, license compliance, and other software supply chain artifacts," and SPDX 3.0.0 shipped in April 2024 with a broadened data model.
CycloneDX grew out of the OWASP ecosystem, originally built to support dependency-analysis tooling such as OWASP Dependency-Track, and is listed today as an OWASP Flagship Project — OWASP's highest project maturity tier. Its history page dates v1.0 to March 2018, as a "security-focused Bill of Materials standard supporting software and hardware components." Its specification has since been formalized as the international standard ECMA-424 through Ecma International's Technical Committee for Software & System Transparency (TC54), which cyclonedx.org states now jointly drives "the continued advancement of the specification" together with the OWASP Foundation.
What is each format built to describe?
| SPDX | CycloneDX | |
|---|---|---|
| Primary origin | License compliance documentation | Dependency/vulnerability analysis tooling |
| Standards-body status | ISO/IEC 5962:2021 (covers SPDX 2.2.1) | ECMA-424 (1st edition June 2024, CycloneDX 1.6) |
| Steward | Linux Foundation | OWASP Foundation + Ecma TC54 |
| First version | 1.0, August 2011 | 1.0, March 2018 |
| Serializations | JSON and other machine/human-readable formats | JSON, XML, Protocol Buffers |
| BOM types beyond software | License Bill of Materials data within the core model | SaaSBOM, CBOM (cryptography), HBOM (hardware), AI/ML-BOM, VEX |
SPDX's strength remains precise license and provenance metadata per component — useful for legal/compliance review of open-source usage. CycloneDX's own site emphasizes a broader family of bill-of-materials types beyond pure software composition: SaaSBOM for service dependencies, CBOM for cryptographic assets, HBOM for hardware, AI/ML-BOM for model supply chains, and VEX for stating whether a known vulnerability in a component is actually exploitable in the shipped product — a distinction that matters a great deal to a device maker trying to triage which CVEs in a dependency actually need a patch. OWASP's project page states CycloneDX tooling is "compatible with over 260 tools across 20+ programming languages."
Which versions are current, and which do regulators name?
As of 2026-11-10, the latest releases are CycloneDX 1.7 and SPDX 3.0.1, and the one regulator text that names minimum versions is Germany's BSI TR-03183-2. Release dates come from the CycloneDX history page, the SPDX overview and the spdx-spec releases:
| Format | Version | Released | Note |
|---|---|---|---|
| CycloneDX | 1.4 | January 2022 | Introduced VEX and VDR |
| CycloneDX | 1.5 | June 2023 | AI/ML transparency, formulation |
| CycloneDX | 1.6 | April 2024 | Ratified as ECMA-424, 1st edition, June 2024 |
| CycloneDX | 1.7 | October 2025 | The current ECMA-424 page describes the standard as defining v1.7 |
| SPDX | 2.2.1 | August 2020 | Prepared for ISO submission; standardized as ISO/IEC 5962:2021 |
| SPDX | 2.3 | August 2022 | "To improve interoperability with other formats" |
| SPDX | 3.0 / 3.0.1 | April 2024 / 17 December 2024 | Profile-based model; 3.0.1 is the current final text |
BSI minimums. BSI TR-03183-2 version 2.1.0 (2025-08-20) says a newly generated or updated SBOM "MUST be in JSON- or XML-format" and valid against CycloneDX 1.6 or higher or SPDX 3.0.1 or higher. Version 2.0.0 (2024-09-20) set CycloneDX 1.5 and SPDX 2.2.1. The guideline lets the immediately preceding version be applied for up to six months after a new one is issued.
How does the same SBOM field look in each format?
The two formats store the same facts in different shapes. Appendix 8.2 of BSI TR-03183-2 v2.1.0 maps each of its required data fields to SPDX 3.0.1 JSON and CycloneDX 1.6 JSON. The BSI notes that "both formats lack some of the values required" and fills the gaps with its own registered CycloneDX property taxonomy:
| Data field | SPDX 3.0.1 | CycloneDX 1.6 |
|---|---|---|
| SBOM creator | CreationInfo.createdBy → a Person or Organization with an email or URL identifier |
metadata.manufacturer (URL or contact email) |
| Timestamp | CreationInfo.created |
metadata.timestamp |
| Component name / version | software_Package name, software_packageVersion |
components[].name (and group), version |
| Component creator | originatedBy → an Agent |
components[].manufacturer |
| Dependencies | Relationship of type contains or dependsOn, with completeness |
dependencies[].dependsOn, completeness in compositions[].aggregate |
| Distribution licence | hasConcludedLicense relationship to a license expression |
licenses[].expression with acknowledgement: "concluded" |
| Hash of deployable component | software_File with a sha512 verifiedUsing hash, linked by hasDistributionArtifact |
externalReferences of type distribution with a SHA-512 hash |
| Filename, executable, archive | software_File name and software_additionalPurpose |
BSI taxonomy properties such as bsi:component:filename |
Source: BSI TR-03183-2 v2.1.0, appendix 8.2, tables 8 and 9.
The NTIA 2021 format survey made the same point for SPDX 2.x: the formats "were originally designed for different purposes," but enough fields correspond for "decent interoperability." Licence names are shared ground: the BSI requires SPDX licence identifiers in either format.
How do the two formats carry vulnerability and VEX data?
Both can state whether a product is affected by a CVE, but with different vocabularies:
| CycloneDX (1.4 and later) | SPDX 3.0.1 Security profile | |
|---|---|---|
| Where it lives | vulnerabilities[], embedded in the SBOM or in a separate VEX document |
A Vulnerability element plus VEX assessment relationships |
| Status values | Six analysis.state values |
Four relationship classes: affected, not affected, fixed, under investigation |
| Not-affected reasons | Nine justifications | Five VexJustificationType values matching the CISA labels |
| Not-affected rule | Justification "should be specified" | One of impactStatement or justificationType "MUST be defined" |
| Scores | ratings[] with methods including CVSS v2–v4, OWASP and SSVC |
Assessment relationships for CVSS v2/v3/v4, EPSS and SSVC |
Field-level detail is in our CycloneDX VEX guide and SPDX 3.0 guide.
What gets lost when you convert between them?
Conversion works for the shared core, but each direction can drop data. The cyclonedx-cli README warns that converting between SPDX and CycloneDX "can result in the loss of some information." What each tool documents:
| Tool | Documented SPDX / CycloneDX support |
|---|---|
cyclonedx-cli convert |
CycloneDX XML, JSON, Protobuf, CSV and SPDX JSON v2.3 |
| protobom | Reads and writes SPDX 2.2, 2.3 and 3.0.1 (JSON-LD) and CycloneDX 1.2–1.7 JSON |
| SPDX tools-java | SPDX 2.0–2.3 and 3.0.1; converts to JSON-LD for 3.0.1 |
| Syft | Emits cyclonedx-json 1.2–1.7 and spdx-json 2.2, 2.3 and 3.0 from one scan |
After any conversion, three checks catch most losses:
Compare countsThe component total and the dependency edges should match the source document. Compare identifiersEvery purl, CPE and hash in the source should survive. ValidateRun the target format's own validator before the file leaves the building.
The free SBOM viewer and SBOM diff read CycloneDX components[] and SPDX packages[] JSON in the browser, which covers a quick count-and-identifier comparison for SPDX 2.x and CycloneDX files.
Where this sits next to SBOM rules device makers actually face
Neither the CRA's Annex I SBOM requirement (see our firmware SBOM guide) nor the 2026 CISA/NSA/FBI-led Minimum Elements document (see our SBOM Minimum Elements guide) mandates one specific data format by name. The Minimum Elements document instead names SPDX and CycloneDX together as the two formats "currently widely used by software ecosystem stakeholders" under its Machine-Processable Data practice, leaving the choice to the organization producing the SBOM. In practice, many open-source SBOM generation tools (Syft, Trivy and others) can emit both formats from the same underlying scan, so the real-world decision is usually driven by what a specific customer's or regulator's downstream tooling can ingest rather than by a hard legal requirement.
Which format should you send to which counterparty?
Start from the request, not from preference. The rows below restate the sources above:
| The counterparty asks for | Send | Basis |
|---|---|---|
| An SBOM conformant with BSI TR-03183-2 | CycloneDX 1.6+ or SPDX 3.0.1+, JSON or XML | BSI TR-03183-2 v2.1.0, section 4 |
| An SBOM under the 2026 CISA Minimum Elements | Either format | Both named as widely used |
| CycloneDX VEX applied in Trivy | A CycloneDX SBOM plus a separate CycloneDX VEX file | Trivy VEX docs |
| A licence review | Either format, with SPDX licence identifiers | Both carry SPDX licence expressions |
A workable starting point
Check what your largest customers or regulators actually requestbefore standardizing on one format — some procurement processes are built around SPDX's license fields, others around CycloneDX's VEX workflow. Generate both from the same scan where tooling allows it, rather than maintaining two separate SBOM pipelines by hand. If vulnerability triage (not just license compliance) is the priority, lean toward CycloneDX's VEX supportto communicate exploitability status alongside the component list. Revisit the choice as the 2026 Minimum Elements' Machine-Processable Data practice gets adopted downstream— both formats continue to evolve (SPDX 3.0.1, CycloneDX 1.7) and tooling support shifts accordingly.
SoftWSP's platform extracts the SBOM from the firmware binary and writes it as CycloneDX 1.6 JSON (components only, no vulnerability data), then matches it against NVD, CISA KEV, FIRST EPSS and vendor CSAF advisories. It writes no SPDX and no VEX, and a 1.6 file is not by itself a BSI TR-03183-2 claim: fields such as hashes and licences come from the manufacturer's release process. If a counterparty needs SPDX or a newer CycloneDX version, the conversion tools above apply. See device & firmware security services.
Which mistakes get an SBOM rejected?
Most rejections are about versions and identity, not about the choice of format:
- Version below the counterparty's minimum. A CycloneDX 1.5 or SPDX 2.3 file does not meet BSI TR-03183-2 v2.1.0.
- Missing version field. CycloneDX requires
specVersionat the top level, and SPDX 3.0 requiresspecVersioninCreationInfo; parsers pick the schema from it. - Lost identifiers after conversion. A component without its purl or hash can no longer be matched against vulnerability data.
- No completeness statement. BSI requires that "the completeness of this enumeration MUST be clearly indicated" for dependencies.
- Licence text instead of an identifier. The BSI says included licence text "MUST NOT be used as a substitute for a licence identifier"; unlisted licences get a
LicenseRef-identifier.
This guide summarises the public CycloneDX and SPDX project sites, CISA's 2026 Minimum Elements resource page, BSI TR-03183-2 v2.1.0, the NTIA 2021 format survey and the tool documentation linked above (read 2026-11-10); it does not constitute legal advice.
Put this guide to work
Frequently asked questions
What are CycloneDX and SPDX?
The two machine-readable data formats for a Software Bill of Materials (SBOM) that national cybersecurity agencies most commonly point to. CycloneDX describes itself on its own site as "a full-stack Bill of Materials (BOM) standard that provides advanced supply chain capabilities for cyber risk reduction," maintained as an OWASP Flagship Project. SPDX describes itself as "an open standard for communicating software bill of material information, including provenance, license, security, and other related information," run as "an open source project hosted by the Linux Foundation." Both produce machine- and human-readable documents listing a software component's parts, versions and relationships.
Who maintains each format, and are either of them ISO or ECMA standards?
CycloneDX is driven jointly by "the OWASP Foundation and Ecma International Technical Committee for Software & System Transparency (TC54)" per cyclonedx.org, and the specification has been formalized as the international standard ECMA-424 through Ecma International's process. SPDX began life in February 2010 inside a Linux Foundation work-group, shipped its first version (1.0) in August 2011, and became "the international open standard for security, license compliance, and other software supply chain artifacts as ISO/IEC 5962:2021," available from August 2021. So both have third-party standards-body recognition — CycloneDX via Ecma, SPDX via ISO — through different standards bodies and different years.
What can each format describe beyond a basic component list?
SPDX's roots are in license compliance: version 2.2 (May 2020) added "SPDX-lite, satisfying NTIA minimum SBOM element requirements," and the format's core strength remains precise license and provenance metadata, with SPDX 3.0.0 released in April 2024 broadening its data model. CycloneDX, per its own site, now spans a wider family of BOM types beyond software — SaaSBOM, CBOM (cryptography), HBOM (hardware), AI/ML-BOM, and VEX (Vulnerability Exploitability eXchange) for communicating whether a known vulnerability is actually exploitable in a given product — and is described as "compatible with over 260 tools across 20+ programming languages." Both ship JSON and XML serializations; CycloneDX additionally supports Protocol Buffers.
Do device makers have to pick just one?
No — the 2026 CISA/NSA/FBI-led Minimum Elements for a Software Bill of Materials names SPDX and CycloneDX as the two data formats "currently widely used by software ecosystem stakeholders" (see our [SBOM Minimum Elements guide](/guides/sbom-minimum-elements/)) without mandating either one specifically, and the EU Cyber Resilience Act's Annex I SBOM requirement (see our [firmware SBOM guide](/guides/firmware-sbom/)) likewise does not name a required format. In practice a firmware vendor may need to emit CycloneDX to a customer whose tooling expects VEX/vulnerability workflows and SPDX to one whose procurement process is built around license auditing — many SBOM generation tools (e.g. Syft, Trivy) can output both from the same scan.
Sources
- CycloneDX — official project site (standard description, maintainers, BOM types, tool compatibility)
- OWASP Foundation: CycloneDX project page (Flagship Project status, BOM type list, format support)
- SPDX — official project site "About" page (origin, Linux Foundation stewardship, ISO/IEC 5962:2021, version history)
- CISA: 2026 Minimum Elements for a Software Bill of Materials (SBOM) — resource page (SPDX/CycloneDX named as widely-used formats)
- CycloneDX: Specification version history (v1.0 March 2018 to v1.7 October 2025)
- Ecma International: ECMA-424 (CycloneDX Bill of Materials specification; 1st edition June 2024)
- SPDX specification releases on GitHub (v2.3, v3.0, 3.0.1)
- BSI TR-03183-2 v2.1.0 (2025-08-20): Cyber Resilience Requirements for Manufacturers and Products, Part 2: SBOM (formats, data fields, transition, SPDX/CycloneDX mapping)
- BSI-Bund: TR-03183 CycloneDX property taxonomy
- NTIA: Survey of Existing SBOM Formats and Standards, version 2021
- SPDX 3.0.1: VexJustificationType vocabulary
- CycloneDX CLI README (convert command, SPDX interoperability note)
- protobom README (supported SPDX and CycloneDX versions)
- SPDX tools-java README (supported SPDX versions and converters)
- Anchore Syft documentation: SBOM output formats and versions
About this guide
SoftWSP Firmware Security Desk
Covers the SBOM cluster: 31 guides.

In this cluster
Questions about this page?
