Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Layer 2 Switch Security Technical Implementation Guide

V8R19 · · · Released 23 Oct 2015 · 56 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

Layer 2 Switch Security Technical Implementation Guide
Digest of Updates vs. V8R16 · 25 Oct 2013 ✎ 46

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.

Content changes 46

  • V-14669 Medium descriptioncheck Network devices must have BSDr commands disabled.
  • V-14671 Medium descriptioncheckfix Network devices must authenticate all NTP messages received from NTP servers and peers.
  • V-14717 Medium checkfix The network device must not allow SSH Version 1 to be used for administrative access.
  • V-15432 Medium checkfix Network devices must use two or more authentication servers for the purpose of granting administrative access.
  • V-15434 High descriptioncheck The emergency account must be set to an appropriate authorization level to perform necessary administrative functions when the authentication server is not online.
  • V-17821 Medium descriptioncheckfix The network devices OOBM interface must be configured with an OOBM network address.
  • V-17832 Medium descriptioncheck The management VLAN must be configured with an IP address from the management network address block.
  • V-23747 Low descriptioncheckfix Network devices must use at least two NTP servers to synchronize time.
  • V-28784 Medium check A service or feature that calls home to the vendor must be disabled.
  • V-3012 High descriptioncheckfix Network devices must be password protected.
  • V-3013 Medium descriptioncheckfix Network devices must display the DoD-approved logon banner warning.
  • V-3014 Medium descriptioncheckfix The network devices must timeout management connections for administrative access after 10 minutes or less of inactivity.
  • V-3020 Low descriptioncheck Network devices must have DNS servers defined if it is configured as a client resolver.
  • V-3021 Medium checkfix Network devices must only allow SNMP access from addresses belonging to the management network.
  • V-3043 Medium checkfix The network device must use different SNMP community names or groups for various levels of read and write access.
  • V-3056 High check Group accounts must not be configured for use on the network device.
  • V-3057 Medium description Authorized accounts must be assigned the least privilege level necessary to perform assigned duties.
  • V-3058 Medium check Unauthorized accounts must not be configured for access to the network device.
  • V-3062 High descriptioncheckfix Network devices must be configured to ensure passwords are not viewable when displaying configuration information.
  • V-3069 Medium check Management connections to a network device must be established using secure protocols with FIPS 140-2 validated cryptographic modules.
  • V-3070 Low check Network devices must log all attempts to establish a management connection for administrative access.
  • V-3072 Low check The running configuration must be synchronized with the startup configuration after changes have been made and implemented.
  • V-3079 Low descriptioncheckfix Network devices must have the Finger service disabled.
  • V-3085 Medium check Network devices must have HTTP service for administrative access disabled.
  • V-3143 High descriptioncheckfix Network devices must not have any default manufacturer passwords.
  • V-3160 Medium checkfix Network devices must be running a current and supported operating system with all IAVMs addressed.
  • V-3175 High check The network device must require authentication prior to establishing a management connection for administrative access.
  • V-3196 High checkfix The network device must use SNMP Version 3 Security Model with FIPS 140-2 validated cryptography for any SNMP agent configured on the device.
  • V-3210 High descriptioncheck The network device must not use the default or well-known SNMP community strings public and private.
  • V-3966 Medium descriptioncheckfix In the event the authentication server is down or unavailable, there must only be one local account of last resort created for emergency use.
  • V-3967 Medium descriptioncheck The network devices must time out access to the console port at 10 minutes or less of inactivity.
  • V-3969 Medium check Network devices must only allow SNMP read-only access.
  • V-3971 Medium descriptioncheckfix VLAN 1 must not be used for user VLANs.
  • V-3972 Low descriptioncheckfix VLAN 1 must be pruned from all trunk and access ports that do not require it.
  • V-3973 Low check Disabled switch ports must be placed in an unused VLAN (do not use VLAN1).
  • V-3984 Medium descriptioncheckfix Access switchports must not be assigned to the native VLAN.
  • V-4582 High check The network device must require authentication for console access.
  • V-4584 Low checkfix The network device must log all messages except debugging and send all log data to a syslog server.
  • V-5611 Medium descriptioncheck The network devices must only allow management connections for administrative access from hosts residing in the management network.
  • V-5612 Medium descriptioncheckfix The network devices must be configured to timeout after 60 seconds or less for incomplete or broken SSH sessions.
  • V-5613 Medium checkfix The network device must be configured for a maximum number of unsuccessful SSH logon attempts set at 3 before resetting the interface.
  • V-5622 Medium descriptioncheckfix The native VLAN must be assigned to a VLAN ID other than the default VLAN for all 802.1q trunk links.
  • V-5623 Medium descriptioncheck Port trunking must be disabled on all access ports (do not configure trunk on, desirable, non-negotiate, or auto--only off).
  • V-5628 Medium descriptioncheckfix A dedicated management VLAN or VLANs must be configured to keep management traffic separate from user data and control plane traffic.
  • V-5646 Medium descriptioncheck The network device must drop half-open TCP connections through filtering thresholds or timeout periods.
  • V-7011 Low check The auxiliary port must be disabled unless it is connected to a secured modem providing encryption and authentication.
Sort by
c
Network devices must be password protected.
High - V-3012 - SV-3012r4_rule
RMF Control
Severity
H
CCI
Version
NET0230
Vuln IDs
  • V-3012
Rule IDs
  • SV-3012r4_rule
Network access control mechanisms interoperate to prevent unauthorized access and to enforce the organization's security policy. Access to the network must be categorized as administrator, user, or guest so the appropriate authorization can be assigned to the user requesting access to the network or a network device. Authorization requires an individual account identifier that has been approved, assigned, and configured on an authentication server. Authentication of user identities is accomplished through the use of passwords, tokens, biometrics, or in the case of multi-factor authentication, some combination thereof. Lack of authentication enables anyone to gain access to the network or possibly a network device providing opportunity for intruders to compromise resources within the network infrastructure.Information Assurance OfficerECSC-1, IAIA-1, IAIA-2
Checks: C-3456r6_chk

Review the network devices configuration to determine if administrative access to the device requires some form of authentication--at a minimum a password is required. If passwords aren't used to administrative access to the device, this is a finding.

Fix: F-3037r6_fix

Configure the network devices so it will require a password to gain administrative access to the device.

b
Network devices must display the DoD-approved logon banner warning.
Medium - V-3013 - SV-3013r4_rule
RMF Control
Severity
M
CCI
Version
NET0340
Vuln IDs
  • V-3013
Rule IDs
  • SV-3013r4_rule
