Future-Proofing Your Network: Enabling Quantum Ciphers on F5 BIG-IP TMOS 17.5.1
The quantum computing revolution is an imminent reality that demands attention from cybersecurity experts. As quantum computers advance toward breaking traditional RSA and elliptic curve cryptography, organizations must prepare their infrastructure with quantum-resistant encryption. F5's BIG-IP TMOS 17.5.1 introduces support for post-quantum cryptographic algorithms, positioning your network security ahead of the quantum curve. Understanding the Quantum Threat Traditional cryptographic methods like RSA-2048 and ECDSA rely on mathematical problems that classical computers find computationally intractable to solve. However, quantum computers running Shor's algorithm can factor large integers exponentially faster. This renders these encryption methods vulnerable within the next decade. The National Institute of Standards and Technology (NIST) has standardized several post-quantum cryptographic algorithms. They are designed to withstand both classical and quantum attacks. TMOS 17.5.1 implements ML-KEM (FIPS 203) for key encapsulation. The standard versions are based on the original CRYSTALS-Kyber and CRYSTALS-Dilithium algorithms. They include important changes to the parameters and requirements for how they are used to make sure they work well together in the future. Prerequisites and Planning Before implementing quantum ciphers on your BIG-IP system, ensure your environment meets these requirements: Hardware Requirements: BIG-IP appliances with sufficient processing power (quantum algorithms are computationally intensive) Minimum 8GB RAM for optimal performance Hardware Security Module (HSM) support recommended for key management Hardware Security Modules are not required to support post-quantum cryptographic algorithms, but they provide a higher level of assurance for cryptographic key storage. F5 offers a range of hardware that has built in hardware security modules. Also, if virtual F5 instances are selected, they offer the ability to integrate with a network based hardware security module. Software Requirements: TMOS version 17.5.1 or later Valid SSL/TLS certificates compatible with hybrid classical-quantum cipher suites Updated client applications capable of negotiating post-quantum algorithms The current implementation is a hybrid approach where classical and post quantum algorithms run in parallel. So you would use "classical" RSA/ECDSA certificates for the server authentication, but the actual TLS handshake would use ML-KEM for establishing quantum-safe session keys. Network Considerations: Increased bandwidth requirements due to larger key sizes and signature lengths Latency impact assessment for time-sensitive applications Compatibility testing with existing security infrastructure Enabling Quantum Ciphers: Step-by-Step Configuration Step 1: Access the BIG-IP Configuration Utility Log into your BIG-IP system through the web-based Configuration utility or connect via SSH for command-line configuration. Navigate to System/Configuration/Device/General to verify you're running TMOS 17.5.1. Or in the cli type tmsh show sys version Then follow along with F5 documentation. The details are all in the article for configuration either via TMUI or TMSH. This can all be configured via APIs or could be set up using tools like Ansible or Terraform if automation is required. https://my.f5.com/manage/s/article/K000149577 Step 2: Create a Cipher Rule Step 3: Create a new Cipher Group Step 4: Create a New Client SSL profile Create a client SSL profile. Associate the ciphergroup with the new client SSL profile. Remove No TLSv1.3 from the enabled options Step 5: Create a Virtual Server Example: tmsh create /ltm virtual quantum { destination 10.0.2.113:443 ip-protocol tcp pool quantumpool profiles add { quantum { context clientside } tcp } } Test In my case, I used Chrome. I enabled the developer tools and in the privacy and developer tools, looked at what was being negotiated. Sure enough, I am getting a quantum-safe connection. Monitoring and Troubleshooting Essential Monitoring Commands Monitor quantum cipher usage and performance: # Check quantum cipher statistics tmsh show ltm profile client-ssl quantum # View quantum key exchange metrics tmsh show ltm virtual quantum Common Issues and Solutions High CPU Usage: Quantum algorithms are computationally intensive. Consider hardware acceleration or load balancing across multiple devices. Compatibility Issues: Not all clients support quantum ciphers yet. Implement graceful fallback mechanisms and maintain hybrid cipher suites during the transition period. Browser Compatibility and the Chrome ML-KEM Transition A critical consideration for BIG-IP quantum cipher deployment is the ongoing browser transition from draft Kyber implementations to standardized ML-KEM. Chrome has phased out Kybersupport in favor of ML-KEM. This shift has significant implications for your BIG-IP configuration strategy. Configuring for Browser Compatibility To ensure seamless browser compatibility during this transition, configure your BIG-IP to prioritize ML-KEM Notably, the following cipher string did not work for me in Chrome as Kyber support has been removed in the latest versions of Chrome. X25519KYBER768 As per the k Article. Note: On June 24, 2025, Google released Chrome 138.7204.49 that no longer includes Kyber support. The chrome://flags options for PQC algorithms was also removed, and MLKEM is enabled by default. My Chrome Version was Version 138.0.7204.158, so Kyber support has gone. This DH cipher string worked for me in Chrome. X25519MLKEM768 The K article recommends the following cipher string. X25519MLKEM768:X25519KYBER768:DEFAULT To reiterate. If you are using anything earlier than TMOS version 17.5.1 and you attempt a test with a new version of Chrome, it will not work with ML-KEM as the support was only introduced in 17.5.1 and Kyber has been removed from Google Chrome, so if you were to test with 17.5.0 you would find that that Chrome would not be able to negotiate a quantum-safe connection. As per the knowledge article. BIG-IP TMOS version 17.5.0 (for Kyber), 17.5.1 (for MLKEM) or later Performance Considerations Quantum cipher implementation introduces several performance implications that require careful consideration. Key exchange operations using ML-KEM-768 consume about 25% more CPU cycles than traditional ECDHE exchanges. They have slightly better performance than the original Kyber implementation due to standardization optimizations. To make your computer run faster, use hardware acceleration when possible. Use intelligent cipher selection algorithms to balance security needs with performance limits. Consider implementing session resumption mechanisms to reduce the frequency of quantum key exchanges. Compliance and Regulatory Considerations Many industries are beginning to mandate post-quantum cryptography readiness. Financial services, healthcare, and government sectors are leading the adoption of quantum-resistant security measures. TMOS 17.5.1's ML-KEM support helps organizations meet emerging compliance requirements and prepare for future regulatory mandates. It also ensures compatibility with major browsers transitioning away from draft Kyber implementations. Ensure your quantum cipher implementation aligns with relevant standards, including NIST SP 800-208, FIPS 203 (ML-KEM), and industry-specific quantum security guidelines. The transition from draft Kyber to standardized ML-KEM is critical for long-term browser compatibility and regulatory compliance. Future-Proofing Your Investment As quantum computing technology evolves, so too will post-quantum cryptographic standards. F5’s modular approach to quantum cipher implementation ensures that your BIG-IP infrastructure can adapt to future algorithm updates and security enhancements without requiring complete system replacement. Regular software updates and security patches will introduce new quantum-resistant algorithms and performance optimizations. Maintain an active support relationship with F5 to stay current with the latest quantum security developments. Conclusion Implementing quantum ciphers on F5 BIG-IP TMOS 17.5.1 represents a critical step in preparing your network infrastructure for the quantum era. While the transition requires careful planning and performance considerations, the security benefits far outweigh the implementation challenges. Start your quantum-resistant journey today by enabling hybrid cipher suites and gradually transitioning to full quantum protection. The quantum threat is real, but with proper preparation and F5's advanced security capabilities, your organization can maintain robust protection against both classical and quantum adversaries. The future of network security is quantum-resistant, and TMOS 17.5.1 provides the tools you need to secure that future today. Begin your quantum security implementation now, before the quantum advantage becomes a quantum threat.Hands-On Quantum-Safe PKI: A Practical Post-Quantum Cryptography Implementation Guide
Updated 01.16.26 for FrodoKEM/BIKE/HQC alternate algorithms Is your Public Key Infrastructure quantum-ready? Remember way back when we built the PQC CNSA 2.0 Implementation guide in October 2025? So long ago! Due to popular request, we've expanded the lab to now include THREE distinct learning paths: NIST FIPS standards, NSA CNSA 2.0 compliance, AND alternative post-quantum algorithms for those wanting diversity or international compliance options.. The GitHub lab guide walks you through building quantum-resistant certificate authorities using OpenSSL with hands-on exercises. Why learn and implement post-quantum cryptography (PQC) now? While quantum computing is a fascinating area of science, all technological advancements can be misused. Nefarious people and nation-states are extracting encrypted data to decrypt at a later date when quantum computers become available, a practice you better know by now called "harvest now, decrypt later." Close your post-quantum cryptographic knowledge gap so you can get secured sooner and reduce the impact(s) that may not surface until after it's too late. Ignorance is not bliss when it comes to cryptography and regulatory fines, so let's get started. The GitHub lab provides step-by-step instructions to create: Quantum-resistant Root CA using ML-DSA-87 (FIPS and CNSA 2.0) Algorithm flexibility based on your compliance needs Quantum-safe server and client certificates OCSP and CRL revocation for quantum-resistant certificates TLS 1.3 key exchange testing with ML-KEM and hybrid modes Alternative algorithm exploration (FrodoKEM, BIKE, HQC) for TLS/KEM usage Access the Complete Lab Guide on GitHub → At A Glance: OpenSSL Quantum-Resistant CA Learning Paths Select the path that aligns with your requirements: FIPS 203/204/205 CNSA 2.0 Alt. Algorithms Target Audience Commercial organizations Government contractors, classified systems Researchers, international compliance, defense-in-depth Compliance Standard NIST FIPS standards NSA CNSA 2.0 Non-NIST algorithms, international standards Algorithm Coverage ML-DSA, ML-KEM, SLH-DSA, Hybrid ML-DSA-65/87, ML-KEM-768/1024 FrodoKEM, BIKE, HQC Use Case General quantum-resistant infrastructure National security systems Algorithm diversity, conservative security 📚 Learning Path 1: NIST FIPS 203/204/205 For commercial organizations implementing quantum-resistant cryptography using NIST standards. This path uses OpenSSL 3.5.x's native post-quantum cryptography support—no external quantum library providers required. So nice, so easy. Modules Module Description 00 - Introduction Overview of FIPS 203/204/205, prerequisites, and lab objectives 01 - Environment Setup Verifying OpenSSL with PQC support 02 - Root CA Building a Root CA with ML-DSA-87 03 - Intermediate CA Creating an Intermediate CA with ML-DSA-65 04 - Certificates Issuing end-entity certificates for servers and users 05 - Revocation Implementing OCSP and CRL certificate revocation 06 - Hybrid Methods IETF hybrid PQC methods (X25519MLKEM768, composite signatures) Algorithms Covered ML-DSA-44/65/87 (FIPS 204) - Lattice-based signatures ML-KEM-512/768/1024 (FIPS 203) - Lattice-based key encapsulation X25519MLKEM768 - Hybrid TLS 1.3 key exchange 📚 Learning Path 2: NSA CNSA 2.0 For government contractors and organizations requiring CNSA 2.0 compliance. This path uses OpenSSL 3.2+ with Open Quantum Safe (OQS) providers for strict CNSA 2.0 algorithm compliance. Modules Module Description 01 - Introduction Overview of CNSA 2.0 requirements and compliance deadlines 02 - Root CA Building a Root CA with ML-DSA-87 03 - Intermediate CA Creating an Intermediate CA with ML-DSA-65 04 - Certificates Issuing CNSA 2.0 compliant certificates 05 - Revocation Implementing OCSP and CRL certificate revocation CNSA 2.0 Approved Algorithms Algorithm Type Approved Algorithms NIST Designation Digital Signatures ML-DSA-65, ML-DSA-87 FIPS 204 Key Establishment ML-KEM-768, ML-KEM-1024 FIPS 203 Hash Functions SHA-384, SHA-512 FIPS 180-4 Note: CNSA 2.0 currently does NOT support ML-DSA-44, SLH-DSA, or Falcon algorithms. 📚 Learning Path 3: Alternative PQC Algorithms (NEW!) For researchers, organizations requiring algorithm diversity, and those interested in international PQC implementations. This path explores post-quantum algorithms outside the primary NIST standards, providing options for defense-in-depth strategies and understanding of the broader PQC landscape. Perfect for organizations wanting to hedge against potential future vulnerabilities in current adopted standards. Modules Module Description 00 - Introduction Overview of non-NIST algorithms, international standards, use cases 01 - Environment Setup OpenSSL and modifying OQS provider configuration 02 - FrodoKEM Conservative unstructured lattice KEM (European recommended: BSI, ANSSI) 03 - BIKE and HQC Code-based KEMs (HQC is NIST-selected backup to ML-KEM) 04 - International PQC EU, South Korean, and Chinese algorithm standards 05 - Performance Analysis Comparing algorithms, latency impacts, use cases, nerd stats Algorithms Covered Algorithm Type Mathematical Basis Key Characteristic FrodoKEM KEM Unstructured lattice (LWE) Conservative security, European endorsed (BSI, ANSSI) BIKE KEM Code-based (QC-MDPC) NIST Round 4 candidate, smaller keys than HQC HQC KEM Code-based (Quasi-cyclic) NIST-selected backup to ML-KEM (standard expected 2027) Why Alternative Algorithms Matter Algorithm Diversity: If a vulnerability is found in lattice-based cryptography (ML-KEM), code-based alternatives provide a backup International Compliance: European agencies (BSI, ANSSI) specifically recommend FrodoKEM for conservative security Future-Proofing: HQC will become a FIPS standard in 2027 as NIST's official backup to ML-KEM Research & Testing: Understand the broader PQC landscape for informed decision-making What This Lab Guide Achieves Complete PKI Hierarchy Implementation The lab walks through building an internal PKI infrastructure from scratch, including: Root Certificate Authority: Using ML-DSA-87 providing the highest quantum-ready NIST security level Intermediate Certificate Authority: Intermediate CA using ML-DSA-65 for operational certificate issuance End-Entity Certificates: Server and user certificates with comprehensive Subject Alternative Names (SANs) for real-world applications Revocation Infrastructure: Both Certificate Revocation Lists (CRL) and Online Certificate Status Protocol (OCSP) implementation TLS 1.3 Key Exchange Testing: Hands-on testing with ML-KEM, hybrid modes, and alternative algorithms Security Best Practices: Restrictive Unix file permissions, secure key storage, and backup procedures throughout Key Takeaways After completing one or more of the labs, you will: Understand ML-DSA Cryptography: Gain hands-on experience with both ML-DSA-65 (Level 3 security) and ML-DSA-87 (Level 5 security) algorithms Explore Algorithm Diversity: Understand when and why to use alternative algorithms like FrodoKEM, BIKE, and HQC Configure Modern PKI Features: Implement SANs with DNS, IP, email, and URI entries, plus both CRL and OCSP revocation mechanisms Test TLS 1.3 Key Exchange: Hands-on experience with ML-KEM and hybrid key exchange in real TLS sessions Troubleshoot Effectively: Learn to diagnose and resolve common issues with opensl and oqsproviders for PQC compatibility Prepare for Migration: Start the practical steps needed to transition existing PKI infrastructure to quantum-resistant algorithms Access the Complete Lab Guide on GitHub → About This Guide We built the first guide for NSA Suite B in the distant past (2017) to learn ECC and modern cipher requirements. It was well received enough to built a new guide for CNSA 2.0 but it's quite specific for US federal audiences. That lead us to build a NIST FIPS PQC guide which should apply to more practical use cases. And now we've added alternative algorithms because things are only going to get a bit more complicated moving forward. In the spirit of Learn Python the Hard Way, it focuses on manual repetition, hands-on interactions and real-world scenarios. It provides the practical experiences needed to implement quantum-resistant PKI in production environments. By building it on GitHub, other PKI fans can help where we may have missed something; or simply to expand on it with additional modules or forks. Have at it! Frequently Asked Questions (FAQs) Q: What is CNSA 2.0? A: CNSA 2.0 (Commercial National Security Algorithm Suite 2.0) is the NSA's updated cryptographic standard requiring quantum-resistant algorithms. Q: When do I need to implement quantum-resistant cryptography? A: The NSA and NIST mandate CNSA 2.0 and FIPS 203/204/205 implementation by 2030. Organizations should begin now due to "harvest now, decrypt later" attacks where adversaries collect encrypted data today for future quantum decryption. Q: What is ML-DSA (Dilithium)? A: ML-DSA (Module-Lattice Digital Signature Algorithm), formerly known as Dilithium, is a NIST-standardized quantum-resistant digital signature algorithm specified in FIPS 204. Q: What is ML-KEM (Kyber)? A: ML-KEM (Module-Lattice Key Encapsulation Mechanism), formerly known as Kyber, is a NIST-standardized quantum-resistant key encapsulation mechanism specified in FIPS 203. ML-KEM-768 provides roughly AES-192 equivalent security. Q: What are the alternative algorithms and why should I care? A: FrodoKEM, BIKE, and HQC are non-NIST-primary algorithms that provide algorithm diversity. If a vulnerability is discovered in lattice-based cryptography (which ML-KEM and ML-DSA use), code-based alternatives like HQC could provide a backup. HQC is actually NIST's selected backup to ML-KEM and will become a FIPS standard in 2027. Q: What's the difference between BIKE and HQC? A: Both are code-based KEMs. BIKE has smaller key sizes but wasn't selected by NIST. HQC has larger keys and was selected as NIST's official backup to ML-KEM. Q: Why do European agencies recommend FrodoKEM? A: FrodoKEM uses unstructured lattices (standard LWE) rather than the structured lattices used in ML-KEM. This provides more conservative security assumptions at the cost of larger key sizes. Germany's BSI and France's ANSSI specifically recommend FrodoKEM for high-security applications. Q: Is this guide suitable for production use? A: NOPE. While the guide teaches production-ready techniques and compliance requirements, always use Hardware Security Modules (HSMs) and air-gapped systems for production Root CAs (cold storage too). The lab is great for internal environments or test harnesses where you may need to test against new quantum-resistant signatures. ALWAYS rely on trusted public PKI infrastructure for production cryptography. 🤓 Happy PKI'ing! Reference Links NIST Post-Quantum Cryptography Standards - Official NIST PQC project page FIPS 203: ML-KEM Standard - Module-Lattice Key Encapsulation Mechanism FIPS 204: ML-DSA Standard - Module-Lattice Digital Signature Algorithm FIPS 205: SLH-DSA Standard - Stateless Hash-Based Digital Signature Algorithm NSA CNSA 2.0 Algorithm Requirements - NSA's official CNSA 2.0 announcement Open Quantum Safe Project - Home of the OQS provider for alternative algorithms OQS Provider for OpenSSL 3 - GitHub repository for OQS provider HQC Specification - Official HQC algorithm documentation BIKE Specification - Official BIKE algorithm documentation OpenSSL 3.5 Documentation - Comprehensive OpenSSL documentationMeeting the Federal Quantum Challenge: How F5 Enables Compliance with New Government Mandates
The U.S. government has made it crystal clear: the transition to quantum-resistant encryption isn't optional—it's mandatory. With new federal directives setting aggressive timelines and billion-dollar funding commitments, organizations must act now to prepare for a post-quantum world. Here's how F5's comprehensive post-quantum cryptography (PQC) solutions can help you meet these critical mandates while protecting your business from tomorrow's threats.Breaking Down the Quantum Challenge: Why Post-Quantum Cryptography Can't Wait
The Quantum Challenge is Now Post-quantum cryptography represents the next steps of our digital security evolution. Sure, quantum systems capable of breaking current encryption may still be an a few years away, but those beginning their transition now will be well-positioned for when the crypto hits the fan. Nation-state adversaries and sophisticated private entities may be collecting data today hoping to decrypt it tomorrow so it's never to early to start solving the problem now. It's an excellent time to get ahead of the curve with quantum-resistant cryptography. What does this mean for your organization? Any sensitive data encrypted today using standard methods (RSA, ECDSA) could potentially become readable to future quantum-powered attackers. F5 Community Evangelist Chase Abbott discusses the real world implications of quantum computing, and how you can prepare and migrate to NIST-approved hybrid PQC standards. The transition to post-quantum cryptography represents a perfect opportunity to modernize enterprise PKI practices. Those of you that begin planning today have ample time to implement these changes thoughtfully and strategically, positioning yourselves as leaders in the next generation of cybersecurity; high fives all around. The Business Impact: Beyond Technical Considerations Regulatory and Compliance Pressure Government regulations across the globe are creating concrete deadlines for migration strategies: NSA CNSA 2.0 mandates quantum-resistant algorithms for classified systems by 2030 NIST has standardized post-quantum cryptography algorithms (FIPS 203, 204, 205) Industry regulations in finance, healthcare, and defense are beginning to incorporate quantum-safety requirements adhering to the update FIPS governance Your Quantum-Ready Roadmap: A Manageable Transition Phase 1: Assessment and Inventory Action items for leadership: Conduct cryptographic inventory across all systems and applications Identify critical data requiring long-term protection Assess vendor and third-party quantum readiness Establish quantum cryptography governance and budget allocation Phase 2: Pilot Implementation Strategic focus areas: Deploy quantum-resistant algorithms in non-critical environments Train IT and security teams on post-quantum cryptography Establish partnerships with quantum-ready technology vendors Begin updating security policies and procedures Phase 3: Production Migration Enterprise-wide deployment: Implement hybrid classical/quantum-resistant systems and software Migrate critical applications and PKI aggregation points to quantum-safe algorithms Update business continuity and disaster recovery plans Achieve full compliance with regulatory requirements as a priority over other systems Key Takeaways for Business Leaders Start planning now: The quantum threat timeline is uncertain, but the need for preparation is immediate Prioritize critical assets: Focus initial efforts on protecting your most sensitive and long-lived data Invest in capabilities: Quantum cryptography expertise will become as essential as any other IT security skill Engage stakeholders: Quantum security requires coordination across IT, compliance, procurement, and business units Monitor developments: Stay informed about quantum computing advances and regulatory updates Mahalo! Further Reading: Post Quantum Cryptography Coalition: PQC Migration Roadmap Post Quantum Cryptography Coalition: International PQC Requirements Post Quantum Cryptography Coalition: Inventory Workbook Essence of Linear Algebra Quantum Computing for the Very Curious Looking Glass Universe: Why I Left Quantum Computing Research US National Quantum Initiative
Exploring Quantum Computing, AI, Networking and Cryptography at AppWorld 2025
Join us as we dive into the exciting world of quantum computing and AI at App World 2025, held at the fabulous Fontainebleau in Las Vegas. I get to host a fascinating discussion with Daniela Pontes and Brett Wolmarans bwolmarans from F5. We explore the latest advancements in AI, the impact of quantum computing on cybersecurity, and what the future holds for post-quantum cryptography. Discover how F5 is leveraging AI to optimize and secure applications, and learn about the recent release of the AI gateway. Daniela delves into the looming threat of quantum computing on current cryptography standards, explaining the importance of transitioning to quantum-resistant algorithms and even a little on quantum networking. Stay tuned for info on how industries like finance and healthcare are preparing for a quantum future. Don't miss this episode full of expert knowledge and cutting-edge technology!
