Cisco NX OS Switch NDM Security Technical Implementation Guide

  • Version/Release: V2R8
  • Published: 2024-02-06
  • Released: 2024-04-24
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
The Cisco switch must be configured to limit the number of concurrent management sessions to an organization-defined number.
AC-10 - Medium - CCI-000054 - V-220474 - SV-220474r879511_rule
RMF Control
AC-10
Severity
Medium
CCI
CCI-000054
Version
CISC-ND-000010
Vuln IDs
  • V-220474
  • V-101491
Rule IDs
  • SV-220474r879511_rule
  • SV-110595
Device management includes the ability to control the number of administrators and management sessions that manage a device. Limiting the number of allowed administrators and sessions per administrator based on account type, role, or access type is helpful in limiting risks related to DoS attacks. This requirement addresses concurrent sessions for administrative accounts and does not address concurrent sessions by a single administrator via multiple administrative accounts. The maximum number of concurrent sessions should be defined based upon mission needs and the operational environment for each system. At a minimum, limits must be set for SSH, HTTPS, account of last resort, and root account sessions.
Checks: C-22189r539143_chk

Review the switch configuration to determine if concurrent management sessions are limited as show in the example below: line vty session-limit 2 If the switch is not configured to limit the number of concurrent management sessions, this is a finding.

Fix: F-22178r539144_fix

Configure the switch to limit the number of concurrent management sessions to an organization-defined number as shown in the example below: SW4(config)# line vty SW4(config)# session-limit 2

b
The Cisco switch must be configured to automatically audit account creation.
AC-2 - Medium - CCI-000018 - V-220475 - SV-220475r879525_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-000018
Version
CISC-ND-000090
Vuln IDs
  • V-220475
  • V-101493
Rule IDs
  • SV-220475r879525_rule
  • SV-110597
Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accomplish this is to create a new account. Notification of account creation helps to mitigate this risk. Auditing account creation provides the necessary reconciliation that account management procedures are being followed. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes.
Checks: C-22190r539146_chk

Review the switch configuration to determine if it automatically audits account creation. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If account creation is not automatically audited, this is a finding.

Fix: F-22179r539147_fix

Configure the switch to log account creation using the following steps: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to automatically audit account modification.
AC-2 - Medium - CCI-001403 - V-220476 - SV-220476r879526_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001403
Version
CISC-ND-000100
Vuln IDs
  • V-220476
  • V-101495
Rule IDs
  • SV-220476r879526_rule
  • SV-110599
Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. Account management by a designated authority ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel with the appropriate and necessary privileges. Auditing account modification along with an automatic notification to appropriate individuals will provide the necessary reconciliation that account management procedures are being followed. If modifications to management accounts are not audited, reconciliation of account management procedures cannot be tracked.
Checks: C-22191r539149_chk

Review the switch configuration to determine if it automatically audits account modification. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If account modification is not automatically audited, this is a finding.

Fix: F-22180r539150_fix

Configure the switch to log account modification using the following steps: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to automatically audit account disabling actions.
AC-2 - Medium - CCI-001404 - V-220477 - SV-220477r879527_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001404
Version
CISC-ND-000110
Vuln IDs
  • V-220477
  • V-101497
Rule IDs
  • SV-220477r879527_rule
  • SV-110601
Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account disabling actions will support account management procedures. When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.
Checks: C-22192r539152_chk

Review the switch configuration to determine if it automatically audits account disabling. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If account disabling is not automatically audited, this is a finding.

Fix: F-22181r539153_fix

Configure the switch to log account disabling using the following steps: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to automatically audit account removal actions.
AC-2 - Medium - CCI-001405 - V-220478 - SV-220478r879528_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001405
Version
CISC-ND-000120
Vuln IDs
  • V-220478
  • V-101499
Rule IDs
  • SV-220478r879528_rule
  • SV-110603
Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized personnel. Auditing account removal actions will support account management procedures. When device management accounts are terminated, user or service accessibility may be affected. Auditing also ensures authorized active accounts remain enabled and available for use when required.
Checks: C-22193r539155_chk

Review the switch configuration to determine if it automatically audits account removal. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If account removal is not automatically audited, this is a finding.

Fix: F-22182r539156_fix

Configure the switch to log account removal using the following steps: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to enforce approved authorizations for controlling the flow of management information within the device based on control policies.
AC-4 - Medium - CCI-001368 - V-220479 - SV-220479r879533_rule
RMF Control
AC-4
Severity
Medium
CCI
CCI-001368
Version
CISC-ND-000140
Vuln IDs
  • V-220479
  • V-101501
Rule IDs
  • SV-220479r879533_rule
  • SV-110605