All network devices must present a DoD-approved warning banner prior to a system administrator logging on. The banner should warn any unauthorized user not to proceed. It also should provide clear and unequivocal notice to both authorized and unauthorized personnel that access to the device is subject to monitoring to detect unauthorized usage. Failure to display the required logon warning banner prior to logon attempts will limit DoD's ability to prosecute unauthorized access and also presents the potential to give rise to criminal and civil liability for systems administrators and information systems managers. In addition, DISA's ability to monitor the device's usage is limited unless a proper warning banner is displayed. DoD CIO has issued new, mandatory policy standardizing the wording of "notice and consent" banners and matching user agreements for all Secret and below DoD information systems, including stand-alone systems by releasing DoD CIO Memo, "Policy on Use of Department of Defense (DoD) Information Systems Standard Consent Banner and User Agreement", dated 9 May 2008. The banner is mandatory and deviations are not permitted except as authorized in writing by the Deputy Assistant Secretary of Defense for Information and Identity Assurance. Implementation of this banner verbiage is further directed to all DoD components for all DoD assets via USCYBERCOM CTO 08-008A.Information Assurance OfficerECWM-1
Checks: C-3474r10_chk

Review the device configuration or request that the administrator logon 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." If the device configuration does not have a logon banner as stated above, this is a finding.

Fix: F-3038r8_fix

Configure all management interfaces to the network device to display the DoD-mandated warning banner verbiage at logon 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."

b
The network devices must timeout management connections for administrative access after 10 minutes or less of inactivity.
Medium - V-3014 - SV-3014r4_rule
RMF Control
Severity
M
CCI
Version
NET1639
Vuln IDs
  • V-3014
Rule IDs
  • SV-3014r4_rule
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled between the managed network device and a PC or terminal server when the later has been left unattended. In addition quickly terminating an idle session will also free up resources committed by the managed network device as well as reduce the risk of a management session from being hijacked. Setting the timeout of the session to 10 minutes or less increases the level of protection afforded critical network components.Information Assurance OfficerECSC-1
Checks: C-3540r6_chk

Review the management connection for administrative access and verify the network device is configured to time-out the connection at 10 minutes or less of inactivity. If the device does not terminate inactive management connections at 10 minutes or less, this is a finding.

Fix: F-3039r5_fix

Configure the network devices to ensure the timeout for unattended administrative access connections is no longer than 10 minutes.

a
Network devices must have DNS servers defined if it is configured as a client resolver.
Low - V-3020 - SV-3020r3_rule
RMF Control
Severity
L
CCI
Version
NET0820
Vuln IDs
  • V-3020
Rule IDs
  • SV-3020r3_rule
The susceptibility of IP addresses to spoofing translates to DNS host name and IP address mapping vulnerabilities. For example, suppose a source host wishes to establish a connection with a destination host and queries a DNS server for the IP address of the destination host name. If the response to this query is the IP address of a host operated by an attacker, the source host will establish a connection with the attacker's host, rather than the intended target. The user on the source host might then provide logon, authentication, and other sensitive data.Information Assurance OfficerECSC-1
Checks: C-3584r5_chk

Review the device configuration to ensure DNS servers have been defined if it has been configured as a client resolver (name lookup). If the device is configured as a client resolver and DNS servers are not defined, this is a finding.

Fix: F-3045r2_fix

Configure the device to include DNS servers or disable domain lookup.

b
Network devices must only allow SNMP access from addresses belonging to the management network.
Medium - V-3021 - SV-3021r3_rule
RMF Control
Severity
M
CCI
Version
NET0890
Vuln IDs
  • V-3021
Rule IDs
  • SV-3021r3_rule
Detailed information about the network is sent across the network via SNMP. If this information is discovered by attackers it could be used to trace the network, show the networks topology, and possibly gain access to network devices.Information Assurance OfficerECSC-1
Checks: C-3586r8_chk

Review the device configuration and verify it is configured to only allow SNMP access from addresses belonging to the management network. If the device is not configured to filter SNMP from the management network only, this is a finding.

Fix: F-3046r4_fix

Configure the network devices to only allow SNMP access from only addresses belonging to the management network.

b
The network device must use different SNMP community names or groups for various levels of read and write access.
Medium - V-3043 - SV-3043r4_rule
RMF Control
Severity
M
CCI
Version
NET1675
Vuln IDs
  • V-3043
Rule IDs
  • SV-3043r4_rule
Numerous vulnerabilities exist with SNMP; therefore, without unique SNMP community names, the risk of compromise is dramatically increased. This is especially true with vendors default community names which are widely known by hackers and other networking experts. If a hacker gains access to these devices and can easily guess the name, this could result in denial of service, interception of sensitive information, or other destructive actions.Information Assurance OfficerECSC-1
Checks: C-3825r7_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. If unique community strings or accounts are not used for SNMP peers, this is a finding.

Fix: F-3068r4_fix

Configure the SNMP community strings on the network device and change them from the default values. SNMP community strings and user passwords must be unique and 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.

c
Group accounts must not be configured for use on the network device.
High - V-3056 - SV-3056r7_rule
RMF Control
Severity
H
CCI
Version
NET0460
Vuln IDs
  • V-3056
Rule IDs
  • SV-3056r7_rule
Group accounts configured for use on a network device do not allow for accountability or repudiation of individuals using the shared account. If group accounts are not changed when someone leaves the group, that person could possibly gain control of the network device. Having group accounts does not allow for proper auditing of who is accessing or changing the network.Information Assurance OfficerIAIA-1, IAIA-2
Checks: C-3503r11_chk

Review the network device configuration and validate there are no group accounts configured for access. If a group account is configured on the device, this is a finding.

Fix: F-3081r9_fix

Configure individual user accounts for each authorized person then remove any group accounts.

b
Authorized accounts must be assigned the least privilege level necessary to perform assigned duties.
Medium - V-3057 - SV-3057r5_rule
RMF Control
Severity
M
CCI
Version
NET0465
Vuln IDs
  • V-3057
Rule IDs
  • SV-3057r5_rule
By not restricting authorized accounts to their proper privilege level, access to restricted functions may be allowed before authorized personnel are trained or experienced enough to use those functions. Network disruptions or outages may occur due to mistakes made by inexperienced persons using accounts with greater privileges than necessary.Information Assurance OfficerECSC-1
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.

b
Unauthorized accounts must not be configured for access to the network device.
Medium - V-3058 - SV-3058r5_rule
RMF Control
Severity
M
CCI
Version
NET0470
Vuln IDs
  • V-3058
Rule IDs
  • SV-3058r5_rule
A malicious user attempting to gain access to the network device may compromise an account that may be unauthorized for use. The unauthorized account may be a temporary or inactive account that is no longer needed to access the device. Denial of Service, interception of sensitive information, or other destructive actions could potentially take place if an unauthorized account is configured to access the network device.Information Assurance OfficerECSC-1, IAAC-1
Checks: C-3505r5_chk

Review the organization's responsibilities list and reconcile the list of authorized accounts 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.

