Cloudflare targets 2029 for full post-quantum security
Key Points
- Full PQ authentication targeted by 2029
- Google and Oratomic advances pulled Q-Day earlier
- Prioritize replacing long‑lived keys and disabling legacy crypto
Summary
Cloudflare is accelerating its post-quantum (PQ) roadmap and now targets 2029 to be fully post-quantum secure, explicitly including post-quantum authentication. Recent independent advances — notably Google’s algorithmic speedup for breaking elliptic curve cryptography and Oratomic’s neutral-atom resource estimates — have meaningfully shortened Q-Day timelines and increased the urgency to upgrade authentication (not just encryption).
Key Points
- Target: Cloudflare aims for full PQ security including authentication by 2029; PQ encryption for most products is already deployed.
- Why now: compounding progress on three fronts — hardware (neutral atoms, superconducting, ion-trap, photonics), error correction (much lower physical-to-logical qubit ratios for reconfigurable qubits), and software (algorithmic optimizations) — pulls Q-Day earlier.
- Priority shift: authentication is now the highest priority because a single quantum-vulnerable key (root cert, code-signing key, API auth) can give attackers persistent access.
- Immediate engineering actions:
- Inventory and prioritize long-lived keys (root certificates, code-signing, API keys, persistent SSH keys) for replacement with PQ algorithms.
- Rotate secrets and credentials that were generated under quantum-vulnerable algorithms; automate rotation where possible.
- Where feasible, disable quantum-vulnerable algorithms and implement downgrade protections (PQ HSTS, certificate transparency) to prevent downgrade attacks.
- Require post-quantum support in procurement and assess third-party dependencies (including non-crypto critical vendors) for PQ readiness.
- Migration reality: upgrading authentication has a long dependency chain (third-party validation, fraud monitoring, federation issues) and will take years — start now.
What to watch
- Progress in neutral-atom hardware and reductions in error-correction overhead.
- Public and private algorithmic improvements that reduce work to break ECC/RSA.
- Vendor and browser adoption paths for PQ certificates and downgrade protections.
Recommended next steps for engineering teams
- Run a prioritized inventory of long-lived and high-value keys and schedule PQ replacements.
- Implement automated certificate and key rotation pipelines.
- Add PQ support as a procurement requirement and audit critical third parties.
- Plan for phased rollout with downgrade protections and monitoring for compatibility issues.