A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If management information flow is not enforced based on approved authorizations, the network device may become compromised. Information flow control regulates where management information is allowed to travel within a network device. The flow of all management information must be monitored and controlled so it does not introduce any unacceptable risk to the network device or data. Application-specific examples of enforcement occur in systems that employ rule sets or establish configuration settings that restrict information system services or message-filtering capability based on message content (e.g., implementing key word searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of management information within the system in accordance with applicable policy.
Checks: C-22194r648767_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement. Step 1: Verify that the line vty has an ACL inbound applied as shown in the example below: line vty access-class MGMT_NET in Step 2: Verify that the ACL permits only hosts from the management network to access the switch. ip access-list MGMT_NET 10 permit ip 10.1.48.0/24 any 20 deny ip any any log NX-OS v8 and later example Step 1: Verify that an ACL has been applied to the management interface inbound as shown in the example below: interface mgmt0 ip access-group MGMT_NET in Step 2: Verify that the ACL permits only hosts from the management network to access the switch. ip access-list MGMT_NET 10 permit ip 10.1.48.0/24 any 20 deny ip any any log If the Cisco switch is not configured to enforce approved authorizations for controlling the flow of management information within the device based on control policies, this is a finding.

Fix: F-22183r648768_fix

Configure the Cisco switch to restrict management access to specific IP addresses as shown in the example below: SW1(config)# ip access-list MGMT_NET SW1(config-acl)# permit ip 10.1.48.0/24 any SW1(config-acl)# deny ip any any log SW1(config-acl)# exit SW1(config)# line vty SW1(config-line)# access-class MGMT_NET in SW1(config-acl)# end NX-OS v8 and later example SW1(config)# ip access-list MGMT_NET SW1(config-acl)# permit ip 10.1.48.0/24 any SW1(config-acl)# deny ip any any log SW1(config-acl)# exit SW1(config)# interface mgmt0 SW1(config-if)# ip access-group MGMT_NET in SW1(config-acl)# end

b
The Cisco switch must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must disconnect the session.
AC-7 - Medium - CCI-000044 - V-220480 - SV-220480r879546_rule
RMF Control
AC-7
Severity
Medium
CCI
CCI-000044
Version
CISC-ND-000150
Vuln IDs
  • V-220480
  • V-101503
Rule IDs
  • SV-220480r879546_rule
  • SV-110607
By limiting the number of failed logon attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced.
Checks: C-22195r802430_chk

Review the Cisco switch configuration to verify that it enforces the limit of three consecutive invalid logon attempts as shown in the example below: ssh login-attempts 3 If the Cisco switch is not configured to enforce the limit of three consecutive invalid logon attempts, this is a finding. NOTE: The NX-OS switch does not lock out the account, it disconnects the session. The AAA server will lock out the user account on three failed attempts.

Fix: F-22184r802431_fix

Configure the Cisco switch to enforce the limit of three consecutive invalid logon attempts as shown in the example below: SW2(config)# ssh login-attempts 3

b
The Cisco switch must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.
AC-8 - Medium - CCI-000048 - V-220481 - SV-220481r879547_rule
RMF Control
AC-8
Severity
Medium
CCI
CCI-000048
Version
CISC-ND-000160
Vuln IDs
  • V-220481
  • V-101505
Rule IDs
  • SV-220481r879547_rule
  • SV-110609
Display of the DoD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notifications are required only for access via logon interfaces with human users.
Checks: C-22196r539164_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: banner motd # 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. # If the Cisco switch is not configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device, this is a finding.

Fix: F-22185r539165_fix

Configure the Cisco switch to display the Standard Mandatory DoD Notice and Consent Banner before granting access as shown in the following example: SW1(config)# banner motd # Enter TEXT message. End with the character '#'. > 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. > # SW1(config)# end

b
The Cisco switch must be configured to protect against an individual falsely denying having performed organization-defined actions to be covered by non-repudiation.
AU-10 - Medium - CCI-000166 - V-220482 - SV-220482r879554_rule
RMF Control
AU-10
Severity
Medium
CCI
CCI-000166
Version
CISC-ND-000210
Vuln IDs
  • V-220482
  • V-101507
Rule IDs
  • SV-220482r879554_rule
  • SV-110611
This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration management process. All configuration changes to the network device are logged, and administrators authenticate with two-factor authentication before gaining administrative access. Together, these processes will ensure the administrators can be held accountable for the configuration changes they implement. To meet this requirement, the network device must log administrator access and activity.
Checks: C-22197r539167_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in steps below: Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If logging of administrator activity is not configured, this is a finding.

Fix: F-22186r539168_fix

Configure the switch to log administrator activity as shown in the steps below: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must produce audit records containing information to establish where the events occurred.
AU-3 - Medium - CCI-000132 - V-220484 - SV-220484r940000_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000132
Version
CISC-ND-000290
Vuln IDs
  • V-220484
  • V-101513
Rule IDs
  • SV-220484r940000_rule
  • SV-110617
In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as device hardware components, device software modules, session identifiers, filenames, host names, and functionality. Associating information about where the event occurred within the network device provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured device.
Checks: C-22199r939999_chk

Step 1: Review the deny statements in all ACLs to determine if the log parameter has been configured as shown in the example below: ip access-list extended BLOCK_INBOUND deny icmp any any log Step 2: Verify that the Optimized Access-list Logging (OAL) has been configured. logging ip access-list cache entries nnnn Note: Once OAL has been enabled, the logged ACL hits can be viewed via the show log ip access-list cache command. If the switch is not configured with the log parameter after any deny statements to note where packets have been dropped via an ACL, this is a finding.

Fix: F-22188r621700_fix

Enable OAL as shown in the example below: SW1(config)# logging ip access-list cache entries nnnn Set the ‘log’ parameter after any ‘deny’ entries in the ACL as referenced in the check text above.

b
The Cisco switch must be configured to generate audit records containing the full-text recording of privileged commands.
AU-3 - Medium - CCI-000135 - V-220485 - SV-220485r879569_rule
RMF Control
AU-3
Severity
Medium
CCI
CCI-000135
Version
CISC-ND-000330
Vuln IDs
  • V-220485
  • V-101515
Rule IDs
  • SV-220485r879569_rule
  • SV-110619
Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. Organizations consider limiting the additional audit information to only that information explicitly needed for specific audit requirements. The additional information required is dependent on the type of information (i.e., sensitivity of the data and the environment within which it resides). At a minimum, the organization must audit full-text recording of privileged commands. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise.
Checks: C-22200r539176_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to generate audit records of configuration changes, this is a finding.

Fix: F-22189r539177_fix

Configure the Cisco switch to log all configuration changes as shown in the example below: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

c
The Cisco switch must be configured to prohibit the use of all unnecessary and nonsecure functions and services.
CM-7 - High - CCI-000382 - V-220486 - SV-220486r879588_rule
RMF Control
CM-7
Severity
High
CCI
CCI-000382
Version
CISC-ND-000470
Vuln IDs
  • V-220486
  • V-101517
Rule IDs
  • SV-220486r879588_rule
  • SV-110621
Network devices are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the network device must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved. Some network devices have capabilities enabled by default; if these capabilities are not necessary, they must be disabled. If a particular capability is used, then it must be documented and approved.
Checks: C-22201r539179_chk

Verify that the switch does not have any unnecessary or non-secure ports, protocols and services enabled. For example, the following features such as telnet should never be enabled, while other features should only be enabled if required for operations. feature telnet feature dhcp feature wccp feature nxapi feature imp If any unnecessary or non-secure ports, protocols, or services are enabled, this is a finding.

Fix: F-22190r539180_fix

Disable features that should not be enabled unless required for operations. SW2(config)# no feature telnet SW2(config)# no feature dhcp SW2(config)# no feature wccp SW2(config)# no feature nxapi SW2(config)# no feature imp Note: Telnet must always be disabled.

b
The Cisco switch must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.
AC-2 - Medium - CCI-001358 - V-220487 - SV-220487r879589_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-001358
Version
CISC-ND-000490
Vuln IDs
  • V-220487
  • V-101519
Rule IDs
  • SV-220487r879589_rule
  • SV-110623
Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. An alternative to using a sealed envelope in a safe would be credential files, separated by technology, located in a secured location on a file server, with the files only accessible to those administrators authorized to use the accounts of last resort, and access to that location monitored by a central log server. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.
Checks: C-22202r539182_chk

Step 1: Review the Cisco switch configuration to verify that a local account for last resort has been configured with a privilege level that will enable the administrator to troubleshoot connectivity to the authentication server. username xxxxxxxxxxxxx password 5 $5$88SPgpAn$Q6/17o5U/5lz4dNL1iQZuj/1a0wcKdrk29ZH1HJsnF. role priv-9 Step 2: Verify that the fallback to use local account has not been disabled as shown in the example below: no aaa authentication login default fallback error local Note: The fallback is enabled by default; hence the above command should not be seen in the configuration. If the Cisco switch is not configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable, this is a finding.

Fix: F-22191r539183_fix

Step 1: Configure a local account with the necessary privilege level to troubleshoot network outage and restore operations as shown in the following example: SW2(config)# switch(config)# username xxxxxxx password xxxxxx role priv-9 Step 2: Configure the authentication to use an AAA server with the fallback to use the local account if the authentication server is not reachable as shown in the following example: SW2(config)# aaa authentication login default group RADIUS_SERVERS SW2(config)# aaa authentication login default fallback error local SW2(config)# end

b
The Cisco switch must be configured to implement replay-resistant authentication mechanisms for network access to privileged accounts.
IA-2 - Medium - CCI-001941 - V-220488 - SV-220488r929031_rule
RMF Control
IA-2
Severity
Medium
CCI
CCI-001941
Version
CISC-ND-000530
Vuln IDs
  • V-220488
  • V-101521
Rule IDs
  • SV-220488r929031_rule
  • SV-110625
A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be vulnerable to a replay attack. An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.
Checks: C-22203r929029_chk

Verify that FIPS mode is enabled as shown in the example below: show fips status Note: Cisco NX-OS software supports only SSH version 2 (SSHv2). Beginning in Cisco NX-OS Release 5.1, SSH runs in FIPS mode. Source: Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x. If the switch is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions, this is a finding.

Fix: F-22192r929030_fix

Enable fips mode via the command "fips mode enable". Note: The switch will require a reboot for fips mode to be enabled.

b
The Cisco switch must be configured to enforce password complexity by requiring that at least one upper-case character be used.
IA-5 - Medium - CCI-000192 - V-220489 - SV-220489r879603_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000192
Version
CISC-ND-000570
Vuln IDs
  • V-220489
  • V-101523
Rule IDs
  • SV-220489r879603_rule
  • SV-110627
Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password is, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Checks: C-22204r539188_chk

Password complexity is enabled by default. Review the Cisco switch configuration to verify that it is compliant with this requirement. The following command should not be found in the configuration: no password strength-check If the Cisco switch is not configured to enforce password complexity by requiring that at least one upper-case character be used, this is a finding.

Fix: F-22193r539189_fix

Configure the Cisco switch to enforce password complexity by requiring that at least one upper-case character be used as shown in the example below: SW1(config)# password strength-check

b
The Cisco switch must be configured to enforce password complexity by requiring that at least one lower-case character be used.
IA-5 - Medium - CCI-000193 - V-220490 - SV-220490r879604_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000193
Version
CISC-ND-000580
Vuln IDs
  • V-220490
  • V-101525
Rule IDs
  • SV-220490r879604_rule
  • SV-110629
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Checks: C-22205r539191_chk

Password complexity is enabled by default. Review the Cisco switch configuration to verify that it is compliant with this requirement. The following command should not be found in the configuration: no password strength-check If the Cisco switch is not configured to enforce password complexity by requiring that at least one lower-case character be used, this is a finding.

Fix: F-22194r539192_fix

Configure the Cisco switch to enforce password complexity by requiring that at least one lower-case character be used as shown in the example below: SW1(config)# password strength-check

b
The Cisco switch must be configured to enforce password complexity by requiring that at least one numeric character be used.
IA-5 - Medium - CCI-000194 - V-220491 - SV-220491r879605_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000194
Version
CISC-ND-000590
Vuln IDs
  • V-220491
  • V-101527
Rule IDs
  • SV-220491r879605_rule
  • SV-110631
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Checks: C-22206r539194_chk

Password complexity is enabled by default. Review the Cisco switch configuration to verify that it is compliant with this requirement. The following command should not be found in the configuration: no password strength-check If the Cisco switch is not configured to enforce password complexity by requiring that at least one numeric character be used, this is a finding.

Fix: F-22195r539195_fix

Configure the Cisco switch to enforce password complexity by requiring that at least one numeric character be used as shown in the example below: SW1(config)# password strength-check

b
The Cisco switch must be configured to enforce password complexity by requiring that at least one special character be used.
IA-5 - Medium - CCI-001619 - V-220492 - SV-220492r879606_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-001619
Version
CISC-ND-000600
Vuln IDs
  • V-220492
  • V-101529
Rule IDs
  • SV-220492r879606_rule
  • SV-110633
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor of several that determine how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Multifactor authentication (MFA) is required for all administrative and user accounts on network devices, except for an account of last resort and (where applicable) a root account. Passwords should only be used when MFA using PKI is not available, and for the account of last resort and root account.
Checks: C-22207r539197_chk

Password complexity is enabled by default. Review the Cisco switch configuration to verify that it is compliant with this requirement. The following command should not be found in the configuration: no password strength-check If the Cisco switch is not configured to enforce password complexity by requiring that at least one special character be used, this is a finding.

Fix: F-22196r539198_fix

Configure the Cisco switch to enforce password complexity by requiring that at least one special character be used as shown in the example below: SW1(config)# password strength-check

c
The Cisco switch must be configured to terminate all network connections associated with device management after five minutes of inactivity.
SC-10 - High - CCI-001133 - V-220493 - SV-220493r916342_rule
RMF Control
SC-10
Severity
High
CCI
CCI-001133
Version
CISC-ND-000720
Vuln IDs
  • V-220493
  • V-101531
Rule IDs
  • SV-220493r916342_rule
  • SV-110635
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 element. Terminating network connections associated with communications sessions includes, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session.
Checks: C-22208r916296_chk

Review the Cisco switch configuration to verify that all network connections associated with a device management have an idle timeout value set to five minutes or less as shown in the following example: line console exec-timeout 5 line vty exec-timeout 5 If the Cisco switch is not configured to terminate all network connections associated with a device management after five minutes of inactivity, this is a finding.

Fix: F-22197r916297_fix

Set the idle timeout value to five minutes or less on all configured login classes as shown in the example below: SW1(config)# line console SW1(config-console)# exec-timeout 5 SW1(config-console)# exit SW1(config)# line vty SW1(config-line)# exec-timeout 5

b
The Cisco switch must be configured to automatically audit account enabling actions.
AC-2 - Medium - CCI-002130 - V-220494 - SV-220494r879696_rule
RMF Control
AC-2
Severity
Medium
CCI
CCI-002130
Version
CISC-ND-000880
Vuln IDs
  • V-220494
  • V-101533
Rule IDs
  • SV-220494r879696_rule
  • SV-110637
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the creation of application user accounts and notifies administrators and Information System Security Officers (ISSO). Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes.
Checks: C-22209r539203_chk

Review the switch configuration to determine if it automatically audits account enabling. The configuration should look similar to the example below: Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If account enabling is not automatically audited, this is a finding.

Fix: F-22198r539204_fix

Configure the switch to log account enabling using the following steps: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to audit the execution of privileged functions.
AC-6 - Medium - CCI-002234 - V-220495 - SV-220495r879720_rule
RMF Control
AC-6
Severity
Medium
CCI
CCI-002234
Version
CISC-ND-000940
Vuln IDs
  • V-220495
  • V-101535
Rule IDs
  • SV-220495r879720_rule
  • SV-110639
Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse and identify the risk from insider threats and the advanced persistent threat.
Checks: C-22210r539206_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement. The configuration example below will log all configuration changes. Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to log all configuration changes, this is a finding.

Fix: F-22199r539207_fix

Configure the Cisco switch to log all configuration changes as shown in the following example: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
AU-4 - Medium - CCI-001849 - V-220496 - SV-220496r879730_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001849
Version
CISC-ND-000980
Vuln IDs
  • V-220496
  • V-101537
Rule IDs
  • SV-220496r879730_rule
  • SV-110641
In order to ensure network devices have a sufficient storage capacity in which to write the audit logs, they need to be able to allocate audit record storage capacity. The task of allocating audit record storage capacity is usually performed during initial device setup if it is modifiable. The value for the organization-defined audit record storage requirement will depend on the amount of storage available on the network device, the anticipated volume of logs, the frequency of transfer from the network device to centralized log servers, and other factors.
Checks: C-22211r539209_chk

Verify that the Cisco switch is configured with a logfile size. The configuration should look like the example below: logging logfile LOGFILE1 6 size nnnnn If the Cisco switch is not configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements, this is a finding.

Fix: F-22200r539210_fix

Configure the buffer size for logging as shown in the example below: SW2(config)# logging logfile LOGFILE1 6 size nnnnn

b
The Cisco switch must be configured to generate an alert for all audit failure events.
AU-5 - Medium - CCI-001858 - V-220497 - SV-220497r879733_rule
RMF Control
AU-5
Severity
Medium
CCI
CCI-001858
Version
CISC-ND-001000
Vuln IDs
  • V-220497
  • V-101539
Rule IDs
  • SV-220497r879733_rule
  • SV-110643
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected. Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).
Checks: C-22212r539212_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: logging server 10.1.48.10 2 Note: The parameter 2 (critical) can replaced with a lesser severity level 3 through 6 (i.e. error, warning, notice, informational). Informational is the default severity level; hence, if the severity level is configured to informational, the parameter 7 will not be shown in the configuration. If the Cisco switch is not configured to generate an alert for all audit failure events, this is a finding.

