OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco switch must be configured to implement message authentication for all control plane protocols.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-221072CISC-RT-000020SV-221072r999681_ruleCCI-000366medium
Description
A rogue switch could send a fictitious routing update to convince a site's perimeter switch to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network, or used to disrupt the network's ability to communicate with other networks. This is known as a "traffic attraction attack" and is prevented by configuring neighbor switch authentication for routing updates. This requirement applies to all IPv4 and IPv6 protocols that are used to exchange routing or packet forwarding information; this includes all Interior Gateway Protocols (such as OSPF, EIGRP, and IS-IS) and Exterior Gateway Protocols (such as BGP), MPLS-related protocols (such as LDP), and multicast-related protocols.
STIGDate
Cisco NX OS Switch RTR Security Technical Implementation Guide2026-03-04

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (8) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.4.1
1.00
3.4.2
1.00
CCI1 mapping
CCI-000366
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-221072r999681_chk)

Review the switch configuration. Verify that neighbor switch authentication is enabled for all routing protocols. The configuration examples below depicts BGP, EIGRP, IS-IS and OSPF authentication. BGP Example router bgp 1 router-id 1.1.1.1 address-family ipv4 unicast neighbor 10.1.12.2 remote-as 2 password 3 3ec66c90c104ad13 EIGRP Example key chain EIGRP_KEY key 1 key-string xxxxxxx … … … interface Ethernet2/21 no switchport ip router eigrp 1 ip authentication mode eigrp 1 md5 ip authentication key-chain eigrp 1 EIGRP_KEY or router eigrp 1 authentication mode md5 authentication key-chain EIGRP_KEY Note: Interface authentication overrides process authentication. IS-IS Example interface Ethernet2/20 no switchport isis authentication-type md5 level-1 isis authentication key-chain xxxxx level-1 ip router isis 1 OSPF Example interface Ethernet2/2 no switchport ip ospf authentication ip ospf authentication key-chain OSPF_KEY ip router ospf 1 area 0.0.0.0 RIP Example interface Ethernet2/8 no switchport ip rip authentication mode md5 ip rip authentication key-chain RIP_KEY If authentication is not enabled on all routing protocols, this is a finding.

Fix Text (F-22776r409706_fix)

Configure authentication to be enabled for every protocol that affects the routing or forwarding tables. The example configuration commands below enable OSPF, EIGRP, IS-IS, and BGP authentication. BGP Example SW1(config)# switch bgp nn SW1(config-router)# neighbor 10.1.12.2 SW1(config-router-neighbor)# password xxxxxxxx SW1(config-router-neighbor)# end EIGRP Example Step 1: Configure the key chain. SW1(config)# key chain EIGRP_KEY SW1(config-keychain)# key 1 SW1(config-keychain-key)# key-string xxxxxx SW1(config-keychain-key)# exit SW1(config-keychain)# exit Step 2: Apply the key chain to the EIGRP process or each neighbor. Authentication for the EIGRP process SW1(config)# router eigrp 1 SW1(config-router)# authentication mode md5 SW1(config-router)# authentication key-chain XXXXXX SW1(config-router)# end or Authentication for the EIGRP neighbor SW1(config)# int e2/21 SW1(config-if)# ip authentication mode eigrp 1 md5 SW1(config-if)# ip authentication key-chain eigrp 1 xxxxx SW1(config-if)# end Note: Interface authentication overrides process authentication. IS-IS Example Step 1: Configure the key chain. SW1(config)# key chain ISIS_KEY SW1(config-keychain)# key 1 SW1(config-keychain-key)# key-string xxxxxx SW1(config-keychain-key)# exit SW1(config-keychain)# exit Step 2: Apply the key chain to each ISIS neighbor. SW1(config)# int e2/20 SW1(config-if)# isis authentication-type md5 level-1 SW1(config-if)# isis authentication key-chain xxxxx level-1 OSPF Example Step 1: Configure the key chain. SW1(config)# key chain OSPF_KEY SW1(config-keychain)# key 1 SW1(config-keychain-key)# key-string xxxxxx SW1(config-keychain-key)# exit SW1(config-keychain)# exit Step 2: Apply the key chain to each OSPF neighbor. SW1(config)# int e2/2 SW1(config-if)# ip ospf authentication SW1(config-if)# ip ospf authentication key-chain OSPF_KEY RIP Example Step 1: Configure the key chain. SW1(config)# key chain RIP_KEY SW1(config-keychain)# key 1 SW1(config-keychain-key)# key-string xxxxxx SW1(config-keychain-key)# exit SW1(config-keychain)# exit Step 2: Apply the key chain to each RIP neighbor. SW1(config)# int e2/8 SW1(config-if)# ip rip authentication mode md5 SW1(config-if)# ip rip authentication key-chain RIP_KEY