F5 integrates NIST-compliant post-quantum cryptographic (PQC) ciphers into ADSP. Learn how hybrid TLS groups protect against
Why post-quantum cryptography matters now
A large enough quantum computer would be able to break the public-key algorithms that secure most TLS traffic today, including the key exchanges that protect session secrets. The threat is not purely future-tense. An attacker can capture encrypted traffic now and store it until the hardware to decrypt it exists — the "harvest now, decrypt later" problem. Any data with a long confidentiality lifetime, such as health records, financial data, or credentials, is exposed to this risk the moment it crosses the wire.
By integrating NIST-compliant post-quantum cryptographic (PQC) ciphers into ADSP, F5 lets you defend against this class of attack at the point where TLS is negotiated, rather than waiting for every backend application to be rewritten around new algorithms.
What hybrid TLS groups actually do
A hybrid TLS group pairs a traditional key-exchange algorithm with a post-quantum one so that both run during the same handshake. The shared secret is derived from the combination, which means the connection stays secure as long as at least one of the two algorithms holds. That design is what makes migration safe: you gain quantum resistance without betting everything on newer, less battle-tested PQC schemes.
Choosing NIST-selected algorithms matters here. Standardization gives you interoperability across clients and vendors, a reviewed security basis, and a clear compliance story for auditors who will increasingly ask what you are doing about quantum risk.
How ADSP applies this at the edge
ADSP sits in front of your applications and terminates or proxies TLS, which makes it the natural place to introduce hybrid key exchange. Because the platform negotiates the handshake with clients, it can offer post-quantum groups to clients that support them while gracefully falling back to classical groups for those that do not. Your origin servers and application code do not need to understand PQC at all.
- Clients that advertise hybrid groups get quantum-resistant key exchange automatically.
- Older clients continue to connect using classical groups, so nothing breaks during rollout.
- Cipher and group policy is managed centrally, so you change posture in one place instead of per-application.
This edge-first model turns a daunting cryptographic migration into a configuration change on the infrastructure you already operate.
Rolling it out sensibly
Start by inventorying which of your services carry data with long-lived confidentiality requirements, since those benefit most from early adoption. Enable hybrid groups in a monitoring or staged posture first so you can observe handshake success rates and catch clients or middleboxes that mishandle the larger key material PQC exchanges use. Watch for connection failures and handshake latency, and keep classical groups available as a fallback until you are confident in client coverage.
Treat this as an ongoing process rather than a one-time switch. The set of NIST-standardized algorithms and the clients that support them will keep changing, so plan to revisit your group policy periodically. Because ADSP centralizes that policy, adjusting your stance as the standards mature stays a manageable operational task rather than another full migration.