SolutionFor vendors bidding into banks

KavachQ Declare

Bank tenders have started asking suppliers for bills of materials and signed declarations. KavachQ produces them from your own code and builds, plus the hardware, AI-model and quantum-device details you declare — signed with a post-quantum signature, so the bank can check them offline.

What's in the pack

Four things a tender asks you for

01 · CERT-In xBOM v2.0

A signed CBOM — and the rest of the set

A CBOM in CycloneDX, built against CERT-In's Technical Guidelines v2.0 and signed with ML-DSA-65 (FIPS 204). Signed QBOM, HBOM and AIBOM come with it, and the SBOM in CycloneDX or SPDX 2.3. What the five BOMs are →

02 · SBI Annexures R–V

The annexures, in their own field names

SBI's October 2026 software RFPs, such as ref. 1506, ask suppliers for an SBOM (Annexure R) and, wherever applicable, a QBOM, CBOM, AIBOM and HBOM (Annexures S–V), kept current. KavachQ lays your BOMs out in those annexures' exact fields, with a coverage sheet showing what is filled and what is left for you.

03 · Self-declaration

The 13-column declaration, assembled

The SBOM/CBOM self-declaration on letterhead that a public-sector bank tender requires, assembled from your SBOM and CBOM. The columns only you can attest stay yours to sign. Column by column →

04 · CI gate + SARIF

Keep it true between releases

A step for your build pipeline that can fail a build when quantum-vulnerable cryptography appears — or only when it increases against a baseline — with SARIF 2.1.0 output for your code-scanning dashboard.

How it runs

Built from three KavachQ products

Discover (code)→Seal→Migrate (roadmap)
KAVACHQ DISCOVER

Scan what you ship

Source code, configuration, keystores and certificates — every finding traced to its file, and code findings to the line. KavachQ Discover →

KAVACHQ SEAL

Sign the set

The BOM set is signed with ML-DSA-65 (FIPS 204), verifiable offline against KavachQ's published trust anchor. KavachQ Seal →

KAVACHQ MIGRATE

Show the bank your plan

A phased P0 / P1 / P2 plan for the quantum-vulnerable cryptography the scan found, with the replacement algorithm for each. KavachQ Migrate →

What this does not claim

  • It does not certify compliance — the bank decides what it accepts.
  • Fields only you can know, such as release dates, end-of-life or warranty, are marked for you to fill. Nothing is guessed.
  • The 13-column format comes from a bank tender, not from CERT-In's guidelines.
Bidding soon?

Get the pack ready before the tender closes

Scope a pilot on one product, or test any vendor's claims first with the Declaration Test.