Information
The neighbor password command enables authentication on a TCP connection with a BGP peer
When utilizing BGP the threat profile becomes much larger as routes external to the data center will be updating routing information in the devices. Much like with the IGP an attacker could redirect traffic to an insecure location where traffic could be analyzed and confidential information extracted. In the case of BGP a peer AS can send erroneous prefix information and as a result could allow packets to be sent to an insecure network. It is recommended that peer authentication be used for all peers. A password or key should be defined for each BGP neighbor regardless of the peer's autonomous system.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Configure passwords for each neighbor as appropriate
router bgp
neighbor {IP address} password