Fix: F-22201r539213_fix

Configure the Cisco switch to send critical to emergency log messages to the syslog server as shown in the example below: SW4(config)# logging server 10.1.48.10 2 Note: The parameter 2 (critical) can replaced with a lesser severity level 3 through 6 (i.e. error, warning, notice, informational).

b
The Cisco switch must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.
AU-8 - Medium - CCI-001893 - V-220498 - SV-220498r879746_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001893
Version
CISC-ND-001030
Vuln IDs
  • V-220498
  • V-101541
Rule IDs
  • SV-220498r879746_rule
  • SV-110645
The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions. Multiple time sources provide redundancy by including a secondary source. Time synchronization is usually a hierarchy; clients synchronize time to a local source while that source synchronizes its time to a more accurate source. The network device must utilize an authoritative time server and/or be configured to use redundant authoritative time sources. This requirement is related to the comparison done in CCI-001891. DoD-approved solutions consist of a combination of a primary and secondary time source using a combination or multiple instances of the following: a time server designated for the appropriate DoD network (NIPRNet/SIPRNet); United States Naval Observatory (USNO) time servers; and/or the Global Positioning System (GPS). The secondary time source must be located in a different geographic region than the primary time source.
Checks: C-22213r539215_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the configuration example below: ntp distribute ntp server 10.1.12.10 ntp server 10.1.22.13 ntp commit If the Cisco switch is not configured to synchronize its clock with redundant authoritative time sources, this is a finding.

