Post-quantum encryption for Cloudflare IPsec is generally available
Key Points
- Post-quantum IPsec GA
- Interoperable with Cisco & Fortinet
- Hybrid ML-KEM (FIPS 203) implemented
Summary
Cloudflare has made post-quantum encryption for its IPsec WAN service generally available using the draft-ietf-ipsecme-ikev2-mlkem hybrid ML-KEM (FIPS 203) handshake. The implementation is interoperable with common branch connectors (Cisco 8000 Series >= 26.1.1 and Fortinet FortiOS >= 7.6.6), requires no special hardware, and is designed to mitigate harvest-now-decrypt-later attacks ahead of Q-Day. This move advances Cloudflare's goal of full post-quantum security by 2029.
Key Points
- Protocol: Implements draft-ietf-ipsecme-ikev2-mlkem hybrid handshake (classical Diffie-Hellman first, then ML-KEM; outputs mixed into session keys for ESP).
- Standard: Uses ML-KEM (Module-Lattice KEM) per FIPS 203; runs in software on existing hardware—no QKD or dedicated links required.
- Interoperability: Confirmed with Cisco 8000 Series (>= 26.1.1) and Fortinet FortiOS (>= 7.6.6); some vendors (e.g., Palo Alto) using earlier RFC 9370 variants may not interoperate yet.
- Security intent: Protects against harvest-now-decrypt-later by combining classical and post-quantum key agreement.
- Roadmap: Cloudflare aims for full post-quantum readiness by 2029 and calls for interoperable PQC authentication standards for IPsec.
Engineer notes / Practical next steps
- Verify branch connector firmware/OS versions (Cisco >= 26.1.1, FortiOS >= 7.6.6) before enabling ML-KEM tunnels.
- Test connectivity in staging with Cloudflare IPsec using the hybrid ML-KEM ciphersuite; expect IKEv2 handshake that performs DH then ML-KEM.
- Monitor vendor support and RFC/ietf drafts for post-quantum authentication updates; avoid vendor-specific nonstandard ciphersuites to reduce interoperability risk.
- Rollout plan: start with selected sites, validate ESP traffic, then expand WAN coverage to mitigate harvest-now-decrypt-later exposures.
References
- draft-ietf-ipsecme-ikev2-mlkem (hybrid ML-KEM)
- FIPS 203 (ML-KEM)
- RFC 9370 (parallel key exchanges guidance)