TL;DR
Google Cloud published an updated post-quantum cryptography (PQC) migration plan in August 2026, adding new detail to the 2029 target Google first announced in March.
The update shows a transition already underway, with milestones spanning encryption, digital signatures, authentication, key management, and hardware. Some changes are targeted for 2027 and 2028, leading toward overall PQC readiness in 2029. Hardware transitions may continue beyond that date.
For enterprises, the update highlights a broader challenge: PQC migration does not happen on a single timeline. Cloud infrastructure, customer applications, physical hardware, and third-party technologies can each move at different speeds.
Google’s August PQC Update Adds Detail to the 2029 Target
Google first announced its 2029 PQC migration target in March 2026. The August Google Cloud update provides a clearer picture of how the company expects to reach it.
Protection against Store Now, Decrypt Later (SNDL) risks is targeted for 2027. Work involving digital signatures, certificates, identity, and access is targeted largely for completion by the end of 2028. Key management and hardware-backed cryptographic services also have milestones extending through 2028.
These efforts are expected to converge in 2029, when Google Cloud plans to reach overall PQC readiness.
The timeline illustrates an important characteristic of PQC migration. A target year may be singular, but the migration itself consists of multiple technology transitions that begin years earlier.
PQC Migration Goes Beyond Encryption
Protecting encrypted information from future quantum attacks remains an early priority. Google Cloud already supports hybrid post-quantum key exchange using the NIST-standardized ML-KEM in parts of its infrastructure and services.
The August update, however, also places significant emphasis on integrity and authentication.
Public-key cryptography supports digital signatures, certificates, software verification, identity systems, and access mechanisms. A future cryptographically relevant quantum computer could therefore affect more than data confidentiality.
Google’s migration plans extend into these areas, with work involving quantum-safe certificates, software supply chain protections, identity and access, and other authentication mechanisms.
This expands the scope of PQC migration. Protecting data in transit is one challenge. Transitioning signatures, certificates, and authentication mechanisms introduces different standards, dependencies, and implementation requirements.
Google's PQC migration is underway
Parts of Google’s transition have already reached production.
Google Cloud has deployed quantum-safe key exchange for API endpoints and made the NIST-standardized ML-KEM, ML-DSA, and SLH-DSA algorithms available through Cloud KMS. Elsewhere in the Google ecosystem, Chrome has deployed post-quantum protections and Android 17 is integrating ML-DSA digital signature protection.
These developments represent only part of a broader transition.
Google is also working on the cryptographic infrastructure behind its services, including key management, identity systems, certificate authorities, and hardware-backed cryptographic capabilities.
Crypto-agility is central to this strategy. Rather than treating PQC as a one-time replacement of existing algorithms, crypto-agility focuses on the ability to adapt cryptographic mechanisms as standards and requirements change.
That distinction matters for enterprises as well. PQC introduces a new migration requirement, but it is unlikely to be the last time organizations need to change the cryptography embedded across their environments.
Customer Systems Have Their Own PQC Migration Timeline
One of the most relevant parts of Google Cloud’s August update is what happens outside Google’s own infrastructure.
Under the shared responsibility model, Google is responsible for transitioning the cryptography protecting its underlying cloud infrastructure. Customers remain responsible for cryptography implemented within their own applications and workloads.
That can require changes to client software, asymmetric keys, configurations, security policies, and other application-level components.
Third-party dependencies introduce another constraint. Applications frequently rely on external software, libraries, hardware, protocols, and services. Even when one system is ready to migrate, another dependent component may not yet support PQC.
This creates overlapping migration timelines.
Cloud providers can transition their infrastructure. Technology suppliers can update their products. Organizations still need to understand which cryptographic mechanisms exist within their own environments and which systems depend on them.
PQC readiness therefore depends partly on visibility: knowing where cryptography is used, how it is being used, and what needs to change.
Some PQC Transitions Will Extend Beyond 2029
Hardware makes the timeline more complicated.
Software can often be updated incrementally. Cryptographic functionality tied to physical infrastructure may require firmware changes, new components, or equipment replacement.
Google Cloud expects to use both active replacement and normal equipment replacement cycles as part of its hardware transition. Some physical components may therefore continue moving toward PQC after 2029.
The same issue can appear in enterprise environments.
Systems do not share identical lifecycles. Some can be updated quickly, while others may depend on hardware replacement, vendor support, or technologies that cannot immediately migrate.
A PQC migration plan therefore has to account for more than the final deadline. It also needs to identify which systems can move first, which depend on other technologies, and where transitional approaches may be required.
What Google’s August Update Shows Enterprises
NIST finalized its first three PQC standards in 2024 and recommends that organizations begin migration. Current NIST transition planning anticipates the deprecation of quantum-vulnerable algorithms after 2030 and their eventual removal from relevant NIST standards by 2035, with higher-risk systems moving earlier.
Google is targeting PQC readiness well ahead of that endpoint.
The August update shows what sits behind such a target. Encryption, authentication, certificates, key management, hardware, customer applications, and external dependencies do not all transition together.
Google recommends that customers begin by identifying their cryptographic resources, updating software to support PQC, and validating applications against quantum-safe services.
For enterprises, that may be the more important message behind the 2029 date.
PQC migration starts with understanding the existing cryptographic environment. From there, organizations can determine what needs to migrate, where dependencies exist, and how different systems can transition over time.
A migration deadline can be set centrally. The actual migration still has to happen wherever the cryptography resides.
Sources
- Google Cloud, “PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap,” August 11, 2026.
https://cloud.google.com/blog/products/identity-security/pqc-in-plaintext-google-clouds-post-quantum-cryptography-roadmap - Google, “Quantum frontiers may be closer than they appear,” March 25, 2026.
https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/ - National Institute of Standards and Technology (NIST), “Post-Quantum Cryptography.”
https://csrc.nist.gov/projects/post-quantum-cryptography/
About CeQureX
CeQureX (CQX) helps organizations prepare for and manage the transition to post-quantum cryptography. The CQX Wave Series supports the PQC journey from cryptographic visibility and assessment through migration and ongoing cryptographic management.