Rule version HFFS-RT-000004 · STIG v1 · 2026-09-02
The perimeter router will not use a routing protocol to advertise NIPRNet addresses to Alternate Gateways. Most ISPs use Border Gateway Protocol (BGP) to share route information with other autonomous systems, that is, any network under a different administrative control and policy than a local site. If BGP is configured on the perimeter router, no BGP neighbors will be defined to peer routers from an AS belonging to any Alternate Gateway. The only allowable method is a static route to reach the Alternate Gateway.
Review the configuration of the HP FlexFabric Switch connecting to the AG.
Verify there are no BGP neighbors configured to the remote AS that belongs to the AG service provider. There should be no BGP peers displayed.
If there are BGP neighbors configured that belong to the AG service provider, this is a finding.
[HP] display bgp peer ipv4
BGP local FlexFabric Switch ID: 2.2.2.0 Local AS number: 1472 Total number of peers: 1 Peers in established state: 0
* - Dynamically created peer Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
Configure a static route on the perimeter HP FlexFabric Switch to reach the AS of a HP FlexFabric Switch connecting to an Alternate Gateway.
[HP] ip route-static 11.11.11.0 16 12.12.12.2