Detections
Analytics

1.44 CISC-RT-000630

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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.

GROUP ID: V-221117
RULE ID: SV-221117r999771

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.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

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

See Also

https://workbench.cisecurity.org/benchmarks/22581

Item Details

References: CAT|I, CCI|CCI-004931, CSCv7|13.3, Rule-ID|SV-221117r999771_rule, STIG-ID|CISC-RT-000630, Vuln-ID|V-221117

Plugin: Cisco

Control ID: 497dbacfa562e4c4b0d4bb94fe5eec37be44b297896c2d3dc3c95a84dc303b79