c
Network devices must be configured to ensure passwords are not viewable when displaying configuration information.
High - V-3062 - SV-3062r4_rule
RMF Control
Severity
H
CCI
Version
NET0600
Vuln IDs
  • V-3062
Rule IDs
  • SV-3062r4_rule
Many attacks on information systems and network devices are launched from within the network. Hence, it is imperative that all passwords are encrypted so they cannot be intercepted by viewing the console or printout of the configuration.Information Assurance OfficerECSC-1
Checks: C-3508r5_chk

Review the network devices configuration to determine if passwords are viewable. If passwords are viewable in plaintext, this is a finding.

Fix: F-3087r7_fix

Configure the network devices to ensure passwords are not viewable when displaying configuration information.

b
Management connections to a network device must be established using secure protocols with FIPS 140-2 validated cryptographic modules.
Medium - V-3069 - SV-3069r5_rule
RMF Control
Severity
M
CCI
Version
NET1638
Vuln IDs
  • V-3069
Rule IDs
  • SV-3069r5_rule
Administration and management connections performed across a network are inherently dangerous because anyone with a packet sniffer and access to the right LAN segment can acquire the network device account and password information. With this intercepted information they could gain access to the router and cause denial of service attacks, intercept sensitive information, or perform other destructive actions.Information Assurance OfficerDCNR-1, ECSC-1
Checks: C-3532r8_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 using 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.

a
Network devices must log all attempts to establish a management connection for administrative access.
Low - V-3070 - SV-3070r4_rule
RMF Control
Severity
L
CCI
Version
NET1640
Vuln IDs
  • V-3070
Rule IDs
  • SV-3070r4_rule
Audit logs are necessary to provide a trail of evidence in case the network is compromised. Without an audit trail that provides a when, where, who and how set of information, repeat offenders could continue attacks against the network indefinitely. With this information, the network administrator can devise ways to block the attack and possibly identify and prosecute the attacker.Information Assurance OfficerECAT-1, ECAT-2
Checks: C-3542r6_chk

Review the configuration to verify all attempts to access the device via management connection are logged. If management connection attempts are not logged, this is a finding.

Fix: F-3095r3_fix

Configure the device to log all access attempts to the device to establish a management connection for administrative access.

a
The running configuration must be synchronized with the startup configuration after changes have been made and implemented.
Low - V-3072 - SV-3072r3_rule
RMF Control
Severity
L
CCI
Version
NET1030
Vuln IDs
  • V-3072
Rule IDs
  • SV-3072r3_rule
If the running and startup router configurations are not synchronized properly and a router malfunctions, it will not restart with all of the recent changes incorporated. If the recent changes were security related, then the routers would be vulnerable to attack.Information Assurance OfficerCOBR-1, ECSC-1
Checks: C-3636r6_chk

Review the running and boot configurations to determine if they are synchronized. 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. If running configuration and boot configurations are not the same, this is a finding.

Fix: F-3097r4_fix

Add procedures to the standard operating procedure to keep the running configuration synchronized with the startup configuration.

a
Network devices must have the Finger service disabled.
Low - V-3079 - SV-3079r3_rule
RMF Control
Severity
L
CCI
Version
NET0730
Vuln IDs
  • V-3079
Rule IDs
  • SV-3079r3_rule
The Finger service supports the UNIX Finger protocol, which is used for querying a host about the users that are logged on. This service is not necessary for generic users. If an attacker were to find out who is using the network, they may use social engineering practices to try to elicit classified DoD information.Information Assurance OfficerECSC-1
Checks: C-3571r5_chk

Review the device configuration to determine if Finger has been implemented. If the Finger service is enabled, this is a finding.

Fix: F-3104r4_fix

Configure the device to disable the Finger service.

b
Network devices must have HTTP service for administrative access disabled.
Medium - V-3085 - SV-3085r3_rule
RMF Control
Severity
M
CCI
Version
NET0740
Vuln IDs
  • V-3085
Rule IDs
  • SV-3085r3_rule
The additional services that the router is enabled for increases the risk for an attack since the router will listen for these services. In addition, these services provide an unsecured method for an attacker to gain access to the router. Most recent software versions support remote configuration and monitoring using the World Wide Web's HTTP protocol. In general, HTTP access is equivalent to interactive access to the router. The authentication protocol used for HTTP is equivalent to sending a clear-text password across the network, and, unfortunately, there is no effective provision in HTTP for challenge-based or one-time passwords. This makes HTTP a relatively risky choice for use across the public Internet. Any additional services that are enabled increase the risk for an attack since the router will listen for these services.Information Assurance OfficerECSC-1
Checks: C-3572r5_chk

Review the device configuration to determine that HTTP is not enabled for administrative access. If the device allows the use of HTTP for administrative access, this is a finding.

Fix: F-3110r4_fix

Configure the device to disable using HTTP (port 80) for administrative access.

c
Network devices must not have any default manufacturer passwords.
High - V-3143 - SV-3143r4_rule
RMF Control
Severity
H
CCI
Version
NET0240
Vuln IDs
  • V-3143
Rule IDs
  • SV-3143r4_rule
Network devices not protected with strong password schemes provide the opportunity for anyone to crack the password thus gaining access to the device and causing network outage or denial of service. Many default vendor passwords are well-known; hence, not removing them prior to deploying the network devices into production provides an opportunity for a malicious user to gain unauthorized access to the device.Information Assurance OfficerECSC-1
Checks: C-40236r3_chk

Review the network devices configuration to determine if the vendor default password is active. If any vendor default passwords are used on the device, this is a finding.

Fix: F-35391r3_fix

Remove any vendor default passwords from the network devices configuration.

b
Network devices must be running a current and supported operating system with all IAVMs addressed.
Medium - V-3160 - SV-3160r4_rule
RMF Control
Severity
M
CCI
Version
NET0700
Vuln IDs
  • V-3160
Rule IDs
  • SV-3160r4_rule
Network devices not running the latest tested and approved versions of software are vulnerable to network attacks. Running the most current, approved version of system and device software helps the site maintain a stable base of security fixes and patches, as well as enhancements to IP security. Viruses, denial of service attacks, system weaknesses, back doors and other potentially harmful situations could render a system vulnerable, allowing unauthorized access to DoD assets.Information Assurance OfficerECSC-1
Checks: C-3549r4_chk

Have the administrator display the OS version in operation. The OS must be current with related IAVMs addressed. If the device is using an OS that does not meet all IAVMs or currently not supported by the vendor, this is a finding.

Fix: F-3185r4_fix

Update operating system to a supported version that addresses all related IAVMs.

c
The network device must require authentication prior to establishing a management connection for administrative access.
High - V-3175 - SV-3175r5_rule
RMF Control
Severity
H
CCI
Version
NET1636
Vuln IDs
  • V-3175
Rule IDs
  • SV-3175r5_rule
