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 select a user session to capture.

DISA Rule

SV-253952r1082341_rule

Vulnerability Number

V-253952

Group Title

SRG-NET-000331-L2S-000001

Rule Version

JUEX-L2-000050

Severity

CAT II

CCI(s)

• CCI-001919 - Provide the capability for organization-defined users or roles to select a user session to record; view; hear; or log the content of a user session under organization-defined circumstances.

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.

To capture packets from the L2 interface ge-0/0/0 and forward out the L2 interface ge-0/0/1, configure the switch similarly to the example:

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 interface <output interface>.<logical unit>

Check Contents

Verify if the switch configuration has an analyzer to capture ingress and egress packets from any designated access interface for the purpose of 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.

If actively capturing packets, verify an analyzer is present.
[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 {
interface <output interface>.<logical unit>;
}
}
}
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, this is a finding.

Vulnerability Number

V-253952

Documentable

False

Rule Version

JUEX-L2-000050

Severity Override Guidance

Verify if the switch configuration has an analyzer to capture ingress and egress packets from any designated access interface for the purpose of 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.

If actively capturing packets, verify an analyzer is present.
[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 {
interface <output interface>.<logical unit>;
}
}
}
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, this is a finding.

Check Content Reference

M

Target Key

5478