<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo" -->

---
title: PQC in Plaintext: Google Cloud’s post-quantum...
description: Google Cloud has published its updated roadmap to achieve full post-quantum cryptography (PQC) readiness by 2029, aligned with NIST and NSA CNSA 2.0 standards....
canonical: https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap | daily.dev
og:description: Google Cloud has published its updated roadmap to achieve full post-quantum cryptography (PQC) readiness by 2029, aligned with NIST and NSA CNSA 2.0 standards....
og:url: https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo
og:image: https://api.daily.dev/og/posts/BMTTgmGmO.png
og:image:alt: PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap

**[Google Cloud](https://daily.dev/sources/gcp)** · 9 min read · 0 upvotes · 0 comments

## Summary

Google Cloud has published its updated roadmap to achieve full post-quantum cryptography (PQC) readiness by 2029, aligned with NIST and NSA CNSA 2.0 standards. The strategy addresses three domains: mitigating Store Now Decrypt Later (SNDL) risks, ensuring integrity against forgery, and building cryptographic agility. Current 2026 milestones include ML-KEM (FIPS 203) hybrid key exchange on all googleapis.com endpoints, PQC support on Application and proxy load balancers via X25519MLKEM768 for TLS 1.3, and general availability of NIST PQC algorithms (ML-KEM, ML-DSA, SLH-DSA) in Cloud KMS. Domain 1 (SNDL mitigation) targets 2027, while Domains 2 (integrity/PKI) and 3 (key management foundations) target 2028. Hardware-backed roots of trust including Caliptra v2.1, TPM 2.0 v185, and OpenTitan are part of the infrastructure transition. Customers are advised to inventory cryptographic assets, update SDKs and libraries to PQC-capable versions, and validate applications against quantum-safe APIs and load balancers.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://cloud.google.com/blog/products/identity-security/pqc-in-plaintext-google-clouds-post-quantum-cryptography-roadmap>

## Questions this post answers

### What PQC algorithms does Google Cloud KMS support and are they generally available?

Google Cloud KMS has reached general availability for three NIST-standardized PQC algorithms: ML-KEM (key encapsulation), ML-DSA (lattice-based signatures), and SLH-DSA (hash-based signatures). These cover both encryption/key exchange and digital signing use cases. Quantum-safe key import is still being enabled as a follow-on step.

_Teams migrating key management infrastructure to PQC track algorithm availability and KMS changes on daily.dev._

### What TLS cipher suite does Google Cloud load balancer use for post-quantum key exchange?

Google Cloud Application and proxy load balancers support X25519MLKEM768 for quantum-safe hybrid key exchange over TLS 1.3. This is initially available on an opt-in basis so customers can validate compatibility before it becomes the default, minimizing disruption to existing applications.

_Engineers enabling PQC on their load balancers find the latest rollout details and community experience on daily.dev._

### When will Google Cloud deprecate classical cryptography and complete its PQC migration?

Google Cloud targets full PQC readiness by 2029, with SNDL mitigations (TLS, VPN, data pipelines) completing by 2027 and integrity/PKI plus key management foundations completing by 2028. Efforts will continue into the 2030s to align with NIST IR 8547 and CNSA 2.0, which anticipate final deprecation of quantum-vulnerable algorithms between 2030 and 2035.

_Security teams planning compliance timelines around PQC deprecation deadlines follow the evolving standards landscape on daily.dev._

## Similar posts on daily.dev

- [Post-Quantum Cryptography in Confluent Cloud](https://daily.dev/posts/post-quantum-cryptography-in-confluent-cloud-ahlwlhfq8) · Confluent Blog · 0 upvotes · 0 comments
- [The State of Post-Quantum Cryptography](https://daily.dev/posts/the-state-of-post-quantum-cryptography-hjfyungt7) · Feisty Duck · 0 upvotes · 0 comments
- [Google bumps up Q Day deadline to 2029, far sooner than previously thought](https://daily.dev/posts/google-bumps-up-q-day-deadline-to-2029-far-sooner-than-previously-thought-egi6cpldo) · Ars Technica · 0 upvotes · 0 comments
- [PQC roadmap remains hazy as vendors race for early advantage](https://daily.dev/posts/pqc-roadmap-remains-hazy-as-vendors-race-for-early-advantage-gp8vfiiph) · CSO Online · 0 upvotes · 0 comments

---

Tags: [#quantum-computing](https://daily.dev/tags/quantum-computing), [#gcp](https://daily.dev/tags/gcp)

[View this post on daily.dev](https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap","url":"https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo"},"datePublished":"2026-08-11T16:12:35.117Z","dateModified":"2026-08-24T06:50:43.595Z","description":"Google Cloud has published its updated roadmap to achieve full post-quantum cryptography (PQC) readiness by 2029, aligned with NIST and NSA CNSA 2.0 standards....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b559a17bb032216a7853ac1742b2da5b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b559a17bb032216a7853ac1742b2da5b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Google Cloud","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Google Cloud","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/gcp","url":"https://daily.dev/sources/gcp"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"quantum-computing,gcp","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Google Cloud","item":"https://daily.dev/sources/gcp"},{"@type":"ListItem","position":3,"name":"PQC in Plaintext: Google Cloud’s post-quantum cryptography roadmap"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/pqc-in-plaintext-google-cloud-s-post-quantum-cryptography-roadmap-bmttgmgmo#faq","mainEntity":[{"@type":"Question","name":"What PQC algorithms does Google Cloud KMS support and are they generally available?","acceptedAnswer":{"@type":"Answer","text":"Google Cloud KMS has reached general availability for three NIST-standardized PQC algorithms: ML-KEM (key encapsulation), ML-DSA (lattice-based signatures), and SLH-DSA (hash-based signatures). These cover both encryption/key exchange and digital signing use cases. Quantum-safe key import is still being enabled as a follow-on step. Teams migrating key management infrastructure to PQC track algorithm availability and KMS changes on daily.dev."}},{"@type":"Question","name":"What TLS cipher suite does Google Cloud load balancer use for post-quantum key exchange?","acceptedAnswer":{"@type":"Answer","text":"Google Cloud Application and proxy load balancers support X25519MLKEM768 for quantum-safe hybrid key exchange over TLS 1.3. This is initially available on an opt-in basis so customers can validate compatibility before it becomes the default, minimizing disruption to existing applications. Engineers enabling PQC on their load balancers find the latest rollout details and community experience on daily.dev."}},{"@type":"Question","name":"When will Google Cloud deprecate classical cryptography and complete its PQC migration?","acceptedAnswer":{"@type":"Answer","text":"Google Cloud targets full PQC readiness by 2029, with SNDL mitigations (TLS, VPN, data pipelines) completing by 2027 and integrity/PKI plus key management foundations completing by 2028. Efforts will continue into the 2030s to align with NIST IR 8547 and CNSA 2.0, which anticipate final deprecation of quantum-vulnerable algorithms between 2030 and 2035. Security teams planning compliance timelines around PQC deprecation deadlines follow the evolving standards landscape on daily.dev."}}]}
```

