STIGViewer Support

The out-of-band management (OOBM) Arista gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-256023ARST-RT-000420SV-256023r991786_ruleCCI-001097medium
Description
The OOBM network is an IP network used exclusively for the transport of OAM&P data from the network being managed to the OSS components located at the NOC. Its design provides connectivity to each managed network device, enabling network management traffic to flow between the managed network elements and the NOC. This allows the use of paths separate from those used by the managed 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
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.

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-256023r991786_chk)

This requirement is not applicable for the DODIN backbone. Review the network topology diagram to determine connectivity between the managed network and the NOC. Review the OOBM gateway router configuration to validate the path that the management traffic traverses. Step 1: To verify only management traffic is forwarded through the OOBM interface or IPsec tunnel, execute the command "sh ip access-list". ip access-list OOBM_to_MGMT 10 permit tcp 10.10.10.0/24 host 10.20.10.1 eq ssh telnet 20 permit ip 10.10.10.0/24 192.168.10.0/24 30 permit udp 10.20.20.0/24 any eq bootps snmp Step 2: To verify the ACL is applied outbound on the OOBM interface, execute the command "sh run int Eth YY". interface ethernet 1 description OOBM to MGMT link ip access-group OOBM_to_MGMT out If traffic other than authorized management traffic is permitted through the OOBM interface or IPsec tunnel, this is a finding.

Fix Text (F-59642r882410_fix)

This requirement is not applicable for the DODIN backbone. Configure filters based on port, source IP address, and destination IP address to permit only authorized management traffic into IPsec tunnels or the OOBM interface used for forwarding management data. Step 1: To configure an ACL to allow only management traffic to be forwarded through the OOBM interface or IPsec tunnel, execute the command "sh ip access-list". ip access-list OOBM_to_MGMT 10 permit tcp 10.10.10.0/24 host 10.20.10.1 eq ssh 20 permit ip 10.10.10.0/24 192.168.10.0/24 30 permit udp 10.20.20.0/24 any eq bootps snmp Step 2: To apply the ACL outbound on the OOBM interface, execute the command "sh run int Eth YY". interface ethernet 1 description OOBM to MGMT link ip access-group OOBM_to_MGMT out