GuideQBOMCERT-In v2.0 · §8

What is a QBOM?

CERT-In's Technical Guidelines v2.0 (July 2025) cover the QBOM alongside the SBOM, CBOM, AIBOM and HBOM — and the term is often misread. Here is what the guidelines ask for, element by element, with a schema-valid sample you can download.

The definition, in CERT-In's words

Section 8.1 of the guidelines describes the QBOM and the CBOM together as “structured inventories” that give visibility into an organisation's cryptographic and quantum-related components. It then separates them: the QBOM “focuses on components related to quantum computing and quantum-safe cryptography” — quantum algorithms, security frameworks and related technologies — while the CBOM is the inventory of cryptographic assets: algorithms, keys, protocols, certificates and their dependencies.

The minimum elements make the split concrete. Table 8 — the QBOM's elements — includes Model Name, Vendor & Origin Information and Hardware. Those are the attributes of a device: a quantum key distribution (QKD) link, a quantum random number generator, a quantum computer or simulator. They are not the attributes of an algorithm running on your web servers.

CBOM and QBOM in CERT-In's guidelines Two overlapping circles. The CBOM covers cryptographic assets everywhere: algorithms, keys, protocols and certificates. The QBOM covers quantum devices, systems and quantum-safe components: model, vendor, hardware, software dependencies, communication protocol, environmental impact. The overlap is Table 9, the cryptographic-asset elements that both use. CBOM Cryptographic assets, wherever they are used Algorithms · Keys Protocols · Certificates RSA-2048 on a payments API, ECDSA in code signing… QBOM Quantum devices, systems and quantum-safe components Model · Vendor & origin Hardware · Software deps Protocol · Environmental impact A QKD link, a QRNG… TABLE 9 Cryptographic- asset elements used by both
Figure 1 · The QBOM's “Cryptographic Asset” element points to Table 9 — the per-asset elements the CBOM is built from. Examples are illustrative. Source: CERT-In Technical Guidelines v2.0, §8.1 and §8.3, pp. 42–48.

Why the distinction matters

You will see “QBOM” used loosely to mean an inventory of cryptography that a quantum computer could break. Under CERT-In's v2.0 guidelines, that inventory is the CBOM. Mixing the two up has practical consequences: a “QBOM” that lists your RSA certificates does not describe your quantum systems, and a CBOM that leaves those certificates out is incomplete.

For most organisations today the CBOM carries most of the weight — cryptography runs everywhere, quantum devices are still rare. §8.4.1.3 asks organisations to keep an accurate, up-to-date CBOM/QBOM for all cryptographic or quantum systems they use, develop or procure. If you run no quantum devices yet, confirm with the procuring entity or regulator what they expect to see.

The 11 minimum elements of a QBOM

A note on the table itself: Table 8 is titled “Minimum Elements of QBOM & CBOM”, but its rows are headed “Elements of QBOM”; the CBOM's per-asset elements are in Table 9. Pick an element to see what CERT-In asks for, an illustrative value for a QKD link, and where it sits in a CycloneDX document. The sample on the right is a real, schema-valid CycloneDX 1.6 file — the highlighted lines change as you go.

Turn on JavaScript to explore the elements, or read the full list in Table 8 of the guidelines.


        
qbom-example.cdx.json · CycloneDX 1.6 · validated against the official schemaDownload the sample
Figure 2 · Table 8 elements with an illustrative QKD link (fictional vendor, values for teaching only). CycloneDX has no QBOM-specific fields, so device elements without a native field are carried as named properties. Source: CERT-In Technical Guidelines v2.0, Table 8, pp. 44–45.

Table 9: what to record for each cryptographic asset

Table 8's “Cryptographic Asset” element defers to Table 9, which sets the elements by asset type — 30 in all. CERT-In's element names track CycloneDX's cryptoProperties closely: the ten certificate elements match one-for-one, and keys map to CycloneDX's related-crypto-material.