Fix: F-22202r539216_fix

Configure the Cisco switch to synchronize its clock with redundant authoritative time sources as shown in the example below: SW1(config)# feature ntp SW1(config)# ntp distribute SW1(config)# ntp server 10.1.12.10 SW1(config)# ntp server 10.1.22.13 SW1(config)# ntp commit SW1(config)# end

b
The Cisco switch must be configured to record time stamps for log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).
AU-8 - Medium - CCI-001890 - V-220499 - SV-220499r879747_rule
RMF Control
AU-8
Severity
Medium
CCI
CCI-001890
Version
CISC-ND-001050
Vuln IDs
  • V-220499
  • V-101543
Rule IDs
  • SV-220499r879747_rule
  • SV-110647
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.
Checks: C-22214r539218_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: clock timezone EST -5 0 Note: UTC is the default; hence, the command set time-zone may not be seen in the configuration. This can be verified using the show system uptime command. If the switch is not configured to record time stamps for log records that can be mapped to UTC or GMT, this is a finding.

Fix: F-22203r539219_fix

Configure the Cisco switch to record time stamps for audit records that can be mapped to UTC or GMT as shown in the example below: SW1(config)# clock timezone EST -5 0

b
The Cisco switch must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).
IA-3 - Medium - CCI-001967 - V-220500 - SV-220500r940003_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-001967
Version
CISC-ND-001130
Vuln IDs
  • V-220500
  • V-101545
