F5 integrates NIST-compliant post-quantum cryptographic (PQC) ciphers into ADSP. Learn how hybrid TLS groups protect against
What F5 ADSP Is Adding
F5 ADSP integrates NIST-compliant post-quantum cryptographic (PQC) ciphers into the traffic path where TLS is terminated and negotiated. The goal is practical: keep today’s classical cryptography working while introducing algorithms designed to resist attacks from large-scale quantum computers. For operators, that means new cipher options and hybrid TLS groups appear in the same control plane you already use for certificate, policy, and protocol settings—without treating PQC as a separate product silo.
NIST-compliant PQC matters because standards reduce guesswork. You can select algorithms that have completed public review rather than experimental suites with unclear lifecycle or interoperability. ADSP’s role is to make those ciphers usable at the application delivery edge: handshake behavior, policy enforcement, logging, and gradual rollout stay inside familiar operational workflows.
Why Hybrid TLS Groups Exist
Hybrid TLS groups combine a classical key-exchange (or key-agreement) mechanism with a post-quantum mechanism in a single handshake. Both sides must complete both legs successfully for the session keys to be derived. If either leg fails cryptographically, the connection fails closed. That design protects against two failure modes at once: a break of the classical algorithm later, and an immature or flawed PQC algorithm that still needs time in production.
The hybrid model is deliberately conservative. Classical TLS remains widely deployed and well understood; pure PQC-only paths can create interoperability gaps with clients, middleboxes, or libraries that only speak classical groups. Hybrid TLS lets you raise the security bar without forcing a hard cutover. It also keeps confidentiality planning aligned with “harvest now, decrypt later” risk: traffic captured today should not become readable solely because classical public-key crypto weakens in the future.
How Hybrid Groups Protect Traffic
In a hybrid handshake, the classical and PQC contributions are combined so session secrets depend on both. An attacker who can break only one of the two algorithms still cannot reconstruct the shared secret from the wire alone. That dual dependence is the core protective property. It also gives you a rollback path: if a PQC component proves operationally costly or poorly supported on a given client fleet, you can adjust policy without abandoning classical protection for the same flows.
- Classical leg: preserves compatibility with existing TLS stacks and certificate workflows.
- PQC leg: adds quantum-resistant key material under NIST-aligned algorithms.
- Combined secrets: session keys require success of both legs, not either alone.
- Policy control: enable hybrids per virtual server, profile, or application tier so you can stage exposure.
Operational Guidance for Rollout
Treat hybrid TLS as a configuration and observability project, not a one-click crypto upgrade. Start by inventorying which applications terminate TLS on ADSP, which clients they serve, and which cipher policies they inherit. Enable hybrid groups in non-production first, then on limited production cohorts. Watch handshake failure rates, latency, CPU on TLS workers, and certificate chain behavior. Document which client platforms complete hybrids cleanly and which need classical-only fallbacks.
Keep certificate lifecycle separate from key-exchange choices: hybrid groups address key agreement and related handshake crypto, not a free replacement for identity, pinning, or mutual TLS policy. Prefer NIST-compliant suites offered by ADSP over ad hoc combinations. When you expand, do it by application criticality and client diversity—internal APIs with controlled clients first, then broader internet-facing services. Log negotiated groups so incident response and compliance reviews can prove what was actually used. The practical outcome is phased quantum readiness: hybrid TLS on F5 ADSP gives you defense against future cryptanalysis of classical algorithms while retaining the operational safety of classical TLS today.