Google Cloud Will Turn On Post-Quantum Encryption by Default Starting October 2026
Dr. Abeer Alshammari · Published 7/29/2026
Executive View
Google Cloud will begin enabling post-quantum key exchange by default on load balancers starting October 2026, using the hybrid X25519MLKEM768 algorithm for TLS 1.3 connections. Organizations can opt out during a one-year transition window (October 2026-2027); after that, the default becomes standard with no opt-out. Decision required: inventory which Google Cloud load balancers have explicit SSL policies today, since only those without one, or without a post-quantum setting specified, are affected by the default change.
Google Cloud confirmed a phased, dated rollout: no default change until October 2026; enabled-by-default with opt-out from October 2026 to October 2027; enabled-by-default with no opt-out after October 2027.
What happened
Google Cloud announced that Cloud Load Balancing will begin enabling post-quantum key exchange by default starting October 2026. This affects load balancers that either have no SSL policy attached, or use an SSL policy that doesn't specify a post-quantum key exchange setting. Where enabled, the load balancer negotiates post-quantum key exchange with clients supporting TLS 1.3 and the hybrid X25519MLKEM768 algorithm -- combining a classical elliptic-curve algorithm with a post-quantum one, so the connection remains secure even if one of the two is eventually broken.
Do I need to act now
Not urgently, but you do need to know your exposure. If your Google Cloud load balancers have an explicit SSL policy with a defined key-exchange setting, this change doesn't affect you automatically. If they don't, your traffic will start using post-quantum key exchange by default starting October 2026, whether or not you've explicitly planned for it.
What should I inventory
- Every Google Cloud load balancer and whether it has an explicit SSL policy attached
- Whether existing SSL policies specify a post-quantum key exchange setting or leave it unset
- Any client systems that connect to your load balancers and might not support TLS 1.3 or hybrid key exchange -- test for compatibility before October 2026
- Whether your organization has a broader PQC migration inventory already underway that this should feed into, rather than being handled as a one-off Google Cloud task
What should I migrate
If you want to control the timing rather than accept the October 2026 default, explicitly set your SSL policy's key-exchange setting now, either to opt in early (to start testing) or to defer for the one-year transition window while you validate client compatibility.
What can wait
Full organizational crypto-agility planning (beyond this one Google Cloud setting) does not need to be rushed for this specific change, since Google's phased rollout already provides a full year of opt-out flexibility after the October 2026 default shift. Use that window for broader PQC inventory work rather than treating this as an emergency deadline.
Governance impact
This is a useful, concrete forcing function: it's a real vendor-set deadline with a defined default-change date, which is rarer in post-quantum migration guidance than abstract "prepare for the quantum threat" advisories. Organizations can use it to test whether their crypto-asset inventory process actually works end-to-end on a real deadline.
Sources
Google Cloud official Post-Quantum TLS documentation and Load Balancing release notes.
The decision worth making now isn't about this one setting -- it's about whether your organization has any process at all for tracking vendor-driven cryptographic defaults as they roll out across your cloud footprint. Google publishing a dated, phased default change is a preview of what PQC migration will look like broadly: gradual, vendor-paced, and easy to miss if nobody owns tracking it.
GCC financial-services and government organizations modernizing cryptographic infrastructure, including those on Google Cloud, should treat this as a concrete, dated milestone to fold into existing PQC-readiness planning rather than a US/global-only announcement.