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.
Configure TLS forward proxy intermediary services to comply with NIST SP 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, click Policy >> Add SSL Access Layer.
4. Right-click the 'Source' field of the existing rule and select 'Set'. Click 'New' and select 'Combined Source Object'.
5. Click 'New' and select 'Client Negotiated Cipher'. Select all ciphers that should be permitted and click 'OK'.
6. Click the upper 'Add' button and click the 'Negate' checkbox.
7. Click 'New' and select 'Client Negotiated SSL Version'. Select all SSL versions that should be permitted and click 'OK'.
8. Click the upper 'Add' button.
9. Click 'OK' and then 'OK' again.
10. Repeat steps 4 to 9 for the 'Destination' field, using the 'Server Negotiated Cipher' and 'Server Negotiated SSL Version' objects.
11. Right-click the 'Action' field of the rule, click 'Set', and select 'Deny'.
12. Click File >> Install Policy on SG Appliance.
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system BlueCoat.