V2R2 changes
Arista MLS EOS 4.X Router STIG V2R2 (2025-04-02) replaced V1R1 (2023-02-01): 10 checks updated. It has 75 checks, against 75 in V1R1.
V2R2 checklistV1R1 checklist Compare V1R1 and V2R2 in STIG Compare
- 0 added
- 0 removed
- 10 updated
Updated fields: CCIs 10Title 1
Updated in V2R2 (10)
V-256023CAT IIThe out-of-band management (OOBM) Arista gateway router must be configured to forward only authorized management traffic to the Network Operations Center (NOC).CCIs
V-256024CAT IIThe 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.CCIs
V-256025CAT IIThe Arista router must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface.Title, CCIs
Title
The Arista router must be configured to only permit management traffic that ingresses and egresses the out-of-band management (OOBM) interface.
CCIs
CCI-001097CCI-001097,CCI-004931
V-256048CAT IIIThe Arista BGP router must be configured to use its loopback address as the source address for iBGP peering sessions.CCIs
V-256049CAT IIIThe MPLS router must be configured to use its loopback address as the source address for LDP peering sessions.CCIs
V-256052CAT IThe PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.CCIs
V-256053CAT IThe PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT).CCIs
V-256054CAT IIThe PE router must be configured to have each VRF with the appropriate Route Distinguisher (RD).CCIs
V-256055CAT IThe PE router providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit.CCIs
V-256056CAT IIIThe Arista Multicast Source Discovery Protocol (MSDP) router must be configured to use its loopback address as the source address when originating MSDP traffic.CCIs
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V2R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.