Network devices with no password for administrative access via a management connection provide the opportunity for anyone with network access to the device to make configuration changes enabling them to disrupt network operations resulting in a network outage.Information Assurance OfficerECSC-1
Checks: C-3516r9_chk

Review the network device configuration to verify all management connections for administrative access require authentication. If authentication isn't configured for management access, this is a finding.

Fix: F-3200r3_fix

Configure authentication for all management connections.

c
The network device must use SNMP Version 3 Security Model with FIPS 140-2 validated cryptography for any SNMP agent configured on the device.
High - V-3196 - SV-3196r4_rule
RMF Control
Severity
H
CCI
Version
NET1660
Vuln IDs
  • V-3196
Rule IDs
  • SV-3196r4_rule
SNMP Versions 1 and 2 are not considered secure. Without the strong authentication and privacy that is provided by the SNMP Version 3 User-based Security Model (USM), an unauthorized user can gain access to network management information used to launch an attack against the network.Information Assurance OfficerECSC-1
Checks: C-3820r6_chk

Review the device configuration to verify it is configured to use SNMPv3 with both SHA authentication and privacy using AES encryption. Downgrades: 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. 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. If the device is configured to use to anything other than SNMPv3 with at least SHA-1 and AES, this is a finding. Downgrades can be determined based on the criteria above.

Fix: F-3221r5_fix

If SNMP is enabled, configure the network device to use SNMP Version 3 Security Model with FIPS 140-2 validated cryptography (i.e., SHA authentication and AES encryption).

c
The network device must not use the default or well-known SNMP community strings public and private.
High - V-3210 - SV-3210r4_rule
RMF Control
Severity
H
CCI
Version
NET1665
Vuln IDs
  • V-3210
Rule IDs
  • SV-3210r4_rule
Network devices may be distributed by the vendor pre-configured with an SNMP agent using the well-known SNMP community strings public for read only and private for read and write authorization. An attacker can obtain information about a network device using the read community string "public". In addition, an attacker can change a system configuration using the write community string "private".Information Assurance OfficerECSC-1, IAIA-1, IAIA-2
Checks: C-3822r7_chk

Review the network devices configuration and verify if either of the SNMP community strings "public" or "private" is being used. If default or well-known community strings are used for SNMP, this is a finding.

Fix: F-3235r4_fix

Configure unique SNMP community strings replacing the default community strings.

b
In the event the authentication server is down or unavailable, there must only be one local account of last resort created for emergency use.
Medium - V-3966 - SV-3966r5_rule
RMF Control
Severity
M
CCI
Version
NET0440
Vuln IDs
  • V-3966
Rule IDs
  • SV-3966r5_rule
Authentication for administrative access to the device is required at all times. A single account of last resort can be created on the device's local database for use in an emergency such as when the authentication server is down or connectivity between the device and the authentication server is not operable. The console or account of last resort logon credentials must be stored in a sealed envelope and kept in a safe.ECSC-1
Checks: C-3502r6_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 of last resort configured locally for an emergency. Verify the username and password for the account of last resort is contained within a sealed envelope kept in a safe. If an authentication server is used and more than one local account exists, this is a finding.

Fix: F-3899r8_fix

Configure the device to only allow one local account of last resort for emergency access and store the credentials in a secure manner.

b
The network devices must time out access to the console port at 10 minutes or less of inactivity.
Medium - V-3967 - SV-3967r4_rule
RMF Control
Severity
M
CCI
Version
NET1624
Vuln IDs
  • V-3967
Rule IDs
  • SV-3967r4_rule
Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition quickly terminating an idle session will also free up resources committed by the managed network device. Setting the timeout of the session to 10 minutes or less increases the level of protection afforded critical network components.Information Assurance OfficerECSC-1
Checks: C-3511r5_chk

Review the configuration and verify a session using the console port will time out after 10 minutes or less of inactivity. If console access is not configured to timeout at 10 minutes or less, this is a finding.

Fix: F-3900r4_fix

Configure the timeout for idle console connection to 10 minutes or less.

b
Network devices must only allow SNMP read-only access.
Medium - V-3969 - SV-3969r5_rule
RMF Control
Severity
M
CCI
Version
NET0894
Vuln IDs
  • V-3969
Rule IDs
  • SV-3969r5_rule
Enabling write access to the device via SNMP provides a mechanism that can be exploited by an attacker to set configuration variables that can disrupt network operations.Information Assurance OfficerECSC-1
Checks: C-3942r10_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 ISSO, 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.

b
VLAN 1 must not be used for user VLANs.
Medium - V-3971 - SV-3971r2_rule
RMF Control
Severity
M
CCI
Version
NET-VLAN-004
Vuln IDs
  • V-3971
Rule IDs
  • SV-3971r2_rule
In a VLAN-based network, switches use VLAN 1 as the default VLAN for in-band management and to communicate with other networking devices using Spanning-Tree Protocol (STP), Cisco Discovery Protocol (CDP), Dynamic Trunking Protocol (DTP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP)--all untagged traffic. As a consequence, VLAN 1 may unwisely span the entire network if not appropriately pruned. If its scope is large enough, the risk of compromise can increase significantly.Information Assurance OfficerDCCS-1
Checks: C-4028r3_chk

Review the device configuration and verify that access ports have not been assigned membership to the VLAN 1. If any access ports are found in VLAN 1, this is a finding.

Fix: F-3904r2_fix

Best practices for VLAN-based networks is to prune unnecessary ports from gaining access to VLAN 1 as well as the management VLAN, and to separate in-band management, device protocol, and data traffic.

a
VLAN 1 must be pruned from all trunk and access ports that do not require it.
Low - V-3972 - SV-3972r2_rule
RMF Control
Severity
L
CCI
Version
NET-VLAN-005
Vuln IDs
  • V-3972
Rule IDs
  • SV-3972r2_rule
VLAN 1 is a special VLAN that tags and handles most of the control plane traffic such as Spanning-Tree Protocol (STP), Cisco Discovery Protocol (CDP), Dynamic Trunking Protocol (DTP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) all VLAN 1 tagged traffic. VLAN 1 is enabled on all trunks and ports by default. With larger campus networks, care needs to be taken about the diameter of the VLAN 1 STP domain; instability in one part of the network could affect VLAN 1, thereby influencing control-plane stability and therefore STP stability for all other VLANs.Information Assurance OfficerECSC-1
Checks: C-4030r3_chk

Review the device configuration to determine if VLAN 1 is pruned from all trunk and access switch ports. If VLAN 1 is not pruned from trunk or access switch ports where it's not required, this is a finding.

Fix: F-3905r2_fix

Best practice for VLAN-based networks is to prune unnecessary ports from gaining access to VLAN 1 and insure that it does not traverse trunks not requiring VLAN 1 traffic.

