STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 1 hour ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Nokia Service Router OS 25.x Router Security Technical Implementation Guide

V-283843

CAT I (High)

The Nokia Provider Edge (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 Multiprotocol Label Switching (MPLS) layer 3 virtual private networks (L3VPNs).

Rule ID

SV-283843r1203778_rule

STIG

Nokia Service Router OS 25.x Router Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000366

Discussion

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 does not leak into any VPN. Hence, it is imperative that each CE-facing interface is associated to only one VRF. This alone is the fundamental framework for traffic separation.

Check Content

Review the design plan for deploying L3VPN and VRF-lite. 

Review all CE-facing interfaces and verify the proper VRF is defined.

Use the command below and verify CE-facing interfaces and the physical ports:

- show router 30 interface "TO-CE"

Interface Table (Service: 30)

Interface-Name                   Adm       Opr(v4/v6)  Mode    Port/SapId
   IP-Address                                                  PfxState
-------------------------------------------------------------------------------
TO-CE                         Up        Up/Down     VPRN    1/1/c3/1
   172.200.200.1/30                                            n/a
-------------------------------------------------------------------------------
Interfaces : 1

If any VRFs are not bound to the appropriate physical or logical interface, this is a finding.

Fix Text

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

Add appropriate physical and logical interfaces to each MPLS L3VPN service, as shown in the example below: 

- configure service vprn 30 customer 1 create
- config>service>vprn# interface "TO-CE" create
- config>service>vprn>if# address 172.200.x.x/30
- config>service>vprn>if# sap 1/1/c3/1 create
- config>service>vprn>if>sap# exit
- config>service>vprn>if# exit
- config>service>vprn#