SLEM 5 must implement DoW-approved encryption to protect the confidentiality of SSH remote connections.

Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.

Remote access is access to DoW nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.

Encryption provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection (e.g., RDP), thereby providing a degree of confidentiality. The encryption strength of a mechanism is selected based on the security categorization of the information.

The system will attempt to use the first cipher presented by the client that matches the server list. Listing the values "strongest to weakest" is a method to ensure the use of the strongest cipher available to secure the SSH connection.

Verify that SLEM 5 implements DoW-approved encryption to protect the confidentiality of SSH remote connections with the following command:

     > sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH '^\s*ciphers'
     /etc/ssh/sshd_config:Ciphers aes256-ctr,aes192-ctr,aes128-ctr

If any ciphers other than "aes256-ctr", "aes192-ctr", or "aes128-ctr" are listed, the order differs from the example above, the line is commented out, or the "Ciphers" keyword is missing, or conflicting results are returned, this is a finding.

Configure the SSH server to only implement FIPS 140-2/140-3 approved ciphers.

Add or modify the following line in the "/etc/ssh/sshd_config" file:

Ciphers aes256-ctr,aes192-ctr,aes128-ctr

Restart the SSH daemon:

     > sudo systemctl restart sshd.service