Page History

Select the required TLS protocol method from the drop-down list:

• TLSv1.0 – Only 2 – Only allow TLS version 1version 1.0 2 protocol (RFC 2246).5246). When selected, connections from endpoints with earlier TLS versions are rejected.  
• TLSv1.2 3 – Only allow TLS version 1.2 3 protocol (RFC 52468446). When selected, connections from endpoints with earlier TLS versions are rejected.  

Adds or restricts the cipher suites offered by this device during a TLS handshake.

Some examples are:

• TLSv1.2
  All cipher suites from TLS version 1.0 2 specification.
• TLSv1+HIGH:!eNULL:!aNULL
  TLSv1 cipher suite. Key size 128 bit or more. No cipher suites with no authentication. No cipher suites with no encryption.
• TLSv1.2
  All cipher suites from TLS version 1.2 specification.TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256
  TLSv1.3 cipher suites

Interface

Provides options to select the interface policies.

Select the X.509 certificate for the interface in PEM format. Select the required certificate from the options in the drop-down list. 

Note: Make sure that the common name (CN) in the certificate matches the domain name or IP of the interface.

Select the peer certificate verification policy from the drop-down list:

• No check – The peer certificate is not verified.
• Verify if provided – Send a client certificate request to clients but continue handshake if the client does not return a certificate. Fail if the certificate is returned and the verification fails.
• Require and Verify – Send a client certificate request to clients and continue only if the client sends a certificate and the certificate verification succeeds.
• Require and Verify Once – Send a client certificate request to clients and continue only if the client sends a certificate and the certificate verification succeeds. Client certificate requests are not sent during renegotiation.