Detections
Analytics
JUEX-RT-000930 - The Juniper 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 routers to have the correct VRF defined with the appropriate RT.set routing-instances <name> description <'appropriate description'>
set routing-instances <name> instance-type vrf
set routing-instances <name> interface <ce-facing interface>.<logical unit>
set routing-instances <name> route-distinguisher 33:33 << Must match the design plan for 'customer 1'.
set routing-instances <name> vrf-target cust1:33:33 << Must match the design plan for 'customer 1'.
set routing-instances <name> vrf-table-label
set routing-instances <name> protocols ospf area <number> interface <ce-facing interface>.<logical unit>
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Juniper_EX_Switches_Y26M01_STIG.zip
Item Details
Audit Name: DISA Juniper EX Series Router v2r1
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6b., CAT|I, CCI|CCI-000366, CCI|CCI-004891, Rule-ID|SV-254065r997538_rule, STIG-ID|JUEX-RT-000930, Vuln-ID|V-254065
Plugin: Juniper
Control ID: 9945192af13125b334e66484ce1d6e9eca6368e34ded59b21dab85d3b788ab3b