Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Verify if the switch configuration has 802.1x authentication implemented for all access switch ports connecting to LAN outlets (i.e., RJ-45 wall plates) or devices not located in the telecom room, wiring closets, or equipment rooms. MAC Authentication Bypass (MAB) must be configured on those switch ports connected to devices that do not support an 802.1x supplicant. Step 1: Verify that 802.1x is configured on all host-facing interfaces as shown in the example below: interface Ethernet1/1 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 interface Ethernet1/2 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 interface Ethernet1/3 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 Note: Host-mode must be set to single-host, multi-domain (for VoIP phone + PC), or multi-auth (multiple PCs connected to a hub). Host-mode multi-host is not compliant with this requirement. Step 2: Verify that 802.1x authentication is configured on the switch as shown in the example below: aaa group server radius RADIUS_GROUP server 1.1.1.1 server 1.2.1.1 … … … aaa authentication dot1x default group RADIUS_GROUP Step 3: Verify that the radius servers have been defined. radius-server host 10.1.1.1 key 7 "xxxxxxxxxxx" authentication accounting timeout 5 retransmit 1 radius-server host 10.2.1.1 key 7 " xxxxxxxxxxx" authentication accounting timeout 5 retransmit 1 If 802.1x authentication or MAB is not configured on all access switch ports connecting to LAN outlets or devices not located in the telecom room, wiring closets, or equipment rooms, this is a finding.
Configure 802.1 x authentications on all host-facing access switch ports. To authenticate those devices that do not support 802.1x, MAC Authentication Bypass must be configured. Step 1: Configure the radius servers as shown in the example below: SW1(config)# radius-server host 10.1.1.1 key xxxx SW1(config)# radius-server host 10.2.1.1 key xxxx Step 2: Enable 802.1x authentication on the switch. SW1(config)# aaa group server radius RADIUS_GROUP SW1(config-radius)# server 10.1.1.1 SW1(config-radius)# server 10.2.1.1 SW1(config-radius)# exit SW1(config)# aaa authentication dot1x default group RADIUS_GROUP SW1(config)# exit Step 3: Enable 802.1x on all host-facing interfaces as shown in the example below: SW1(config)# int e1/1 - 80 SW1(config-if-range)# dot1x port-control auto SW1(config-if-range)# dot1x host-mode single-host SW1(config-if-range)# end Note: Host-mode must be set to single-host, multi-domain (for VoIP phone + PC), or multi-auth (multiple PCs connected to a hub). Host-mode multi-host is not compliant with this requirement.
Review the switch configuration to verify if VTP is enabled. Step 1: Enter the show feature command to determine if vtp is enabled. Step 2: Enter the show vtp status command to determine operating mode. SW1# show vtp status VTP Status Information ---------------------- VTP Version : 2 (capable) Configuration Revision : 0 Maximum VLANs supported locally : 1005 Number of existing VLANs : 5 VTP Operating Mode : Transparent VTP Domain Name : XXXXX VTP Pruning Mode : Disabled (Operationally Disabled) VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 Digest : 0x0C 0x5E 0xC3 0x74 0x3F 0xB0 0x2F 0x49 If mode is set to anything other than off or transparent, verify that a password has been configured using the show vtp password command. Note: VTP authenticates all messages using an MD5 hash that consists of the VTP version + The VTP Password + VTP Domain + VTP Configuration Revision. If VTP is enabled on the switch and is not authenticating VTP messages with a hash function using a configured password, this is a finding.
Configure the switch to authenticate all VLAN Trunk Protocol (VTP) messages with a hash function using a configured password as shown in the example below: SW1(config)# vtp password xxxxxxxxx
Verify that the switch is capable of capturing ingress and egress packets from any designated switch port for the purpose of monitoring a specific user session. The example configuration below will capture packets from interface Ethernet1/66 and replicate the packets to interface Ethernet1/68. monitor session 1 source interface Ethernet1/66 both destination interface Ethernet1/68 If the switch is not capable of capturing ingress and egress packets from a designated switch port, this is a finding.
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. The example configuration below will capture packets from interface Ethernet1/66 and replicate the packets to Ethernet1/68. SW1(config)# monitor session 1 SW1(config-monitor)# source interface ethernet 1/66 SW1(config-monitor)# destination interface ethernet 1/68 SW1(config-monitor)# end
Verify that the switch is capable of capturing ingress and egress packets from any designated switch port for the purpose of remotely monitoring a specific user session. The example configuration below will capture packets from interface Ethernet1/66 and replicate the packets to interface Ethernet1/68. monitor session 1 source interface Ethernet1/66 both destination interface Ethernet1/68 If the switch is not capable of capturing ingress and egress packets from a designated switch port for the purpose of remotely monitoring a specific user session, this is a finding.
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. The example configuration below will capture packets from interface Ethernet1/66 and replicate the packets to Ethernet1/68. SW1(config)# monitor session 1 SW1(config-monitor)# source interface ethernet 1/66 SW1(config-monitor)# destination interface ethernet 1/68 SW1(config-monitor)# end
Verify if the switch configuration has 802.1x authentication implemented for all access switch ports connecting to LAN outlets (i.e., RJ-45 wall plates) or devices not located in the telecom room, wiring closets, or equipment rooms. MAC Authentication Bypass (MAB) must be configured on those switch ports connected to devices that do not provide an 802.1x supplicant. Step 1: Verify that 802.1x is configured on all host-facing interfaces as shown in the example below: interface Ethernet1/1 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 interface Ethernet1/2 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 interface Ethernet1/3 dot1x pae authenticator dot1x port-control auto dot1x host-mode single-host switchport access vlan 10 Note: Host-mode must be set to single-host, multi-domain (for VoIP phone + PC), or multi-auth (multiple PCs connected to a hub). Host-mode multi-host is not compliant with this requirement. Step 2: Verify that 802.1x authentication is configured on the switch as shown in the example below: aaa group server radius RADIUS_GROUP server 1.1.1.1 server 1.2.1.1 … … … aaa authentication dot1x default group RADIUS_GROUP Step 3: Verify that the radius servers have been defined. radius-server host 10.1.1.1 key 7 "xxxxxxxxxxx" authentication accounting timeout 5 retransmit 1 radius-server host 10.2.1.1 key 7 " xxxxxxxxxxx" authentication accounting timeout 5 retransmit 1 If 802.1x authentication or MAB is not on configured on all access switch ports connecting to LAN outlets or devices not located in the telecom room, wiring closets, or equipment rooms, this is a finding.
Configure 802.1 x authentications on all host-facing access switch ports. To authenticate those devices that do not support 802.1x, MAC Authentication Bypass must be configured. Step 1: Configure the radius servers as shown in the example below: SW1(config)# radius-server host 10.1.1.1 key xxxx SW1(config)# radius-server host 10.2.1.1 key xxxx Step 2: Enable 802.1x authentication on the switch. SW1(config)# aaa group server radius RADIUS_GROUP SW1(config-radius)# server 10.1.1.1 SW1(config-radius)# server 10.2.1.1 SW1(config-radius)# exit SW1(config)# aaa authentication dot1x default group RADIUS_GROUP SW1(config)# exit Step 3: Enable 802.1x on all host-facing interfaces as shown in the example below: SW1(config)# int e1/1 - 80 SW1(config-if-range)# dot1x port-control auto SW1(config-if-range)# dot1x host-mode single-host SW1(config-if-range)# end Note: Host-mode must be set to single-host, multi-domain (for VoIP phone + PC), or multi-auth (multiple PCs connected to a hub). Host-mode multi-host is not compliant with this requirement.
Review the switch topology as well as the configuration to verify that Root Guard is enabled on all switch ports connecting to access layer switches. interface Ethernet1/1 … … … spanning-tree guard root interface Ethernet1/2 … … … spanning-tree guard root interface Ethernet1/3 … … … spanning-tree guard root If the switch has not enabled Root Guard on all switch ports connecting to access layer switches, this is a finding.
Configure the switch to have Root Guard enabled on all ports connecting to access layer switches. SW1(config)# int e1/1 – 44 SW1(config-if-range)# spanning-tree guard root SW1(config-if-range)# end
Review the switch configuration to verify that BPDU Guard is enabled on all user-facing or untrusted access switch ports as shown in the configuration example below: interface Ethernet1/1 … … … spanning-tree bpduguard enable interface Ethernet1/2 … … … spanning-tree bpduguard enable If the switch has not enabled BPDU Guard, this is a finding.
Configure the switch to have BPDU Guard enabled on all user-facing or untrusted access switch ports as shown in the configuration example below: SW1(config)# int e1/1 -44 SW1(config-if-range)# spanning-tree bpduguard enable Note: BPDU guard can also be enabled globally on all edge ports via the following command: spanning-tree port type edge bpduguard default
Review the switch configuration to verify that STP Loop Guard is enabled as shown in the configuration example below: hostname SW1 … … … spanning-tree loopguard default If STP Loop Guard is not enabled, this is a finding.
Configure the switch to have STP Loop Guard enabled via the spanning-tree loopguard default global command.
Review the switch configuration to verify that UUFB is enabled on all access switch ports as shown in the configuration example below: interface Ethernet1/1 switchport block unicast interface Ethernet1/2 switchport block unicast … … … interface Ethernet1/32 switchport block unicast If any access switch ports do not have UUFB enabled, this is a finding.
Configure the switch to have Unknown Unicast Flood Blocking (UUFB) enabled as shown in the configuration example below: SW1(config)# int e1/1-32 SW1(config-if-range)# switchport block unicast SW1(config-if-range)# end
Step 1: Review the switch configuration and verify that DHCP snooping is enabled on a per-VLAN basis as shown in the example below: vlan 1,4,6-10 ip dhcp snooping … … … ip dhcp snooping vlan 4,6-10 Note: Switchports assigned to a user VLAN would have drops in the area where the user community would reside; hence, the "untrusted" term is used. Server and printer VLANs would not be applicable. By default, DHCP snooping is disabled on all VLANs. If the switch does not have DHCP snooping enabled for all user VLANs to validate DHCP messages from untrusted sources, this is a finding.
Step 1: Enable the DHCP feature. SW1(config)# feature dhcp Step 2: Configure the switch to have DHCP snooping for all user VLANs to validate DHCP messages from untrusted sources as shown in the example below: SW1(config)# ip dhcp snooping SW1(config)# ip dhcp snooping vlan 4,6-10
Review the switch configuration to verify that IP Source Guard is enabled on all user-facing or untrusted access switch ports as shown in the example below: interface Ethernet1/1 ip verify source dhcp-snooping-vlan interface Ethernet1/2 ip verify source dhcp-snooping-vlan … … … interface Ethernet1/32 ip verify source dhcp-snooping-vlan Note: the IP Source Guard feature depends on the entries in the DHCP snooping database or static IP-MAC-VLAN configuration commands to verify IP-to-MAC address bindings. If the switch does not have IP Source Guard enabled on all untrusted access switch ports, this is a finding.
Configure the switch to have IP Source Guard enabled on all user-facing or untrusted access switch ports. SW1(config)# int e1/1-32 SW1(config-if-range)# ip verify source dhcp-snooping-vlan
Review the switch configuration to verify that Dynamic Address Resolution Protocol (ARP) Inspection (DAI) feature is enabled on all user VLANs. hostname SW2 … … … ip arp inspection vlan 2,4-8,11 Note: DAI depends on the entries in the DHCP snooping binding database to verify IP-to-MAC address bindings in incoming ARP requests and ARP responses. If DAI is not enabled on all user VLANs, this is a finding.
Configure the switch to have Dynamic Address Resolution Protocol (ARP) Inspection (DAI) enabled on all user VLANs as shown in the example below: SW1(config)# ip arp inspection vlan 2,4-8,11
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 If storm control is not enabled at a minimum for broadcast traffic, this is a finding.
Configure storm control for each host-facing interface as shown in the example below: SW1(config)#int range e0/2 – 8 SW1(config-if-range)# storm-control unicast level 50 SW1(config-if-range)# storm-control broadcast level 40
Review the switch configuration to verify that IGMP or MLD snooping has been configured for IPv4 and IPv6 multicast traffic respectively. The example below are the steps to verify that IGMP snooping is enabled for each VLAN. Step 1: Verify that IGMP or MLD snooping is enabled globally. By default, IGMP snooping is enabled globally; hence, the following command should not be in the switch configuration: no ip igmp snooping Step 2: Verify that IGMP snooping is not disabled for any VLAN as shown in the example below: no ip igmp snooping vlan 11 Note: When globally enabled, it is also enabled by default on all VLANs, but can be disabled on a per-VLAN basis. If global snooping is disabled, VLAN snooping cannot be enabled. If global snooping is enabled, VLAN snooping cannot be enabled or disabled. If the switch is not configured to implement IGMP or MLD snooping for each VLAN, this is a finding.
Configure IGMP or MLD snooping for IPv4 and IPv6 multicast traffic respectively globally. SW1(config)# ip igmp snooping
If any of the switch ports have fiber optic interconnections with neighbors, review the switch configuration to verify that either UDLD is enabled globally or not explicitly disabled on a per interface basis as shown in the examples below. hostname SW1 … … … feature udld or interface GigabitEthernet0/3 udld disabled Note: By default, UDLD is enabled on all interfaces with fiber optic connections. An alternative implementationwhen UDLD is not supported by connected device is to deploy a single member Link Aggregation Group (LAG) via IEEE 802.3ad Link Aggregation Control Protocol (LACP). If the switch has fiber optic interconnections with neighbors and UDLD is not enabled, this is a finding.
Configure the switch to enable Unidirectional Link Detection (UDLD) to protect against one-way connections. SW1(config)# feature udld
Step 1: Review the switch configurations and examine all access switch ports. Each access switch port not in use should have membership to an inactive VLAN. interface Ethernet1/81 shutdown switchport access vlan 999 interface Ethernet1/82 shutdown switchport access vlan 999 interface Ethernet1/83 shutdown switchport access vlan 999 Step 2: Verify that traffic from the inactive VLAN is not allowed on any trunk links as shown in the example below: interface Ethernet1/1 switchport mode trunk switchport trunk allowed vlan 1-998,1000-4094 Note: Switch ports configured for 802.1x are exempt from this requirement. If there are any access switch ports not in use and not in an inactive VLAN, this is a finding.
Assign all switch ports not in use to an inactive VLAN. Step 1: Assign the disabled interfaces to an inactive VLAN. SW1(config)# int e1/81-128 SW1(config-if-range)# switchport access vlan 999 SW1(config-if-range)# end Step 2: Configure trunk links to not allow traffic from the inactive VLAN. SW1(config-if)# switchport trunk allowed vlan except 999 SW1(config-if)# end
Review the switch configurations and verify that no access switch ports have been assigned membership to the default VLAN (i.e., VLAN 1). VLAN assignments can be verified via the show vlan command. In the example below, interfaces 1/1 and 1/2 are trunk links. SW1# show vlan VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Eth1/1, Eth1/2 10 VLAN0010 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19, Eth1/20 Eth1/21, Eth1/22, Eth1/23 Eth1/24, Eth1/25, Eth1/26 Eth1/27, Eth1/28, Eth1/29 Eth1/30 11 VLAN0011 active Eth1/1, Eth1/2, Eth1/31 Eth1/32, Eth1/33, Eth1/34 Eth1/35, Eth1/36, Eth1/37 Eth1/38, Eth1/39, Eth1/40 If there are access switch ports assigned to the default VLAN, this is a finding.
Remove the assignment of the default VLAN from all access switch ports.
Review the switch configuration and verify that the default VLAN is pruned from trunk links that do not require it. SW1# show interface trunk -------------------------------------------------------------------------------- Port Native Status Port Vlan Channel -------------------------------------------------------------------------------- Eth1/1 1 trunking -- Eth1/2 1 trunking -- -------------------------------------------------------------------------------- Port Vlans Allowed on Trunk -------------------------------------------------------------------------------- Eth1/1 1-998,1000-4094 Eth1/2 1-998,1000-4094 If the default VLAN is not pruned from trunk links that should not be transporting frames for the VLAN, this is a finding.
Step 1: Prune VLAN 1 from any trunk links as necessary. SW1(config)# int e1/2 SW1(config-if)# switchport trunk allowed vlan except 1, 999 SW1(config-if)# end Step 2: Verify VLAN 1 is not allowed on the trunk link. SW1# show interface trunk -------------------------------------------------------------------------------- Port Native Status Port Vlan Channel -------------------------------------------------------------------------------- Eth1/1 1 trunking -- Eth1/2 1 trunking -- -------------------------------------------------------------------------------- Port Vlans Allowed on Trunk -------------------------------------------------------------------------------- Eth1/1 1-998,1000-4094 Eth1/2 2-998,1000-4094
Review the switch configuration and verify that the default VLAN is not used to access the switch for management. interface Vlan1 interface Vlan44 description Management VLAN ip address 10.1.12.1/24 If the default VLAN is being used for management access to the switch, this is a finding.
Configure the switch for management access to use a VLAN other than the default VLAN. SW1(config)# interface vlan 44 SW1(config-if)# ip add 10.1.12.1/24 SW1(config-if)# end
Review the switch configurations and examine all user-facing or untrusted switchports. The example below depicts both access and trunk ports. interface Ethernet1/1 switchport switchport mode trunk switchport trunk allowed vlan 1-998,1000-4094 interface Ethernet1/2 switchport switchport mode trunk switchport trunk allowed vlan 2-998,1000-4094 interface Ethernet1/3 interface Ethernet1/4 switchport access vlan 10 Note: Switchport mode access is the default and hence will not be shown in the configuration. If any of the user-facing switch ports are configured as a trunk, this is a finding.
Disable trunking on all user-facing or untrusted switch ports. SW1(config)# int e1/3-128 SW1(config-if)# switchport mode access SW1(config-if)# end
Review the switch configurations and examine all trunk links. Verify the native VLAN has been configured to a VLAN ID other than the ID of the default VLAN (i.e. VLAN 1) as shown in the example below: interface Ethernet0/1 switchport switchport mode trunk switchport trunk native vlan 44 Note: An alternative to configuring a dedicated native VLAN is to ensure that all native VLAN traffic is tagged. This will mitigate the risk of VLAN hopping since there will always be an outer tag for native traffic as it traverses an 802.1q trunk link. If the native VLAN has the same VLAN ID as the default VLAN, this is a finding.
To ensure the integrity of the trunk link and prevent unauthorized access, the ID of the native VLAN of the trunk port must be changed from the default VLAN (i.e., VLAN 1) to its own unique VLAN ID. SW1(config)#int e0/1 SW1(config-if)#switchport trunk native vlan 44 Note: The native VLAN ID must be the same on both ends of the trunk link; otherwise, traffic could accidentally leak between broadcast domains.
Review the switch configurations and examine all access switch ports. Verify that they do not belong to the native VLAN as shown in the example below: interface Ethernet0/1 switchport switchport mode trunk switchport trunk native vlan 44 interface Ethernet0/2 switchport switchport access vlan 11 interface Ethernet0/3 switchport switchport access vlan 12 If any access switch ports have been assigned to the same VLAN ID as the native VLAN, this is a finding.
Configure all access switch ports to a VLAN other than the native VLAN.