<>

Google Cloud Sets 2029 Roadmap for Quantum-Safe Shift

Google Cloud has established an aggressive 2029 roadmap for a full post-quantum cryptography migration across its infrastructure, tightening public industry timelines by several years. According to a blog post by Heather Adkins, vice president of security engineering, and Sophie Schmieg, senior cryptography engineer, the initiative aims to protect enterprise data and cloud architecture against future cryptographically relevant quantum computers before current asymmetric encryption standards fail.

Decoding the 2029 Timeline Acceleration

The decision to target 2029 surprised many cryptographic experts who had aligned their deployment schedules with guidelines from defense agencies and government frameworks. Brian LaMacchia, a cryptography engineer who led Microsoft’s post-quantum transition between 2015 and 2022 and now works at Farcaster Consulting Group, noted in an interview with Ars Technica that Google’s schedule significantly compresses public transition timelines. While Google did not detail specific catalysts for the tighter deadline, research published last year by Google scientists led by Craig Gidney suggested that a 2,048-bit RSA key could be broken in under a week using a quantum computer featuring one million noisy qubits. That projection drastically reduced older estimates that required roughly 20 million qubits, shifting the engineering calculus for enterprise platforms.

Domain-by-Domain Cloud Migration Strategy

According to Google Cloud’s published architecture docs on Google Cloud Blog, the migration is partitioned into distinct risk domains. Domain one addresses Store Now, Decrypt Later (SNDL) vulnerabilities, where adversaries capture encrypted traffic today to decrypt it once a viable quantum machine arrives. Google Cloud is deploying quantum-confidential TLS 1.3 handshakes for customer load balancers, alongside quantum-safe transport for admin pathways like Cloud VPN and Cloud Interconnect by 2027.

Domain two targets integrity and non-repudiation, focusing on software supply chain security and public key infrastructure (PKI). Google is integrating ML-DSA and SLH-DSA certificates into internal and external certificate authorities. Implementing these pure post-quantum algorithms introduces large signature sizes that can impact certificate chain validation performance. To handle this, Google is experimenting with Merkle Tree Certificates for Web PKI, ensuring that identity verification remains performant under heavier cryptographic loads.

Android 17 and Hardware Root of Trust Integration

Beyond server infrastructure, Google outlined a comprehensive plan to make the Android ecosystem quantum-resistant. Starting with the Android 17 beta release, the company is adding support for ML-DSA—a digital signature algorithm standardized by the National Institute of Standards and Technology (NIST)—into Android’s hardware root of trust. ML-DSA has already been added to the Android Verified Boot library to secure the operating system startup sequence against tampering.

Subsequent updates will push ML-DSA support into remote attestation, the Android Keystore for on-device key generation, and eventually the Play Store app-signing infrastructure.

Future-Proofing Enterprise Architecture

Google’s aggressive timeline signals that the transition from classical cryptography to post-quantum standards is no longer a distant theoretical exercise. Organizations failing to audit their cryptographic posture risk exposing long-lived intellectual property to retroactive decryption.

>