STIGQter STIGQter: STIG Summary: Arista MLS EOS 4.X Router Security Technical Implementation Guide Version: 2 Release: 2 Benchmark Date: 02 Apr 2025:

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.

DISA Rule

SV-256024r991787_rule

Vulnerability Number

V-256024

Group Title

SRG-NET-000205-RTR-000011

Rule Version

ARST-RT-000430

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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

Check Contents

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.

Vulnerability Number

V-256024

Documentable

False

Rule Version

ARST-RT-000430

Severity Override Guidance

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.

Check Content Reference

M

Target Key

5513