Rule ID
SV-288253r1252951_rule
Version
V1R0.1
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 Transport Layer Security (TLS) gateways (also known as Secure Sockets Layer [SSL] gateways), web servers, and web applications 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 for client negotiation on either DoW-only or public-facing servers.
Review the application documentation and deployed configuration to determine whether the application's remote access mechanism uses TLS 1.2 or greater to protect the confidentiality and integrity of all remote access sessions. If the application's remote access mechanism does not use TLS 1.2 or greater to protect the confidentiality and integrity of all remote access sessions, this is a finding.
Navigate to the remote access configuration within the application. Configure the application's remote access mechanism to use TLS 1.2 or greater to protect the confidentiality and integrity of all remote access sessions.