STIGQter: STIG Summary: Juniper EX Series Switches Layer 2 Switch Security Technical Implementation Guide Version: 2 Release: 5 Benchmark Date: 01 Jul 2026:

The Juniper EX switch must be configured to permit authorized users to remotely view, in real time, all content related to an established user session from a component separate from the layer 2 switch.

DISA Rule

SV-253953r1082342_rule

Vulnerability Number

V-253953

Group Title

SRG-NET-000332-L2S-000002

Rule Version

JUEX-L2-000060

Severity

CAT II

CCI(s)

• CCI-001920 - Provide the capability for authorized users to remotely view and hear content related to an established user session in real time.

Weight

10

Fix Recommendation

Enable the feature or configure the switch so that it is capable of capturing ingress and egress packets from any designated switch port for the purpose of monitoring a specific user session.

set vlans <destination VLAN name> vlan-id <VLAN ID>

set interfaces <interface name> unit 0 family ethernet-switching interface-mode trunk
set interfaces <interface name> unit 0 family ethernet-switching vlan members <destination VLAN name>

set forwarding-options analyzer <analyzer name> input ingress interface <input interface>.<logical unit>
-or-
set forwarding-options analyzer <analyzer name> input ingress interface irb.<logical unit>

set forwarding-options analyzer <analyzer name> input egress interface <input interface>.<logical unit>
-or-
set forwarding-options analyzer <analyzer name> input egress interface irb.<logical unit>

set forwarding-options analyzer <analyzer name> output vlan <destination VLAN name>

Check Contents

Verify if the switch configuration has an analyzer to capture ingress and egress packets from any designated switch port for the purpose of remotely monitoring a specific user session.

Packet capture using the [edit forwarding-options analyzer <analyzer name>] configuration will only be present and enabled when actively monitoring sessions.

The Juniper switch supports either output interface or output vlan. To output to a VLAN that is trunked to a remote location, configure the switch with the destination VLAN, configure the uplink interface as trunked, and include the remote analyzer VLAN in the uplink trunk.

If actively capturing packets, verify an analyzer is present.
[edit vlans]
<destination VLAN name> {
vlan-id <VLAN ID>;
}

[edit interfaces]
<interface name> {
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members <destination VLAN name>;
}
}
}
}

[edit forwarding-options]
analyzer {
<analyzer name> {
input {
ingress {
interface <input interface>.<logical unit>;
-or-
interface irb.<logical unit>;
}
egress {
interface <input interface>.<logical unit>;
-or-
interface irb.<logical unit>;
}
output {
vlan {
<destination VLAN name>;
}
}
}
}
Note: Simultaneously mirroring both ingress and egress traffic may exceed the output interface capacity. Packet mirroring consumes resources and should only be enabled when actively monitoring sessions.

If active monitoring is not currently required, the lack of an analyzer, or the presence of an inactive (disabled) analyzer, is not a finding.

If the switch is not configured to capture ingress and egress packets from a designated access interface for the purpose of remotely monitoring a specific user session, this is a finding.

Vulnerability Number

V-253953

Documentable

False

Rule Version

JUEX-L2-000060

Severity Override Guidance

Verify if the switch configuration has an analyzer to capture ingress and egress packets from any designated switch port for the purpose of remotely monitoring a specific user session.

Packet capture using the [edit forwarding-options analyzer <analyzer name>] configuration will only be present and enabled when actively monitoring sessions.

The Juniper switch supports either output interface or output vlan. To output to a VLAN that is trunked to a remote location, configure the switch with the destination VLAN, configure the uplink interface as trunked, and include the remote analyzer VLAN in the uplink trunk.

If actively capturing packets, verify an analyzer is present.
[edit vlans]
<destination VLAN name> {
vlan-id <VLAN ID>;
}

[edit interfaces]
<interface name> {
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members <destination VLAN name>;
}
}
}
}

[edit forwarding-options]
analyzer {
<analyzer name> {
input {
ingress {
interface <input interface>.<logical unit>;
-or-
interface irb.<logical unit>;
}
egress {
interface <input interface>.<logical unit>;
-or-
interface irb.<logical unit>;
}
output {
vlan {
<destination VLAN name>;
}
}
}
}
Note: Simultaneously mirroring both ingress and egress traffic may exceed the output interface capacity. Packet mirroring consumes resources and should only be enabled when actively monitoring sessions.

If active monitoring is not currently required, the lack of an analyzer, or the presence of an inactive (disabled) analyzer, is not a finding.

If the switch is not configured to capture ingress and egress packets from a designated access interface for the purpose of remotely monitoring a specific user session, this is a finding.

Check Content Reference

M

Target Key

5478