Cloudflare Launches Post-Quantum GeoKey Manager Beta
Cloudflare transitions GeoKey Manager to hybrid post-quantum encryption, prioritizing data sovereignty and quantum-resistant security.
1Transitioning to Post-Quantum Security
Cloudflare has initiated a closed beta for its redesigned GeoKey Manager, replacing previous attribute-based encryption with a hybrid post-quantum approach. This update utilizes ML-KEM-768 and X25519 to secure geographically fenced decryption keys. The move addresses long-term threats like harvest-now-decrypt-later attacks while ensuring compliance with evolving global data sovereignty requirements for plaintext processing.
2Abandoning Attribute-Based Encryption
The company decided to drop its 2022 ciphertext-policy attribute-based encryption scheme due to the lack of production-ready post-quantum variants. Additionally, customer feedback indicated that the extensive regional granularity provided by the old system was unnecessary. The new architecture simplifies key management by focusing on regional root keys and application-specific key pairs.
3Hybrid Encryption Architecture Details
Key protection now relies on HPKE as defined in RFC 9180. The system employs a key encapsulation mechanism combining ML-KEM-768 with X25519, alongside HKDF-SHA-256 and AES-256-GCM. By moving away from complex policy expressions, the design ensures that application keys are derived from regional root secrets, enhancing overall security posture and operational predictability.
4Rigorous Edge Server Authentication
Before receiving a regional root key, edge servers must pass three distinct validation checks. This includes TPM hardware identity verification, a lookup in the Zinc inventory system to map location, and authorization from the provisioning service. Keys are loaded directly into the kernel keyring rather than disk, ensuring they remain volatile and secure.
5Epoch-Based Rotation Mechanism
To manage key rotation without causing service downtime, Cloudflare introduced an epoch-based model. Soft rotations allow for overlapping epochs, ensuring continuity during transitions. Conversely, hard rotations rewrap affected keys under a new epoch and revoke access to previous ones. This mechanism addresses concerns regarding the operational impact of frequent key updates.
6Operational Risks and Fail-Closed Design
The design explicitly adopts a fail-closed approach, meaning any failure in service context, region, or epoch validation results in a request rejection. If a key is missing or malformed, the service will not start. While this ensures strict security, it introduces the risk of regional service outages if provisioning or synchronization processes fail.
7Trust Boundaries and Data Storage
The trust boundary encompasses the key-management, provisioning, and authorized edge key services. Quicksilver, the globally replicated key-value store, remains outside this boundary because it only handles wrapped keys and metadata. This separation ensures that even if the replication layer is compromised, the underlying root keys remain protected within the secure provisioning environment.
8Broader Post-Quantum Strategy
This beta represents a continuation of Cloudflare's broader post-quantum roadmap, following the adoption of hybrid ML-KEM for IPsec services. With plans for a quantum-safe certificate authority, the company is systematically hardening its infrastructure. The beta will ultimately determine if the strict fail-closed design is acceptable to customers operating at a massive regional scale.
Original article: InfoQ — Cloudflare Launches Post-Quantum GeoKey Manager Beta