| Checked | Name | Title |
|---|
| ☐ | SV-206646r382903_rule | The layer 2 switch must be configured to disable non-essential capabilities. |
| ☐ | SV-206647r385501_rule | The layer 2 switch must uniquely identify all network-connected endpoint devices before establishing any connection. |
| ☐ | SV-206648r1188386_rule | When using VLAN Trunk Protocol (VTP) or similar features, the layer 2 switch must authenticate all VTP messages with a hash function using the most secured cryptographic algorithm available. |
| ☐ | SV-206649r385534_rule | The layer 2 switch must manage excess bandwidth to limit the effects of packet flooding types of denial of service (DoS) attacks. |
| ☐ | SV-206650r383119_rule | The layer 2 switch must be configured to fail securely in the event of an operational failure. |
| ☐ | SV-206653r856583_rule | The layer 2 switch must authenticate all network-connected endpoint devices before establishing any connection. |
| ☐ | SV-206654r856584_rule | The layer 2 switch must have Root Guard enabled on all switch ports connecting to access layer switches and hosts. |
| ☐ | SV-206655r856585_rule | The layer 2 switch must have BPDU Guard enabled on all user-facing or untrusted access switch ports. |
| ☐ | SV-206656r856586_rule | The layer 2 switch must have STP Loop Guard enabled on all non-designated STP switch ports. |
| ☐ | SV-206657r856587_rule | The layer 2 switch must have Unknown Unicast Flood Blocking (UUFB) enabled. |
| ☐ | SV-206658r856588_rule | The layer 2 switch must have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources. |
| ☐ | SV-206659r856589_rule | The layer 2 switch must have IP Source Guard enabled on all user-facing or untrusted access switch ports. |
| ☐ | SV-206660r856590_rule | The layer 2 switch must have Dynamic Address Resolution Protocol (ARP) Inspection (DAI) enabled on all user VLANs. |
| ☐ | SV-206661r385561_rule | The layer 2 switch must have Storm Control configured on all host-facing switch ports. |
| ☐ | SV-206662r385561_rule | The layer 2 switch must have IGMP or MLD Snooping configured on all VLANs |
| ☐ | SV-206663r385561_rule | The layer 2 switch must implement Rapid STP where VLANs span multiple switches with redundant links. |
| ☐ | SV-206664r1188389_rule | The layer 2 switch must be configured to protect against one-way connections. |
| ☐ | SV-206665r1188390_rule | The layer 2 switch must have all trunk links enabled statically. |
| ☐ | SV-206666r385561_rule | The layer 2 switch must have all disabled switch ports assigned to an unused VLAN. |
| ☐ | SV-206667r385561_rule | The layer 2 switch must not have the default VLAN assigned to any host-facing switch ports. |
| ☐ | SV-206668r385561_rule | The layer 2 switch must have the default VLAN pruned from all trunk ports that do not require it. |
| ☐ | SV-206669r385561_rule | The layer 2 switch must not use the default VLAN for management traffic. |
| ☐ | SV-206670r385561_rule | The layer 2 switch must have all user-facing or untrusted ports configured as access switch ports. |
| ☐ | SV-206671r539568_rule | The layer 2 switch must have the native VLAN assigned to an ID other than the default VLAN for all 802.1q trunk links. |
| ☐ | SV-206672r385561_rule | The layer 2 switch must not have any switch ports assigned to the native VLAN. |
| ☐ | SV-216507r539569_rule | The layer 2 switch must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
| ☐ | SV-263667r1137762_rule | The layer 2 switch must implement physically or logically separate subnetworks to isolate organization-defined critical system components and functions. |
| ☐ | SV-263668r982575_rule | The layer 2 switch must establish organization-defined alternate communications paths for system operations organizational command and control. |
| ☐ | SV-278980r1137765_rule | The layer 2 switch must dynamically associate security attributes with organization-defined subjects in accordance with organization-defined security policies as information is created and combined. |
| ☐ | SV-278981r1137768_rule | The layer 2 switch must validate the integrity of transmitted security attributes. |
| ☐ | SV-278982r1137771_rule | The layer 2 switch must use organization-defined security attributes associated with organization-defined information, source, and destination objects to enforce organization-defined information flow control policies as a basis for flow control decisions. |
| ☐ | SV-278983r1137774_rule | The layer 2 switch must uniquely identify and authenticate source by organization, system, application, and/or individual for information transfer. |
| ☐ | SV-278984r1137777_rule | The layer 2 switch must uniquely identify and authenticate destination by organization, system, application, and/or individual for information transfer. |
| ☐ | SV-278985r1137780_rule | The layer 2 switch, when transferring information between different security domains, must apply the same security policy filtering to metadata as it applies to data payloads. |
| ☐ | SV-278986r1137783_rule | The layer 2 switch must fail securely in the event of an operational failure of a boundary protection device. |
| ☐ | SV-278987r1137786_rule | The layer 2 switch must dynamically associate security attributes with organization-defined objects in accordance with organization-defined security policies as information is created and combined. |
STIGQter: STIG Summary: