STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Arista MLS EOS 4.X Router Security Technical Implementation Guide

V-256003

CAT I (High)

The Arista perimeter router must be configured to not be a Border Gateway Protocol (BGP) peer to an alternate gateway service provider.

Rule ID

SV-256003r882351_rule

STIG

Arista MLS EOS 4.X Router Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-001414

Discussion

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.

Check Content

This requirement is not applicable for the DODIN backbone.

Review the Arista router configuration of the router connecting to the alternate gateway.

To verify no BGP neighbors are configured to the remote AS that belongs to the alternate gateway service provider and the static route is configured, execute the command "show ip route static".

ip route 192.168.67.0/24 12.15.4.9

If BGP neighbors are connecting the remote AS of the alternate gateway service provider, this is a finding.

Fix Text

This requirement is not applicable for the DODIN backbone.

Configure a static route on the perimeter router to reach the AS of a router connecting to an alternate gateway.

router(config)#ip route 192.168.67.0/24 12.15.4.9