What changed in Cisco NX OS Switch NDM STIG V3R6V3R6 changes

Title

The Cisco switch must be configured to authenticate Network Time Protocol (NTP) sources using authentication withat is FIPS-cryptogramphlicallynt balgorithmsed.

Check text

Review the Cisco switch configuration to verify that it isauthenticates compliantNTP sources using authentication with thisFIPS-compliant requirementalgorithms as shown in the configuration example below: show running-config ntp ntp distributeauthentication-key 1 md5 xxxxxx ntp server 10.1.12.10 key 1 ntp server 10.1.22.13 trusted-key 1 ntp authenticate ntp Note: authenticationCisco NX-keyOS 1is hmac-sha2-256limited xxxxxx ntpto trusted-keyMD5 1 ntpfor commitNTP authentication, and incurs a permanent finding as it is not FIPS compliant. MD5 partially reduces the risk but cannot fully mitigate it. If the Cisco switch is not configured to authenticate NTP sources using authentication thatwith isFIPS-compliant cryptographically basedalgorithms, this is a finding.

Fix text

Configure the Cisco switch to authenticate NTP sources using authentication thatwith isFIPS-compliant cryptographicallyalgorithms based as shown in the example below: SW1# configure terminal SW1(config)# ntpfeature authenticatentp SW1(config)# ntp authentication-key 1 hmac-sha2-256md5 xxxxxx SW1(config)# ntp trusted-key 1 SW1(config)# ntp server 10.1.12.10 key 1authenticate SW1(config)# ntp server 10.1.2212.1310 key 1 SW1(config)# ntp commit SW1(config)# end SW1# copy running-config startup-config Note: The ntp commit command can be omitted if CFS is not enabled for NTP.

Discussion

If NetworkNTP Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.

V-220502 in V3R6