Google Cloud has established an aggressive roadmap to migrate its entire infrastructure and customer-facing products to post-quantum cryptography by 2029, a timeline that significantly outpaces traditional government and industry projections, according to company announcements. The initiative aims to protect critical data, digital signatures, and authentication systems against future quantum computers capable of breaking conventional cryptographic methods. The plan involves a phased approach across multiple security domains, setting strict deadlines for mitigation strategies like addressing “Store Now, Decrypt Later” risks.
Store Now, Decrypt Later Mitigation by 2027
To counter threats where malicious actors capture encrypted traffic today to decode it once quantum systems mature, Google Cloud targets the end of 2027 for its first major milestone domain. According to company documents, this phase encompasses core infrastructure services including Cloud VPN, Cloud Interconnect, GCE OS Login, Cloud SDK, gCloud CLI, GKE service mesh, and client libraries. Additionally, data pipeline tools such as the Cloud Storage SDK, Storage Transfer Service, BigQuery CLI, and Data Transfer Service are included in this rollout.
As an immediate operational step, Google Cloud API endpoints now support quantum-safe key exchange for incoming traffic across properties like google.com and googleapis.com. This deployment utilizes the NIST-standardized ML-KEM algorithm operating in hybrid mode. Furthermore, application and proxy load balancers support hybrid key exchange for TLS 1.3 on an opt-in basis, allowing enterprise users to test handshakes ahead of broader production deployments.
Software Supply Chain and Integrity Targets for 2028
The second major domain focuses on integrity and non-repudiation, targeting completion by the end of 2028. According to Google Cloud, this stage addresses digital signatures, software supply chain controls, certificate systems, and identity services to prevent credential forgery and software tampering. Certificate migration strategies will align with ongoing developments at the Internet Engineering Task Force (IETF).
Google Cloud has participated in experiments involving Merkle Tree Certificates to manage larger signature sizes associated with post-quantum schemes. Chrome and Cloudflare have similarly explored these signature management techniques. Moreover, Cloud KMS generally provides NIST-standardized post-quantum algorithms—including ML-KEM, ML-DSA, and SLH-DSA—for standard encryption and signing keys.
Industry Implications and Accelerated Timelines
Google Cloud’s 2029 deadline marks a notable shift from conventional government and defense planning horizons, which typically target full quantum readiness between 2030 and 2033. Brian LaMacchia, a cryptography engineer who led Microsoft’s post-quantum transition between 2015 and 2022 and currently works at Farcaster Consulting Group, noted in an interview with Ars Technica that Google’s schedule represents a significant acceleration over standard public transition timelines. While Google did not detail specific catalysts for the tightened timeline, company researchers previously published findings suggesting that a 2,048-bit RSA key could be broken in under a week by a quantum computer holding one million noisy qubits.
Pro Tip: Organizations preparing for post-quantum migrations should begin by conducting a comprehensive inventory of their cryptographic assets, updating developer toolsets, and validating application behavior against quantum-safe APIs, as recommended by Google Cloud.
Shared Responsibility Model for Cloud Customers
Google Cloud frames the transition as a shared responsibility framework between the provider and its users. While Google handles foundational infrastructure security—such as global front ends, server hardware, transport protocols, and internal networks—customers retain direct responsibility for managing their own client software, application code, service configurations, and key lifecycles.
To prepare internal environments, Google Cloud advises customers to follow a three-step path: inventory existing cryptographic dependencies, update software used by development and site reliability engineering teams, and test application behavior against available quantum-safe endpoints and load balancers.
Frequently Asked Questions
What is post-quantum cryptography?
Post-quantum cryptography refers to cryptographic algorithms designed to be secure against attacks conducted by quantum computers, which could potentially break widely used asymmetric encryption standards like RSA and ECC.
When does Google Cloud expect to complete its PQC migration?
According to Google Cloud, the company plans to achieve full post-quantum cryptography readiness across its infrastructure and services by 2029.
What are Store Now, Decrypt Later attacks?
Store Now, Decrypt Later attacks involve adversaries intercepting and storing encrypted network traffic today with the intention of decrypting it in the future once practical, cryptographically relevant quantum computers become available.
How can cloud customers start testing post-quantum encryption?
Customers can test post-quantum mechanisms today by utilizing hybrid key exchange on supported API endpoints and opt-in TLS 1.3 application and proxy load balancers, alongside using NIST-standardized algorithms available in Cloud KMS.
Stay Updated on Enterprise Security
Subscribe to our newsletter for the latest updates on cloud infrastructure developments, cryptographic standardizations, and enterprise security strategies.
Worth a look