Google Sets 2029 Deadline for Quantum-Safe Cryptography

What happened

Google set a 2029 deadline for quantum-safe cryptography across its systems, products, and services as it accelerates its post-quantum migration plans. The company announced the timeline in a blog post authored by Heather Adkins, vice president of security engineering, and Sophie Schmieg, senior staff cryptography engineer at Google. The article says Google has already begun rolling out post-quantum cryptography within its infrastructure for internal operations and products. It also said the company is focusing on three areas during the migration: crypto agility, securing critical shared infrastructure, and facilitating ecosystem shifts. In addition to the 2029 target, the article says Android 17 is integrating post-quantum digital signature protection using ML-DSA, adding to previously announced support for post-quantum technologies in Google Chrome and Google Cloud. 

Who is affected

The direct impact falls on Google systems, products, and services covered by the company’s post-quantum migration plan. The article also says the shift is relevant to organizations that rely on cryptography for encryption, authentication, and digital signatures, especially where partner interoperability may depend on future post-quantum readiness. 

Why CISOs should care

This matters because Google is putting a concrete timeline on post-quantum migration and explicitly prioritizing authentication services in its threat model. The article also notes that organizations that do not prepare may face not only future cryptographic risk, but also interoperability problems with partners that move faster on post-quantum adoption. 

3 practical actions

1. Inventory cryptography use now: Build a clear inventory of where cryptography is used across your environment so post-quantum migration planning is based on actual dependencies and not assumptions. 
2. Engage critical providers early: Press cloud platforms, VPN vendors, and software partners to confirm their post-quantum migration plans, since the article identifies third-party dependence as a key issue for many organizations. 
3. Prioritize long-lived sensitive systems: Focus first on systems protecting data and authentication workflows that must remain secure well into the future, because the article highlights those as the highest-concern areas. 

For more news about enterprise security planning and cryptographic modernization, click Cybersecurity to read more.