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 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Arista MLS EOS 4.2x Router Security Technical Implementation Guide

V-256044

CAT II (Medium)

The Arista perimeter router must be configured to block all outbound management traffic.

Rule ID

SV-256044r882474_rule

STIG

Arista MLS EOS 4.2x Router Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001097

Discussion

For in-band management, the management network must have its own subnet in order to enforce control and access boundaries provided by Layer 3 network nodes, such as routers and firewalls. Management traffic between the managed network elements and the management network is routed via the same links and nodes as that used for production or operational traffic. Safeguards must be implemented to ensure that the management traffic does not leak past the perimeter of the managed network.

Check Content

This requirement is not applicable for the DODIN backbone.

The Arista perimeter router of the managed network must be configured with an access control list (ACL) or filter on the egress interface to block all management traffic.

Step 1: To verify the configuration is blocking all outbound traffic destined to management network, execute the command "sh ip access-list".

ip access-list FILTER_MANAGEMENT_SUBNET
  deny ip any 172.20.1.0 0.0.0.255 log
  permit ip any any

Step 2: To verify the filter is applied on egress interface, execute the command "sh run int ethernet YY".

interface ethernet 3
ip access-group FILTER_MANAGEMENT_SUBNET out

If management traffic is not blocked at the perimeter, this is a finding.

Fix Text

This requirement is not applicable for the DODIN backbone.

Configure the Arista perimeter router of the managed network with an ACL or filter on the egress interface to block all outbound management traffic.

Step 1: Configure the filter to block all outbound traffic destined to the management network.

LEAF-1A(config-if-Et3)#ip access-list FILTER_MANAGEMENT_SUBNET
LEAF-1A(config-acl-FILTER_MANAGEMENT_SUBNET)#  deny ip any 172.20.1.0 0.0.0.255 log
LEAF-1A(config-acl-FILTER_MANAGEMENT_SUBNET)#  permit ip any any

Step 2: Apply the filter egress on the interface.

LEAF-1A(config-acl-FILTER_MANAGEMENT_SUBNET)#interface ethernet 3
LEAF-1A(config-if-Et3)#ip access-group FILTER_MANAGEMENT_SUBNET out