← All notes

Google's key preview tackles an awkward cloud trade-off

· re: Sovereign AI in Europe: New ways to control your AI stack (Google Cloud)

Editorial card about Google’s Confidential External Key Management preview, announced 18 November 2026. Customers or their local partner hold root keys outside Google Cloud; key operations run in a hardware-attested confidential computing environment. No measured cEKM latency results are given in the announcement. Footer: Test revocation. Test the outage behaviour.

Google’s new key-management preview is worth testing. It aims to reduce the delay and availability risks of sending key requests to an external system.

In its 18 November announcement, Google describes Confidential External Key Management (cEKM). Customers, or their chosen local partner, hold the root keys outside Google Cloud. Key operations run inside a hardware-attested confidential computing environment.

Google says the aim is to retain external key control while reducing those risks. (Procurement has enough round trips already.)

The catch is that this is a preview. The announcement gives no measured cEKM latency results or detail on what happens when its external key service becomes unavailable.

My read: this is a useful direction for sovereign AI procurement. I’d ask for a demonstration of revoking access and the behaviour during an outage before treating it as a solved problem.