CERT-In elementWhat it recordsCycloneDX 1.6 field
NameThe algorithm, e.g. “AES-128-GCM”name
Asset Type“algorithm”cryptoProperties.assetType
Primitivee.g. “signature” for SHA512withRSAalgorithmProperties.primitive
Modee.g. “gcm”algorithmProperties.mode
Crypto Functionse.g. key generation, encryption, decryption, tag generationalgorithmProperties.cryptoFunctions
Classical security levelStrength against classical attacks — 128 bits for AES-128algorithmProperties.classicalSecurityLevel
OIDe.g. 2.16.840.1.101.3.4.1.6 for AES-128-GCMcryptoProperties.oid
ListThe algorithms the quantum device or system employsNo single field — list the algorithm components the device depends on
CERT-In elementWhat it recordsCycloneDX 1.6 field
NameA unique name for the keyname
Asset Type“key”assetType: related-crypto-material
idKey ID or reference numberrelatedCryptoMaterialProperties.id
stateActive, revoked, expired… (CERT-In's examples)relatedCryptoMaterialProperties.state — CycloneDX uses the NIST SP 800-57 key states: pre-activation, active, suspended, deactivated, compromised, destroyed
sizeIn bits, e.g. 2048 for an RSA keyrelatedCryptoMaterialProperties.size
Creation DateWhen the key was createdrelatedCryptoMaterialProperties.creationDate
Activation DateWhen it became operationalrelatedCryptoMaterialProperties.activationDate
CERT-In elementWhat it recordsCycloneDX 1.6 field
NameTLS, IPsec, SSH…name and protocolProperties.type
Asset Type“protocol”cryptoProperties.assetType
Versione.g. TLS 1.2 or TLS 1.3protocolProperties.version
Cipher SuitesThe algorithms and parameters the protocol supportsprotocolProperties.cipherSuites
OIDThe protocol's object identifiercryptoProperties.oid
CERT-In elementWhat it recordsCycloneDX 1.6 field
NameUsually the subject or entity it representsname
Asset Type“certificate”cryptoProperties.assetType
Subject NameThe subject's Distinguished NamecertificateProperties.subjectName
Issuer NameThe issuing CA's Distinguished NamecertificateProperties.issuerName
Not Valid BeforeStart of validitycertificateProperties.notValidBefore
Not Valid AfterExpirycertificateProperties.notValidAfter
Signature Algorithm ReferenceThe algorithm that signed it, with its OIDcertificateProperties.signatureAlgorithmRef
Subject Public Key ReferenceThe subject's public key and its algorithmcertificateProperties.subjectPublicKeyRef
Certificate Formate.g. X.509certificateProperties.certificateFormat
Certificate Extensione.g. .crtcertificateProperties.certificateExtension
Figure 3 · Source: CERT-In Technical Guidelines v2.0, Table 9, pp. 45–48; CycloneDX 1.6 JSON schema.
ONE FIELD WORTH ADDING

Table 9 asks for an algorithm's classical security level only. CycloneDX also defines nistQuantumSecurityLevel — NIST's post-quantum security category, where 0 means none of the categories is met. It is the number that separates RSA or ECDSA (0) from ML-KEM and ML-DSA, so record it alongside the classical level.

What §8.4 asks organisations to do

CERT-In's recommendations for the CBOM and QBOM, in brief. Read the clause text in the guidelines for the exact wording.

  1. §8.4.1.1Government, public-sector and essential-services organisations shall require a CBOM for cryptographic assets and a QBOM for quantum systems in all related procurements, developments and integrations.
  2. §8.4.1.2Suppliers of software, systems or devices involving cryptographic or quantum technologies must provide a complete CBOM and/or QBOM.
  3. §8.4.1.3Keep an accurate, up-to-date CBOM/QBOM for every cryptographic or quantum system used, developed or procured.
  4. §8.4.1.4Give detailed transparency into implementations: hardware, software, algorithms, protocols and supporting components.
  5. §8.4.1.5Use recognised industry-standard formats such as SPDX or CycloneDX.
  6. §8.4.1.6When a vulnerability is found, issue a VEX document classifying it as Not Affected, Affected, Fixed or Under Investigation.
  7. §8.4.1.7Integrate CBOM/QBOM data with vulnerability databases, CERT-In advisories, threat intelligence and vendor bulletins.
  8. §8.4.1.8Consumer organisations build an internal CBOM/QBOM aligned with the supplier's data.
  9. §8.4.1.9Bring the inventories into vulnerability-management workflows.
  10. §8.4.1.10Audit the CBOM/QBOM periodically for completeness, accuracy and compliance.
  11. §8.4.1.11Cross-reference component data with VEX status to prioritise mitigation.
  12. §8.4.1.12Store and transmit the data securely — encryption, access control and integrity mechanisms.
  13. §8.4.1.13Update the CBOM/QBOM as new components, cryptographic algorithms or quantum technologies are introduced, or as existing components are modified or deprecated.

The best practices in §8.4.2 add, among others: one access-controlled inventory for cryptographic and quantum components (§8.4.2.1), complete keymaps “from root to leaf” (§8.4.2.2), distinguishing libraries that implement algorithms from applications that use them (§8.4.2.4), and scheduled reviews at least quarterly (§8.4.2.8).

CERT-In's guidelines use “shall” and “must”, but they are technical guidelines; how they bind you depends on your regulator and your contracts. Public-sector bank tenders in India have begun asking suppliers for SBOM and CBOM declarations — see the Vendor Field Kit.

How KavachQ produces a QBOM

KavachQ generates the QBOM as its own CycloneDX document, alongside the CBOM, against Table 8:

  • Observed entries come from the scan — post-quantum and hybrid algorithms seen in use, certificates with post-quantum keys or signatures, and libraries that are post-quantum-capable (labelled as capability, not use).
  • Declared entries come from your quantum-device registry — QKD links or QRNG appliances that no scan can observe. KavachQ carries your statement and labels it as declared.
  • Every Table 8 element is present on every component, either as a value or explicitly marked unknown, not applicable or withheld — never silently missing.
  • The signed variant carries an ML-DSA (FIPS 204) signature over the document, verifiable offline against KavachQ's published trust anchor.

QBOM: frequently asked questions

What is a QBOM?

In CERT-In's Technical Guidelines v2.0 (9 July 2025), a Quantum Bill of Materials (QBOM) is a structured inventory of quantum devices and systems and the components related to quantum computing and quantum-safe cryptography. Table 8 sets 11 minimum elements, from the model name and vendor to the cryptographic assets the device uses and a digital signature for the QBOM.

How is a QBOM different from a CBOM?

A CBOM inventories cryptographic assets — algorithms, keys, protocols and certificates — wherever they are used. A QBOM inventories quantum devices and systems and the components related to quantum computing and quantum-safe cryptography. The QBOM's Cryptographic Asset element points to Table 9, the same per-asset elements the CBOM records. The list of your quantum-vulnerable RSA and elliptic-curve cryptography belongs in the CBOM.

Who should ask for or provide a QBOM?

Section 8.4.1.1 says government, public-sector and essential-services organisations shall require a CBOM for cryptographic assets and a QBOM for quantum systems in all related procurements, developments and integrations. Section 8.4.1.2 says suppliers of software, systems or devices involving cryptographic or quantum technologies must provide a complete CBOM and/or QBOM.

What format should a QBOM use?

Section 8.4.1.5 asks for recognised industry-standard formats such as SPDX or CycloneDX. CycloneDX 1.6 models cryptographic assets natively but has no QBOM-specific fields, so device elements such as communication protocol or environmental impact are carried as named properties.

How often should a QBOM be updated?

Section 8.4.1.13 asks for workflows that update the CBOM/QBOM as new components, cryptographic algorithms or quantum technologies are introduced, or as existing components are modified or deprecated, and section 8.4.2.8 recommends scheduled reviews at least quarterly.

Does a QBOM have to be signed?

Table 8 lists Attestations — a digital signature for the QBOM to ensure authenticity and integrity — among its minimum elements.

Sources

  1. CERT-In (Ministry of Electronics and Information Technology), Technical Guidelines on SBOM | QBOM & CBOM | AIBOM | HBOM, Version 2.0, 9 July 2025 — §8 (pp. 42–52), Tables 8–9 (pp. 44–48).
  2. OWASP CycloneDX, CycloneDX 1.6 JSON schema — cryptoProperties.
  3. ETSI, GS QKD 014 — protocol and data format of a REST-based key delivery API (used in the illustrative example).

Related: xBOM — all five bills of materials · What a CBOM actually is · CERT-In xBOM v2.0, clause by clause · The 13-column self-declaration.

CBOM and QBOM, signed

See what your estate actually runs

Start with a free scan of a public domain, then scope a pilot that produces a signed CBOM and QBOM for a real slice of your estate.