V-94221

Discussion

SP 800-52 provides guidance on using the most secure version and configuration of the TLS/SSL protocol. Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol. This requirement applies to TLS gateways (also known as SSL gateways) and is not applicable to VPN devices. Application protocols such as HTTPS and DNSSEC use TLS as the underlying security protocol and thus are in scope for this requirement. NIST SP 800-52 provides guidance. NIST SP 800-52 sets TLS version 1.1 as a minimum version; therefore, all versions of SSL are not allowed (including for client negotiation) either on DoD-only or public-facing servers.

Check Content

Verify that TLS forward proxy intermediary services are configured to comply with NIST 800-52 TLS settings.

1. Log on to the Web Management Console.
2. Click Configuration >> Visual Policy Manager. 
3. Click "Launch". While in the Visual Policy Manager, for each SSL Access Layer that is configured, Verify there is a rule with an action set to "Deny" that also has "Source" and "Destination" fields that contain restricted SSL/TLS protocols and ciphers.

If Symantec ProxySG providing forward proxy intermediary services for TLS is not configured to comply with the required TLS settings in NIST SP 800-52, this is a finding.