Bringing post-quantum cryptography to geographically fenced key management
Web page · https://blog.cloudflare.com/post-quantum-geo-key-manager
Cloudflare's new post-quantum GeoKey Manager protects geographically fenced decryption keys from harvest now, decrypt later attacks. Learn how we redesigned our cryptography stack to support strict data sovereignty in a post-quantum world.
First seen by Oriel on .
AI summary
Cloudflare launched a closed beta of a post-quantum GeoKey Manager that restricts where customer private keys can be unwrapped, supporting data sovereignty while protecting against harvest-now, decrypt-later attacks.
- The design combines ML-KEM-768 and X25519, deriving service- and region-specific application key pairs from 256-bit regional root keys.
- Wrapped private keys and metadata are distributed globally through Quicksilver, while a separate provisioning service delivers regional root keys only to authorized edge servers.
- Server authorization uses TPM-backed identity, Zinc location records, and regional configuration; root keys are held in the Linux kernel keyring rather than persisted on disk.
- The system fails closed: missing keys or failed service, region, or epoch checks cause startup or requests to be rejected, trading availability for regional enforcement.
- Soft rotation retains limited previous epochs during transitions; hard rotation rewraps affected keys so access to the prior epoch can be removed. General availability is planned for Q1 2027.
#post-quantum cryptography #ml-kem #key management #data sovereignty
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| Cloudflare Blog | 01M5MYFG0SHDEYME96N0A4Z6PH | https://blog.cloudflare.com/post-quantum-geo-key-manager/ Read discussion |