Rule ID
SV-255765r961554_rule
Version
V1R2
This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents of those sessions will be susceptible to manipulation, potentially allowing alteration and hijacking of maintenance sessions. Satisfies: SRG-APP-000411-NDM-000330, SRG-APP-000412-NDM-000331
Log on to the MQ Appliance CLI as a privileged user. Display the SSL Server Profile associated with the WebGUI (CLI). Enter: co show web-mgmt Verify the following: An ssl-server is associated with the WebGUI. [Note the name of the ssl-server.] List parameters of the SSL Server (CLI). Enter: co crypto ssl-server <ssl-server name> show Verify the following: protocols TLSv1d2 If TLS protocol is not configured for use with the ssl-server, this is a finding.
Log on to the MQ Appliance CLI as a privileged user. Display the SSL Server Profile associated with the WebGUI (CLI). Enter: co show web-mgmt [Note the name of the ssl-server.] Define the cache parameters of the SSL Server (CLI). Enter: co crypto ssl-server <ssl-server name> protocols TLSv1d2 exit exit write mem y