V-217012

Discussion

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.

Check Content

Review the router configuration. Verify that neighbor router authentication is enabled for all routing protocols as shown in the example configuration below.

protocols {
    bgp {
        group AS_5 {
            type external;
            peer-as 5;
            neighbor x.x.x.x {
                authentication-key "$8$tBga0ORx7VsYoIEgJ"; ## SECRET-DATA
            }
        }
    }
    ospf {
        area 0.0.0.0 {
            interface ge-0/0/0.0 {
                authentication {
                    simple-password "$8$NHVb2mPQ3nCYg/t"; ## SECRET-DATA
                }
            }
            interface ge-0/1/0.0 {
                authentication {
                    simple-password "$8$Lgb7NbHkPTQnVwF/"; ## SECRET-DATA
                }
            }
            interface lo0.0;
            interface ge-0/2/0.0 {
                authentication {
                    simple-password "$8$7DdVY.mTF39s26A"; ## SECRET-DATA
                }
            }
        }
    }
   isis {
        level 1 {
            authentication-key "$8$n2OT9CuvMXN-wp0VY"; ## SECRET-DATA
            authentication-type md5;
        }
        level 2 {
            authentication-key "$8$8G9x7ViHm5T3dbz6"; ## SECRET-DATA
            authentication-type md5;
        }
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
    }
    ldp {
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
        session 10.3.3.3 {
            authentication-key "$8$3hus/u1ylMNVYX7qf"; ## SECRET-DATA
        }
        session 10.1.2.2 {
            authentication-key "$8$Qq0I3nCrlMLX-9A7V"; ## SECRET-DATA
        }
    }
    rip {
        authentication-type md5;
        authentication-key "$8$34fM/u1ylMNVYX7qf"; ## SECRET-DATA
        group RIP_GROUP {
                 neighbor ge-1/0/1.0;
        }
    }
}

If authentication is not enabled for all control plane protocols, this is a finding.