Rule IDs
  • SV-220500r940003_rule
  • SV-110649
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, Internet). A remote connection is any connection with a device communicating through an external network (e.g., the Internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
Checks: C-22215r940001_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: snmp-server user NETOPS auth sha 5Er23@#as178 priv aes-128 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx snmp-server host 10.1.48.10 traps version 3 priv NETOPS Authentication used by the SNMP users can be viewed via the show snmp user command as shown in the example below: SW1# show snmp user ______________________________________________________________ SNMP USERS ______________________________________________________________ User Auth Priv(enforce) Groups acl_filter ____ ____ ___________ ______ __________ NETOPS sha aes-128 network-operator If the Cisco switch is not configured to authenticate SNMP messages using a FIPS-validated HMAC, this is a finding.

Fix: F-22204r940002_fix

Configure the Cisco switch to authenticate SNMP messages as shown in the example below: SW1(config)# snmp-server user NETOPS auth sha xxxxxxxxxxxxx priv aes-128 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SW1(config)# snmp-server host 10.1.48.10 traps version 3 priv NETOPS

b
The Cisco switch must be configured to encrypt SNMP messages using a FIPS 140-2 approved algorithm.
AC-17 - Medium - CCI-000068 - V-220501 - SV-220501r940006_rule
RMF Control
AC-17
Severity
Medium
CCI
CCI-000068
Version
CISC-ND-001140
Vuln IDs
  • V-220501
  • V-101547
Rule IDs
  • SV-220501r940006_rule
  • SV-110651
Without the strong encryption that is provided by the SNMP Version 3 User-based Security Model (USM), an unauthorized user can gain access to network management information that can be used to create a network outage.
Checks: C-22216r940004_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: snmp-server user NETOPS auth sha 5Er23@#as178 priv aes-128 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx snmp-server host 10.1.48.10 traps version 3 priv NETOPS Encryption used by the SNMP users can be viewed via the show snmp user command as shown in the example below: SW1# show snmp user ______________________________________________________________ SNMP USERS ______________________________________________________________ User Auth Priv(enforce) Groups acl_filter ____ ____ ___________ ______ __________ NETOPS sha aes-128 network-operator If the Cisco switch is not configured to encrypt SNMP messages using a FIPS 140-2 approved algorithm, this is a finding.

Fix: F-22205r940005_fix

Configure the Cisco switch to encrypt SNMP messages using a FIPS 140-2 approved algorithm as shown in the example below: SW1(config)# snmp-server user NETOPS auth sha xxxxxxxxxxxxx priv aes-128 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SW1(config)# snmp-server host 10.1.48.10 traps version 3 priv NETOPS

b
The Cisco switch must be configured to authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.
IA-3 - Medium - CCI-001967 - V-220502 - SV-220502r879768_rule
RMF Control
IA-3
Severity
Medium
CCI
CCI-001967
Version
CISC-ND-001150
Vuln IDs
  • V-220502
  • V-101549
Rule IDs
  • SV-220502r879768_rule
  • SV-110653
If Network Time Protocol is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to network devices, which will make log timestamps inaccurate and affect scheduled actions. NTP authentication is used to prevent this tampering by authenticating the time source.
Checks: C-22217r539227_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the configuration example below: ntp distribute ntp server 10.1.12.10 key 1 ntp server 10.1.22.13 key 1 ntp authenticate ntp authentication-key 1 md5 xxxxxxxxxx 7 ntp trusted-key 1 ntp commit If the Cisco switch is not configured to authenticate NTP sources using authentication that is cryptographically based, this is a finding.

Fix: F-22206r539228_fix

Configure the Cisco switch to authenticate NTP sources using authentication that is cryptographically based as shown in the example below: SW1(config)# ntp authenticate SW1(config)# ntp authentication-key 1 md5 xxxxxxxxxxxxx SW1(config)# ntp trusted-key 1 SW1(config)# ntp server 10.1.12.10 key 1 SW1(config)# ntp server 10.1.22.13 key 1 SW1(config)# ntp commit SW1(config)# end

c
The Cisco switch must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of remote maintenance sessions.
MA-4 - High - CCI-002890 - V-220503 - SV-220503r929034_rule
RMF Control
MA-4
Severity
High
CCI
CCI-002890
Version
CISC-ND-001200
Vuln IDs
  • V-220503
  • V-101551
Rule IDs
  • SV-220503r929034_rule
  • SV-110655
Unapproved mechanisms used for authentication to the cryptographic module are not verified; therefore, they cannot be relied upon to provide confidentiality or integrity, and DOD data may be compromised. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Currently, HMAC is the only FIPS-approved algorithm for generating and verifying message/data authentication codes in accordance with FIPS 198-1. Products that are FIPS 140-2 validated will have an HMAC that meets specification; however, the option must be configured for use as the only message authentication code used for authentication to cryptographic modules. Separate requirements for configuring applications and protocols used by each application (e.g., SNMPv3, SSHv2, NTP, HTTPS, and other protocols and applications that require server/client authentication) are required to implement this requirement. Where SSH is used, the SSHv2 protocol suite is required because it includes Layer 7 protocols such as SCP and SFTP, which can be used for secure file transfers.
Checks: C-22218r929032_chk

Verify that FIPS mode is enabled as shown in the example below: show fips status Note: Cisco NX-OS software supports only SSH version 2 (SSHv2). Beginning in Cisco NX-OS Release 5.1, SSH runs in FIPS mode. Source: Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x. If the switch is not configured to use FIPS-validated HMAC to protect the integrity of remote maintenance sessions, this is a finding.

Fix: F-22207r929033_fix

Enable FIPS mode via the command "fips mode enable". Note: The switch will require a reboot for FIPS mode to be enabled.

c
The Cisco switch must be configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions.
MA-4 - High - CCI-003123 - V-220504 - SV-220504r929037_rule
RMF Control
MA-4
Severity
High
CCI
CCI-003123
Version
CISC-ND-001210
Vuln IDs
  • V-220504
  • V-101553
Rule IDs
  • SV-220504r929037_rule
  • SV-110657
This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instead of HTTP. If unsecured protocols (lacking cryptographic mechanisms) are used for sessions, the contents of those sessions will be susceptible to eavesdropping, potentially putting sensitive data (including administrator passwords) at risk of compromise and potentially allowing hijacking of maintenance sessions.
Checks: C-22219r929035_chk

Verify that FIPS mode is enabled as shown in the example below: show fips status Note: Cisco NX-OS software supports only SSH version 2 (SSHv2). Beginning in Cisco NX-OS Release 5.1, SSH runs in FIPS mode. Source: Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x. If the switch is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions, this is a finding.

Fix: F-22208r929036_fix

Enable FIPS mode via the command "fips mode enable". Note: The switch will require a reboot for FIPS mode to be enabled.

b
The Cisco switch must be configured to generate log records when administrator privileges are modified.
AU-12 - Medium - CCI-000172 - V-220506 - SV-220506r879866_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
CISC-ND-001240
Vuln IDs
  • V-220506
  • V-101557
Rule IDs
  • SV-220506r879866_rule
  • SV-110661
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).
Checks: C-22221r539239_chk

Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to generate log records when administrator privileges are modified, this is a finding.

Fix: F-22210r539240_fix

Configure the Cisco switch to generate log records when account privileges are modified as shown in the example below: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to generate log records when administrator privileges are deleted.
AU-12 - Medium - CCI-000172 - V-220507 - SV-220507r879870_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
CISC-ND-001250
Vuln IDs
  • V-220507
  • V-101559
Rule IDs
  • SV-220507r879870_rule
  • SV-110663
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).
Checks: C-22222r539242_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to generate log records when administrator privileges are deleted, this is a finding.

