01 · ProtectRecorded traffic stays private
With hybrid key exchange, a session captured today cannot be decrypted by a future quantum computer.
02 · KeepNo client is cut off
Clients without ML-KEM connect as they do now. Turning the gateway on is not a compatibility event.
03 · ControlIt runs on your side
The gateway sends KavachQ a status heartbeat only. That heartbeat carries no application addresses and no certificate or key material, and a KavachQ outage does not affect your traffic.
04 · CheckObserved, signed, yours to keep
Only a hybrid handshake that KavachQ observed on the wire counts as protected. Each check leaves a signed record an auditor can verify without access to KavachQ.
What this does not claim
- It protects the key exchange. The certificate stays RSA or ECDSA, so authentication is a separate migration step.
- The signed record covers the key exchange on the public endpoint at the time of the check, and nothing else.
- It covers the hop from the client to the gateway. The hop from the gateway to the application uses whatever the application speaks.
- The outside check works on public endpoints. A gateway on a private address cannot be checked from KavachQ today.
- It is not a VPN, a CDN or a web application firewall.