OpenControls Logo

STIG Viewer

STIGViewer Support

The out-of-band management (OOBM) Arista gateway router must be configured to block any traffic destined to itself that is not sourced from the OOBM network or the NOC.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256024ARST-RT-000430SV-256024r991787_ruleCCI-001097medium
Description
If the gateway router is not a dedicated device for the OOBM network, several safeguards must be implemented for containment of management and production traffic boundaries. It is imperative that hosts from the managed network are not able to access the OOBM gateway router.
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-256024r991787_chk)

This requirement is not applicable for the DODIN backbone. Review the access control list (ACL) or filter for the router receive path. Verify only traffic sourced from the OOBM network or the NOC is allowed to access the router. Note: If the platform does not support the receive path filter, verify all non-OOBM interfaces have an ingress ACL to restrict access to that interface address or any of the router's loopback addresses to only traffic sourced from the management network. An exception would be to allow packets destined to these interfaces used for troubleshooting, such as ping and traceroute. Step 1: To verify the ACL is configured, execute "show ip access-list OOBM_ACL". Step 2: Determine the NOC management network subnet, which is 172.16.12.0/24. Step 3: Verify the ACL restricts all management plane traffic. ip access-list OOBM_ACL permit tcp 192.168.10.0/24 any eq ssh permit udp host 172.16.12.42 any eq snmp permit udp host 172.16.12.41 any eq ntp permit icmp 172.16.12.0/24 any deny ip any any log Step 4: To verify the ACL is applied ingress on the OOBM interface, execute the command "sh run int Eth YY". interface ethernet 1 description LAN link ip access-group OOBM_ACL in If the Arista router does not block any traffic destined to itself that is not sourced from the OOBM network or the NOC, this is a finding.

Fix Text (F-59643r882413_fix)

This requirement is not applicable for the DODIN backbone. Ensure traffic from the managed network is not able to access the OOBM gateway router using either receive path or interface ingress ACLs. Step 1: Configure the ACL to restrict all management plane traffic. ip access-list OOBM_ACL permit tcp 192.168.10.0/24 any eq ssh permit udp host 172.16.12.42 any eq snmp permit udp host 172.16.12.41 any eq ntp permit icmp 172.16.12.0/24 any deny ip any any log Step 2: Apply the ACL ingress. Execute the command "sh run int Eth YY". interface ethernet 1 description LAN link ip access-group OOBM_ACL in