What “xBOM” means
“xBOM” is shorthand for the family: the x stands for software, cryptographic, quantum, AI or hardware. CERT-In — the Indian Computer Emergency Response Team, under the Ministry of Electronics and Information Technology — published Version 2.0 of its Technical Guidelines on SBOM, QBOM & CBOM, AIBOM and HBOM on 9 July 2025. The guidelines are addressed particularly to the public sector, government, essential services, and organisations in software export and software services.
They share one idea: you cannot secure, patch or migrate what you have not listed. Each BOM lists one layer.
One rule across all five: VEX
When a vulnerability is discovered, CERT-In asks the supplier for a Vulnerability Exploitability eXchange (VEX) document that classifies the vulnerability's status in each product as Not Affected, Affected, Fixed or Under Investigation — for software (§6), cryptographic and quantum components (§8.4.1.6), AI models (§9.4.1.6) and hardware (§10.4.1.5, which also accepts an equivalent hardware vulnerability statement). For software and hardware, a CSAF advisory with the detail should follow.
SBOM — Software Bill of Materials
The guidelines define an SBOM as a list of all the components, libraries and modules that make up a piece of software. Table 5 sets three kinds of minimum element: data fields (below), automation support (machine-readable formats — SPDX and CycloneDX) and practices and processes (frequency, depth, known unknowns, distribution and delivery, access control, and accommodation of mistakes).
- Component Name
- Component Version
- Component Description
- Component Supplier
- Component License
- Component Origin
- Component Dependencies
- Vulnerabilities
- Patch Status
- Release Date
- End-of-Life (EOL) Date
- Criticality
- Usage Restrictions
- Checksums or Hashes
- Comments or Notes
- Author of SBOM Data
- Timestamp
- Executable Property
- Archive Property
- Structured Property
- Unique Identifier
What is an SBOM? The full guide, with a schema-valid sample →
SBOMs are also classified by where in the lifecycle they are produced — six classes, from design to runtime (§3.2):
And by depth (§3.1, Figure 2): a top-level SBOM summarises the components directly used; an n-level SBOM goes to any depth; a delivery SBOM covers everything in a release package; a transitive SBOM adds indirect dependencies; a complete SBOM is the exhaustive list with metadata. CERT-In suggests a tailored SBOM for consumers and an internal one kept at the “complete” level.
CBOM — Cryptographic Bill of Materials
The CBOM is the inventory of cryptographic assets — algorithms, keys, protocols and certificates, with metadata such as usage and expiry (§8.1). Table 9 sets the elements per asset type: 8 for algorithms, 7 for keys, 5 for protocols and 10 for certificates. This is where your RSA and elliptic-curve exposure lives, and where a post-quantum migration starts.
Read the CBOM guide →
QBOM — Quantum Bill of Materials
The QBOM inventories quantum devices and systems, and the components related to quantum computing and quantum-safe cryptography (§8.1) — Table 8's 11 elements run from model name, version and vendor to hardware, software dependencies, environmental impact and a digital signature for the QBOM. Its “Cryptographic Asset” element points to the same Table 9 elements as the CBOM. (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.) It is not the list of your quantum-vulnerable cryptography.
What is a QBOM? The full guide, with a schema-valid sample →
AIBOM — Artificial Intelligence Bill of Materials
An AIBOM is a comprehensive list of the components used to build, train and deploy AI models: hardware, software (models, frameworks, development tools), data sources and other essentials (§9.1). Table 10 sets 19 elements:
- Model Name
- Model Version
- Model Type
- Model Developer
- Model Licensing Information
- Software Dependencies
- ML Models and Algorithms
- Model Performance Metrics
- Data Source
- Data Sets
- Hardware
- Security Requirements
- Input
- Output
- Intended Usage
- Out of Scope Usage
- Environmental Impact
- Vulnerabilities
- AttestationsDigital signature for the model or AIBOM
What is an AIBOM? The full guide, with a schema-valid sample →
HBOM — Hardware Bill of Materials
An HBOM is a structured inventory of all physical components, sub-components, embedded devices and associated materials in a hardware system or product (§10.1). Table 11 has 20 rows — supplier information and location appear twice, once for whoever sold the product and once for the direct supplier of each component:
- Product Name
- Product Version
- Product Details
- Warranty/AMC
- Manufacturer Name
- Manufacturer Location
- Manufacturing Date
- Supplier InformationWho provided or sold the product
- Supplier LocationThe product supplier's address
- Model Number
- Serial Number
- Technical Specification
- Supplier InformationWho supplied the component to the manufacturer
- Supplier LocationThe component supplier's city and country
- Technology NodeFor integrated circuits, e.g. 7 nm
- Compliancee.g. RoHS, CE
- Power Supply
- License Information
- Test Result
- Sub-componentRecursive: parts within parts
For hardware supplied to government and public-sector entities, §10.4.1.4 also names data fields such as firmware version, origin, criticality rating and associated vulnerabilities.
What is an HBOM? The full guide, with a schema-valid sample →
How KavachQ produces the set
KavachQ generates all five as CycloneDX documents — the CBOM in CycloneDX 1.7, and the SBOM in SPDX 2.3 as well — each against its CERT-In table:
- In the CBOM, QBOM, AIBOM and HBOM, every entry says how KavachQ knows it: observed by a scan, or declared by you in a registry for things no scan can see — the AI models you run, the hardware you ship, the quantum devices you operate.
- In those four, elements that cannot be filled are marked unknown, not applicable or withheld — never silently left out.
- The SBOM is built natively from your code's manifests, or carried from the SBOM your supplier provides, and exported in CycloneDX 1.6 or SPDX 2.3.
- The CBOM, QBOM, AIBOM and HBOM have signed variants, carrying an ML-DSA (FIPS 204) signature verifiable offline against the published trust anchor.
- For tenders, KavachQ also produces the 13-column SBOM/CBOM self-declaration that a public-sector bank tender in India requires, and VEX documents — see the Vendor Field Kit.
xBOM: frequently asked questions
What is an xBOM?
xBOM is shorthand for the family of bills of materials — software (SBOM), cryptographic (CBOM), quantum (QBOM), AI (AIBOM) and hardware (HBOM). Each is a structured, machine-readable inventory of one layer of a system. CERT-In's Technical Guidelines v2.0 (9 July 2025) set minimum elements for all five.
Which bills of materials do CERT-In's v2.0 guidelines cover?
Five: the SBOM (sections 2–7, Table 5), the QBOM and CBOM together (section 8, Tables 8 and 9), the AIBOM (section 9, Table 10) and the HBOM (section 10, Table 11).
Are xBOMs mandatory in India?
CERT-In's documents are technical guidelines. Their recommendations use “shall” and “must” for government, public-sector and essential-services organisations and their suppliers, and the executive summary encourages making SBOMs a mandatory standard practice in procurement and development. How they bind a given organisation depends on its regulator and its contracts; at least one public-sector bank tender in India (Punjab & Sind Bank, 2026) asks suppliers for SBOM and CBOM declarations.
Which format should an xBOM use?
SPDX or CycloneDX for the SBOM, CBOM, QBOM and AIBOM (Table 5, sections 8.4.1.5 and 9.4.1.5). For the HBOM, section 10.4.1.6 recommends structured, machine-readable formats, preferably extended SBOM formats like CycloneDX or custom XML/JSON schemas.
Do we need all five?
Each covers a different layer, so the answer depends on what you build, buy and run. Most organisations run software and cryptography everywhere, so the SBOM and CBOM apply broadly; the HBOM applies to hardware you supply or procure, the AIBOM to AI systems, and the QBOM to quantum systems and quantum-safe components.