The 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.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-256052 | ARST-RT-000730 | SV-256052r991791_rule | CCI-004931 | high |
| Description | ||||
| The primary security model for an MPLS L3VPN infrastructure is traffic separation. The service provider must guarantee the customer that traffic from one VPN does not leak into another VPN or into the core, and that core traffic must not leak into any VPN. Hence, it is imperative that each CE-facing interface can only be associated to one VRF—that alone is the fundamental framework for traffic separation. | ||||
| STIG | Date | |||
| Arista MLS EOS 4.X Router Security Technical Implementation Guide | 2025-02-20 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2equal to
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (5) derived by us, not asserted by any source
Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1our copyintersects(normalised)
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-004931
1.00
- DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
Details
Check Text (C-256052r991791_chk)
Review the design plan for deploying L3VPN and VRF-lite.
Review all CE-facing interfaces and verify the proper VRF is defined.
To verify the interfaces toward CE facing with proper VRF defined, execute the command "sh run int ethernet YY".
vrf instance PROD
vrf instance DEVP
ip routing vrf PROD
ip routing vrf DEVP
interface Ethernet3
no routerport
vrf PROD
ip address 10.1.99.11/24
interface Ethernet4
no routerport
vrf DEVP
ip address 10.11.5.11/24
If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.
Fix Text (F-59671r882497_fix)
Configure the Arista PE router to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.
Configure the VRF on the CE facing interfaces.
PE11(config)#vrf instance PROD
PE11(config)#vrf instance DEVP
!
PE11(config)#ip routing vrf PROD
PE11(config)#ip routing vrf DEVP
!
PE11(config)#interface Ethernet3
PE11(config-if-Et3)#no routerport
PE11(config-if-Et3)#vrf PROD
PE11(config-if-Et3)#ip address 10.1.99.11/24
!
PE11(config)#interface Ethernet4
PE11(config-if-Et3)#no routerport
PE11(config-if-Et3)#vrf DEVP
PE11(config-if-Et3)#ip address 10.11.5.11/24