The Cisco PE switch 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-221117	CISC-RT-000630	SV-221117r999771_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
Cisco NX OS Switch RTR Security Technical Implementation Guide			2026-03-04

Related Frameworks

1 mapping across 3 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.

BCD-10.4Alternate Communications Channels

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(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.

SC-47Alternate Communications Paths

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-5(2)Capacity, Bandwidth, and Redundancy

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(normalised)
DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-7Boundary Protection

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(normalised)
DISA STIG Benchmark (XCCDF)V2R2our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V2R2intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-7(11)Restrict Incoming Communications Traffic

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(normalised)
DISA STIG Benchmark (XCCDF)V2R1our copyintersects(normalised)
DISA STIG Benchmark (XCCDF)V2R1intersects(normalised)
DISA CCI List2025-01-23equal to(normalised)

SC-7(29)Separate Subnets to Isolate Functions

1.00

DISA STIG Benchmark (XCCDF)V3R4intersects(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)V3R4intersects(normalised)

Details

Check Text (C-221117r999771_chk)

Step 1: Review the design plan for deploying MPLS/L3VPN. Step 2: Review all CE-facing interfaces and verify that the proper VRF is defined via the ip vrf forwarding command. In the example below, customer 1 is bound to interface Ethernet2/1, while customer 2 is bound to Ethernet2/2. interface Ethernet2/1 no switchport vrf member CUST1 ip address x.2.22.3/24 interface Ethernet2/2 no switchport vrf member CUST2 ip address x.2.8.4/24 If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.

Fix Text (F-22821r409841_fix)

Configure the PE switch to have each VRF bound to the appropriate physical or logical interfaces to maintain traffic separation between all MPLS L3VPNs.