KavachQ
— CBOM EVIDENCE STANDARD
PQC · BFSI · INDIA
KavachQ
Quantum-safe evidence for regulated India

Proof of cryptographic readiness,
column by column.

CERT-In's Technical Guidelines on SBOM, QBOM & CBOM v2.0 define what a cryptographic inventory must contain. Bank procurement has started enforcing it: at least one public-sector bank tender on GeM (Punjab & Sind Bank, 2026) requires bidders to submit an SBOM and a CBOM plus a 13-column self-declaration on letterhead — before deployment, then quarterly or within 15 days of any material change, with non-compliance classified as a material breach. This page describes how KavachQ produces that evidence, which columns a tool may honestly fill, and which only the vendor can sign.

The obligation, in four lines
  1. 01Submit SBOM and CBOM per CERT-In guidelines — "including all the dependencies up to the last level", covering third-party and supply-chain components.
  2. 02Submit 13 details as a self-declaration on letterhead, with machine-readable files.
  3. 03Before deployment, then quarterly or within 15 days of any material change, with known vulnerabilities and remediation plans disclosed.
  4. 04Non-compliance = material breach, penalties per SLA. (Observed live: Punjab & Sind Bank GeM tender GEM/2026/B/7366718, Ch. 4 §B.)

— The 13 columns: evidence source and owner

#ColumnEvidence sourceWho signs
01Component / software nameSBOM + cryptographic scanKAVACHQ
02Version, supplier / manufacturerSBOM (supplier, else publisher)KAVACHQ
03Component typeSBOM type / SPDX purposeKAVACHQ
04Dependency type (direct / transitive)SBOM dependency graph — left unfilled when the file cannot support the claimKAVACHQ
05License detailsSBOM licenses (SPDX concluded → declared)KAVACHQ
06Usage / purpose within the systemBusiness knowledge — no tool can know thisVENDOR
07Cryptographic assets / algorithmsCrypto graph; CERT-In xBOM v2.0 Table 9 elements incl. OIDsKAVACHQ
08Key length / strengthCrypto graphKAVACHQ
09Known vulnerabilities (CVE)SBOM vulnerability records, where carriedKAVACHQ
10Compliance statusDerived from evidence classification (vocabulary overleaf)KAVACHQ
11Last update / review dateScan timestampKAVACHQ
12Applicability — Yes / N.A. with justificationVendor judgement; an unjustified "N.A." is refused on the rowVENDOR
13Risk / mitigation measuresMigration path where knownKAVACHQ + VENDOR
KavachQ
CBOM EVIDENCE STANDARD · 02 / 02

— Column 10 vocabulary: there is no "compliant" value, by design

A scan evidences exposure and serves as the inventory artifact CERT-In requires; it cannot discharge an organisational obligation. So the status vocabulary states only what the evidence supports:

ValueMeans
exposure_evidenced_quantum_vulnerableQuantum-vulnerable cryptography directly observed.
exposure_inferred_quantum_vulnerableInferred from a dependency name — weaker evidence, labelled as such, needs confirmation.
exposure_evidenced_classically_brokenBroken today (DES, 3DES, MD5, SHA-1). More urgent than any quantum timeline.
weakened_under_groverGrover's algorithm halves effective strength (e.g. AES-128).
pqc_algorithm_observedAn actual FIPS 203 / 204 / 205 algorithm observed in use.
not_quantum_vulnerableStrong classical cryptography (e.g. AES-256). Not the same as PQC.
known_cve_recordedThe SBOM records a CVE against the component.
no_crypto_observed_not_assessedNothing observed. Absence of observation ≠ absence of cryptography.

— The honesty rules

What makes a declaration signable

— How the evidence is produced

01 · COLLECT
On site, read-only, offline

Nothing installed on vendor systems. Source, binaries, certificates and manifests read in place; SBOM built natively (Maven, npm, pip, NuGet, Go) or carried through from a supplier.

02 · ASSESS
Classify against CERT-In xBOM v2.0

Crypto assets mapped to CERT-In CBOM elements with OIDs; exposure classified per the column-10 vocabulary above.

03 · DECLARE
Signed, refreshable, verifiable

Letterhead declaration + CycloneDX 1.7 CBOM, ML-DSA-65-signed (FIPS 204). Stable row keys — vendor answers survive the quarterly refresh.

CERT-IN xBOM v2.0 CYCLONEDX 1.7 FIPS 203 / 204 / 205 READ-ONLY COLLECTION QUARTERLY REFRESH ML-DSA SIGNED
What this standard does not claim
For bidders facing a CBOM clause

SBOM + CBOM + 13-column declaration, evidence-backed, in days — not weeks. One read-only visit populates both halves. Write via kavachq.in.