CISC-ND-001200 - The Cisco switch must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of remote maintenance sessions.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


Unapproved mechanisms used for authentication to the cryptographic module are not verified; therefore, they cannot be relied upon to provide confidentiality or integrity, and DOD data may be compromised.

Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network.

Currently, HMAC is the only FIPS-approved algorithm for generating and verifying message/data authentication codes in accordance with FIPS 198-1. Products that are FIPS 140-2 validated will have an HMAC that meets specification; however, the option must be configured for use as the only message authentication code used for authentication to cryptographic modules.

Separate requirements for configuring applications and protocols used by each application (e.g., SNMPv3, SSHv2, NTP, HTTPS, and other protocols and applications that require server/client authentication) are required to implement this requirement. Where SSH is used, the SSHv2 protocol suite is required because it includes Layer 7 protocols such as SCP and SFTP, which can be used for secure file transfers.


Enable FIPS mode via the command 'fips mode enable'.

Note: The switch will require a reboot for FIPS mode to be enabled.

See Also

Item Details

References: CAT|I, CCI|CCI-002890, Rule-ID|SV-220503r929034_rule, STIG-ID|CISC-ND-001200, STIG-Legacy|SV-110655, STIG-Legacy|V-101551, Vuln-ID|V-220503

Plugin: Cisco

Control ID: 9f171801c0709347ecd00be8b2468af6c19e02624b7c0f0b1c9818ce762546f2