Detections
Analytics
ARST-RT-000740 - The PE router must be configured to have each Virtual Routing and Forwarding (VRF) instance with the appropriate Route Target (RT).
Information
The primary security model for an MPLS L3VPN as well as a VRF-lite infrastructure is traffic separation. Each interface can only be associated to one VRF, which is the fundamental framework for traffic separation. Forwarding decisions are made based on the routing table belonging to the VRF. Control of what routes are imported into or exported from a VRF is based on the RT. It is critical that traffic does not leak from one COI tenant or L3VPN to another; hence, it is imperative that the correct RT is configured for each VRF.NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Configure all J-PE Arista routers to have the correct VRF defined with the appropriate RT.Configure the route-target's for import and export.
PE11(config)#router bgp 65000
PE11(config-router-bgp)#vrf PROD
PE11(config-router-bgp-vrf-PROD)#rd 200:200
PE11(config-router-bgp-vrf-PROD)#route-target import vpn-ipv4 200:200
PE11(config-router-bgp-vrf-PROD)#route-target export vpn-ipv4 200:200
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Arista_MLS_EOS_4-X_Y25M07_STIG.zip
Item Details
Audit Name: DISA Arista MLS EOS 4.X Router STIG v2r2
Category: CONTINGENCY PLANNING
References: 800-53|CP-8, CAT|I, CCI|CCI-004931, Rule-ID|SV-256053r991792_rule, STIG-ID|ARST-RT-000740, Vuln-ID|V-256053
Plugin: Arista
Control ID: 7bb41855a5d6c06453bcdd99e24c24689e8252d6074b66349ba96845b846bd34