a
Disabled switch ports must be placed in an unused VLAN (do not use VLAN1).
Low - V-3973 - SV-3973r2_rule
RMF Control
Severity
L
CCI
Version
NET-VLAN-002
Vuln IDs
  • V-3973
Rule IDs
  • SV-3973r2_rule
It is possible that a disabled port that is assigned to a user or management VLAN becomes enabled by accident or by an attacker and as a result gains access to that VLAN as a member.Information Assurance OfficerECSC-1
Checks: C-4035r3_chk

Review the device configuration to determine if all disabled ports have been placed into an unused VLAN. The VLAN must not be VLAN 1. If disabled ports are not assigned to an unused VLAN or have been placed into VLAN 1, this is a finding.

Fix: F-3906r2_fix

Assign all disabled ports to an unused VLAN. Do not use VLAN1.

b
Access switchports must not be assigned to the native VLAN.
Medium - V-3984 - SV-3984r2_rule
RMF Control
Severity
M
CCI
Version
NET-VLAN-009
Vuln IDs
  • V-3984
Rule IDs
  • SV-3984r2_rule
Double encapsulation can be initiated by an attacker who has access to a switch port belonging to the native VLAN of the trunk port. Knowing the victim's MAC address and with the victim attached to a different switch belonging to the same trunk group, thereby requiring the trunk link and frame tagging, the malicious user can begin the attack by sending frames with two sets of tags. The outer tag that will have the attacker's VLAN ID (probably the well-known and omnipresent VLAN 1) is stripped off by the switch, and the inner tag that will have the victim's VLAN ID is used by the switch as the next hop and sent out the trunk port.Information Assurance OfficerECSC-1
Checks: C-4034r2_chk

Review the switch configurations and examine all access ports. Verify that they do not belong to the native VLAN. If any access switch ports are assigned to the native VLAN, it is a finding.

Fix: F-3917r2_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 VLAN 1 to its own unique VLAN. Access switchports must never be assigned to the native VLAN.

c
The network device must require authentication for console access.
High - V-4582 - SV-4582r5_rule
RMF Control
Severity
H
CCI
Version
NET1623
Vuln IDs
  • V-4582
Rule IDs
  • SV-4582r5_rule
Network devices with no password for administrative access via the console provide the opportunity for anyone with physical access to the device to make configuration changes enabling them to disrupt network operations resulting in a network outage.Information Assurance OfficerIAIA-1, IAIA-2
Checks: C-3510r6_chk

Review the network device's configuration and verify authentication is required for console access. If authentication is not configured for console access, this is a finding.

Fix: F-4515r4_fix

Configure authentication for console access on the network device.

a
The network device must log all messages except debugging and send all log data to a syslog server.
Low - V-4584 - SV-4584r3_rule
RMF Control
Severity
L
CCI
Version
NET1021
Vuln IDs
  • V-4584
Rule IDs
  • SV-4584r3_rule
Logging is a critical part of router security. Maintaining an audit trail of system activity logs (syslog) can help identify configuration errors, understand past intrusions, troubleshoot service disruptions, and react to probes and scans of the network. Syslog levels 0-6 are the levels required to collect the necessary information to help in the recovery process.Information Assurance OfficerECAT-1, ECAT-2, ECSC-1
Checks: C-3950r6_chk

Review the network device 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 If logging does not capture of up severity level 6, this is a finding.

Fix: F-4517r6_fix

Configure the network device to log all messages except debugging and send all log data to a syslog server.

b
The network devices must only allow management connections for administrative access from hosts residing in the management network.
Medium - V-5611 - SV-5611r4_rule
RMF Control
Severity
M
CCI
Version
NET1637
Vuln IDs
  • V-5611
Rule IDs
  • SV-5611r4_rule
Remote administration is inherently dangerous because anyone with a sniffer and access to the right LAN segment could acquire the device account and password information. With this intercepted information they could gain access to the infrastructure and cause denial of service attacks, intercept sensitive information, or perform other destructive actions.Information Assurance OfficerECSC-1
Checks: C-3527r6_chk

Review the configuration and verify management access to the device is allowed only from hosts within the management network. If management access can be gained from outside of the authorized management network, this is a finding.

Fix: F-5522r4_fix

Configure an ACL or filter to restrict management access to the device from only the management network.

b
The network devices must be configured to timeout after 60 seconds or less for incomplete or broken SSH sessions.
Medium - V-5612 - SV-5612r3_rule
RMF Control
Severity
M
CCI
Version
NET1645
Vuln IDs
  • V-5612
Rule IDs
  • SV-5612r3_rule
An attacker may attempt to connect to the device using SSH by guessing the authentication method, encryption algorithm, and keys. Limiting the amount of time allowed for authenticating and negotiating the SSH session reduces the window of opportunity for the malicious user attempting to make a connection to the network device.Information Assurance OfficerECSC-1
Checks: C-3534r6_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. If the device is not configured to drop broken SSH sessions after 60 seconds, this is a finding.

Fix: F-5523r5_fix

Configure the network devices so it will require a secure shell timeout of 60 seconds or less.

b
The network device must be configured for a maximum number of unsuccessful SSH logon attempts set at 3 before resetting the interface.
Medium - V-5613 - SV-5613r4_rule
RMF Control
Severity
M
CCI
Version
NET1646
Vuln IDs
  • V-5613
Rule IDs
  • SV-5613r4_rule
An attacker may attempt to connect to the device using SSH by guessing the authentication method and authentication key or shared secret. Setting the authentication retry to 3 or less strengthens against a Brute Force attack.Information Assurance OfficerECSC-1
Checks: C-3538r8_chk

Review the configuration and verify the number of unsuccessful SSH logon attempts is set at 3. If the device is not configured to reset unsuccessful SSH logon attempts at 3, this is a finding.

Fix: F-5524r9_fix

Configure the network device to require a maximum number of unsuccessful SSH logon attempts at 3.

b
The native VLAN must be assigned to a VLAN ID other than the default VLAN for all 802.1q trunk links.
Medium - V-5622 - SV-5622r2_rule
RMF Control
Severity
M
CCI
Version
NET-VLAN-008
Vuln IDs
  • V-5622
Rule IDs
  • SV-5622r2_rule
VLAN hopping can be initiated by an attacker who has access to a switch port belonging to the same VLAN as the native VLAN of the trunk link connecting to another switch in which the victim is connected to. If the attacker knows the victim's MAC address, it can forge a frame with two 802.1q tags and a layer 2 header with the destination address of the victim. Since the frame will ingress the switch from a port belonging to its native VLAN, the trunk port connecting to victim's switch will simply remove the outer tag because native VLAN traffic is to be untagged. The switch will forward the frame unto the trunk link unaware of the inner tag with a VLAN ID for which the victim's switchport is a member of.Information Assurance OfficerECSC-1
Checks: C-3770r3_chk

