The Complete Guide to CycloneDX | FOSSA Learning Center

A Practical Guide to CycloneDX

Get an overview of the CycloneDX bill of materials standard, including use cases, strategies for generating an SBOM, and comparisons to SPDX.

Contents

Introduction to CycloneDX

CycloneDX is a full-stack bill of materials specification designed for modern software supply chains. It's best known as a software bill of materials (SBOM) standard — and SBOMs are a top use case — but CycloneDX can also be used for vulnerability reports and many other bill of materials varieties.

CycloneDX has gained significant popularity and increased adoption since it was listed as an approved SBOM data format in the U.S. federal government's 2021 cybersecurity executive order. But the standard has been in existence for several years, dating back to 2017 when the initial prototype was released.

The current CycloneDX v1.7 was published in October, 2025. This followed the release of CycloneDX 1.6 in April, 2024, and CycloneDX 1.5 in June, 2023.

What is CycloneDX used for?

While primarily used for SBOMs, CycloneDX supports multiple use cases including vulnerability management (VEX), operations bill of materials (OBOM), machine learning bill of materials (ML-BOM), and hardware bill of materials.

CycloneDX Evolution Timeline

2017

CycloneDX Created

OWASP Foundation established CycloneDX as a security-focused SBOM standard.

2021

Executive Order 14028

CycloneDX was approved as an SBOM standard in President Biden's cybersecurity order.

2023

CycloneDX 1.5 Released

Added support for ML-BOM, MBOM, and SBOM for Low Code Application Platforms.

2024

CycloneDX 1.6 Released

Added support for Cryptographic Bill of Materials (CBOM) and other enhancements.

2025

CycloneDX 1.7 Released

Added patent-related fields, structured citations for provenance, and expanded cryptography support.

CycloneDX Use Cases

Although CycloneDX is often thought of exclusively as a software bill of materials format, it can be used for other important supply chain security initiatives. These include OBOM (operations bill of materials), BOV (bill of vulnerabilities), VDR (vulnerability disclosure report), and VEX (vulnerability exploitability exchange), among others.

CycloneDX 1.5 added three new use cases to support supply chain security and transparency in even more industries: Machine Learning Bill of Materials (ML-BOM), Manufacturing Bill of Materials (MBOM), and SBOM for Low Code Application Platforms, while CycloneDX 1.6 added support for Cryptographic Bill of Materials (CBOM).

CycloneDX can represent services too

CycloneDX can describe endpoint URIs, trust boundary traversals, authentication requirements, data classifications, directional flow of data, and providers for SaaS and other services your software relies on.

Primary CycloneDX Use Cases

Elements of a CycloneDX Bill of Materials

The CycloneDX bill of materials model consists of 11 root-level elements that provide a comprehensive framework for describing software components and their relationships.

Root-Level Elements Explained

CycloneDX is extensible

CycloneDX includes multiple extension points to enable fast prototyping of new capabilities and support for specialized and future use cases, making it adaptable to evolving needs.

CycloneDX vs. SPDX

CycloneDX and SPDX occupy a special place in the modern software bill of materials landscape. They're both human- and machine-readable, and they're the two approved full-stack SBOM formats under the U.S. government's 2021 cybersecurity executive order.

SBOM Format Comparison

CycloneDX SPDX
CycloneDX is an OWASP Foundation standard designed specifically for application security and supply chain component analysis. While it supports license information, CycloneDX was created with a primary focus on security use cases.

Key Features

Pros

Cons

Key Differences

Origin Stories

SPDX was originally developed primarily for open source license compliance and intellectual property use cases, while CycloneDX was created with security in mind. Both standards have evolved significantly since their initial releases, but their origins are still evident in their designs and capabilities.

"As an OWASP project, we came from a security context, which is a little bit different than some of the other formats and their origin stories," CycloneDX Core Working Group Chair Steve Springett told FOSSA in a recent webinar. "Our origin story was really about security, and we bring that expertise to the format."

File Formats

Both SPDX and CycloneDX are available in JSON and XML. SPDX also supports tag/value (which it describes as a "simple text-based format"), YAML, and Excel spreadsheets, while CycloneDX also supports Protocol Buffers.

Generating a CycloneDX SBOM

There are multiple ways to generate a CycloneDX software bill of materials, but as a general rule, we recommend doing so during the build process. This is because running an SBOM report right after the completion of your build will produce the most accurate inventory of dependencies possible.

Best practice for SBOM generation

For maximum accuracy, generate your SBOMs during the build process when all dependencies are present and accounted for in their exact versions. This creates a precise snapshot of your software at build time.

With FOSSA, you can easily generate a CycloneDX SBOM in either JSON or XML formats. Here's how it works:

For New FOSSA Users

  1. Start by creating your free FOSSA account.
  2. Then, navigate to Projects > Add Project to import your first project. (You can integrate locally with our CLI or import code from a VCS like GitHub.)

Generate Your CycloneDX SBOM

  1. Log into your account, and click on the "Projects" button in the header menu
  2. Click on the Project that you'd like your SBOM to describe
  3. Select the "Generate a Compliance Report" button from the "Actions" menu (on the right side of your screen)
  4. Select your SBOM export format (FOSSA supports SPDX, Plain Text, CSV, Markdown, PDF, and HTML in addition to CycloneDX)
  5. Decide which elements to include in your report — you can do this by checking (or unchecking) boxes in the "Customize Report Information" menu
  6. Click on "Edit Dependency Info" in the "Customize Report Information" menu to decide which dependency metadata (e.g. author, package manager, file path, etc) to include in your SBOM
  7. Generate your report — either download a copy to distribute yourself, or create a public link for your file

FOSSA also supports the import of third-party CycloneDX SBOMs. You can use this feature to understand the composition of third-party software, including any security or license compliance risks it might pose.