STIGQter STIGQter: STIG Summary: Juniper Router RTR Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 25 Oct 2019: 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-101191r1_rule

Vulnerability Number

V-90981

Group Title

SRG-NET-000512-RTR-000008

Rule Version

JUNI-RT-000650

Severity

CAT I

CCI(s)

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.

[edit protocols l2circuit]
set neighbor 8.8.8.8 interface em0 virtual-circuit-id 13

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. In the example below ge-0/1/0 is the CE-facing interface that is configured for VPWS (aka pseudowire).

interfaces {
ge-0/1/0.0 {
encapsulation ethernet-ccc;
unit 0 {
}
}



protocols {



}
l2circuit {
neighbor 8.8.8.8 {
interface ge-0/1/0.0{
virtual-circuit-id 13;
}
}
}

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-90981

Documentable

False

Rule Version

JUNI-RT-000650

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. In the example below ge-0/1/0 is the CE-facing interface that is configured for VPWS (aka pseudowire).

interfaces {
ge-0/1/0.0 {
encapsulation ethernet-ccc;
unit 0 {
}
}



protocols {



}
l2circuit {
neighbor 8.8.8.8 {
interface ge-0/1/0.0{
virtual-circuit-id 13;
}
}
}

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

3387

Comments