OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper EX switch must be configured to enable STP Loop Protection on all non-designated STP switch ports.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-253957JUEX-L2-000100SV-253957r843904_ruleCCI-002385medium
Description
The Spanning Tree Protocol (STP) Loop Protection feature provides additional protection against STP loops. An STP loop is created when an STP blocking port in a redundant topology erroneously transitions to the forwarding state. In its operation, STP relies on continuous reception and transmission of BPDUs based on the port role. The designated port transmits BPDUs, and the non-designated port receives BPDUs. When one of the ports in a physically redundant topology no longer receives BPDUs, the STP conceives that the topology is loop free. Eventually, the blocking port from the alternate or backup port becomes a designated port and moves to a forwarding state. This situation creates a loop. The loop protection feature makes additional checks. If BPDUs are not received on a non-designated port and loop protection is enabled, that port is moved into the STP loop-inconsistent blocking state.
STIGDate
Juniper EX Series Switches Layer 2 Switch Security Technical Implementation Guide2025-03-07

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (13) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-01Continuous Monitoring
1.00
MON-01.1Intrusion Detection & Prevention Systems (IDS & IPS)
1.00
MON-01.3Inbound & Outbound Communications Traffic
1.00
MON-01.4System Generated Alerts
1.00
MON-01.8Security Event Monitoring
1.00
NET-01Network Security Controls (NSC)
1.00
NET-02Layered Network Defenses
1.00
SEA-01Secure Engineering Principles
1.00
SEA-02Alignment With Enterprise Architecture
1.00
CAP-01Capacity & Performance Management
0.50

+3 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (36) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-17(9)Disconnect or Disable Access
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
AU-5Response to Audit Logging Process Failures
1.00
CM-11(2)Software Installation with Privileged Status
1.00

+26 more (top 10 by confidence shown)

CCI1 mapping
CCI-002385
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

DE.CM-01
1.00
PR.IR-01
1.00
PR.IR-04
0.50

Who does this work

12 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-253957r843904_chk)

Review the switch configuration to verify that STP Loop Protection is enabled on all non-designated STP switch ports. Verify STP Loop Protection for RSTP and VSTP. [edit protocols] rstp { interface <interface name> { bpdu-timeout-action { block; } } } vstp { interface <interface name> { bpdu-timeout-action { block; } } } Verify Loop Protection for all instances on an MSTP interface: [protocols] mstp { interface <interface name> { bpdu-timeout-action { block; } } } Note: Loop Protection and Root Protection are mutually exclusive and cannot be simultaneously configured on the same interface. If STP Loop Protection is not configured on non-designated STP ports, this is a finding.

Fix Text (F-57360r843903_fix)

Configure the switch to have STP Loop Protection enabled on all non-designated STP interfaces. RSTP or VSTP non-designated interface loop protection: set protocols rstp interface <interface name> bpdu-timeout-action block set protocols vstp interface <interface name> bpdu-timeout-action block All instances on an MSTP interface: set protocols mstp interface <interface name> bpdu-timeout-action block Note: Loop Protection and Root Protection are mutually exclusive and cannot be simultaneously configured on the same interface.