CISC-RT-000040 - The Cisco router must be configured to use encryption for routing protocol authentication - EIGRP
A rogue router could send a fictitious routing update to convince a site's perimeter router 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 router authentication for routing updates. However, using clear-text authentication provides little benefit since an attacker can intercept traffic and view the authentication key. This would allow the attacker to use the authentication key in an attack. 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. NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Configure all routing protocol authentications to encrypt the authentication key. BGP Example R1(config)#router bgp nn R1(config-router)#neighbor x.x.x.x password xxxxxx EIGRP Example R2(config)#int g0/1 R2(config-if)#ip authentication mode eigrp 1 md5 R2(config-if)#ip authentication key-chain eigrp 1 EIGRP_KEY_CHAIN IS-IS Example R5(config)#int g0/1 R5(config-if)#isis authentication mode md5 R5(config-if)#isis authentication key-chain ISIS_KEY_CHAIN OSPF Example R1(config)#int g1/0 R1(config-if)#ip ospf authentication message-digest R1(config-if)#ip ospf message-digest-key 1 md5 xxxxxx RIP Example R2(config)#int g1/0 R2(config-if)#ip rip authentication mode md5 R2(config-if)#ip rip authentication key-chain RIP_KEY_CHAIN