Detections
Analytics

1.39 CISC-RT-000580

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

The Cisco BGP switch must be configured to use its loopback address as the source address for iBGP peering sessions.

GROUP ID: V-221112
RULE ID: SV-221112r999769

Using a loopback address as the source address offers a multitude of uses for security, access, management, and scalability of the BGP switches. It is easier to construct appropriate ingress filters for switch management plane traffic destined to the network management subnet since the source addresses will be from the range used for loopback interfaces instead of a larger range of addresses used for physical interfaces. Log information recorded by authentication and syslog servers will record the switch's loopback address instead of the numerous physical interface addresses.

When the loopback address is used as the source for eBGP peering, the BGP session will be harder to hijack since the source address to be used is not known globally, making it more difficult for a hacker to spoof an eBGP neighbor. By using traceroute, a hacker can easily determine the addresses for an eBGP speaker when the IP address of an external interface is used as the source address. The switches within the iBGP domain should also use loopback addresses as the source address when establishing BGP sessions.

Solution

Configure the switch to use its loopback address as the source address for all iBGP peering.

SW1(config)# router bgp xx
SW1(config-router)# neighbor 10.1.12.2
SW1(config-router-neighbor)# update-source lo0
SW1(config-router-neighbor)# end

See Also

https://workbench.cisecurity.org/benchmarks/22581

Item Details

References: CAT|III, CCI|CCI-004931, CSCv7|13.3, Rule-ID|SV-221112r999769_rule, STIG-ID|CISC-RT-000580, Vuln-ID|V-221112

Plugin: Cisco

Control ID: ee8db83b4492263d34e3b6114680012ab09f7ae376af18f5661952e781d5d288