OpenControls Logo

STIG Viewer

STIGViewer Support

The Arista router must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256025ARST-RT-000440SV-256025r991788_ruleCCI-001097medium
Description
The OOBM access router will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic, thereby providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network.
STIGDate
Arista MLS EOS 4.X Router Security Technical Implementation Guide2025-02-20

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (19) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

BCD-10.4Alternate Communications Channels
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
MON-01Continuous Monitoring
1.00

+9 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (11) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-5(2)Capacity, Bandwidth, and Redundancy
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
SI-4System Monitoring
1.00

+1 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.1
1.00
3.13.2
1.00
3.13.5
1.00
CCI2 mappings
CCI-001097
1.00
CCI-004931
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-01
1.00
PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
PR.IR-01
1.00

Who does this work

15 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-256025r991788_chk)

Step 1: To verify the Arista router managed interface has an inbound and outbound ACL configured, execute "show run int Eth YY". router#show interface Ethernet 3 interface ethernet 3 ip access-group FILTER_INBOUND in ip access-group FILTER_OUTBOUND out Step 2: To verify the ingress filter only allows management, IGP, and ICMP traffic, execute "show ip access-list". router#show ip access-list ip access-list FILTER_INBOUND 10 permit ospf any any 20 permit icmp any any echo 30 permit icmp any any echo-reply 40 permit ip 10.10.10.0/24 any 50 deny ip any any log ! ip access-list FILTER_OUTBOUND 10 permit ospf any any 20 permit icmp any any echo 30 permit icmp any any echo-reply 40 permit ip any 10.10.10.0/24 50 deny ip any any log ! Note: If the management interface is a true OOBM interface, this requirement is not applicable. If the Arista router does not restrict traffic that ingresses and egresses the management interface, this is a finding.

Fix Text (F-59644r882416_fix)

If the Arista management interface is a routed interface, it must be configured with both an ingress and egress ACL. Step 1: Configure the ingress filter to only allow management, IGP, and ICMP traffic. LEAF-1A(config)#ip access-list FILTER_INBOUND LEAF-1A(config-acl-FILTER_INBOUND)#permit ospf any any LEAF-1A(config-acl-FILTER_INBOUND)#permit icmp any any echo LEAF-1A(config-acl-FILTER_INBOUND)#permit icmp any any echo-reply LEAF-1A(config-acl-FILTER_INBOUND)#permit ip 10.10.10.0/24 any LEAF-1A(config-acl-FILTER_INBOUND)#deny ip any any log Step 2: Configure the outbound filter to only allow management, IGP, and ICMP traffic. LEAF-1A(config)#ip access-list FILTER_OUTBOUND LEAF-1A(config-acl-FILTER_OUTBOUND)#permit ospf any any LEAF-1A(config-acl-FILTER_OUTBOUND)#permit icmp any any echo LEAF-1A(config-acl-FILTER_OUTBOUND)#permit icmp any any echo-reply LEAF-1A(config-acl-FILTER_OUTBOUND)#permit ip any 10.10.10.0/24 LEAF-1A(config-acl-FILTER_OUTBOUND)#deny ip any any log Step 3: Set the managed interface to have an inbound and outbound ACL configured. LEAF-1A(config)#interface ethernet 3 LEAF-1A(config-if-Et3)# ip access-group FILTER_INBOUND in LEAF-1A(config-if-Et3)# ip access-group FILTER_OUTBOUND out