ARST-RT-000430 - 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.

Information

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.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

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

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Arista_MLS_EOS_4-2x_Y24M07_STIG.zip

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-7a., CAT|II, CCI|CCI-001097, CCI|CCI-004931, Rule-ID|SV-256024r991787_rule, STIG-ID|ARST-RT-000430, Vuln-ID|V-256024

Plugin: Arista

Control ID: 73ed33a85e8de8f89079fad149e793cddf67a0ebeb5b560ed1290b7bc02b618b