Review the device configuration and examine all trunk links. Verify the native VLAN has been configured to a VLAN other than the default VLAN 1. If the native VLAN has been configured to VLAN 1, this is a finding.

Fix: F-5533r2_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 VLAN 1 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.

b
Port trunking must be disabled on all access ports (do not configure trunk on, desirable, non-negotiate, or auto--only off).
Medium - V-5623 - SV-5623r2_rule
RMF Control
Severity
M
CCI
Version
NET-VLAN-007
Vuln IDs
  • V-5623
Rule IDs
  • SV-5623r2_rule
Double encapsulation can be initiated by an attacker who has access to a switch port belonging to the native VLAN of the trunk port. Knowing the victims MAC address and with the victim attached to a different switch belonging to the same trunk group, thereby requiring the trunk link and frame tagging, the malicious user can begin the attack by sending frames with two sets of tags. The outer tag that will have the attackers VLAN ID (probably the well-known and omnipresent VLAN 1) is stripped off by the switch, and the inner tag that will have the victims VLAN ID is used by the switch as the next hop and sent out the trunk port.Information Assurance OfficerECSC-1
Checks: C-58983r1_chk

Review the device configuration to determine if trunking has been disabled on access ports. If trunking is enabled on any access port, this is a finding.

Fix: F-5534r1_fix

Disable trunking on all access ports.

b
The IAO/NSO will ensure if 802.1x Port Authentication is implemented, re-authentication must occur every 60 minutes.
Medium - V-5624 - SV-5624r1_rule
RMF Control
Severity
M
CCI
Version
NET-NAC-012
Vuln IDs
  • V-5624
Rule IDs
  • SV-5624r1_rule
Eliminating unauthorized access to the network from inside the enclave is vital to keeping a network secure. Internal access to the private network is enabled by simply connecting a workstation or laptop to a wall plate or access point located in the work area.Information Assurance OfficerECSC-1
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.

c
The switch must be configured to use 802.1x authentication on host facing access switch ports.
High - V-5626 - SV-5626r3_rule
RMF Control
Severity
H
CCI
Version
NET-NAC-009
Vuln IDs
  • V-5626
Rule IDs
  • SV-5626r3_rule
The IEEE 802.1x standard is a client-server based access control and authentication protocol that restricts unauthorized clients from connecting to a local area network through host facing switch ports. The authentication server authenticates each client connected to to a switch port before making any services available to the client from the LAN. Unless the client is successfully authenticated, 802.1x access control allows only Extensible Authentication Protocol over LAN (EAPOL) traffic through the port to which the client is connected. After authentication is successful, normal traffic can pass through the port. Without the use of 802.1x, a malicious user could use the switch port to connect an unauthorized piece of computer or other network device to inject or steal data from the network without detection.At this time, NET-NAC-009 can be downgraded to a CAT III finding if Static MAC filter is used in lieu of 802.1x authentication on host facing switch ports.Information Assurance OfficerECSC-1
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.

b
A dedicated management VLAN or VLANs must be configured to keep management traffic separate from user data and control plane traffic.
Medium - V-5628 - SV-5628r2_rule
RMF Control
Severity
M
CCI
Version
NET-VLAN-006
Vuln IDs
  • V-5628
Rule IDs
  • SV-5628r2_rule
All ports, including the internal sc0 interface, are configured by default to be members of VLAN 1. In a VLAN-based network, switches use VLAN 1 as the default VLAN for in-band management and to communicate with other networking devices using Spanning-Tree Protocol (STP), Cisco Discovery Protocol (CDP), Dynamic Trunking Protocol (DTP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) all untagged traffic. As a consequence, VLAN 1 may unwisely span the entire network if not appropriately pruned. If its scope is large enough, the risk of compromise can increase significantly.Information Assurance OfficerECSC-1
Checks: C-3767r3_chk

Review the device configurations to determine if a dedicated VLAN(s) have been implemented for the management network. VLAN 1 must not be used. If a dedicated VLAN or VLANs have not been established for the management network, this is a finding. If VLAN 1 is used for management, this is also a finding.

Fix: F-5539r2_fix

Best practices for VLAN-based networks is create a dedicated management VLAN, prune unnecessary ports from gaining access to VLAN 1 as well as the management VLAN, and to separate in-band management, device protocol, and data traffic.

b
The network device must drop half-open TCP connections through filtering thresholds or timeout periods.
Medium - V-5646 - SV-5646r5_rule
RMF Control
Severity
M
CCI
Version
NET0965
Vuln IDs
  • V-5646
Rule IDs
  • SV-5646r5_rule
A TCP connection consists of a three-way handshake message sequence. A connection request is transmitted by the originator, an acknowledgement is returned from the receiver, and then an acceptance of that acknowledgement is sent by the originator. An attacker's goal in this scenario is to cause a denial of service to the network or device by initiating a high volume of TCP packets, then never sending an acknowledgement, leaving connections in a half-opened state. Without the device having a connection or time threshold for these half-opened sessions, the device risks being a victim of a denial of service attack. Setting a TCP timeout threshold will instruct the device to shut down any incomplete connections. Services such as SSH, BGP, SNMP, LDP, etc. are some services that may be prone to these types of denial of service attacks. If the router does not have any BGP connections with BGP neighbors across WAN links, values could be set to even tighter constraints.Information Assurance OfficerECSC-1
Checks: C-3604r11_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 cannot 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. If the device is not configured in a way to drop half-open TCP connections using filtering or timeout periods, this is a finding.

Fix: F-5557r6_fix

Configure the device to drop half-open TCP connections through threshold filtering or timeout periods.

a
The auxiliary port must be disabled unless it is connected to a secured modem providing encryption and authentication.
Low - V-7011 - SV-7365r4_rule
RMF Control
Severity
L
CCI
Version
NET1629
Vuln IDs
  • V-7011
Rule IDs
  • SV-7365r4_rule
The use of POTS lines to modems connecting to network devices provides clear text of authentication traffic over commercial circuits that could be captured and used to compromise the network. Additional war dial attacks on the device could degrade the device and the production network. Secured modem devices must be able to authenticate users and must negotiate a key exchange before full encryption takes place. The modem will provide full encryption capability (Triple DES) or stronger. The technician who manages these devices will be authenticated using a key fob and granted access to the appropriate maintenance port, thus the technician will gain access to the managed device (router, switch, etc.). The token provides a method of strong (two-factor) user authentication. The token works in conjunction with a server to generate one-time user passwords that will change values at second intervals. The user must know a personal identification number (PIN) and possess the token to be allowed access to the device.Information Assurance OfficerECSC-1
Checks: C-3513r5_chk

Review the configuration and verify the auxiliary port is disabled unless a secured modem providing encryption and authentication is connected. If the auxiliary port is enabled without the use of a secured modem, this is a finding.

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.