Fix: F-22211r539243_fix

Configure the Cisco switch to generate log records when administrator privileges are deleted as shown in the example below: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must be configured to generate audit records when successful/unsuccessful logon attempts occur.
AU-12 - Medium - CCI-000172 - V-220508 - SV-220508r879874_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
CISC-ND-001260
Vuln IDs
  • V-220508
  • V-101561
Rule IDs
  • SV-220508r879874_rule
  • SV-110665
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).
Checks: C-22223r539245_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the examples below: logging logfile LOG_FILE 6 logging level authpri 6 If the Cisco switch is not configured to generate audit records when successful/unsuccessful logon attempts occur, this is a finding.

Fix: F-22212r539246_fix

Configure the Cisco switch to generate audit records when successful/unsuccessful logon attempts occur as shown in the example below: Step 1: Lower the authpriv level to 6. SW1(config)# logging level authpriv 6 Step 2: Configure a logfile to record log messages at level 6. SW1(config)# logging logfile LOG_FILE 6

b
The Cisco switch must be configured to generate log records for privileged activities.
AU-12 - Medium - CCI-000172 - V-220509 - SV-220509r879875_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
CISC-ND-001270
Vuln IDs
  • V-220509
  • V-101563
Rule IDs
  • SV-220509r879875_rule
  • SV-110667
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).
Checks: C-22224r539248_chk

Step 1: Verify that account records will be sent to an AAA server as shown in the example below: aaa accounting default group RADIUS_SERVERS Step 2: Verify that the referenced group name has defined AAA servers that are online. aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.12 Note: Cisco NX-OS devices report configuration activity to TACACS+ or RADIUS servers in the form of accounting records. Each accounting record contains accounting attribute-value (AV) pairs and is stored on the AAA server. If the Cisco switch is not configured to generate log records for privileged activities, this is a finding.

Fix: F-22213r539249_fix

Configure the Cisco switch to generate log records for privileged activities as shown in the example below: Step 1: Configure the AAA servers as shown in the example below: SW1(config)# radius-server host 10.1.48.10 SW1(config)# radius-server host 10.1.48.12 Step 2: Configure an AAA server group as shown in the example below: SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.12 SW1(config-radius)# exit Step 3: Enable AAA accounting as shown in the example below: SW1(config)# aaa accounting default group RADIUS_SERVERS SW1(config)# end

b
The Cisco switch must generate audit records showing starting and ending time for administrator access to the system.
AU-12 - Medium - CCI-000172 - V-220510 - SV-220510r879876_rule
RMF Control
AU-12
Severity
Medium
CCI
CCI-000172
Version
CISC-ND-001280
Vuln IDs
  • V-220510
  • V-101565
Rule IDs
  • SV-220510r879876_rule
  • SV-110669
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).
Checks: C-22225r539251_chk

Verify that the switch is configured to generate log records showing starting and ending time for administrator access as shown in the example below: logging level authpri 6 If the switch is not configured to generate log records showing starting and ending time for administrator access, this is a finding.

Fix: F-22214r539252_fix

Configure the switch to log session start and ending per admin session as shown in the example below: SW1(config)# logging level authpriv 6

b
The Cisco switch must be configured to off-load log records onto a different system than the system being audited.
AU-4 - Medium - CCI-001851 - V-220512 - SV-220512r879886_rule
RMF Control
AU-4
Severity
Medium
CCI
CCI-001851
Version
CISC-ND-001310
Vuln IDs
  • V-220512
  • V-101569
Rule IDs
  • SV-220512r879886_rule
  • SV-110673
Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity.
Checks: C-22227r539257_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement as shown in the example below: logging server 10.1.48.10 6 If the Cisco switch is not configured to off-load log records onto a different system than the system being audited, this is a finding.

Fix: F-22216r539258_fix

Configure the Cisco switch to send log records to a syslog server as shown in the example below: SW4(config)# logging server 10.1.48.10 6

c
The Cisco switch must be configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access.
CM-6 - High - CCI-000370 - V-220513 - SV-220513r916111_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000370
Version
CISC-ND-001370
Vuln IDs
  • V-220513
  • V-101571
Rule IDs
  • SV-220513r916111_rule
  • SV-110675
Centralized management of user accounts and authentication increases the administrative access to the switch. This control is particularly important protection against the insider threat. With robust centralized management, audit records for administrator account access to the organization's network devices can be more readily analyzed for trends and anomalies. The alternative method of defining administrator accounts on each device exposes the device configuration to remote access authentication attacks and system administrators with multiple authenticators for each network device.
Checks: C-22228r916091_chk

Review the Cisco switch configuration to verify that the device is configured to use at least two authentication servers as primary source for authentication. Step 1: Verify that an AAA server group is configured for login authentication for both in-band and console access methods. aaa authentication login default group RADIUS_SERVERS aaa authentication login console group RADIUS_SERVERS Step 2: Verify that at least two AAA servers have been defined for the server group as shown in the example below: radius-server host 10.1.48.10 key 7 "xxxxxx" radius-server host 10.1.48.11 key 7 "xxxxxx" authentication accounting aaa group server radius RADIUS_SERVERS server 10.1.48.10 server 10.1.48.11 If the Cisco switch is not configured to use at least two authentication servers for the purpose of authenticating users prior to granting administrative access, this is a finding.

Fix: F-22217r916092_fix

Configure the Cisco switch to use at least two authentication servers as shown in the following example: Step 1: Define the authentication servers. SW1(config)# radius-server host 10.1.48.10 key xxxxxx SW1(config)# radius-server host 10.1.48.11 key xxxxxx Step 2: Configure the AAA group. SW1(config)# aaa group server radius RADIUS_SERVERS SW1(config-radius)# server 10.1.48.10 SW1(config-radius)# server 10.1.48.11 Step 3: Use the AAA servers for login authentication for both in-band and console access methods. SW1(config)# aaa authentication login default group RADIUS_SERVERS SW1(config)# aaa authentication login console group RADIUS_SERVERS

b
The Cisco switch must be configured to support organizational requirements to conduct backups of the configuration when changes occur.
CM-6 - Medium - CCI-000366 - V-220514 - SV-220514r916221_rule
RMF Control
CM-6
Severity
Medium
CCI
CCI-000366
Version
CISC-ND-001410
Vuln IDs
  • V-220514
  • V-101573
Rule IDs
  • SV-220514r916221_rule
  • SV-110677
