[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fMv1Phfv82FTQxJejwi3JrIYtagX_TjtjypELBnrnQLI":3},{"article":4,"iocs":54},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"full_text":11,"url":12,"image_url":13,"published_at":14,"ingested_at":15,"relevance_score":16,"entities":17,"category_id":31,"category":32,"article_tags":36},"d1e70f10-14fe-462e-a87f-31660f0c0c8f","Google Cloud Sets Out Post-Quantum Roadmap With 2029 Readiness Goal","google-cloud-sets-out-post-quantum-roadmap-with-2029-readiness-goal-b67e79","Google Cloud outlines its roadmap to full post-quantum cryptography readiness, with key milestones targeted for 2027 and 2028. The post Google Cloud Sets Out Post-Quantum Roadmap With 2029 Readiness Goal appeared first on SecurityWeek.","Google Cloud has updated its roadmap to transition its infrastructure to post-quantum cryptography (PQC) by 2029, driven by rapid advancements in quantum hardware. The plan focuses on mitigating 'Store Now Decrypt Later' risks, enhancing digital signatures, and building cryptographic agility. Key milestones include hybrid key exchange for APIs and load balancers, and general availability of PQC algorithms in Cloud KMS.","Google Cloud outlines its post-quantum cryptography readiness roadmap, targeting 2029.","Google Cloud has published an updated roadmap for migrating its infrastructure to post-quantum cryptography (PQC), targeting full readiness by 2029, with some work expected to continue into the next decade. In March, Google announced it was moving up its timeline for transitioning to PQC, setting a 2029 target after faster-than-expected advances in quantum hardware and error correction. The tech giant announced this week that the plan, built around its own Quantum Threat Model, organizes work into three priority areas: mitigating Store Now Decrypt Later (SNDL) risk, strengthening digital signatures against forgery, and building the cryptographic agility needed to adopt new standards as they emerge. Several milestones are already in place. Google Cloud’s API endpoints, including google.com and googleapis.com, now use NIST-standardized ML-KEM key exchange in hybrid mode. Application and proxy load balancers support quantum-safe hybrid key exchange for TLS 1.3 on an opt-in basis, allowing customers to validate the change in their own environments. In addition, cloud KMS has also reached general availability for NIST-standardized PQC algorithms covering both key exchange and digital signatures. The roadmap sets end-of-2027 as the target for mitigating SNDL risk across customer-facing workloads, administrative and developer tooling such as Cloud VPN and Interconnect, and data transfer services including the BigQuery CLI and Storage Transfer Service.Advertisement. Scroll to continue reading. Signature integrity and identity protections carry a longer runway, targeted for completion by the end of 2028. This covers quantum-resistant software supply chain attestations, the rollout of quantum-safe certificates across Google’s infrastructure, and hardening of identity mechanisms such as Cloud IAM. Foundational key management work carries the same end-of-2028 target overall, though individual pieces move at different speeds: Cloud KMS is set to support quantum-safe key import as early as 2026, while hardware-backed protections such as confidential computing and Cloud HSM, along with external key management and partner-enabled key sovereignty options, are slated for 2028. On the hardware side, Google says it is anchoring trust in open source silicon components, including Caliptra and OpenTitan, the latter of which already supports quantum-secure boot. “We anticipate continuing those efforts into the 2030s to support broader industry guidance and evolving global standards. These standards include CNSA 2.0 and the transition paths defined in NIST IR 8547, which anticipate the final deprecation of legacy, quantum-vulnerable algorithms between 2030 and 2035,” Google noted. The company frames infrastructure security as its own responsibility, while customers remain responsible for updating client-side software, managing the lifecycle of their own encryption keys, and reconfiguring services to use quantum-safe settings once available. For customers, Google recommends three initial steps: inventorying cryptographic assets such as keys and certificates, updating development and operations tooling to support PQC-capable libraries, and testing existing applications against the quantum-safe APIs and load balancers that are already available. Related: Keyfactor Scores $1 Billion+ Investment for AI, Post-Quantum Security Related: Trump Signs Executive Order Accelerating Post-Quantum Cryptography Migration Related: Google Slashes Quantum Resource Requirements for Breaking Cryptocurrency Encryption Written By Eduard Kovacs Eduard Kovacs (@EduardKovacs) is senior managing editor at SecurityWeek. He worked as a high school IT teacher before starting a career in journalism in 2011. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering. Daily Briefing Newsletter Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights. More from Eduard Kovacs White House Mobilizes Security Firms for Operations Against Foreign Cybercrime GangsSharePoint Vulnerability Exploited Shortly After PoC ReleaseWhatsApp Unveils New Scam Alert FeatureChipmaker Patch Tuesday: Intel, AMD Fix Over 80 Vulnerabilities CombinedICS Patch Tuesday: Vulnerabilities Fixed by Siemens, Schneider, Phoenix ContactCisco Patches Firewall Zero-Day Exploited for DoS AttacksUS Water Systems Get Cyber Boost From New Senate Bill and ‘Water Watch Center’Extension Banned for Stealing AI Chats Returns to Chrome Store, Resumes Malicious Activities Latest News In Other News: Rapid7 Layoffs, Hacking a Boeing 737, Refrigeration System VulnerabilitiesTrivy, Not LiteLLM Behind the 2,500 Org Compromise1.6 Million Likely Impacted by RingCentral Data BreachOver 1,000 Charities Hit by Beacon CRM Data Breach14,000 Trezor Customers Impacted by Data Breach at ShipMonkHackers Exploiting Unpatched GeoServer Zero-DayAmnesiaStealer macOS Malware Steals Data, Controls Browser SessionsCybersecurity M&A Roundup: 21 Deals Announced in July 2026 Trending Daily Briefing NewsletterSubscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts. Webinar: Rethinking Cyber Defense for AI-Speed Attacks August 18, 2026 Join this live webinar as we explore if detection-first security operations can keep pace with AI, or if it’s time to rethink prevention as the strongest default. Register Virtual Event: CodeSecCon 2026 August 19, 2026 CodeSecCon bridges the gap between dev and security. Discover best practices for secure coding, innovative risk-reduction tools, and safe AI integration to cultivate a true DevSecOps culture. Safely secure your apps! Register People on the MoveErika Dean has been appointed Chief Information Security Officer at Tricentis.C1 has named Jeff St. Clair Chief Revenue Officer.John Opala has joined Ralph Lauren as Chief Information Security Officer.More People On The MoveExpert Insights The AI Governance Gap Is a Leadership Problem: Waiting Won’t Close It Organizations are rushing to implement AI without fully grasping where its legal protections begin and end. (Steve Durbin) Rethinking AI Security: Why CASB and DLP Need an Interaction-Aware Layer Build your strategy around answering these questions to ensure employees use AI productively while keeping sensitive data, IP, and agent behavior within the boundaries set for safe AI use. (Etay Maor) Timeless Compliance: Why Better Questions Beat Bigger Frameworks The best compliance programs aren't the biggest ones. They're the ones built on a short list of questions that can actually be answered, and that still hold true when the models change. (Matt Honea) Is Patching Dead? Vulnerability Management in the Post-Mythos Era You cannot out-patch a machine that writes a working exploit from a vulnerability description in twenty hours. Stop trying to optimize a game you cannot win. (Danelle Au) When Identity Verification Fails: Lessons from a Real-World SIM Swap and Near Account Takeover Identity confidence changes throughout every interaction and should be reassessed continuously as new risk signals emerge. (Torsten George) Flipboard Reddit Whatsapp Whatsapp Email","https:\u002F\u002Fwww.securityweek.com\u002Fgoogle-cloud-sets-out-post-quantum-roadmap-with-2029-readiness-goal\u002F","https:\u002F\u002Fwww.securityweek.com\u002Fwp-content\u002Fuploads\u002F2026\u002F08\u002FPQC-post-quantum-cryptography.jpeg","2026-08-14T11:00:00+00:00","2026-08-14T12:00:24.499192+00:00",7,[18,21,23,25,27,29],{"name":19,"type":20},"Cloud KMS","product",{"name":22,"type":20},"Cloud VPN",{"name":24,"type":20},"Interconnect",{"name":26,"type":20},"BigQuery CLI",{"name":28,"type":20},"Storage Transfer Service",{"name":30,"type":20},"Cloud IAM","0493c7e9-989a-4692-b4e6-136f5ec09675",{"id":31,"icon":33,"name":34,"slug":35},null,"Cryptography","cryptography",[37,39,44,49],{"category":38},{"id":31,"icon":33,"name":34,"slug":35},{"category":40},{"id":41,"icon":33,"name":42,"slug":43},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":45},{"id":46,"icon":33,"name":47,"slug":48},"c70f3a41-2f0c-4608-870d-b8cbcd8be076","Cloud Security","cloud-security",{"category":50},{"id":51,"icon":33,"name":52,"slug":53},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[]]