Where KavachQ runs
KavachQ is deployed in the environment your policies require: inside your own cloud tenancy (VPC), in your data centre, or in an air-gapped network, as self-hosted Docker. The cryptographic inventory, findings and evidence stay inside that boundary.
- No key custody. KavachQ never stores your keys. For an approved change applied over SSH, the key is supplied with the request and held only in memory.
- No cloud credentials. Cloud, Kubernetes, HSM and similar sources are read from read-only exports you provide. There are no live connectors into your cloud accounts, and KavachQ does not connect to your HSMs.
- Collection you control. For internal networks, an in-network collector produces one evidence bundle that your team imports; collectors can be enrolled and revoked.
See the deployment diagram on the platform page.
What it can change
Collect, Assess, Roadmap, Attest and Monitor read and advise. They never change your systems' cryptography. Roadmap writes only tickets and CMDB records, and only when you choose to push them to Jira or ServiceNow.
Change, inside KavachQ Migrate, is the one part that can alter a system, and it is deliberately narrow:
- It works on TLS terminators only (nginx, HAProxy and Apache), plus ACME certificate renewal. It does not rewrite application code or touch OT.
- It prepares a change pack your team can apply, or applies it over SSH only after a named approver on your side signs off.
- No change is applied without a rollback that has been tested first, and the endpoint is probed again afterwards to confirm the change took effect.
- Every change leaves a migration evidence record.
Evidence you can verify
Every CBOM a self-hosted KavachQ deployment produces is signed with ML-DSA-65 (NIST FIPS 204), as CycloneDX 1.7 by default. Anyone, whether an auditor, a regulator or a tender committee, can verify it offline against the signing key's published fingerprint, without contacting us or trusting our servers. In a self-hosted deployment that key is generated in your environment, so you publish its fingerprint; for evidence KavachQ signs itself, the fingerprint is on our signing trust anchor page. The QBOM, HBOM and AIBOM are signed the same way, and the BOM pack carries the full set in one signed pack.
The free scan
The free scan and the scan inside Aegis send the domain you enter to our scan API (api.kavachq.in), which performs a short series of read-only TLS handshakes against the public host. It needs no sign-in, and KavachQ stores no scan data. Only if you ask for the full report do the contact details you submit, with that scan's result, travel to us through our form provider. The free scan's CBOM is a preview and is not signed. The privacy notice has the detail.
This website
- Post-quantum in transit. kavachq.in negotiates the hybrid X25519MLKEM768 key exchange with browsers that support it. You can check with our own free scan.
- Strict headers. HTTPS is enforced with HSTS, and a Content-Security-Policy allows scripts only from this site, plus one hash-pinned inline script.
- No analytics. We do not run site analytics or advertising trackers.
- Few providers. Cloudflare hosts and delivers the site, Formspree handles contact forms, the scan API runs on Fly.io in the Mumbai region, fonts load from Google Fonts, and the flag images on the World Tracker load from flagcdn.com. The privacy notice explains what each receives.
Reporting a vulnerability
If you believe you have found a security vulnerability in kavachq.in, api.kavachq.in or KavachQ software, please tell us privately so we can fix it before it is disclosed. Do not test KavachQ deployments that you do not own or operate; report issues in the software itself to us.
- Email demo@kavachq.in with "Security report" in the subject.
- Include what you found, where, the steps to reproduce it and the impact you expect. Screenshots or a short proof of concept help.
- Give us a reasonable time to respond and fix the issue before you share it publicly.
We will acknowledge your report, keep you informed as we work on it and, if you wish, credit you once it is fixed. We do not run a paid bug bounty.
Please do not run denial-of-service or load tests, use social engineering or physical attacks, access or change data that is not yours, or test the services of our providers (Cloudflare, Formspree, Fly.io, Google). Use only the access you need to show the issue. If you reach personal data, stop, do not keep or share it, and tell us in your report.
Machine-readable contact details are in /.well-known/security.txt.