STIGQter: STIG Summary: Juniper EX Series Switches Router Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 24 Jul 2024:

The Juniper PE router providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit.

DISA Rule

SV-254067r844234_rule

Vulnerability Number

V-254067

Group Title

SRG-NET-000512-RTR-000008

Rule Version

JUEX-RT-000950

Severity

CAT I

CCI(s)

• CCI-000366 - Implement the security configuration settings.

Weight

10

Fix Recommendation

Assign globally unique VC IDs for each virtual circuit and configure the attachment circuits with the appropriate VC ID.

Configure the same VC ID on both ends of the VC.

set interfaces <interface name> unit <number> encapsulation vlan-ccc
set protocols l2circuit neighbor <neighbor> interface <interface>.<logical unit> virtual-circuit-id <1..4294967295>

Check Contents

Review the ingress and egress PE router configuration for each virtual circuit that has been provisioned.

Verify that the correct and unique VCID has been configured for the appropriate attachment circuit.

[edit interfaces]
<interface name> {
encapsulation ethernet-ccc;
unit <number> {
<additional configuration>
}
}

[edit protocols]
l2circuit {
neighbor 1.1.1.1 {
interface <interface name>.<logical unit> {
virtual-circuit-id <1..4294967295>;
}
}
}

If the correct VC ID has not been configured on both routers, this is a finding.

Note: Ethernet over MPLS in VLAN mode transports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN over a core MPLS network. The VC ID must be unique and the same on each end as it is used to connect the endpoints of the VC.

Vulnerability Number

V-254067

Documentable

False

Rule Version

JUEX-RT-000950

Severity Override Guidance

Review the ingress and egress PE router configuration for each virtual circuit that has been provisioned.

Verify that the correct and unique VCID has been configured for the appropriate attachment circuit.

[edit interfaces]
<interface name> {
encapsulation ethernet-ccc;
unit <number> {
<additional configuration>
}
}

[edit protocols]
l2circuit {
neighbor 1.1.1.1 {
interface <interface name>.<logical unit> {
virtual-circuit-id <1..4294967295>;
}
}
}

If the correct VC ID has not been configured on both routers, this is a finding.

Note: Ethernet over MPLS in VLAN mode transports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN over a core MPLS network. The VC ID must be unique and the same on each end as it is used to connect the endpoints of the VC.

Check Content Reference

M

Target Key

5479