Layer 2 Switch Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
Digest of Updates No substantive changes
Comparison against the immediately-prior release (V8R16). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.
No substantive changes detected against the previous release. 56 rules matched cleanly.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0230
- Vuln IDs
-
- V-3012
- Rule IDs
-
- SV-3012r2_rule
Checks: C-3456r3_chk
Review the network element configuration to determine if administrative access to the device requires some form of authentication—at a minimum a password is required.
Fix: F-3037r5_fix
Configure the network element so it will require a password to gain administrative access to the device.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0340
- Vuln IDs
-
- V-3013
- Rule IDs
-
- SV-3013r2_rule
Checks: C-3474r8_chk
Review the device configuration or request that the administrator login to the device and observe the terminal. Verify either Option A or Option B (for systems with character limitations) of the Standard Mandatory DoD Notice and Consent Banner is displayed at logon. The required banner verbiage follows and must be displayed verbatim: Option A You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. Option B If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't.”
Fix: F-3038r6_fix
Configure all management interfaces to the network device to display the DoD mandated warning banner verbiage at login regardless of the means of connection or communication. The required banner verbiage that must be displayed verbatim is as follows: Option A You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. Option B If the system is incapable of displaying the required banner verbiage due to its size, a smaller banner must be used. The mandatory verbiage follows: “I've read & consent to terms in IS user agreem't.”
- RMF Control
- Severity
- M
- CCI
- Version
- NET1639
- Vuln IDs
-
- V-3014
- Rule IDs
-
- SV-3014r2_rule
Checks: C-3540r4_chk
Review the management connection for administrative access and verify the network element is configured to time-out the connection after 10 minutes or less of inactivity.
Fix: F-3039r4_fix
Configure the network element to ensure the timeout for unattended administrative access connections is no longer than 10 minutes.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0820
- Vuln IDs
-
- V-3020
- Rule IDs
-
- SV-3020r2_rule
Checks: C-3584r3_chk
Review the device configuration to ensure DNS servers have been defined if it has been configured as a client resolver (name lookup).
Fix: F-3045r2_fix
Configure the device to include DNS servers or disable domain lookup.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0890
- Vuln IDs
-
- V-3021
- Rule IDs
-
- SV-3021r2_rule
Checks: C-3586r6_chk
Review the device configuration and verify it is configured to only allow SNMP access from addresses belonging to the management network.
Fix: F-3046r3_fix
Configure the network element to only allow SNMP access from only addresses belonging to the management network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1675
- Vuln IDs
-
- V-3043
- Rule IDs
-
- SV-3043r2_rule
Checks: C-3825r5_chk
Review the SNMP configuration of all managed nodes to ensure different community names (V1/2) or groups/users (V3) are configured for read-only and read-write access.
Fix: F-3068r2_fix
Configure the SNMP community strings on the network element and change them from the default values. SNMP community strings and user passwords must be unique and do not match any other network device passwords. Different community strings (V1/2) or groups (V3) must be configured for various levels of read and write access.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0460
- Vuln IDs
-
- V-3056
- Rule IDs
-
- SV-3056r5_rule
Checks: C-3503r9_chk
Review the network device configuration and validate there are no group accounts configured for access.
Fix: F-3081r9_fix
Configure individual user accounts for each authorized person then remove any group accounts.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0465
- Vuln IDs
-
- V-3057
- Rule IDs
-
- SV-3057r3_rule
Checks: C-3504r6_chk
Review the accounts authorized for access to the network device. Determine if the accounts are assigned the lowest privilege level necessary to perform assigned duties. User accounts must be set to a specific privilege level which can be mapped to specific commands or a group of commands. Authorized accounts should have the greatest privilege level unless deemed necessary for assigned duties. If it is determined that authorized accounts are assigned to greater privileges than necessary, this is a finding.
Fix: F-3082r5_fix
Configure authorized accounts with the least privilege rule. Each user will have access to only the privileges they require to perform their assigned duties.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0470
- Vuln IDs
-
- V-3058
- Rule IDs
-
- SV-3058r3_rule
Checks: C-3505r4_chk
Review the organization's responsibilities list and reconcile the list of authorized account with those accounts defined for access to the network device. If an unauthorized account is configured for access to the device, this is a finding.
Fix: F-3083r5_fix
Remove any account configured for access to the network device that is not defined in the organization's responsibilities list.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0600
- Vuln IDs
-
- V-3062
- Rule IDs
-
- SV-3062r3_rule
Checks: C-3508r3_chk
Review the network element configuration to determine if passwords are viewable.
Fix: F-3087r6_fix
Configure the network element to ensure passwords are not viewable when displaying configuration information.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1638
- Vuln IDs
-
- V-3069
- Rule IDs
-
- SV-3069r3_rule
Checks: C-3532r7_chk
Review the network device configuration to verify only secure protocols using FIPS 140-2 validated cryptographic modules are used for any administrative access. Some of the secure protocols used for administrative and management access are listed below. This list is not all inclusive and represents a sample selection of secure protocols. -SSHv2 -SCP -HTTPS -SSL -TLS If management connections are established using protocols without FIPS 140-2 validated cryptographic modules, this is a finding.
Fix: F-3094r5_fix
Configure the network device to use secure protocols with FIPS 140-2 validated cryptographic modules.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1640
- Vuln IDs
-
- V-3070
- Rule IDs
-
- SV-3070r2_rule
Checks: C-3542r4_chk
Review the configuration to verify all attempts to access the device via management connection are logged.
Fix: F-3095r3_fix
Configure the device to log all access attempts to the device to establish a management connection for administrative access.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1030
- Vuln IDs
-
- V-3072
- Rule IDs
-
- SV-3072r2_rule
Checks: C-3636r5_chk
IOS Procedure: With online editing, the "show running-config" command will only show the current running configuration settings, which are different from the IOS defaults. The "show startup-config" command will show the NVRAM startup configuration. Compare the two configurations to ensure they are synchronized. JUNOS Procedure: This will never be a finding. The active configuration is stored on flash as juniper.conf. A candidate configuration allows configuration changes while in configuration mode without initiating operational changes. The router implements the candidate configuration when it is committed; thereby, making it the new active configuration—at which time it will be stored on flash as juniper.conf and the old juniper.conf will become juniper.conf.1.
Fix: F-3097r4_fix
Add procedures to the standard operating procedure to keep the running configuration synchronized with the startup configuration.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0730
- Vuln IDs
-
- V-3079
- Rule IDs
-
- SV-3079r2_rule
Checks: C-3571r3_chk
Ensure finger has not been implemented in the configuration by verifying the vendor default and reviewing the configuration.
Fix: F-3104r3_fix
Disable the finger service.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0740
- Vuln IDs
-
- V-3085
- Rule IDs
-
- SV-3085r2_rule
Checks: C-3572r3_chk
Review the device configuration to determine that HTTP is not enabled for administrative access.
Fix: F-3110r4_fix
Configure the device to disable using HTTP (port 80) for administrative access.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0240
- Vuln IDs
-
- V-3143
- Rule IDs
-
- SV-3143r2_rule
Checks: C-40236r1_chk
Review the network element configuration to determine if the vendor default password is active.
Fix: F-35391r2_fix
Remove any vendor default passwords from the network element configuration.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0700
- Vuln IDs
-
- V-3160
- Rule IDs
-
- SV-3160r2_rule
Checks: C-3549r2_chk
Have the administrator display the OS version in operation. The OS must be current with related IAVMs addressed.
Fix: F-3185r2_fix
Update operating system and address all related IAVMs.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1636
- Vuln IDs
-
- V-3175
- Rule IDs
-
- SV-3175r3_rule
Checks: C-3516r7_chk
Review the network device configuration to verify all management connections for administrative access require authentication.
Fix: F-3200r3_fix
Configure authentication for all management connections.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1660
- Vuln IDs
-
- V-3196
- Rule IDs
-
- SV-3196r2_rule
Checks: C-3820r5_chk
Review the device configuration to verify it is configured to use SNMPv3 with both SHA authentication and privacy using AES encryption. If the site is using Version 1 or Version 2 with all of the appropriate patches and has developed a migration plan to implement the Version 3 Security Model, this finding can be downgraded to a Category II. To verify the appropriate patches on CISCO devices: Check the following IAVMs associated with SNMPv1: 1. 2001-B-0001 (V0005809) Cisco IOS Software SNMP Read-Write ILMI Community String Vulnerability 2. 2002-A-SNMP-001 (V0005835) Multiple Simple Network Management Protocol Vulnerabilities in Perimeter Devices (Cisco Security Advisory: Malformed SNMP Message-Handling Vulnerabilities) To verify the appropriate patches on other vendors refer to this web site: http://www.cert.org/advisories/CA-2002-03.html. If the targeted asset is running SNMPv3 and does not support SHA or AES, but the device is configured to use MD5 authentication and DES or 3DES encryption, then the finding can be downgraded to a Category III. If the site is using Version 1 or Version 2 and has installed all of the appropriate patches or upgrades to mitigate any known security vulnerabilities, this finding can be downgraded to a Category II. In addition, if the device does not support SNMPv3, this finding can be downgraded to a Category III provided all of the appropriate patches to mitigate any known security vulnerabilities have been applied and has developed a migration plan that includes the device upgrade to support Version 3 and the implementation of the Version 3 Security Model.
Fix: F-3221r3_fix
If SNMP is enabled, configure the network element to use SNMP Version 3 Security Model with FIPS 140-2 validated cryptography (i.e., SHA authentication and AES encryption).
- RMF Control
- Severity
- H
- CCI
- Version
- NET1665
- Vuln IDs
-
- V-3210
- Rule IDs
-
- SV-3210r2_rule
Checks: C-3822r5_chk
Review the network element configuration and verify if either of the SNMP community strings “public” or “private” is being used.
Fix: F-3235r4_fix
Configure unique SNMP community strings replacing the default community strings.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0440
- Vuln IDs
-
- V-3966
- Rule IDs
-
- SV-3966r3_rule
Checks: C-3502r4_chk
Review the network device configuration to determine if an authentication server is defined for gaining administrative access. If so, there must be only one account configured locally for an emergency. Verify the username and password for the emergency account is contained within a sealed envelope kept in a safe.
Fix: F-3899r4_fix
Configure the device to only allow one local account for emergency access and store the credentials in a secret manner.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1624
- Vuln IDs
-
- V-3967
- Rule IDs
-
- SV-3967r2_rule
Checks: C-3511r3_chk
Review the configuration and verify a session using the console port will time out after 10 minutes or less of inactivity.
Fix: F-3900r4_fix
Configure the timeout for idle console connection to 10 minutes or less.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0894
- Vuln IDs
-
- V-3969
- Rule IDs
-
- SV-3969r3_rule
Checks: C-3942r9_chk
Review the network device configuration and verify SNMP community strings are read-only when using SNMPv1, v2c, or basic v3 (no authentication or privacy). Write access may be used if authentication is configured when using SNMPv3. If write-access is used for SNMP versions 1, 2c, or 3-noAuthNoPriv mode and there is no documented approval by the IAO, this is a finding.
Fix: F-3902r7_fix
Configure the network device to allow for read-only SNMP access when using SNMPv1, v2c, or basic v3 (no authentication or privacy). Write access may be used if authentication is configured when using SNMPv3.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-VLAN-004
- Vuln IDs
-
- V-3971
- Rule IDs
-
- SV-3971r1_rule
Checks: C-4028r1_chk
Review the switch configurations and verify that no access ports have been assigned membership to the VLAN 1. A good method of ensuring there is not membership to VLAN 1 is to have the following configured: interface VLAN1 no ip address shutdown This technique does not prevent switch control plane protocols such as CDP, DTP, VTP, and PAgP from using VLAN 1. A show vlan 1 command can be used to verify what ports are assigned to VLAN 1.
Fix: F-3904r1_fix
Best practices for VLAN-based networks is to prune unnecessary ports from gaining access to VLAN1 as well as the management VLAN, and to separate in-band management, device protocol, and data traffic.
- RMF Control
- Severity
- L
- CCI
- Version
- NET-VLAN-005
- Vuln IDs
-
- V-3972
- Rule IDs
-
- SV-3972r1_rule
Checks: C-4030r1_chk
Review the switch configurations and note any ports assigned to VLAN 1. A show vlan command can also be used to verify what ports are assigned to VLAN 1.
Fix: F-3905r1_fix
Best practice for VLAN-based networks is to prune unnecessary ports from gaining access to VLAN1 and insure that it does not traverse trunks not requiring VLAN1 traffic.
- RMF Control
- Severity
- L
- CCI
- Version
- NET-VLAN-002
- Vuln IDs
-
- V-3973
- Rule IDs
-
- SV-3973r1_rule
Checks: C-4035r1_chk
Review the switch configurations and examine all interfaces. Each interface not in use should have membership to a VLAN that is not used for any other purpose. Below would be an example.interface FastEthernet0/5switchport mode accessswitchport access vlan 999shutdownFor older switches such as the Catalyst 1900, you would see something like the following:interface FastEthernet0/5vlan-membership static 999shutdown
Fix: F-3906r1_fix
Assign all disabled ports to an unused VLAN. Do not use VLAN1.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-VLAN-009
- Vuln IDs
-
- V-3984
- Rule IDs
-
- SV-3984r1_rule
Checks: C-4034r1_chk
Review the switch configurations and examine all access ports. Verify that they do not belong to the native VLAN. If a native VLAN has not been configured (see NET-VLAN-008), the default is VLAN 1.
Fix: F-3917r1_fix
To insure the integrity of the trunk link and prevent unauthorized access, the native VLAN of the trunk port should be changed from the default VLAN1 to its own unique VLAN. Access switchports must never be assigned to the native VLAN.
- RMF Control
- Severity
- H
- CCI
- Version
- NET1623
- Vuln IDs
-
- V-4582
- Rule IDs
-
- SV-4582r3_rule
Checks: C-3510r4_chk
Review the network device's configuration and verify authentication is required for console access.
Fix: F-4515r4_fix
Configure authentication for console access on the network device.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1021
- Vuln IDs
-
- V-4584
- Rule IDs
-
- SV-4584r2_rule
Checks: C-3950r3_chk
Review the network element’s configuration to ensure all messages up to and including severity level 6 (informational) are logged and sent to a syslog server. Severity Level Message Type 0 Emergencies 1 Alerts 2 Critical 3 Errors 4 Warning 5 Notifications 6 Informational 7 Debugging
Fix: F-4517r2_fix
Configure the network element to log all messages except debugging and send all log data to a syslog server.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1637
- Vuln IDs
-
- V-5611
- Rule IDs
-
- SV-5611r2_rule
Checks: C-3527r4_chk
Review the configuration and verify management access to the device is allowed only from hosts within the management network.
Fix: F-5522r3_fix
Configure an ACL or filter to restrict management access to the device from only the management network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1645
- Vuln IDs
-
- V-5612
- Rule IDs
-
- SV-5612r2_rule
Checks: C-3534r4_chk
Review the configuration and verify the timeout is set for 60 seconds or less. The SSH service terminates the connection if protocol negotiation (that includes user authentication) is not complete within this timeout period.
Fix: F-5523r4_fix
Configure the network element so it will require a secure shell timeout of 60 seconds or less.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1646
- Vuln IDs
-
- V-5613
- Rule IDs
-
- SV-5613r2_rule
Checks: C-3538r4_chk
Review the configuration and verify the number of unsuccessful SSH login attempts is set at 3.
Fix: F-5524r7_fix
Configure the network element to require a maximum number of unsuccessful SSH login attempts at 3.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-VLAN-008
- Vuln IDs
-
- V-5622
- Rule IDs
-
- SV-5622r1_rule
Checks: C-3770r1_chk
Review the switch configurations and examine all trunk links. Verify the native VLAN has been configured to a VLAN other than the default VLAN 1. Following is an example of assigning a trunk port to a VLAN: Review the switch configurations and examine all trunk links. Verify that the native VLAN has been configured to a VLAN other than the default VLAN 1. Following is an example of defining the native VLAN for a trunk port: interface FastEthernet0/23 description Trunk Port no ip address no cdp enable switchport trunk encapsulation dot1q switchport mode trunk switchport trunk native vlan 55 no shutdown A show vlan command can also be used to verify what VLAN the trunked ports are assigned to. An alterative 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. For CatOS, the switch can be configured with the dot1q-all-tagged global command. Introduced with IOS release 12.2(25), the global command vlan dot1q tag native can be used.
Fix: F-5533r1_fix
To ensure the integrity of the trunk link and prevent unauthorized access, the native VLAN of the trunk port should be changed from the default VLAN1 to its own unique VLAN. The native VLAN must be the same on both ends of the trunk link; otherwise traffic could accidently leak between broadcast domains.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-VLAN-007
- Vuln IDs
-
- V-5623
- Rule IDs
-
- SV-5623r1_rule
Checks: C-3769r1_chk
Review the switch configurations and examine all access ports. Verify that the port is not in trunk mode (i.e. for Catalyst using IOS the interface should have the command switchport mode access—not switchport mode trunk or older switches trunk off and not trunk on). A show trunk command can also be used to display all ports in trunk mode. Trace the connections from the physical port with trunk mode. This should be a Gigabit Ethernet or Fast Ethernet connection to another switch or router—it should not be connected to a workstation.
Fix: F-5534r1_fix
Disable trunking on all access ports.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-NAC-012
- Vuln IDs
-
- V-5624
- Rule IDs
-
- SV-5624r1_rule
Checks: C-3773r1_chk
Review the switch configuration for the following interface command: dot1x reauthentication Once re-authentication is enabled, the default is 60 minutes. The interval can be made smaller. For example, if you would want re-authentication to occur every 30 minutes, you would configure the following interface commnand: dot1x timeout reauth-period 1800
Fix: F-5535r1_fix
Ensure 802.1x reauthentication occurs every 60 minutes.
- RMF Control
- Severity
- H
- CCI
- Version
- NET-NAC-009
- Vuln IDs
-
- V-5626
- Rule IDs
-
- SV-5626r3_rule
Checks: C-23203r7_chk
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. If 802.1x authentication is not configured on these host-facing access switch ports, this is a CAT 1 finding. If MAC address filtering is implemented in lieu of 802.1x authentication, this finding will be downgraded to a CAT 3. NOTE: The section below is intended for classified networks. If it’s determined that 802.1x is not implemented on a classified network, the Traditional review team must be notified to determine if the physical requirements are implemented. For a site to be downgraded to a CAT III open finding, the physical security requirements must be implemented in addition to static MAC or sticky secure MAC port security. If both physical and logical downgrades are not implemented, a CAT I open finding will be issued. If classified LAN drops are not authenticated by an 802.1x implementation, they must be located within spaces properly established as Secret vaults, Secret Secure Rooms (AKA: Collateral Classified Open Storage Areas), TS secure room, or SCIF. Otherwise, one of the following supplemental physical security controls must be implemented. 1. Wall jacks must be secured when unattended by persons with Secret or higher clearance with a properly constructed lock box (Hoffman or similar commercial product or locally fabricated). The lock box must have no exposed or removable hinges. The hasp hardware must be riveted to the box or otherwise installed so that removal will require physical breaking of the box; thereby leaving evidence of actual or attempted entry. The lock box must be secured with a 3-position high security combination padlock (IAW the NSTISSI 7003). The S&G 8077 combination padlock is the only existing padlock meeting this standard. 2. If lock boxes are not used, the alternative is to physically disconnect the SIPRNet link at the SIPRNet point of presence (PoP) after normal duty hours. The PoP must be located within a proper Secret or higher secure room.
Fix: F-5537r4_fix
Configure 802.1x authentication on all host facing access switch ports.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-VLAN-006
- Vuln IDs
-
- V-5628
- Rule IDs
-
- SV-5628r1_rule
Checks: C-3767r1_chk
If switch clustering is used, review the configuration of the VLAN command switch and look for the command cluster management-vlan. The new management VLAN ID follows this command. For unclustered switches, review the configuration of each switch. All ports, including the internal management interface (sc0), are configured by default to be members of VLAN 1. The management VLAN can be identified by its switch virtual interface (SVI) defined that contains the IP address for the internal management interface. Note the IP address defined for the sc0 interface. The IP address of the sc0 interface can be accessed only by hosts connected to ports that belong to the management VLAN. Below is an example of disabling VLAN 1 and creating an SVI that could be used for the management VLAN. interface VLAN1 no ip address shutdown interface VLAN10 ip address 10.0.1.10 255.255.255.0 no shutdown Note: The management VLAN can also be defined by the set command when configuring the IP address of the Sc0. set interface sc0 10.0.1.10 255.255.255.0
Fix: F-5539r1_fix
Best practices for VLAN-based networks is create a dedicated management VLAN, prune unnecessary ports from gaining access to VLAN1 as well as the management VLAN, and to separate in-band management, device protocol, and data traffic.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0965
- Vuln IDs
-
- V-5646
- Rule IDs
-
- SV-5646r4_rule
Checks: C-3604r8_chk
Review the device configuration to determine if threshold filters or timeout periods are set for dropping excessive half-open TCP connections. For timeout periods, the time should be set to 10 seconds or less. If the device can not be configured for 10 seconds or less, it should be set to the least amount of time allowable in the configuration. Threshold filters will need to be determined by the organization for optimal filtering.
Fix: F-5557r6_fix
Configure the device to drop half-open TCP connections through threshold filtering or timeout periods.
- RMF Control
- Severity
- L
- CCI
- Version
- NET1629
- Vuln IDs
-
- V-7011
- Rule IDs
-
- SV-7365r2_rule
Checks: C-3513r3_chk
Review the configuration and verify the auxiliary port is disabled unless a secured modem providing encryption and authentication is connected.
Fix: F-6614r3_fix
Disable the auxiliary port. If used for out-of-band administrative access, the port must be connected to a secured modem providing encryption and authentication.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0744
- Vuln IDs
-
- V-14669
- Rule IDs
-
- SV-15313r2_rule
Checks: C-12779r4_chk
Review the device configuration and verify there are no BSDr commands (e.g., rsh, rlogin, rcp, rdump, rrestore, and rdist) enabled.
Fix: F-14130r4_fix
Configure the device to disable BSDr command services.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0813
- Vuln IDs
-
- V-14671
- Rule IDs
-
- SV-15327r2_rule
Checks: C-12793r5_chk
Review the device configuration and verify it is authenticating the NTP messages received from the NTP server or peer. Authentication must be performed using either PKI (supported in NTP v4) or SHA-1 hashing algorithm. If SHA-1 is not supported by both the NTP client and server, then MD5 can be used.
Fix: F-14132r1_fix
Configure the device to authenticate all received NTP messages using either PKI (supported in NTP v4) or SHA-1 hashing algorithm. If SHA-1 is not supported by this client or the NTP peer or server, then MD5 can be used.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1647
- Vuln IDs
-
- V-14717
- Rule IDs
-
- SV-15459r2_rule
Checks: C-12924r6_chk
Review the configuration and verify SSH Version 1 is not being used for administrative access.
Fix: F-14184r3_fix
Configure the network element to use SSH version 2.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0433
- Vuln IDs
-
- V-15432
- Rule IDs
-
- SV-16259r2_rule
Checks: C-14439r4_chk
Verify an authentication server is required to access the device and that there are two or more authentication servers defined.
Fix: F-15096r2_fix
Ensure an authentication server is required to access the device and that there are two or more authentication servers defined.
- RMF Control
- Severity
- H
- CCI
- Version
- NET0441
- Vuln IDs
-
- V-15434
- Rule IDs
-
- SV-16261r2_rule
Checks: C-14441r3_chk
Review the emergency account configured on the network element and verify that it has been assigned to a privilege level that will enable the administrator to perform necessary administrative functions when the authentication server is not online.
Fix: F-15098r6_fix
Assign a privilege level to the emergency account to allow the administrator to perform necessary administrative functions when the authentication server is not online.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0990
- Vuln IDs
-
- V-17820
- Rule IDs
-
- SV-19074r1_rule
Checks: C-19237r1_chk
Examine the connection from the OOBM access switch to the managed network elements. Verify which interface is being used at the managed network elements so that it can be determined if the interface is a true OOBM interface.
Fix: F-17735r1_fix
Physically connected the OOBM access switch to the managed network element OOBM interface.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0991
- Vuln IDs
-
- V-17821
- Rule IDs
-
- SV-19075r2_rule
Checks: C-19238r3_chk
The managed network element’s OOBM interface must be configured with an IP address from the address space belonging to the OOBM network. After determining which interface is connected to the OOBM access switch, review the managed device configuration and verify the interface has been assigned an address from the local management address block.
Fix: F-17736r1_fix
Configure the managed network element’s OOBM interface with an IP address from the address space belonging to the OOBM network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0994
- Vuln IDs
-
- V-17824
- Rule IDs
-
- SV-19078r1_rule
Checks: C-19241r1_chk
Review the managed switch configuration and verify that the access port connected to the OOBM access switch has been assigned to the management VLAN.
Fix: F-17739r1_fix
If the management interface is an access switchport, assign it to a separate management VLAN while the remainder of the access switchports can be assigned to user VLANs belonging to the managed network. This provides some level of separation between the management network and the managed network.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0995
- Vuln IDs
-
- V-17825
- Rule IDs
-
- SV-19079r1_rule
Checks: C-19242r1_chk
Review the managed switch configuration and verify that an address has been configured for management VLAN from space belonging to the OOBM network that has been assigned to that site.
Fix: F-17740r1_fix
Assign an IP address to the management VLAN from the address space belonging to the OOBM network.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0996
- Vuln IDs
-
- V-17826
- Rule IDs
-
- SV-19080r1_rule
Checks: C-19243r1_chk
Review the managed switch configuration and verify that the access port connected to the OOBM access switch is the only port has been assigned to the management VLAN.
Fix: F-17741r1_fix
Ensure that the access switchport connecting to the OOBM access switch is the only port with membership to the management VLAN
- RMF Control
- Severity
- L
- CCI
- Version
- NET0997
- Vuln IDs
-
- V-17827
- Rule IDs
-
- SV-19081r1_rule
Checks: C-19244r1_chk
By default all the VLANs that exist on a switch are active on a trunk link. Since the switch is being managed via OOBM connection, management traffic should not traverse any trunk links.
Fix: F-17744r1_fix
Prune the management VLAN from any VLAN trunk links belonging to the managed network’s infrastructure.
- RMF Control
- Severity
- M
- CCI
- Version
- NET1003
- Vuln IDs
-
- V-17832
- Rule IDs
-
- SV-19090r1_rule
Checks: C-19249r1_chk
Review the switch configuration and verify that the management VLAN has been assigned an IP address from the management network address block. Following is an example for a Cisco Catalyst switch: interface VLAN 10 description Management VLAN ip address 10.1.1.10 255.255.255.0 Note: The IP address of the switch can be accessed only by nodes connected to ports that belong to the management VLAN.
Fix: F-17749r1_fix
Configure the management VLAN with an IP address from the management network address block.
- RMF Control
- Severity
- L
- CCI
- Version
- NET-VLAN-023
- Vuln IDs
-
- V-18544
- Rule IDs
-
- SV-20088r2_rule
Checks: C-21399r3_chk
Review the device configuration to determine if a VLAN has been established for printers.
Fix: F-19148r3_fix
Create a VLAN on the device for print type devices and assign printers to the VLAN ID.
- RMF Control
- Severity
- L
- CCI
- Version
- NET-NAC-032
- Vuln IDs
-
- V-18565
- Rule IDs
-
- SV-20109r1_rule
Checks: C-21652r1_chk
A shutdown action puts the interface into the error-disabled state immediately and sends an SNMP trap notification if it receives a frame with a different layer 2 source address that what has been configured or learned for port security. The following Catalyst IOS interface command will shutdown the interface when such an event occurs: switchport port-security violation shutdown
Fix: F-19192r1_fix
Configure the port to shutdown when insecure hosts are connected to the wall jack.
- RMF Control
- Severity
- M
- CCI
- Version
- NET-NAC-031
- Vuln IDs
-
- V-18566
- Rule IDs
-
- SV-20110r3_rule
Checks: C-21653r5_chk
Review the switch configuration to verify each access port is configured for a single registered MAC address. Some technologies are exempt from requiring a single MAC address per access port; however, restrictions still apply. VoIP or VTC endpoints may provide a PC port so a PC can be connected. Each of the devices will need to be statically assigned to each access port. Another green initiative where a single LAN drop is shared among several devices is called "hot-desking", which is related to conservation of office space and teleworking. Hot-desking is where several people are assigned to work at the same desk at different times, each user with their own PC. In this case, a different MAC address needs to be permitted for each PC that is connecting to the LAN drop in the workspace. Additionally, this workspace could contain a single phone (and possibly desktop VTC endpoint) used by all assignees and the PC port on it might be the connection for their laptop. In this case, it is best not to use sticky port security, but to use a static mapping of authorized devices or implement 802.1x. If this is not a teleworking remote location, this exemption does not apply.
Fix: F-19193r3_fix
Configure the switch to limit the maximum number of registered MAC addresses on each access switch port to one.
- RMF Control
- Severity
- L
- CCI
- Version
- NET0812
- Vuln IDs
-
- V-23747
- Rule IDs
-
- SV-28651r2_rule
Checks: C-3581r3_chk
Review the configuration and verify two NTP servers have been defined.
Fix: F-3044r1_fix
Specify two NTP server IP addresses on the device to be used to request time from.
- RMF Control
- Severity
- M
- CCI
- Version
- NET0405
- Vuln IDs
-
- V-28784
- Rule IDs
-
- SV-36774r2_rule
Checks: C-35853r2_chk
Verify the call home service or feature is disabled on the device.
Fix: F-31103r1_fix
Configure the network device to disable the call home service or feature.