System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the execution and operation of the device. Information system backup is a critical step in ensuring system integrity and availability. If the system fails and there is no backup of the system-level information, a denial of service condition is possible for all who utilize this critical network component. This control requires the network device to support the organizational central backup process for system-level information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups.
Checks: C-22229r539263_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement. The example configuration below will send the configuration to a TFTP server when a configuration change occurs. event manager applet BACKUP_CONFIG event syslog pattern "SYSLOG_CONFIG_I" action 1 cli command "copy startup-config tftp://10.1.48.10/nx-config vrf default" action 2 syslog priority informational msg "Configuration backup was executed" If the Cisco switch is not configured to conduct backups of the configuration when changes occur, this is a finding.

Fix: F-22218r539264_fix

Configure the Cisco switch to send the configuration to an TFTP or FTP server when a configuration change occurs as shown in the example below: SW4(config)# event manager applet BACKUP_CONFIG SW4(config-applet)# event syslog pattern "SYSLOG_CONFIG_I" SW4(config-applet)# action 1 cli command "copy startup-config tftp://10.1.48.10/nx-config vrf default” SW4(config-applet)# action 2 syslog priority informational msg "Configuration backup was executed" SW4(config-applet)# end

b
The Cisco switch must be configured to obtain its public key certificates from an appropriate certificate policy through an approved service provider.
SC-17 - Medium - CCI-001159 - V-220515 - SV-220515r879887_rule
RMF Control
SC-17
Severity
Medium
CCI
CCI-001159
Version
CISC-ND-001440
Vuln IDs
  • V-220515
  • V-101575
Rule IDs
  • SV-220515r879887_rule
  • SV-110679
For user certificates, each organization obtains certificates from an approved, shared service provider, as required by OMB policy. For federal agencies operating a legacy public key infrastructure cross-certified with the Federal Bridge Certification Authority at medium assurance or higher, this Certification Authority will suffice.
Checks: C-22230r539266_chk

If PKI certificates are not implemented on the switch, this requirement is not applicable. Step 1: Review the switch configuration to determine if a CA trust point has been configured as shown in the example below: crypto ca trustpoint CA_X enrollment terminal Step 2: Verify the CA is a DoD or DoD-approved service provider by entering the following command: show crypto ca certificates The output will list the following information for each certificate: Trustpoint (will map to a configured trustpoint from step 1) Common Name (CN) of the issuer Organization (O) of the issuer Organization Unit (OU) of the issuer Note: Cisco NX-OS software supports only the manual cut-and-paste method for certificate enrollment If the switch is not configured to obtain its public key certificates from a DoD or DoD-approved service provider, this is a finding.

Fix: F-22219r539267_fix

Ensure that certificate requests are only sent to DoD or DoD-approved service providers.

c
The Cisco switch must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO).
AU-4 - High - CCI-001851 - V-220516 - SV-220516r916114_rule
RMF Control
AU-4
Severity
High
CCI
CCI-001851
Version
CISC-ND-001450
Vuln IDs
  • V-220516
  • V-101577
Rule IDs
  • SV-220516r916114_rule
  • SV-110681
The aggregation of log data kept on a syslog server can be used to detect attacks and trigger an alert to the appropriate security personnel. The stored log data can used to detect weaknesses in security that enable the network IA team to find and address these weaknesses before breaches can occur. Reviewing these logs, whether before or after a security breach, are important in showing whether someone is an internal employee or an outside threat.
Checks: C-22231r916094_chk

Verify that the switch is configured to send logs to at least two syslog servers. The configuration should look similar to the example below: logging server 10.1.48.10 6 logging server 10.1.48.11 6 If the switch is not configured to send log data to the syslog servers, this is a finding.

Fix: F-22220r916095_fix

Configure the switch to send log messages to the syslog servers as shown in the example below: SW4(config)# logging server 10.1.48.10 6 SW4(config)# logging server 10.1.48.11 6

c
The Cisco switch must be running an IOS release that is currently supported by Cisco Systems.
CM-6 - High - CCI-000366 - V-220517 - SV-220517r879887_rule
RMF Control
CM-6
Severity
High
CCI
CCI-000366
Version
CISC-ND-001470
Vuln IDs
  • V-220517
  • V-101579
Rule IDs
  • SV-220517r879887_rule
  • SV-110683
Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilities. Running a supported release also enables operations to maintain a stable and reliable network provided by improved quality of service and security features.
Checks: C-22232r539272_chk

Verify that the switch is in compliance with this requirement by having the switch administrator enter the following command: show version Verify that the release is still supported by Cisco. All releases supported by Cisco can be found on the following URL: www.cisco.com/c/en/us/support/ios-nx-os-software If the switch is not running a supported release, this is a finding.

Fix: F-22221r539273_fix

Upgrade the switch to a supported release.

b
The Cisco switch must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.
SC-5 - Medium - CCI-002385 - V-260464 - SV-260464r950985_rule
RMF Control
SC-5
Severity
Medium
CCI
CCI-002385
Version
CISC-ND-001220
Vuln IDs
  • V-260464
  • V-101555
Rule IDs
  • SV-260464r950985_rule
  • SV-110659
DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mitigate the impact of DoS attacks that have occurred or are ongoing on device availability. For each network device, known and potential DoS attacks must be identified and solutions for each type implemented. A variety of technologies exist to limit or, in some cases, eliminate the effects of DoS attacks (e.g., limiting processes or restricting the number of sessions the device opens at one time). Employing increased capacity and bandwidth, combined with service redundancy, may reduce the susceptibility to some DoS attacks. The security safeguards cannot be defined at the DOD level because they vary according to the capabilities of the individual network devices and the security controls applied on the adjacent networks (e.g., firewalls performing packet filtering to block DoS attacks).
Checks: C-22794r950982_chk