b
Network devices must have BSDr commands disabled.
Medium - V-14669 - SV-15313r3_rule
RMF Control
Severity
M
CCI
Version
NET0744
Vuln IDs
  • V-14669
Rule IDs
  • SV-15313r3_rule
Berkeley Software Distribution (BSD) "r" commands allow users to execute commands on remote systems using a variety of protocols. The BSD "r" commands (e.g., rsh, rlogin, rcp, rdump, rrestore, and rdist) are designed to provide convenient remote access without passwords to services such as remote command execution (rsh), remote login (rlogin), and remote file copy (rcp and rdist). The difficulty with these commands is they use address-based authentication. An attacker who convinces a server that he is coming from a "trusted" machine can essentially get complete and unrestricted access to a system. The attacker can convince the server by impersonating a trusted machine and using IP address, by confusing DNS so that DNS thinks that the attacker's IP address maps to a trusted machine's name, or by any of a number of other methods.Information Assurance OfficerECSC-1
Checks: C-12779r5_chk

Review the device configuration and verify there are no BSDr commands (e.g., rsh, rlogin, rcp, rdump, rrestore, and rdist) enabled. If BSDr commands are enabled, this is a finding.

Fix: F-14130r4_fix

Configure the device to disable BSDr command services.

b
Network devices must authenticate all NTP messages received from NTP servers and peers.
Medium - V-14671 - SV-15327r4_rule
RMF Control
Severity
M
CCI
Version
NET0813
Vuln IDs
  • V-14671
Rule IDs
  • SV-15327r4_rule
Since NTP is used to ensure accurate log file timestamp information, NTP could pose a security risk if a malicious user were able to falsify NTP information. To launch an attack on the NTP infrastructure, a hacker could inject time that would be accepted by NTP clients by spoofing the IP address of a valid NTP server. To mitigate this risk, the time messages must be authenticated by the client before accepting them as a time source. Two NTP-enabled devices can communicate in either client-server mode or peer-to-peer mode (aka "symmetric mode"). The peering mode is configured manually on the device and indicated in the outgoing NTP packets. The fundamental difference is the synchronization behavior: an NTP server can synchronize to a peer with better stratum, whereas it will never synchronize to its client regardless of the client's stratum. From a protocol perspective, NTP clients are no different from the NTP servers. The NTP client can synchronize to multiple NTP servers, select the best server and synchronize with it, or synchronize to the averaged value returned by the servers. A hierarchical model can be used to improve scalability. With this implementation, an NTP client can also become an NTP server providing time to downstream clients at a higher stratum level and of decreasing accuracy than that of its upstream server. To increase availability, NTP peering can be used between NTP servers. In the event the device loses connectivity to it upstream NTP server, it will be able to choose time from one of its peers. The NTP authentication model is opposite of the typical client-server authentication model. NTP authentication enables an NTP client or peer to authenticate time received from their servers and peers. It's not used to authenticate NTP clients because NTP servers don't care about the authenticity of their clients, as they never accept any time from them.Information Assurance OfficerECSC-1
Checks: C-12793r7_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 NTP messages are not authenticated using PKI or SHA-1 hashing, this is a finding.

Fix: F-14132r2_fix

Configure the device to authenticate all received NTP messages using either PKI (supported in NTP v4) or SHA-1 hashing algorithm.

b
The network device must not allow SSH Version 1 to be used for administrative access.
Medium - V-14717 - SV-15459r4_rule
RMF Control
Severity
M
CCI
Version
NET1647
Vuln IDs
  • V-14717
Rule IDs
  • SV-15459r4_rule
SSH Version 1 is a protocol that has never been defined in a standard. Since SSH-1 has inherent design flaws which make it vulnerable to attacks, e.g., man-in-the-middle attacks, it is now generally considered obsolete and should be avoided by explicitly disabling fallback to SSH-1.Information Assurance OfficerECSC-1
Checks: C-12924r8_chk

Review the configuration and verify SSH Version 1 is not being used for administrative access. If the device is using an SSHv1 session, this is a finding.

Fix: F-14184r5_fix

Configure the network device to use SSH version 2.

b
Network devices must use two or more authentication servers for the purpose of granting administrative access.
Medium - V-15432 - SV-16259r4_rule
RMF Control
Severity
M
CCI
Version
NET0433
Vuln IDs
  • V-15432
Rule IDs
  • SV-16259r4_rule
The use of Authentication, Authorization, and Accounting (AAA) affords the best methods for controlling user access, authorization levels, and activity logging. By enabling AAA on the routers in conjunction with an authentication server such as TACACS+ or RADIUS, the administrators can easily add or remove user accounts, add or remove command authorizations, and maintain a log of user activity. The use of an authentication server provides the capability to assign router administrators to tiered groups that contain their privilege level that is used for authorization of specific commands. For example, user mode would be authorized for all authenticated administrators while configuration or edit mode should only be granted to those administrators that are permitted to implement router configuration changes.Information Assurance OfficerIAIA-1
Checks: C-14439r6_chk

Verify an authentication server is required to access the device and that there are two or more authentication servers defined. If the device is not configured for two separate authentication servers, this is a finding.

Fix: F-15096r3_fix

Configure the device to use two separate authentication servers.

c
The emergency account must be set to an appropriate authorization level to perform necessary administrative functions when the authentication server is not online.
High - V-15434 - SV-16261r4_rule
RMF Control
Severity
H
CCI
Version
NET0441
Vuln IDs
  • V-15434
Rule IDs
  • SV-16261r4_rule
The emergency account is to be configured as a local account on the network devices. It is to be used only when the authentication server is offline or not reachable via the network. The emergency account must be set to an appropriate authorization level to perform necessary administrative functions during this time.Information Assurance OfficerECSC-1
Checks: C-14441r5_chk

Review the emergency account configured on the network devices 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. If the emergency account is configured for more access than needed to troubleshoot issues, this is a finding.

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.

b
The OOBM access switch is not physically connected to the managed network element OOBM interface.
Medium - V-17820 - SV-19074r1_rule
RMF Control
Severity
M
CCI
Version
NET0990
Vuln IDs
  • V-17820
Rule IDs
  • SV-19074r1_rule
The OOBM access switch will connect to the management interface of the managed network elements. The management interface of the managed network element must be directly connected to the OOBM network to ensure seperation. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. System AdministratorInformation Assurance OfficerECSC-1
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.

b
The network devices OOBM interface must be configured with an OOBM network address.
Medium - V-17821 - SV-19075r4_rule
RMF Control
Severity
M
CCI
Version
NET0991
Vuln IDs
  • V-17821
Rule IDs
  • SV-19075r4_rule
The OOBM access switch will connect to the management interface of the managed network device. The management interface of the managed network device will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the OOBM interface does not have an IP address from the managed network address space, it will not have reachability from the NOC using scalable and normal control plane and forwarding mechanisms.System AdministratorInformation Assurance OfficerECSC-1
Checks: C-19238r5_chk

