Google Cloud Targets 2029 to Be Quantum-Safe, and Here Is What That Means for You

Key points

• Google Cloud set a 2029 target in March 2025 to be ready for quantum computing threats, moving the deadline forward after faster-than-expected advances in quantum hardware.
• The biggest near-term risk is called "Store Now Decrypt Later": criminals collect encrypted data today and plan to crack it once quantum computers are powerful enough.
• Google's customer-facing API endpoints already use a new quantum-safe key-exchange standard approved by the US National Institute of Standards and Technology (NIST).
• Customers must take their own steps, including checking what encryption keys they hold and testing their software against Google's new quantum-safe settings.
• Legacy encryption algorithms are expected to be formally retired globally between 2030 and 2035.

Why does quantum computing threaten your data right now?

Quantum computers, machines that use physics rather than ordinary circuits to solve problems, are advancing faster than most experts predicted. They are not powerful enough yet to break today's encryption. The danger is that criminals are already collecting encrypted data today and will decode it later once the machines are ready. Security professionals call this "Store Now Decrypt Later."

For ordinary people, that means data from a medical record, a bank transfer, or a government form sent over the internet today could be readable by criminals in a decade. Google's new roadmap is built largely around closing that window.

What has Google actually done so far?

Several protections are already live. Google Cloud's main API endpoints, meaning the connection points that apps and services use to talk to Google, now use ML-KEM, a new key-exchange method that NIST standardised specifically to resist quantum attacks. Key exchange is the handshake that sets up a secure connection before any data moves.

Google is running ML-KEM in "hybrid mode", pairing it with the older method so that nothing breaks if there is a compatibility problem. Load balancers, which distribute web traffic across Google's servers, also support this quantum-safe handshake for TLS 1.3 (the current standard for encrypting web traffic), though customers must opt in to activate it.

Cloud KMS, Google's key management service where customers store and control their encryption keys, now supports the new NIST algorithms at general availability, meaning it is out of testing and open to all customers.

When does the rest happen?

What should customers do right now?

Google is clear that protecting its own infrastructure is its job. Protecting the software and keys customers run on top of that infrastructure is the customer's job.

Google recommends three starting steps: make an inventory of every encryption key and certificate your organisation holds; update developer tools and software libraries to versions that support the new quantum-safe standards; and test your existing applications against the quantum-safe APIs and load balancers Google has already switched on.

For individuals, there is no action needed today. But if you work in an organisation that stores sensitive records, now is a sensible time to ask your IT team whether they have a quantum-readiness plan.

Common questions

Will my passwords or accounts be at risk?

Not immediately. Quantum computers powerful enough to break current encryption do not exist yet, and Google's roadmap aims to have protections in place well before they do.

Does MFA (multi-factor authentication, which requires a second proof of identity like a code texted to your phone) help here?

MFA does not directly address quantum decryption risk, which targets encrypted data in transit or storage rather than login processes. It remains essential for account security, just for different reasons.