Workshop Description
Network architecture migration to PQC is not a single project but a sequenced transition across multiple protocol layers. TLS protects web traffic and API communications. IPsec and WireGuard protect VPN tunnels. PKI certificate chains authenticate every encrypted connection. DNSSEC protects name resolution. Each layer uses classical key agreement (RSA or ECDH) or digital signatures (RSA or ECDSA) that a cryptographically relevant quantum computer would break. The migration challenge is that these layers are interdependent: you cannot migrate TLS certificates without addressing the CA hierarchy, and you cannot update the CA hierarchy without planning for the larger certificate and CRL sizes that PQC algorithms produce.
This workshop works through that migration layer by layer. Participants examine TLS 1.3 hybrid key exchange deployment on reverse proxies and load balancers, with concrete data on handshake size increases and client compatibility. VPN migration covers IPsec IKEv2 PQC configuration on major vendor platforms (Cisco, Palo Alto, Fortinet) and the Rosenpass PQC layer for WireGuard. Certificate lifecycle management addresses CA hierarchy re-signing with ML-DSA, ACME protocol PQC support, and OCSP/CRL scaling for larger PQC signatures. Internal network coverage extends PQC to zero trust microsegmentation and DNSSEC zone signing. Each layer includes a rollback procedure and monitoring guidance for the transition period.
What participants cover
- TLS 1.3 hybrid mode: ML-KEM-768 + X25519 key exchange, ML-DSA-65 certificates, handshake overhead data, and phased deployment from reverse proxy to internal services
- VPN PQC migration: IPsec IKEv2 ML-KEM configuration on Cisco, Palo Alto, and Fortinet. WireGuard Rosenpass as an interim PQC layer. Remote access VPN prioritised over site-to-site.
- Certificate lifecycle: CA hierarchy migration (root re-signing, cross-signing), ACME PQC automation, and OCSP/CRL scaling strategies for ML-DSA signature sizes
- Internal network PQC: zero trust mTLS with PQC certificates, DNSSEC ML-DSA zone signing, and IDS/IPS compatibility with PQC handshakes (Suricata, Zeek)
- Compliance: NIST FIPS 203/204 timelines, CNSA 2.0 network encryption deadlines, and ENISA/BSI/ANSSI/NCSC migration guidance
- Migration sequencing: internet-facing TLS, then VPN, then internal east-west, then DNS. Rollback procedures and connection monitoring for each phase.