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. 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.
Configure authentication to be enabled for all control plane protocols as shown in the example below. [edit protocols ospf area 0.0.0.0] set interface ge-0/0/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/1/0 authentication simple-password xxxxxxxxxxxx set interface ge-0/2/0 authentication simple-password xxxxxxxxxxxx [edit protocols isis] set level 1 authentication-type md5 set level 1 authentication-key xxxxxxxx set level 2 authentication-type md5 set level 2 authentication-key xxxxxxxx [edit protocols rip] set authentication-type md5 set authentication-key xxxxxxxx [edit protocols bgp group AS_2 neighbor x.x.x.x] set authentication-key xxxxxxxxxxxxxxx [edit protocols ldp] set session 10.1.2.2 authentication-key xxxxxxxxxx