Cloudflare’s Post-Quantum GeoKey Manager Keeps Key Unwrapping Region-Bound
- Cargo
- Machine Learning
- Shipped
- Shipper
- Chetan Agrawal
- Readers
- 848
Cloudflare’s closed-beta service pairs hybrid post-quantum key wrapping with regional controls, while failing closed when keys or location checks are missing.

Cloudflare’s new GeoKey Manager is designed to let customer data travel across a global network while keeping the ability to decrypt it tied to an approved region. The service, now in closed beta as part of the Data Localization Suite, wraps customer decryption keys so only authorized Cloudflare servers in the selected geography can unwrap and use them. General availability is planned for Q1 2027.
The design combines that geographic boundary with hybrid post-quantum cryptography. That matters for data whose confidentiality needs to last years or decades: an attacker could store conventionally encrypted data now and try to decrypt it later, once quantum computers can break the public-key cryptography protecting it. Cloudflare’s approach aims to protect key material against that “harvest now, decrypt later” scenario while restricting where keys can be used.
GeoKey Manager is one part of a larger data-localization system. It controls where protected keys can be unwrapped. Separate Cloudflare systems determine where tunnels end, where traffic is inspected and routed, and where plaintext is processed. Those controls depend on the key boundary: TLS traffic can only be decrypted in a location where the corresponding private key is available.
From fixed locations to post-quantum key wrapping
Cloudflare introduced its original GeoKey Manager in 2017 to restrict where private TLS keys could be unwrapped on its anycast network. A customer could, for example, choose India, so requests would be decrypted by Cloudflare’s India network rather than anywhere on the global network.
In 2022, Cloudflare moved to ciphertext policy attribute-based encryption, or ABE. That approach represented location requirements through attributes such as “region = European Union” or “region = Canada + United States + Mexico.” It could give newly authorized servers matching decryption capabilities without requiring every customer key to be wrapped again.
The new post-quantum version uses a simpler structure. Cloudflare says no production-ready post-quantum ABE scheme is available, and customers generally don’t need a large number of geographic regions. Instead, a symmetric regional root key is tied to a region, and Cloudflare derives application-specific key pairs from it for individual services such as Gateway or Tunnel.
The key-wrapping path combines ML-KEM-768 and X25519. ML-KEM-768 is a NIST standard. In Cloudflare’s Cloudflare One implementation, the combination is used within Hybrid Public Key Encryption (HPKE), alongside HKDF-SHA-256 for key derivation and AES-256-GCM for authenticated encryption. The hybrid construction is intended to retain confidentiality if at least one of the post-quantum and classical components remains secure.
Global distribution, regional access
Cloudflare distributes wrapped customer keys and their metadata across its network using Quicksilver, its global configuration system. Those wrapped keys can be present globally, but they cannot be used without the matching regional root key and service context. Root keys follow a separate path: a provisioning service stores them in an on-premises Vault system and delivers them only to authorized edge servers.
This separation is central to the security model. A wrapped key can be broadly replicated to support availability, while the secret needed to unwrap it remains limited to servers assigned to the relevant region. A server’s regional configuration determines which root keys it may receive.
Each wrapped customer key carries metadata for three attributes: the Cloudflare service that will use it, the permitted regional boundary, and the root-key epoch. An epoch identifies a generation of a regional root key; each rotation creates a new one. A regional boundary can refer to a country such as Germany or a broader area such as the European Union.
For example, Acme Co. could have one Germany-bound key for Tunnel and another for Gateway. Road Runner Inc. could have a Germany-bound Tunnel key and a European Union-bound Gateway key. Keys sharing the same service, region and epoch use the same application-specific key pair. A compromise of the Tunnel-Germany application private key could therefore expose keys for Tunnel in Germany across customers, but not their Gateway keys. A compromise of the Germany root key could affect every application key derived from that root for the same epoch.
For each customer key, the key-management service uses the requested region to find the relevant root key and current epoch. It derives the corresponding application-specific key pair, then uses the public component to wrap the customer’s private key material. The wrapped key and its metadata are sent through Quicksilver. Although the wrapped material is globally distributed, unwrapping still requires the appropriate regional root key.
How servers receive regional root keys
Before an edge server can retrieve a root key, the provisioning service checks three inputs. A Trusted Platform Module (TPM) establishes the server’s registered hardware identity. Zinc, Cloudflare’s server inventory system, maps that identity to a data center and location. The provisioning service then determines which regional root keys that location is authorized to access.
Zinc’s membership records change as servers are added, maintained or decommissioned. When Cloudflare changes which data centers count as part of a region, that information is propagated through Quicksilver so the network can update its regional assignments. TPM-backed identity, inventory records and regional configuration together determine which keys a server can request. Cloudflare says the location mapping also supports FIPS 140-3 compliance.
Each edge server contacts the provisioning service with its registered hardware identity. After checking that identity and the server’s regional membership, the service issues a token that permits retrieval of only the root keys authorized for that location. The server loads those keys into the Linux kernel keyring rather than storing them on disk. Process-level access controls limit which services can use them.
The keys are volatile: a machine restart removes them, and the server must authenticate and retrieve them again. That adds a provisioning step during recovery, but reduces the amount of persistent key material on a server. The edge key service uses in-memory copies after startup.
Fail-closed behavior and key rotation
Cloudflare’s edge key service checks at startup that every regional root key required by its configuration is present. If a key is missing or malformed, the service does not start. It also rejects an individual request if the request’s metadata identifies a region whose root key is not available locally. A Germany-bound request reaching a server in Spain or France, for instance, cannot be decrypted there because those locations do not have Germany’s root key.
This is a deliberate fail-closed policy: when a required check fails, the request is rejected instead of allowing a key to be unwrapped outside its approved region. The checks include service context, location and epoch. In practice, an edge server handles requests for a region only after its configuration and key provisioning are complete.
Cloudflare describes two rotation modes. A soft rotation creates a new root-key epoch while keeping controlled access to a limited number of earlier epochs. New customer keys are wrapped using the newest epoch, while existing wrapped keys can remain usable during a transition. This can preserve service continuity while customers move to new key material.
A hard rotation rewraps affected customer keys under a replacement epoch so access to the old epoch can be removed. The choice changes the balance between transition flexibility and retiring older key material. The system’s epoch metadata lets the service identify which generation is required for each wrapped key.
Trust boundaries and day-to-day operation
The services that can access regional root keys form GeoKey Manager’s trust boundary: the key-management service derives application keys, the provisioning service stores and distributes roots, and authorized edge key services use local copies. Quicksilver sits outside that boundary because it receives wrapped customer keys and metadata, not regional root keys.
Regional membership also changes as Cloudflare’s network changes. The provisioning layer refreshes the list of servers belonging to each region several times a day, independently of key rotation and without requiring customer action. When membership changes, the service synchronizes the server’s kernel keyring with its newly authorized root keys. The edge key service caches keys in process memory until it restarts or the cache expires, then reloads the current authorized set.
The approach offers a clear operational tradeoff: global replication supports network availability, while separate provisioning and local key checks constrain decryption. Its protection depends on the accuracy of server identity and regional inventory, as well as the security of the services inside the root-key trust boundary. Fail-closed checks reduce the chance that missing configuration silently broadens access, but can make a provisioning problem visible as rejected requests or a service that will not start.
Cloudflare One and CDN plans
Cloudflare says GeoKey Manager will underpin an improved Regional Services offering for Cloudflare One, with details expected in a few months. The company already has geographic controls for private keys associated with CDN certificates through earlier GeoKey Manager versions. A separate integration is in development to bring the new post-quantum system to that CDN capability; Cloudflare says testing and transition details will follow when ready.
Current Data Localization Suite customers regionalizing CDN traffic can register interest in testing the feature before general availability through Cloudflare’s test registration form. For teams assessing the closed beta, the practical questions are which regions and products are supported for their workflow, how rotation will fit their key lifecycle, and how their services should handle a fail-closed provisioning or configuration error.