Post-quantum hybrid mode in AppGate ZTNA

Prev Next

Starting in AppGate ZTNA v7.0, you can protect connections between the clients and Gateways and between clients and Controllers against attacks from future quantum computers. Post-quantum hybrid mode is off by default, and you enable it separately on each appliance.

An attacker can record encrypted traffic today and store it until a quantum computer can break its classical key exchange. Post-quantum hybrid mode adds a post-quantum key exchange to each TLS handshake where both sides support it. Traffic from these connections stays protected against future quantum decryption.

The U.S. Department of Defense (DoD), the National Security Agency (NSA), and the Cybersecurity and Infrastructure Security Agency (CISA) require vendors to begin migrating to quantum-safe cryptography. Post-quantum hybrid mode is the first phase of that migration in AppGate ZTNA.


How post-quantum hybrid mode works

In hybrid mode, each TLS v1.3 handshake performs two key exchanges in parallel and combines the results into one shared secret. To decrypt the session, an attacker must break both key exchanges. As a result, the connection is at least as strong as a classical-only connection.

The hybrid key exchange group combines these algorithms:

Component

Algorithm

Protects against

Classical

Elliptic-curve Diffie-Hellman over P-256

Current attacks

Post-quantum

Module-lattice-based key-encapsulation mechanism (ML-KEM-768), standardized by the National Institute of Standards and Technology (NIST) in Federal Information Processing Standard (FIPS) 203

Future quantum attacks

The combined group appears in logs and in the admin UI as SECP256R1MLKEM768.

Negotiation and fallback

When you enable post-quantum hybrid mode, the appliance offers both the hybrid group and classical groups, and it prefers the hybrid group. If the other side of the connection does not support the hybrid group, the connection uses a classical group. The connection succeeds in both cases. Because of this fallback, clients can connect to Controllers and Gateways whether or not those appliances have hybrid mode enabled.

Connections covered

Post-quantum hybrid mode applies to TLS connections that the appliance terminates, including:

  • Client tunnels to a Gateway, over both TLS v1.3 and QUIC

  • Client tunnels to a Controller, over both TLSv1.3 and QUIC

  • HTTPS connections to the Gateway or Controller appliance, including the admin UI and the admin API

  • Internal TLS connections used for logging and configuration on the appliance

Diagram shows clients and administrators connecting to Controller and Gateway through post-quantum hybrid TLS termination.


Requirements and limitations

Review these requirements before you enable post-quantum hybrid mode on any appliance:

  • FIPS mode: Post-quantum hybrid mode is not compatible with FIPS mode. The ML-KEM implementation in AppGate ZTNA v7.0 is not FIPS-validated.

  • Scope: The setting is local to each appliance. Enabling it on one appliance does not enable it on any other appliance in the Collective.

  • Mobile clients: Mobile clients do not support quantum-safe encryption. They can still connect to appliances that have quantum-safe encryption enabled, but they use only classical key exchange.

  • Gateway restart: Changing the setting on a Gateway restarts the tunnel service. All active client tunnels on that Gateway disconnect and reconnect.

  • Fallback: A connection uses the hybrid group only when both sides offer it. Otherwise, the connection uses a classical group.

NOTE

Enable post-quantum hybrid mode on Gateways during a maintenance window to limit the impact of disconnected client tunnels.

Plan for a phased rollout

Because appliances with and without hybrid mode continue to communicate, you can enable it one appliance at a time. Enable it on every Controller, Gateway, LogServer, and Portal that requires post-quantum protection, and then verify each appliance.


Enabling post-quantum hybrid mode

To enable post-quantum hybrid mode on an appliance with the cz-config command, complete these steps:

  1. Connect to the appliance using SSH.

  2. Run this command:

sudo cz-config set tls/pq true -j

The appliance regenerates its TLS configuration. On a Gateway, the tunnel service restarts and active client tunnels reconnect.

  1. Repeat these steps on each appliance that requires post-quantum protection.

  2. Verify that connections use the hybrid group, as described in Verify post-quantum connections.


Verify post-quantum connections

You can confirm which key exchange group each client tunnel negotiated in the admin UI or in the audit log. In TLS v1.3, the cipher suite does not identify the key exchange group. Use one of the following methods instead.

Check Gateway Stats in the admin UI

In the Active Sessions page, the Gateway Stats tab displays the Key Exchange Group that each active tunnel uses.

Active session details showing Gateway stats and key exchange group information.

Check the tunnel_connected audit event

Each time a client tunnel connects, the Gateway writes a tunnel_connected audit event. Starting in AppGate ZTNA v7.0, this event includes these fields:

Field

Description

cipher

The TLS cipher suite, such as TLS13-AES256-GCM-SHA384.

negotiated_group

The key exchange group the tunnel negotiated.

Use the value of negotiated_group to confirm whether the tunnel uses post-quantum hybrid mode:

Value

Mode

SECP256R1MLKEM768

Post-quantum hybrid mode

A classical curve, such as SECP256R1.

Classical key exchange

If a tunnel uses a classical group, confirm that you enabled post-quantum hybrid mode on that Gateway. Then confirm that the client version supports the hybrid group.


Disabling post-quantum hybrid mode

To return an appliance to classical key exchange only, complete the following steps:

  1. Connect to the appliance using SSH.

  2. Run this command:

sudo cz-config set tls/pq false -j

On a Gateway, the tunnel service restarts and active client tunnels reconnect.