Rule ID
SV-216577r1117237_rule
Version
V3R4
CCIs
ISPs use BGP to share route information with other autonomous systems (i.e., other ISPs and corporate networks). If the perimeter router was configured to BGP peer with an ISP, NIPRNet routes could be advertised to the ISP, thereby creating a backdoor connection from the internet to the NIPRNet.
This requirement is not applicable for the DODIN backbone. Review the router configuration and verify that it is not BGP peering with an approved gateway service provider. Step 1: Determine the IP address of the ISP router. interface GigabitEthernet0/2 description Link to ISP ip address x.22.1.15 255.255.255.240 Step 2: Verify that the router is not BGP peering with this router. router bgp nn no synchronization bgp log-neighbor-changes neighbor x.11.1.7 remote-as nn neighbor x.11.1.7 password xxxxxxx no auto-summary In the example above, the router is not peering with the ISP. If the router is BGP peering with an approved gateway service provider, this is a finding.
This requirement is not applicable for the DODIN backbone. Remove any BGP neighbors belonging to the approved gateway service provider and configure a static route to forward internet-bound traffic to the approved gateway as shown in the example below. R5(config)#ip route 0.0.0.0 0.0.0.0 x.22.1.14