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.
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 →
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.
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 →
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.
Source code, configuration, keystores and certificates — every finding traced to its file, and code findings to the line. KavachQ Discover →
The BOM set is signed with ML-DSA-65 (FIPS 204), verifiable offline against KavachQ's published trust anchor. KavachQ Seal →
A phased P0 / P1 / P2 plan for the quantum-vulnerable cryptography the scan found, with the replacement algorithm for each. KavachQ Migrate →
Scope a pilot on one product, or test any vendor's claims first with the Declaration Test.