V-69129

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 merely 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

Verify for OSPF that Authentication is not set to "None" and for BGP password has been configured.

Log onto vSphere Web Client with credentials authorized for administration.

Navigate and select Networking and Security >> select the "NSX Edges" tab on the left-side menu. 

Double-click the edgeID in question, as denoted by the "Logical Router" type.

Select the "Manage" tab on the top of the new screen >> Routing.

If OSPF is configured, select OSPF >> Area Definitions.

Select the configured areas.

Click the "pencil" icon.

Verify "authentication" is set to something other than "none".

If Authentication is set to "None", this is a finding.

If BGP is configured, select BGP >> Neighbors >> select the configured neighbor >> Click the "pencil" icon >> verify "password" is configured.

If a password has not been configured for BGP, this is a finding.