The Cisco switch must be configured to implement replay-resistant authentication mechanisms for network access to privileged accounts.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-220488CISC-ND-000530SV-220488r1026069_ruleCCI-001941medium
Description
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.
STIGDate
Cisco NX OS Switch NDM Security Technical Implementation Guide2024-09-10

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.5.4
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-001941
1.00
  • DISA · V3R2 · disa_xccdf · related

Details

Check Text (C-220488r1026069_chk)

Review the Cisco router configuration to verify it is compliant with this requirement as shown in the example below. SSH Example ssh macs hmac-sha2-256 hmac-sha2-512 NOTE: Using "fips mode enable" to enable all FIPS protocols disables TACACS+ and RADIUS, which is required for authentication server requirements. It is recommended to enable FIPS-validated protocols manually and keep FIPS mode disabled. If the Cisco router is not configured to use FIPS-validated HMAC to protect the integrity of remote maintenance sessions, this is a finding.

Fix Text (F-22192r1015484_fix)

Configure SSH to use FIPS-validated HMAC for remote maintenance sessions as shown in the following example: SSH Example R1(config)#ssh macs hmac-sha2-256 hmac-sha2-512