Google Accelerates Quantum Threat Timeline to 2029; Defense Crypto Migration Enters Urgent Phase
Google's acceleration of Q Day forces the DoD and defense primes into a choice between accepting cryptographic vulnerability during the 2027-2029 transition window or pre-funding crypto replacement on weapons platforms that are already in full-rate production (F-35, Aegis, ICBM command & control).
This converts a technical timeline into a procurement bottleneck: if NIST post-quantum standards are not finalized and certified by mid-2027, the DoD cannot begin fielding replacement systems in time to cover the gap before quantum threat maturity.
Defense contractors, intelligence agencies, and critical infrastructure operators face an immediate procurement and operational security crisis.
Systems certified to current NIST standards for encryption will become vulnerable within 36 months. The DoD, which relies on RSA-2048 and EC-based encryption across weapons systems, communications networks, and supply chain IT, must either accelerate hardware and software replacement cycles or accept a window of cryptographic vulnerability during the transition.
This is not a future risk—it is a 2027-2029 operational reality. Contractors with legacy cryptographic architectures in active programs (F-35, Aegis, satellite command & control) face retrofit costs and certification delays.
The intelligence community faces a secondary threat: adversaries may already be harvesting encrypted communications today for decryption once quantum capability arrives ('harvest now, decrypt later'), meaning signals collected in 2024-2025 become readable in 2029-2030.
The article does not specify which NIST post-quantum cryptography standards Google is recommending, whether NIST has formally ratified them, or what the compliance timeline looks like for federal procurement.
Fault Lines
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.