Review the device configuration to determine if the OOB management interface is assigned an appropriate IP address from the authorized OOB management network. If an IP address assigned to the interface is not from an authorized OOB management network, this is a finding.

Fix: F-17736r2_fix

Configure the OOB management interface with an IP address from the address space belonging to the OOBM network.

b
The management interface is an access switchport and has not been assigned to a separate management VLAN.
Medium - V-17824 - SV-19078r1_rule
RMF Control
Severity
M
CCI
Version
NET0994
Vuln IDs
  • V-17824
Rule IDs
  • SV-19078r1_rule
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network.System AdministratorInformation Assurance OfficerECSC-1
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.

a
An address has not been configured for the management VLAN from space belonging to the OOBM network assigned to that site.
Low - V-17825 - SV-19079r1_rule
RMF Control
Severity
L
CCI
Version
NET0995
Vuln IDs
  • V-17825
Rule IDs
  • SV-19079r1_rule
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. System AdministratorInformation Assurance OfficerECSC-1
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.

b
The access switchport connecting to the OOBM access switch is not the only port with membership to the management VLAN.
Medium - V-17826 - SV-19080r1_rule
RMF Control
Severity
M
CCI
Version
NET0996
Vuln IDs
  • V-17826
Rule IDs
  • SV-19080r1_rule
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. System AdministratorECSC-1
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

a
The management VLAN is not pruned from any VLAN trunk links belonging to the managed network’s infrastructure.
Low - V-17827 - SV-19081r1_rule
RMF Control
Severity
L
CCI
Version
NET0997
Vuln IDs
  • V-17827
Rule IDs
  • SV-19081r1_rule
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic; thereby, providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network. ISL and 802.1q trunking enables multiple VLANs to traverse the same physical links between layer 2 switches or between a layer 2 switch and a router. If the management VLAN is not pruned from any VLAN trunk links belonging to the managed network’s infrastructure, management traffic has the potential to leak into the production network. System AdministratorInformation Assurance OfficerECSC-1
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.

b
The management VLAN must be configured with an IP address from the management network address block.
Medium - V-17832 - SV-19090r2_rule
RMF Control
Severity
M
CCI
Version
NET1003
Vuln IDs
  • V-17832
Rule IDs
  • SV-19090r2_rule
If the management systems reside within the same layer 2 switching domain as the managed network device, then separate VLANs will be deployed to provide separation at that level. In this case, the management network still has its own subnet while at the same time it is defined as a unique VLAN.System AdministratorInformation Assurance OfficerECSC-1
Checks: C-19249r2_chk

Review the switch configuration to determine if the management VLAN has been assigned an IP address from the management network address block. If the management VLAN interface has not been assigned an IP address from the management network address block, this is a finding.

Fix: F-17749r1_fix

Configure the management VLAN with an IP address from the management network address block.

a
Printers must be assigned to a VLAN that is not shared by unlike devices.
Low - V-18544 - SV-20088r2_rule
RMF Control
Severity
L
CCI
Version
NET-VLAN-023
Vuln IDs
  • V-18544
Rule IDs
  • SV-20088r2_rule
Aspects of hardening the network wall plate may include traffic filtering or restrictions on connectivity to enforce a device-, community of interest-, or user-specific security policy. For example, if a printer were plugged into a switch port, it would be prudent to ensure that only printer traffic is allowed on that switch port. If the printer is unplugged and a substitute device other than a printer is plugged into that switch port, the substitute device should not be able to communicate arbitrarily with other devices because only printer traffic is allowed on that switch port.Information Assurance OfficerDCSP-1
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.

a
The IAO will ensure that all switchports configured using MAC port security will shutdown upon receiving a frame with a different layer 2 source address than what has been configured or learned for port security.
Low - V-18565 - SV-20109r1_rule
RMF Control
Severity
L
CCI
Version
NET-NAC-032
Vuln IDs
  • V-18565
Rule IDs
  • SV-20109r1_rule
The Port Security feature remembers the Ethernet MAC address connected to the switch port and allows only that MAC address to communicate on that port. If any other MAC address tries to communicate through the port, port security will disable the port. Information Assurance OfficerDCSP-1
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.

b
The switch must only allow a maximum of one registered MAC address per access port.
Medium - V-18566 - SV-20110r3_rule
RMF Control
Severity
M
CCI
Version
NET-NAC-031
Vuln IDs
  • V-18566
Rule IDs
  • SV-20110r3_rule
Limiting the number of registered MAC addresses on a switch access port can help prevent a CAM table overflow attack. This type of attack lets an attacker exploit the hardware and memory limitations of a switch. If there are enough entries stored in a CAM table before the expiration of other entries, no new entries can be accepted into the CAM table. An attacker will able to flood the switch with mostly invalid MAC addresses until the CAM table’s resources have been depleted. When there are no more resources, the switch has no choice but to flood all ports within the VLAN with all incoming traffic. This happens because the switch cannot find the switch port number for a corresponding MAC address within the CAM table, allowing the switch to become a hub and traffic to be monitored.Information Assurance OfficerDCSP-1
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.

a
Network devices must use at least two NTP servers to synchronize time.
Low - V-23747 - SV-28651r4_rule
RMF Control
Severity
L
CCI
Version
NET0812
Vuln IDs
  • V-23747
Rule IDs
  • SV-28651r4_rule
Without synchronized time, accurately correlating information between devices becomes difficult, if not impossible. If logs cannot be successfully compared between each of the routers, switches, and firewalls, it will be very difficult to determine the exact events that resulted in a network breach incident. NTP provides an efficient and scalable method for network devices to synchronize to an accurate time source.System AdministratorInformation Assurance OfficerECSC-1
Checks: C-3581r5_chk

Review the configuration and verify two NTP servers have been defined. If the device is not configured to use two separate NTP servers, this is a finding.

Fix: F-3044r2_fix

Configure the device to use two separate NTP servers.

b
A service or feature that calls home to the vendor must be disabled.
Medium - V-28784 - SV-36774r4_rule
RMF Control
Severity
M
CCI
Version
NET0405
Vuln IDs
  • V-28784
Rule IDs
  • SV-36774r4_rule
Call home services or features will routinely send data such as configuration and diagnostic information to the vendor for routine or emergency analysis and troubleshooting. The risk that transmission of sensitive data sent to unauthorized persons could result in data loss or downtime due to an attack.Information Assurance OfficerNetwork Security OfficerECSC-1
Checks: C-35853r3_chk

Review the device configuration to determine if the call home service or feature is disabled on the device. If the call home service is enabled on the device, this is a finding.

Fix: F-31103r1_fix

Configure the network device to disable the call home service or feature.