Review the Cisco switch configuration to verify that it is compliant with this requirement. Step 1: Verify traffic types have been classified based on importance levels. The following is an example configuration: class-map match-all CoPP_CRITICAL match access-group name CoPP_CRITICAL class-map match-any CoPP_IMPORTANT match access-group name CoPP_IMPORTANT match protocol arp class-map match-all CoPP_NORMAL match access-group name CoPP_NORMAL class-map match-any CoPP_UNDESIRABLE match access-group name CoPP_UNDESIRABLE class-map match-all CoPP_DEFAULT match access-group name CoPP_DEFAULT Step 2: Review the ACLs referenced by the class maps to determine if the traffic is being classified appropriately. The following is an example configuration: ip access-list extended CoPP_CRITICAL remark our control plane adjacencies are critical permit ospf host [OSPF neighbor A] any permit ospf host [OSPF neighbor B] any permit pim host [PIM neighbor A] any permit pim host [PIM neighbor B] any permit pim host [RP addr] any permit igmp any 224.0.0.0 15.255.255.255 permit tcp host [BGP neighbor] eq bgp host [local BGP addr] permit tcp host [BGP neighbor] host [local BGP addr] eq bgp deny ip any any ip access-list extended CoPP_IMPORTANT permit tcp host [TACACS server] eq tacacs any permit tcp [management subnet] 0.0.0.255 any eq 22 permit udp host [SNMP manager] any eq snmp permit udp host [NTP server] eq ntp any deny ip any any ip access-list extended CoPP_NORMAL remark we will want to rate limit ICMP traffic permit icmp any any echo permit icmp any any echo-reply permit icmp any any time-exceeded permit icmp any any unreachable deny ip any any ip access-list extended CoPP_UNDESIRABLE remark other management plane traffic that should not be received permit udp any any eq ntp permit udp any any eq snmp permit tcp any any eq 22 permit tcp any any eq 23 remark other control plane traffic not configured on switch permit eigrp any any permit udp any any eq rip deny ip any any ip access-list extended CoPP_DEFAULT permit ip any any Note: Explicitly defining undesirable traffic with ACL entries enables the network operator to collect statistics. Excessive ARP packets can potentially monopolize Route Processor resources, starving other important processes. Currently, ARP is the only Layer 2 protocol that can be specifically classified using the match protocol command. Step 3: Review the policy-map to determine if the traffic is being policed appropriately for each classification. The following is an example configuration: policy-map CONTROL_PLANE_POLICY class CoPP_CRITICAL police 512000 8000 conform-action transmit exceed-action transmit class CoPP_IMPORTANT police 256000 4000 conform-action transmit exceed-action drop class CoPP_NORMAL police 128000 2000 conform-action transmit exceed-action drop class CoPP_UNDESIRABLE police 8000 1000 conform-action drop exceed-action drop class CoPP_DEFAULT police 64000 1000 conform-action transmit exceed-action drop Step 4: Verify that the CoPP policy is enabled. The following is an example configuration: control-plane service-policy input CONTROL_PLANE_POLICY If the Cisco switch is not configured to protect against known types of DoS attacks by employing organization-defined security safeguards, this is a finding.

Fix: F-22313r950984_fix

Configure the Cisco switch to protect against known types of DoS attacks on the route processor. Implementing a CoPP policy as shown in the example below is a best practice method. Step 1: Configure ACLs' specific traffic types. SW1(config)# ip access-list CoPP_CRITICAL SW1(config-acl)# remark our control plane adjacencies are critical SW1(config-acl)# permit ospf host 10.1.12.1 any SW1(config-acl)# permit ospf host 10.1.22.1 any SW1(config-acl)# permit pim host 10.1.12.1 any SW1(config-acl)# permit pim host 10.1.22.1 any SW1(config-acl)# permit pim host 10.1.33.4 any SW1(config-acl)# permit igmp any 224.0.0.0 15.255.255.255 SW1(config-acl)# permit tcp host 10.2.33.3 eq bgp host 10.2.33.4 SW1(config-acl)# permit tcp host 10.2.33.3 host 10.2.33.4 eq bgp SW1(config-acl)# deny ip any any SW1(config-acl)# exit SW1(config)# ip access-list CoPP_IMPORTANT SW1(config-acl)# permit tcp host 10.1.33.5 eq tacacs any SW1(config-acl)# permit tcp 10.1.33.0 0.0.0.255 any eq 22 SW1(config-acl)# permit udp host 10.1.33.7 any eq snmp SW1(config-acl)# permit udp host 10.1.33.9 eq ntp any SW1(config-acl)# deny ip any any SW1(config-acl)# exit SW1(config)# ip access-list CoPP_NORMAL SW1(config-acl)# remark we will want to rate limit ICMP traffic SW1(config-acl)# permit icmp any any echo SW1(config-acl)# permit icmp any any echo-reply SW1(config-acl)# permit icmp any any time-exceeded SW1(config-acl)# permit icmp any any unreachable SW1(config-acl)# deny ip any any SW1(config-acl)# exit SW1(config)# ip access-list CoPP_UNDESIRABLE SW1(config-acl)# remark other management plane traffic that should not be received SW1(config-acl)# permit udp any any eq ntp SW1(config-acl)# permit udp any any eq snmp SW1(config-acl)# permit tcp any any eq 22 SW1(config-acl)# permit tcp any any eq 23 SW1(config-acl)# remark other control plane traffic not configured on switch SW1(config-acl)# permit eigrp any any SW1(config-acl)# permit udp any any eq rip SW1(config-acl)# deny ip any any SW1(config-acl)# exit SW1(config)# ip access-list CoPP_DEFAULT SW1(config-acl)# permit ip any any SW1(config-acl)# exit Step 2: Configure class maps referencing each of the ACLs. SW1(config)# class-map match-all CoPP_CRITICAL SW1(config-cmap)# match access-group name CoPP_CRITICAL SW1(config-cmap)# class-map match-any CoPP_IMPORTANT SW1(config-cmap)# match access-group name CoPP_IMPORTANT SW1(config-cmap)# match protocol arp SW1(config-cmap)# class-map match-all CoPP_NORMAL SW1(config-cmap)# match access-group name CoPP_NORMAL SW1(config-cmap)# class-map match-any CoPP_UNDESIRABLE SW1(config-cmap)# match access-group name CoPP_UNDESIRABLE SW1(config-cmap)# class-map match-all CoPP_DEFAULT SW1(config-cmap)# match access-group name CoPP_DEFAULT SW1(config-cmap)# exit Step 3: Configure a policy map referencing the configured class maps and apply appropriate bandwidth allowance and policing attributes. SW1(config)# policy-map CONTROL_PLANE_POLICY SW1(config-pmap)# class CoPP_CRITICAL SW1(config-pmap-c)# police 512000 8000 conform-action transmit exceed-action transmit SW1(config-pmap-c-police)# class CoPP_IMPORTANT SW1(config-pmap-c)# police 256000 4000 conform-action transmit exceed-action drop SW1(config-pmap-c-police)# class CoPP_NORMAL SW1(config-pmap-c)# police 128000 2000 conform-action transmit exceed-action drop SW1(config-pmap-c-police)# class CoPP_UNDESIRABLE SW1(config-pmap-c)# police 8000 1000 conform-action drop exceed-action drop SW1(config-pmap-c-police)# class CoPP_DEFAULT SW1(config-pmap-c)# police 64000 1000 conform-action transmit exceed-action drop SW1(config-pmap-c-police)# exit SW1(config-pmap-c)# exit SW1(config-pmap)# exit Step 4: Apply the policy map to the control plane. SW1(config)# control-plane SW1(config-cp)# service-policy input CONTROL_PLANE_POLICY SW1(config-cp)# end