Title

The ISEC7 EMM Suite must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access. (Cat II impact)

Discussion

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 virtual private network (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 DoD-only or on public-facing servers.

Check Content

Login to the EMM Console. Navigate to Administration >> Configuration >> Apache Tomcat Settings. Verify sslProtocol is set to TLSv1.2. If the sslProtocol is not set to TLSv1.2, this is a finding.

Fix Text

Login to the EMM Console. Navigate to Administration >> Configuration >> Apache Tomcat Settings. Using the dropdown menu for sslProtocol, select TLSv1.2. Click Update. Restart the ISEC7 EMM Suite Web service.

Additional Identifiers

Rule ID: SV-224762r505933_rule

Vulnerability ID: V-224762

Group Title: SRG-APP-000014

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.