DuoKey

Migrating to Post-Quantum Cryptography

Whitepaper. 28 pages, version 1.0, June 2026.

A practical guide to moving to post-quantum cryptography. It covers what a quantum computer breaks and when, which algorithms NIST has standardised, how far the public web has moved, and how to order an inventory and migration around data that must stay confidential longest. Download it as the reference for your own post-quantum roadmap, with the standards, data, and order of work in one place.

Cover of the DuoKey whitepaper, Migrating to Post-Quantum Cryptography.

Get the download

Tell us where to send the link. A business email is required.

DuoKey uses these details only to send the download link. Privacy notice

Experts' median estimate for a quantum computer that can break today's encryption is 2035. A full cryptographic migration takes years. That leaves less time than most roadmaps assume.

This is the guide to start that work. It opens with an executive summary you can hand to leadership, then the full chapters:

  • The threat explains harvest-now-decrypt-later and gives a median expert estimate of 2035 for a quantum computer that can break current encryption.
  • Technical solutions covers the NIST standards and hybrid deployment.
  • The state of the web shows how far TLS has already moved.
  • The road to a roadmap sets out an order of work, starting with the data that must stay confidential longest.

Definitions and references are at the end. Download the 28 pages and use them as the reference for your own post-quantum roadmap.

FAQ

Who is this for?

Security architects, platform teams, and CISOs who need to plan a post-quantum migration.

What are the chapters?

The threat, technical solutions, the state of the web, the road to a roadmap, definitions, and references.

Which algorithms does it cover?

The NIST standards ML-KEM, ML-DSA, and SLH-DSA, plus FN-DSA and HQC, which are still pending.

How current is the data?

Version 1.0, June 2026. For example, it reports that 70.2 percent of Cloudflare TLS traffic uses the hybrid X25519MLKEM768 key exchange.