TLS
TLSv1.3 is the default for all communications. The tunnel protocol used for the VPN connection can be configured in Sites > General
Cipher suites and authentication
The following table describes the cipher suites and authentication methods used for each communication type:
Communication type | Cipher suite | Authentication |
|---|---|---|
Appliance to appliance (port 443) |
| Mutual certificate-based authentication with DN checking |
Client and admin to appliance (port 443 and 8443) |
| |
SSH to appliance |
| |
Client to Gateway tunnel |
| Mutual certificate-based authentication with DN checking |
Single Packet Authorization |
| |
Claim and entitlement token encryption |
| |
Database encryption |
| |
Backup file encryption | GPG symmetric ( |
Appliance certificates
Certificates generated by a Controller use SHA-512 with RSA, key size 4096.
The Certificate Authority (CA) has the following properties:
Maximum number of intermediate CAs: 0
basicConstraints=critical, CA:true, pathlen:0keyUsage=critical, digitalSignature, cRLSign, keyCertSignextendedKeyUsage=clientAuth, serverAuth(used for Controller-client authentication when communicating with appliances)
FIPS compliance
AppGate ZTNA updates FIPS compliance as soon as a compliant cryptographic module is available from wolfCrypt.
Version 6.4.1 and later: Desktop clients and appliances comply with FIPS 140-3 for appliance-to-appliance and client-to-appliance communication using the wolfCrypt module. See the certificate. Also see FIPS 140-3: Security Requirements for Cryptographic Modules.
Version 6.4.0: Desktop clients and appliances comply with FIPS 140-2.
Common Criteria and NIAP Protection Profile
Version 6.4.2 clients clients were certified in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme for the Protection Profile for Application Software Version 1.4, with the Functional Package for Transport Layer Security (TLS) Version 1.1 applied.
Version 7.0 appliances were filed for Common Criteria evaluation on May 19, 2026, in accordance with the CCEVS process for the Protection Profile for Application Software Version 2.0, with the Functional Package for Transport Layer Security Version 2.1 (TLS-PKG v2.1) and the Functional Package for X.509 Version 1.0 applied.