Where cryptography lives in a CycloneDX file
A CBOM (cryptographic bill of materials) is not a separate file format. It is an ordinary CycloneDX document whose components array contains entries of type cryptographic-asset. That component type first appears in the CycloneDX 1.6 schema; the 1.5 schema has no such type and no cryptoProperties[1].
Each crypto component carries the usual name (required, alongside type) and, in practice, a bom-ref — a document-unique identifier that other entries point to. The cryptographic detail sits in one object, cryptoProperties, whose only required field is assetType[1]. An optional oid (object identifier) sits beside it for every asset type.
The assetType value decides which property object you fill in. There are four, and they line up closely with the four asset groups in CERT-In's Table 9[8].
assetType | Property object | Fields you will use most | CERT-In Table 9 group |
|---|---|---|---|
algorithm | algorithmProperties | primitive, parameterSetIdentifier, mode, padding, cryptoFunctions, classicalSecurityLevel, nistQuantumSecurityLevel | Algorithms (8 elements) |
certificate | certificateProperties | subjectName, issuerName, notValidBefore, notValidAfter, signatureAlgorithmRef, subjectPublicKeyRef, certificateFormat | Certificates (10 elements) |
protocol | protocolProperties | type, version, cipherSuites, ikev2TransformTypes | Protocols (5 elements) |
related-crypto-material | relatedCryptoMaterialProperties | type, id, state, size, algorithmRef, dates, securedBy | Keys (7 elements) |
oid sits beside them on cryptoProperties for every type. Source: CycloneDX 1.6 JSON schema [1]; CERT-In Technical Guidelines v2.0, Table 9, pp. 45–48 [8].Algorithms: algorithmProperties
An algorithm component describes one concrete algorithm configuration — for example RSA-2048 signatures on a payments API, or AES-256-GCM on a database. The fields are mostly enums, which is what makes a CBOM machine-comparable across suppliers.
parameterSetIdentifieris free text. The schema's own examples: “128” in AES128 (key length), “256” in SHA256 (digest length) and “SHA2-128s” for an SLH-DSA parameter set[1].classicalSecurityLevelis the classical strength in bits.nistQuantumSecurityLevelis the NIST security strength category, an integer from 0 to 6 where 0 means none of the categories is met[1]. This is the field that separates RSA and elliptic-curve algorithms from ML-KEM and ML-DSA in a query.certificationLevelrecords FIPS 140 or Common Criteria validation of the implementation, not of the algorithm in the abstract.
| Field | Allowed values (schema enum or type) |
|---|---|
primitive | drbg, mac, block-cipher, stream-cipher, signature, hash, pke, xof, kdf, key-agree, kem, ae, combiner, other, unknown (1.7 adds key-wrap) |
mode | cbc, ecb, ccm, gcm, cfb, ofb, ctr, other, unknown |
padding | pkcs5, pkcs7, pkcs1v15, oaep, raw, other, unknown |
cryptoFunctions (array) | generate, keygen, encrypt, decrypt, digest, tag, keyderive, sign, verify, encapsulate, decapsulate, other, unknown |
executionEnvironment | software-plain-ram, software-encrypted-ram, software-tee, hardware, other, unknown |
implementationPlatform | generic, x86_32, x86_64, armv7-a, armv7-m, armv8-a, armv8-m, armv9-a, armv9-m, s390x, ppc64, ppc64le, other, unknown |
certificationLevel (array) | none; FIPS 140-1, 140-2 and 140-3 levels 1–4 (e.g. fips140-3-l1); Common Criteria cc-eal1 to cc-eal7+; other, unknown |
classicalSecurityLevel | Integer, minimum 0 — classical strength in bits |
nistQuantumSecurityLevel | Integer 0–6 — NIST security strength category; 0 means none is met |
algorithmProperties [1][2].An ML-KEM-768 algorithm component
The snippet below describes ML-KEM-768, the middle parameter set of the module-lattice key-encapsulation mechanism in FIPS 203. FIPS 203 places ML-KEM-768 in security category 3[6], and NIST's object register assigns id-alg-ml-kem-768 the arc { nistAlgorithms 4 2 }, i.e. 2.16.840.1.101.3.4.4.2[7]. The algorithmFamily field needs CycloneDX 1.7; drop it for a 1.6 document.
{
"type": "cryptographic-asset",
"bom-ref": "crypto/algorithm/ml-kem-768",
"name": "ML-KEM-768",
"cryptoProperties": {
"assetType": "algorithm",
"algorithmProperties": {
"primitive": "kem",
"algorithmFamily": "ML-KEM",
"parameterSetIdentifier": "768",
"executionEnvironment": "software-plain-ram",
"implementationPlatform": "x86_64",
"cryptoFunctions": ["keygen", "encapsulate", "decapsulate"],
"nistQuantumSecurityLevel": 3
},
"oid": "2.16.840.1.101.3.4.4.2"
}
}
We checked this component, inside a minimal BOM, against the official 1.7 JSON schema; without algorithmFamily it also passes the 1.6 schema. The execution environment and platform values are illustrative — record what you actually observed. We left classicalSecurityLevel out deliberately: FIPS 203 describes ML-KEM strength by category rather than as a single bit figure[6].
Certificates: certificateProperties
In 1.6 a certificate carries subjectName, issuerName, notValidBefore, notValidAfter, certificateFormat (for example X.509), certificateExtension (the file extension, such as crt) and two references: signatureAlgorithmRef, the bom-ref of the algorithm that signed it, and subjectPublicKeyRef, the bom-ref of the subject's public key[1]. Those two references are what let you ask “which certificates are still signed with SHA256withRSA?” without parsing the certificates again.
Keys and other material: relatedCryptoMaterialProperties
Keys are not their own asset type. They are related-crypto-material, with a type drawn from: private-key, public-key, secret-key, key, ciphertext, signature, digest, initialization-vector, nonce, seed, salt, shared-secret, tag, additional-data, password, credential, token, other and unknown[1].
The state field uses the key states of NIST SP 800-57, as the schema says: pre-activation, active, suspended, deactivated, compromised and destroyed. Alongside sit id, size (in bits), algorithmRef, creation, activation, update and expiration dates, and securedBy, which names the protecting mechanism (the schema's examples include HSM and TPM) and an optional algorithm reference[1]. Avoid value for secret material: a CBOM should describe a private key, not contain it.
Protocols: protocolProperties
A protocol component has a type (in 1.6: tls, ssh, ipsec, ike, sstp, wpa, other, unknown), a version, and a list of cipherSuites. Each cipher suite has a name, an algorithms array of bom-refs pointing to algorithm components, and identifiers (the schema's examples are hex values such as 0xC0)[1]. IPsec deployments can use ikev2TransformTypes for the encryption, PRF, integrity, key-exchange and authentication transforms.
Linking assets: dependencies and provides
CycloneDX separates two relationships in its top-level dependencies array. dependsOn says one component uses another. provides lists components that a component implements; the schema's own example is “a cryptographic library which implements a cryptographic algorithm”, and it adds that implementing something “does not imply that the implementation is in use”[1].
So a library entry with provides: [ML-KEM-768, SHA256withRSA] says what the library can do; an application's dependsOn link to a specific algorithm says what it does use. CERT-In's best practices ask for exactly this distinction between libraries that implement algorithms and applications that use them (§8.4.2.4)[8]. For protocols, the link runs through the cipher suite: the TLS component lists its suites, and each suite's algorithms array points at the key-exchange, signature, cipher and hash components.
What changed in CycloneDX 1.7
CycloneDX 1.7 was released on 21 October 2025[4] and is published as the second edition of ECMA-424 (December 2025)[5]. The release notes list “cryptographic transparency” support among the additions and say various CBOM fields were deprecated in favour of new structures[3]; the announcement highlights the standardised lists of algorithm families and elliptic curves[4]. Comparing the two schemas field by field gives the detail.
| Area | What 1.7 adds or changes |
|---|---|
| Algorithm identity | New algorithmFamily, an enum defined in a separate cryptography-defs.schema.json (77 families at release, including ML-KEM, ML-DSA, SLH-DSA, LMS and XMSS). New ellipticCurve enum (246 named curves, e.g. nist/P-256); the free-text curve is deprecated. |
| Primitives | key-wrap added to primitive. |
| Certificates | New serialNumber, fingerprint, certificateState (pre-activation, active, suspended, deactivated, revoked, destroyed, or a custom state, each with an optional reason), creation, activation, deactivation, revocation and destruction dates, and certificateExtensions (e.g. keyUsage, subjectAlternativeName). certificateFileExtension replaces the deprecated certificateExtension. |
| Relationships | New relatedCryptographicAssets (a list of type + ref) on certificates, protocols and related crypto material. On certificates it replaces the now-deprecated signatureAlgorithmRef and subjectPublicKeyRef; on protocols it replaces cryptoRefArray; on related crypto material it replaces algorithmRef. |
| Keys and other material | New fingerprint and relatedCryptographicAssets. |
| Protocols | New types dtls, quic, eap-aka, eap-aka-prime, prins, 5g-aka. Cipher suites gain tlsGroups and tlsSignatureSchemes. IKEv2 transform types become structured objects (name, key length, algorithm reference); the bare reference form is deprecated. |
Deprecated 1.6 fields still validate under 1.7, so a 1.7 file can carry both signatureAlgorithmRef and relatedCryptographicAssets during a transition. If you consume CBOMs from several suppliers, say which specVersion you accept and whether you want algorithmFamily populated; the enum turns “RSA? RSASSA-PSS? rsaEncryption?” naming drift into one comparable value.
How this maps to CERT-In Table 9
CERT-In's Technical Guidelines v2.0 name 30 minimum elements across algorithms, keys, protocols and certificates, and recommend CycloneDX or SPDX as the format (§8.4.1.5)[8]. Most map directly to the fields above. Two details are worth knowing. CERT-In's “Certificate Extension” means the file extension, which is certificateExtension in 1.6 and certificateFileExtension in 1.7. And CERT-In's examples of key state (“active, revoked, or expired”) do not all exist in the SP 800-57 enum, so map them deliberately rather than inventing values. For the element-by-element mapping, see our QBOM page, which maps CERT-In's Table 8 (QBOM) and Table 9 (CBOM) elements to CycloneDX; for checking a finished file, see how to validate a CBOM.
How KavachQ helps
KavachQ's CBOM is a CycloneDX 1.7 document:
- It carries the cryptographic-asset elements in CERT-In's Table 9.
- Each CBOM is signed with ML-DSA-65 (FIPS 204) and verifiable offline against the signing key's published fingerprint.
- CBOMs from other tools can be imported and merged into the same inventory.