Back to blog

Post-Quantum TLS: What Web Teams Should Actually Do This Year

The standards are finalized and browsers already negotiate hybrid key exchange. Separating the parts that are handled for you from the parts that still need planning.

Abstract visualization of encrypted network traffic

Post-quantum cryptography generates a lot of anxiety and a lot of vendor emails. The practical picture for a web team is narrower and more manageable than the marketing suggests.

What the threat actually is

A sufficiently large quantum computer could break the elliptic-curve and RSA key exchange that protects TLS today. No such machine exists. The reason to act now is harvest now, decrypt later: an adversary can record encrypted traffic today and decrypt it years later. That matters only if the data still has value then.

What is already handled

NIST finalized its standards in 2024 — ML-KEM for key encapsulation, plus ML-DSA and SLH-DSA for signatures. Major browsers have supported hybrid X25519 with ML-KEM in TLS 1.3 since Chrome 124, and large CDNs rolled hybrid key exchange out to their edge some time ago. If your site sits behind one of those CDNs and the client is a current browser, your connections are very likely already negotiating post-quantum-protected key exchange without anyone at your company doing anything.

Encrypted data streams represented as abstract light paths
The key exchange layer is largely solved; signatures and long-lived artifacts are not.

What still needs attention

  • Internal hops. TLS between your edge and your origin, and between services, often runs on older libraries. That is where the unprotected traffic usually is.
  • Long-lived signed artifacts. Signed audit logs, software signatures, archived documents and long-expiry SAML assertions all need a migration plan. Short-lived JWTs do not.
  • Crypto-agility. The real deliverable is not "use algorithm X", it is being able to change algorithms without a rewrite. Centralize crypto behind one module so the next migration is a configuration change.
  • Inventory. You cannot migrate what you cannot list. Write down where keys are generated, stored and verified. Most teams discover surprises here.

What does not need attention

Symmetric encryption such as AES-256 remains fine; it is not meaningfully threatened. WebAuthn and passkey signatures, while theoretically vulnerable, are per-origin credentials with no harvestable ciphertext, so they are not an urgent migration. And for a site serving purely public content, the urgency of the whole topic is close to zero.

Proportional response

Scale your effort to the confidentiality lifetime of your data. Public marketing site: confirm your CDN does hybrid key exchange and move on. Financial or health records with a ten-year sensitivity window: build the inventory, plan the internal TLS upgrade, and put crypto-agility on the roadmap this year.

And keep perspective. The far larger risk to most web applications is still the boring list — weak authentication, injection, misconfigured access control. A team that has not yet shipped passkeys or a content security policy should finish those before worrying about quantum computers.

Post-Quantum TLS: What Web Teams Should Actually Do This Year — 1Post-Quantum TLS: What Web Teams Should Actually Do This Year — 2Post-Quantum TLS: What Web Teams Should Actually Do This Year — 3
Written by

Hesam Ziaee, a web developer and programmer who builds fast, user-friendly websites with Vue.js, Quasar and Node.js.