What changed in Cisco NX OS Switch L2S STIG V3R4V3R4 changes

Cisco NX OS Switch L2S STIG V3R4 (2026-07-01) replaced V3R3 (2026-01-05): 1 check updated. It has 22 checks, against 22 in V3R3.

  • 0 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Discussion 1

Updated in V3R4 (1)

V-220687CAT IIIThe Cisco switch must have Storm Control configured on all host-facing switchports.Check text, Discussion

Check text

Review the switch configuration to verify that storm control is enabled on all host-facing interfaces as shown in the example below: interface GigabitEthernet0/3 switchport access vlan 12 storm-control unicast unicast level 50.00 storm-control broadcast broadcast level 40 Note: Bandwidth percentage thresholds (via level parameter) can be used in lieu of PPS rate. The storm control values in the STIG's example configuration are for illustrative purposes and do not constitute a mandatory value for this setting. Network engineers are responsible for determining and applying appropriate storm control levels based on the specific operational and mission-based bandwidth requirements of each port. A setting must be determined and intentionally configured. If storm control is not enabled at a minimum for broadcast traffic, this is a finding.

Discussion

A traffic storm occurs when packets flood a LAN, creating excessive traffic and degrading network performance. Traffic storm control prevents network disruption by suppressing ingress traffic when the number of packets reaches a configured threshold levelslevel. Traffic storm control monitors ingress traffic levels on a port and drops traffic when the number of packets reaches the configured threshold level during any one-second interval. The primary intent of this control is to mitigate the risk of denial-of-service (DoS) attacks, not to arbitrarily restrict bandwidth needed for operations. Consequently, some ports may be configured to operate at full line-rate speed if deemed necessary by the engineer to meet mission requirements. The ultimate responsibility for managing bandwidth to prevent a DoS while ensuring service availability rests with the network engineer.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V3R4 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.