Quantum-safe TLS: what hybrid key agreement achieves today
Since August 2026, hybrid post-quantum key agreement for TLS 1.3 has been an IETF standard. What that means and why it is not enough on its own.

- Hybrid key agreement combines a proven and a post-quantum algorithm and stays secure as long as one of them holds.
- With RFC 10024 it has been an IETF standard for TLS 1.3 since August 2026; current browsers already use it automatically.
- TLS only protects transport. Certificates, internal connections and stored data need their own steps.
Anyone who opens a website with a current browser today is very likely already using quantum-safe TLS without noticing. The connection is set up with a combination of a classical and a post-quantum algorithm. That is good news. But it is only part of the story — and the less demanding part.
Why key agreement comes first
Every TLS connection starts with browser and server agreeing on a shared secret key. Everything sent over the line is then encrypted with this key. The algorithms commonly used for this agreement today are considered vulnerable once sufficiently powerful quantum computers exist.
The dangerous part: an attacker does not have to wait. He can record encrypted traffic today and decrypt it later. This strategy is called "harvest now, decrypt later" — more in our article on the topic. For key agreement, what matters is therefore not when quantum computers arrive, but how long the transmitted data must remain confidential.
What "hybrid" means
Hybrid key agreement runs two algorithms in parallel, a proven classical one and a NIST-standardised post-quantum one. Both results feed into the shared key. The IETF defines the goal as follows: the connection stays secure as long as at least one of the two algorithms is not broken.
That is a deliberate safeguard in both directions:
- If a future quantum computer breaks the classical algorithm, the post-quantum algorithm protects.
- If the still young post-quantum algorithm unexpectedly shows a weakness, the classical one continues to protect.
Germany's BSI explicitly recommends post-quantum key agreement in this hybrid form. In its Technical Guideline TR-02102-1 it has also set an expiry date: from the end of 2031, classical asymmetric algorithms should only be used in combination with post-quantum cryptography, and from the end of 2030 for applications with particularly high protection needs (BSI TR-02102).
Quantum-safe TLS is now a standard
For a long time buyers objected: "That's still only a draft." That objection is gone. In August 2026 the IETF published hybrid key agreement for TLS 1.3 as RFC 10024 on the standards track (IETF Datatracker). The document defines three combinations; the most common of them is marked as recommended in the official registry.
In practice the standard was in use before that: current browsers and operating systems offer the hybrid variant automatically, and large network operators report that well over half of human-initiated web traffic is now protected this way. No configuration switch is needed on the user's side.
Rule of thumb: Hybrid key agreement in TLS is no longer a pilot but a standard. The question is not whether, but where it is still missing in your environment.
Where TLS stops
As welcome as the progress is, three gaps remain:
- The other side has to play along. The browser offers the hybrid variant; the server must accept it. Many internal services, older load balancers, VPN gateways and devices in production networks do not yet. Then classical negotiation happens without warning.
- Server authenticity is still classical. Certificates and their signatures rely on today's algorithms. That is less urgent because a signature cannot be broken retroactively, but it must be migrated before powerful quantum computers arrive. How that continues is explained in a separate article on certificates and SSH.
- TLS only protects transport. On the server, in the cloud, in backups and in mailboxes the data is unencrypted again or encrypted with the provider's keys. Confidential documents need end-to-end encryption that starts before upload.
What you can do now
- Enable TLS 1.3 everywhere: hybrid key agreement only exists there. Gradually switch off older protocol versions.
- Take stock: which servers, gateways, APIs and appliances terminate TLS? Which libraries and versions run there?
- Do not forget internal connections: links between data centres, to partners and between services often stay unchanged longer than the website.
- Ask vendors: does the product support RFC 10024? From which version? How will algorithms be swapped in future (crypto agility)?
- Protect data with long confidentiality additionally: encrypt contracts, design data and personnel data end-to-end, independently of transport.
How PQVault handles this
PQVault does not rely on transport alone: content is encrypted end-to-end on the device, additionally with NIST-standardised post-quantum algorithms in hybrid form. For data rooms there is PQVault Spaces; whoever wants to secure their own applications uses the PQVault SDK. Background on the standards themselves is in the article NIST standards for post-quantum cryptography.
PQVault is a product of QuantiCor Security GmbH, Darmstadt — specialists in post-quantum cryptography. More about QuantiCor Security

