The Cisco router must be configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions.

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 eavesdropping, potentially putting sensitive data (including administrator passwords) at risk of compromise and potentially allowing hijacking of maintenance sessions.

Review the Cisco router configuration to verify that it is compliant with this requirement.

SSH Example

ip ssh version 2 ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr

HTTPS Example

ip http secure-server ip http secure-ciphersuite aes-128-cbc-sha ip http secure-client-auth ip http secure-trustpoint CA_XXX

If the router is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm, this is a finding.

Configure the Cisco router to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm as shown in the examples below.

SSH Example

R1(config)#ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr

HTTPS Example

R2(config)#ip http secure-ciphersuite aes-128-cbc-sha