# What is a CBOM? The cryptographic bill of materials, explained

URL: https://sbombox.com/blog/cryptographic-bill-of-materials-cbom
By SBOMBox SBOM experts. Published 2026-11-13

> A CBOM inventories the cryptography in your software: algorithms, keys, certificates, protocols. Why post-quantum migration needs one, with an example.

Short answer: a CBOM (cryptographic bill of materials) is an inventory of the cryptography in a piece of software or a system: which algorithms, key lengths, certificates, protocols and crypto libraries it uses, and where. It extends the SBOM idea from components to cryptographic assets. CycloneDX has supported CBOMs natively since version 1.6. The main driver is post-quantum migration: you cannot replace RSA and elliptic-curve cryptography until you know where they are.

## Why CBOMs matter now

- Post-quantum cryptography is here. NIST published its first post-quantum standards in August 2024: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA). Migration plans start with an inventory.
- Governments ask for the inventory. In the US, National Security Memorandum 10 and OMB memo M-23-02 (2022) require agencies to inventory their cryptographic systems. The EU's coordinated post-quantum roadmap (2025) asks Member States to start the transition by the end of 2026 and to protect high-risk use cases by 2030.
- Regulations already expect strong cryptography. The Cyber Resilience Act's Annex I asks for confidentiality of data 'by state of the art mechanisms'; see the [Annex I checklist](https://sbombox.com/blog/cra-annex-i-essential-requirements). India's CERT-In SBOM guidelines (version 2.0) name the CBOM explicitly.
- Crypto hides in dependencies. Most cryptography is called from libraries, so a source search misses much of it, while an SBOM alone shows the library but not the algorithms in use.

## What goes in a CBOM

**CBOM asset types (CycloneDX 1.6)**

| Asset type | Examples | Key properties |
| --- | --- | --- |
| Algorithm | RSA-2048, ECDSA P-256, AES-256-GCM, ML-KEM-768 | Primitive (signature, key encapsulation, block cipher, hash), parameter set, mode, NIST quantum security level |
| Certificate | TLS server certificate, code-signing certificate | Subject, issuer, validity dates, signature algorithm |
| Protocol | TLS 1.2, TLS 1.3, SSH, IPsec | Version, cipher suites |
| Related crypto material | Private keys, public keys, secret keys, tokens | Type, size, state, where it is stored (never the key itself) |

Each crypto asset is a component with type `cryptographic-asset`, linked by dependency relationships to the library or application that uses it. That linkage is what turns a list into something you can act on.

## A minimal CBOM example

```json
{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "version": 1,
  "components": [
    {
      "type": "library",
      "bom-ref": "pkg:generic/openssl@3.0.13",
      "name": "openssl",
      "version": "3.0.13",
      "purl": "pkg:generic/openssl@3.0.13"
    },
    {
      "type": "cryptographic-asset",
      "bom-ref": "crypto/algorithm/rsa-2048",
      "name": "RSA-2048",
      "cryptoProperties": {
        "assetType": "algorithm",
        "algorithmProperties": {
          "primitive": "signature",
          "parameterSetIdentifier": "2048",
          "executionEnvironment": "software-plain-ram",
          "nistQuantumSecurityLevel": 0
        },
        "oid": "1.2.840.113549.1.1.1"
      }
    }
  ],
  "dependencies": [
    { "ref": "pkg:generic/openssl@3.0.13", "provides": ["crypto/algorithm/rsa-2048"] }
  ]
}
```

The `nistQuantumSecurityLevel` of 0 is the signal that matters: this asset is not quantum-safe and belongs on the migration list.

## How to build a CBOM

- Start with an SBOM of the release, so you know which crypto libraries are present. See [SBOM minimum elements](https://sbombox.com/blog/sbom-minimum-elements).
- Scan the code and binaries for cryptographic calls. IBM's open-source CBOMkit, now hosted by the Post-Quantum Cryptography Alliance, is one starting point; certificate and TLS scanners cover what runs in production.
- Record each algorithm, protocol and certificate as a `cryptographic-asset` component and link it to the component that uses it.
- Flag assets with a NIST quantum security level of 0 and those already weak today, such as SHA-1, MD5, RSA below 2048 bits and TLS below 1.2.
- Regenerate with every release, like an SBOM. Crypto changes when libraries change.

## CBOM vs SBOM vs AI-BOM

They are the same idea applied to different assets, and CycloneDX can hold all three in one document. An SBOM lists software components; an [AI-BOM](https://sbombox.com/blog/ai-bill-of-materials) adds models and datasets; a CBOM adds cryptographic assets. If you are choosing a format, CycloneDX covers all three today; see [CycloneDX or SPDX?](https://sbombox.com/blog/cyclonedx-vs-spdx-which-to-pick).

## Frequently asked questions

### What does CBOM stand for?

Cryptographic bill of materials: an inventory of the cryptographic assets (algorithms, keys, certificates, protocols and crypto libraries) in software or a system.

### Is a CBOM part of an SBOM?

It extends one. CycloneDX 1.6 lets a single document contain software components and cryptographic assets, linked by dependencies. You can also keep the CBOM as a separate document.

### Why do I need a CBOM for post-quantum migration?

Quantum computers are expected to break RSA and elliptic-curve cryptography. You cannot replace those algorithms until you know where they are used, and a CBOM is that inventory.

### Which format supports CBOMs?

CycloneDX, from version 1.6 (2024), with the cryptographic-asset component type and cryptoProperties object.
