Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-253955 | JUEX-L2-000080 | SV-253955r843898_rule | Low |
Description |
---|
Spanning Tree Protocol (STP) does not provide any means for the network administrator to securely enforce the topology of the switched network. Any switch can be the root bridge in a network. However, a more optimal forwarding topology places the root bridge at a specific predetermined location. With the standard STP, any bridge in the network with a lower bridge ID takes the role of the root bridge. The administrator cannot enforce the position of the root bridge but can set the root bridge priority to 0 in an effort to secure the root bridge position. The Root Protection feature provides a way to enforce the root bridge placement in the network. If the bridge receives superior STP Bridge Protocol Data Units (BPDUs) on a Root Protection-enabled interface, Root Protection ignores the superior BPDU and places the interface into block and a root-inconsistent state. To enforce the position of the root bridge it is imperative that Root Protection is enabled on all interfaces where the root bridge should never appear. |
STIG | Date |
---|---|
Juniper EX Series Switches Layer 2 Switch Security Technical Implementation Guide | 2022-08-31 |
Check Text ( C-57407r843896_chk ) |
---|
Review the switch topology as well as the switch configuration to verify that Root Protection is enabled on all interfaces connecting to access layer switches and hosts. [edit protocols] mstp { interface no-root-port; } } Note: Root Protection and Loop Protection are mutually exclusive and cannot be simultaneously configured on the same interface. If the switch has not enabled Root Protection on all interfaces connecting to access layer switches and hosts, this is a finding. |
Fix Text (F-57358r843897_fix) |
---|
Configure the switch to have Root Protection enabled on all switch ports connecting to access layer switches and hosts using trunked interfaces. set protocols mstp interface Note: Root Protection and Loop Protection are mutually exclusive and cannot be simultaneously configured on the same interface. |