Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Review the Cisco IOS XE router configuration to see if the device limits the number of concurrent SSH sessions to an organization-defined number. The following commands should be in the configuration: line vty 0 1 exec-timeout 60 0 session-limit 2 login authentication TEST transport input ssh transport output ssh line vty 2 4 exec-timeout 60 0 session-limit 2 login authentication TEST transport input none transport output none If the number of concurrent sessions are not limited, this is a finding.
Configure the Cisco IOS XE router to limit the number of concurrent SSH sessions to an organization-defined number. The configuration will look similar to the example below: line vty 0 1 exec-timeout 60 0 session-limit 2 login authentication TEST transport input ssh transport output ssh line vty 2 4 exec-timeout 60 0 session-limit 2 login authentication TEST transport input none transport output none
Review the Cisco IOS XE router configuration to determine if there is an authentication server defined. The configuration should look similar to the example below: aaa new-model aaa authentication login default group radius local radius server RADIUS address ipv4 1.1.1.1 key <pre-shared key> If there is no authentication server defined, this is a finding.
Configure the Cisco IOS XE router to use an authentication server. The configuration should look similar to the example below: aaa new-model aaa authentication login default group radius local radius server RADIUS address ipv4 1.1.1.1 key <pre-shared key>
Review the Cisco IOS XE router configuration to determine if it automatically audits account creation. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account creation is not automatically audited, this is a finding.
Configure the Cisco IOS XE router to automatically audit the creation of accounts. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is configured to audit account modification. The configuration should like similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account modification is not audited, this is a finding.
Enter the following commands to audit account modification: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits account removal. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account removal is not automatically audited, this is a finding.
Configure the Cisco IOS XE router to automatically audit the removal of accounts. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router has ACLs configured and apply to the appropriate interfaces to control the flow of traffic. The configuration should look similar to the example below: interface GigabitEthernet 0/0/1 description MGMT link ip address x.x.x.x 255.255.255.0 ip access-group Authorized_Sources_ACL in ... Extended IP access list Authorized_Source_ACL 10 permit 22 host 2.2.2.2 host 3.3.3.3 log 20 deny ip any any log If ACLs are not configured, this is a finding.
Configure the Cisco IOS XE router with ACLs, applied to the appropriate interfaces to control the flow of management information. The configuration should look similar to the example below: interface GigabitEthernet 0/0/1 description MGMT link ip address x.x.x.x 255.255.255.0 ip access-group Authorized_Sources_ACL in ... Extended IP access list Authorized_Source_ACL 10 permit 22 host 2.2.2.2 host 3.3.3.3 log 20 deny ip any any log
Review the Cisco router configuration to verify that it enforces the limit of three consecutive invalid logon attempts within a fifteen-minute period as shown in the example below. login block-for 600 attempts 3 within 900 Note: The configuration example above will block any logon attempt for 10 minutes after three consecutive invalid logon attempts. If the Cisco router is not configured to enforce the limit of three consecutive invalid logon attempts within a fifteen-minute period, this is a finding.
Configure the Cisco router to enforce the limit of three consecutive invalid logon attempts within a fifteen-minute period as shown in the example below. login block-for 600 attempts 3 within 900
Verify that the Cisco IOS XE router has a logon banner configured. The configuration should look similar to the example below: banner login ^C 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. ^C If the logon banner is not configured, this is a finding.
Add the banner logon command and the text of the banner to the Cisco IOS XE router configuration. The configuration will look similar to the example below: banner login ^C 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. ^C
Verify that the Cisco IOS XE router has a logon banner configured. The configuration should look similar to the example below: banner login ^C 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. ^C If the login banner is not configured, this is a finding.
Add the banner logon command and the text of the banner to the Cisco IOS XE router configuration. The configuration will look similar to the example below: banner login ^C 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. ^C
Review the Cisco IOS XE router configuration to determine if logging is enabled to prevent repudiation. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not enabled, this is a finding.
Configure the Cisco IOS XE router to enable logging. The configuration should like similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is generating audit records. The configuration should look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If audit records are not being generated, this is a finding.
Enter the following commands to enable auditing: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is configured to only allow individuals in the proper role to select audited events. The configuration should look similar to the example below: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging If this is not configured, this is a finding.
Configure the Cisco IOS XE router using the following commands: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging
Verify that the Cisco IOS XE router is configured to generate audit records when successful/unsuccessful attempts to access privileges. The configuration should look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If audit records are not being generated, this is a finding.
Configure the Cisco IOS XE router to enable auditing. The configuration should look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured, this is a finding.
Enter the following commands to enable auditing. The configuration will look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured to produce audit log records containing sufficient information to establish what type of event occurred, this is a finding.
Enter the following commands to enable auditing. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: service timestamps log datetime If time stamps is not configured, this is a finding.
Enter the following commands to enable time stamps for auditing: service timestamps log datetime
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured to produce audit records containing information to establish where the events occurred, this is a finding.
Enter the following commands to enable auditing. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured to produce log records containing information to establish the source of events, this is a finding.
Enter the following commands to enable auditing. The configuration will look similar to the example below: archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured to log the outcome of events, this is a finding.
Enter the following commands to enable auditing. The configuration will look similar to the example below: logging userinfo login on-failure log login on-success log archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that logging of user information is configured on the Cisco IOS XE router. The configuration will look similar to the example below: logging userinfo If logging of user information is not configured, this is a finding.
Enter the following commands to enable logging of user information: logging userinfo
Verify that logging is properly configured on the Cisco IOS XE router. The configuration will look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If logging is not configured to log the full-text recording of privileged commands, this is a finding.
Enter the following commands to enable auditing: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is configured to use internal system clocks to generate time stamps for audit records. The configuration should look similar to the example below: service timestamps log datetime If internal systems clocks are not being used, this is a finding.
Configure the Cisco IOS XE router to use internal clocks to generate time stamps for audit records. The configuration should look similar to the example below: service timestamps log datetime
Verify that the Cisco IOS XE router is configured to use syslog. The configuration should look similar to the example below: logging host 1.1.1.1 If syslog is not configured, this is a finding.
Configure the Cisco IOS XE router to use syslog. The configuration should look similar to the example below: logging host 1.1.1.1
Verify that the Cisco IOS XE router does not have any unnecessary or non-secure ports, protocols and services enabled. For example, the following commands should not be in the configuration: ip bootp server ip dns server ip finger ip http server ip identd ip rcmd rcp-enable ip rcmd rsh-enable service config service finger service tcp-small-servers service udp-small-servers service pad transport input telnet transport output telnet If any unnecessary or non-secure ports, protocols or services are enabled, this is a finding.
Disable all unnecessary or non-secure ports, protocols, and services. If any of the following commands are in the configuration, remove them. ip bootp server ip dns server ip identd ip finger ip http-server ip rcmd rcp-enable ip rcmd rsh-enable service config service fingerDisable all unnecessary or non-secure ports, protocols and services. no ip bootp server no ip dns server no ip finger no ip http server no ip identd no ip rcmd rcp-enable no ip rcmd rsh-enable no service config no service udp-small-servers no service tcp-small-servers no service finger no service pad line vty 0 4 no transport input no transport output transport input ssh transport output ssh Note: transport input and output for telnet service can’t be disabled individually; hence, ssh must be reinserted for access to the line vty configuration. service tcp-small-servers service udp-small-servers service pad
Verify that there is one local account configured on the Cisco IOS XE router. The configuration should look similar to the example below: username <username> privilege 15 password <password string> If there is not a local account configured, this is a finding. If there is more than one local account configured, this is a finding.
If there is more than one local account, delete the additional account by using the NO form of the username command. If there is no local account, create one using the following username command: <username> privilege 15 password <password>
Verify that the Cisco IOS XE router enforces a minimum password length of "15" characters. The configuration should look similar to the example below: aaa common-criteria policy <Policy Name> min-length 15 If a minimum password length of "15" characters is not enforced, this is a finding.
Use the following commands to configure minimum password length: aaa common-criteria policy <Policy Name> min-length 15
Verify that the Cisco IOS XE router is configured to use complex passwords. The configuration should look similar to the example below: aaa common-criteria policy PASSWORD_POLICY min-length 15 upper-case 1 If the use of complex passwords is not configured, this is a finding.
Use the following commands to configure password complexity: aaa common-criteria policy PASSWORD_POLICY min-length 15 upper-case 1
Verify that the Cisco IOS XE router is configured to use complex passwords. The configuration should look similar to the example below: aaa common-criteria policy PASSWORD_POLICY min-length 15 upper-case 1 lower-case 1 If the use of complex passwords is not configured, this is a finding.
Use the following commands to configure password complexity: aaa common-criteria policy PASSWORD_POLICY min-length 15 upper-case 1 lower-case 1
Verify that the Cisco IOS XE router is configured to use complex passwords. The configuration should look similar to the example below: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1 If the use of complex passwords is not configured, this is a finding.
Use the following commands to configure password complexity: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1
Verify that the Cisco IOS XE router is configured to use complex passwords. The configuration should look similar to the example below: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1 special-case 1 If the use of complex passwords is not configured, this is a finding.
Use the following commands to configure password complexity: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1 special-case 1
Verify that the Cisco IOS XE router is configured to use complex passwords. The configuration should look similar to the example below: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1 special-case 1 char-changes 8 If the use of complex passwords is not configured, this is a finding.
Use the following commands to configure password complexity: aaa common-criteria policy PASSWORD_POLICY min-length 15 numeric-count 1 upper-case 1 lower-case 1 special-case 1 char-changes 8
Verify that Cisco IOS XE router has password encryption enabled. The configuration should look similar to the example below: password encryption aes service password-encryption If password encryption is not enabled, this is a finding.
Add the following command to encrypt local passwords: service password-encryption
Verify that the Cisco IOS XE router is configured to enforce a 60-day maximum password life. The configuration should look like the example below: aaa common-criteria policy <Policy Name> lifetime month 2 If a 60-day maximum password life is not configured, this is a finding.
Use the following commands to configure a 60-day maximum password life: aaa common-criteria policy <Policy Name> lifetime month 2
Verify that the Cisco IOS XE router is configured to support session time outs and idle time outs on all management interfaces. The configuration should look similar to the example below: line con 0 exec-timeout 10 0 line vty 0 5 exec-timeout 10 0 If it is not configured to support session idle time outs on all management interfaces, this is a finding.
Configure session time outs and idle time outs on all management interfaces using the following commands: line con 0 exec-timeout 10 0 line vty 0 5 exec-timeout 10 0
Verify that the Cisco IOS XE router is configured to reveal error messages only to authorized individuals. The configuration should look similar to the example below: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging If it is not configured to reveal error messages only to authorized individuals, this is a finding.
Use CLI views to control who can view error messages. The configuration should look similar to the example below: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging
Verify that the Cisco IOS XE router is configured to automatically terminate sessions. The configuration should look similar to the example below: line vty 0 5 exec-timeout 10 0 If sessions do not automatically terminate, this is a finding.
Configure session time outs and idle time outs on all management interfaces using the following commands: line vty 0 5 exec-timeout 10 0
Verify that the Cisco IOS XE router automatically audits account enabling actions. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account enabling actions are not audited, this is a finding.
Enter the following commands to enable auditing: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router automatically audits execution of privileged functions. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If privileged functions are not audited, this is a finding.
Enter the following commands to enable auditing: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is configured to only allow individuals in the proper role to select audited events. The configuration should look similar to the example below: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging If this is not configured to only allow individuals in the proper role to select audited events, this is a finding.
Configure the Cisco IOS XE router using the following commands: parser view Senior-Admin secret 5 $1$hW3m$PE.3zCJYeSrvYflFey71R. commands exec include all configure commands exec include all show parser view Auditor secret 5 $1$qb3F$SrdJW2oyyDzq1L94I7eED. commands exec include show logging
Verify that the Cisco IOS XE router is configured with a logging buffer size. The configuration should look like the example below: logging buffered 4096 If a logging buffer size is not configured, this is a finding.
Add the following command to configure a buffer size (The range is 4096 to 2147483647 in bytes). logging buffered 4096
Verify that at least two NTP servers are configured and that system clocks update the time every 24 hours. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1 If there are not at least two NTP servers configured, and clocks are updated at least every 24 hours, this is a finding.
Configure the router to use NTP. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1
Verify that at least two NTP servers are configured and that system clocks update the time every 24 hours. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1 If there are not at least two NTP servers configured, and clocks are updated at least every 24 hours, this is a finding.
Configure the router to use NTP. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1
Verify that at least two NTP servers are configured and that system clocks update the time every 24 hours. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1 ntp server 2.2.2.2 key 1 If there are not at least two NTP servers configured, and clocks are updated at least every 24 hours, this is a finding.
Configure the router to use NTP. The configuration should look similar to the example below: ntp authentication-key 1 md5 072C285F4D06 7 ntp authenticate ntp trusted-key 1 ntp server 1.1.1.1 key 1 ntp server 2.2.2.2 key 1
Verify that the Cisco IOS XE router time stamps for audit logs can be mapped to UTC or GMT by using the show logging command. The configuration should look similar to the following example: clock timezone MST -7 0 service timestamps datetime localtime If the time stamps cannot be map to UTC or GMT, this is a finding.
Configure the timezone for the local time, then map the time stamps back to UCT or GMT. The configuration should look similar to the example below: clock timezone MST -7 0 service timestamps datetime localtime
Verify that the time stamps for audit records have a granularity of one second. The configuration should look similar to the example below: service timestamps debug datetime msec service timestamps log datetime year If the time stamps have a granularity larger than one second, this is a finding.
Configure the Cisco IOS XE router to have a granularity of one second for audit log time stamps. The configuration should look like the example below: service timestamps debug datetime msec service timestamps log datetime year
Verify that the Cisco IOS XE router is configured to secure connections. The configuration should look similar to the example below: ip ssh version 2 ip ssh dh min size 2048 ntp authentication-key 1 md5 075B706F471A1A0A464058 7 ntp authenticate ntp trusted-key 1 ntp peer 192.168.2.1 key 1 snmp-server user new-user new-group v3 auth sha password priv aes 128 Cisco If the Cisco IOS XE router is not configured to secure all management connections, this is a finding.
Configure the Cisco IOS XE router so that connections are secure. The configuration should look similar to the example below: ip ssh version 2 ip ssh dh min size 2048 ntp authentication-key 1 md5 075B706F471A1A0A464058 7 ntp authenticate ntp trusted-key 1 ntp peer 192.168.2.1 key 1 snmp-server user new-user new-group v3 auth sha password priv aes 128 Cisco
Verify that the Cisco IOS XE router is using SSHv2 for remote access. The configuration should look like the example below: ip ssh version 2 ! line vty 0 98 transport input ssh If secure applications are not being used, this is a finding.
Configure the Cisco IOS XE router to use SSHv2 for remote access. The configuration should look like the example below: ip ssh version 2 ! line vty 0 98 transport input ssh
Verify that the Cisco IOS XE router is using SSHv2 for remote access. The configuration should look like the example below: ip ssh version 2 ! line vty 0 98 transport input ssh If secure applications are not being used, this is a finding.
Configure the Cisco IOS XE router to use SSHv2 for remote access. The configuration should look like the example below: ip ssh version 2 ! line vty 0 98 transport input ssh
Determine whether control plane protection has been implemented on the Cisco IOS XE router by verifying traffic types have been classified based on importance levels and a policy has been configured to filter and rate limit the traffic according to each class. The configuration should look similar to the following example: class-map match-any CoPP_UNDESIRABLE match access-group name CoPP_UNDESIRABLE class-map match-any CoPP_IMPORTANT match access-group name CoPP_IMPORTANT match protocol arp class-map match-all CoPP_DEFAULT match access-group name CoPP_DEFAULT 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 If control plane protection has not been implemented, this is a finding. If control plane protection has been implemented but is not configured to verify traffic types have been classified based on importance levels and a policy has been configured to filter and rate limit the traffic according to each class, this is a finding.
Implement control plane protection by classifying traffic types based on importance and configure filters to restrict and rate limit the traffic directed to and processed by the route processor according to each class. The configuration would look similar to the one below: class-map match-any CoPP_UNDESIRABLE match access-group name CoPP_UNDESIRABLE class-map match-any CoPP_IMPORTANT match access-group name CoPP_IMPORTANT match protocol arp class-map match-all CoPP_DEFAULT match access-group name CoPP_DEFAULT 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
Verify that the Cisco IOS XE router is configured with different privilege levels for different users. The configuration should look like the example below: username USER1 privilege 7 password 7 08751D6D000A061843595F username USER2 privilege 15 password 7 06525E02455D0A16544541 If different privilege levels are not defined, this is a finding.
Configure the Cisco IOS XE router with different privilege levels for different users. The configuration should look similar to the example below: username USER1 privilege 7 password 7 08751D6D000A061843595F username USER2 privilege 15 password 7 06525E02455D0A16544541
Review the Cisco IOS XE router configuration to determine if it automatically audits account modification. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account modification is not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits account modification. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account modification is not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits account logon. The configuration should look similar to the example below: logging userinfo ! login on-failure log login on-success log ! archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account logon is not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo ! login on-failure log login on-success log ! archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits privileged activities. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If privileged activities are not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits start and end times for administrator access. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If administrator access is not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits concurrent logons from different workstations. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If concurrent logons from different workstations are not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Review the Cisco IOS XE router configuration to determine if it automatically audits account creations, modifications, etc. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys If account creations, modification, etc. are not automatically audited, this is a finding.
Configure the Cisco IOS XE router for auditing. The configuration should look similar to the example below: logging userinfo archive log config logging enable logging size 1000 notify syslog contenttype plaintext hidekeys
Verify that the Cisco IOS XE router is configured to send logs to a syslog server. The configuration should look similar to the example below: logging host 1.1.1.1 If it is not configured to send logs to a syslog server, this is a finding.
Configure the Cisco IOS XE router to enable syslog. The configuration should look similar to the example below: logging host 1.1.1.1
Review the router configuration to determine if it is in compliance with this requirement. The configuration should look similar to the example below. logging buffered nnnn informational logging console informational logging trap warning logging host x.x.x.x Note: Severity levels can be set to operational requirements. Informational is the default severity level; hence, if the severity level is configured to informational, the “logging trap” command will not be shown in the configuration. If the router is not configured to generate audit log events for a locally developed list of auditable events, this is a finding.
Configure the router to send logs to the console, buffer, and syslog server as shown in the example below. logging buffered nnnn informational logging console informational logging trap warning logging host x.x.x.x Note: Severity levels can be set to operational requirements.
Verify that administrative accounts are configured on the authentication server. The configuration should look similar to the example below: aaa authentication login default radius radius server RADIUS1 address ipv4 1.1.1.1 key <pre-shared key> If administrative accounts are not configured on the authentication server, this is a finding.
Configure the Cisco IOS XE router to use multiple authentication servers. The configuration should look similar to the example below: aaa authentication login default radius radius server RADIUS1 address ipv4 1.1.1.1 key <pre-shared key>
Verify that the Cisco IOS XE router has the event manager configured to do automated backups. The configuration should look similar to the example below: event manager applet backup-config event timer watchdog time 86400 action 1.0 cli command "enable" action 2.0 info type routername action 3.0 cli command "copy runn tftp://x.x.x.x/$_info_routername.cfg" pattern "Address" action 4.0 cli command "" pattern "Destination" action 5.0 cli command "" If the event manager is not configured for automated backups, this is a finding.
Configure the event manager for automated backups. The configuration should look similar to the example below: event manager applet backup-config event timer watchdog time 86400 action 1.0 cli command "enable" action 2.0 info type routername action 3.0 cli command "copy runn tftp://x.x.x.x/$_info_routername.cfg" pattern "Address" action 4.0 cli command "" pattern "Destination" action 5.0 cli command ""
Review the router configuration to determine if a CA trust point has been configured. The CA trust point will contain the URL of the CA in which the router has enrolled with. Verify this is a DoD or DoD-approved CA. This will ensure the router has enrolled and received a certificate from a trusted CA. A remote end-point's certificate will always be validated by the router by verifying the signature of the CA on the certificate using the CA's public key, which is contained in the router's certificate it received at enrollment. The CA trust point configuration would look similar to the following example: crypto pki trustpoint APPROVED_CA enrollment url http://xxx.example.com If the router is not configured to obtain its public key certificates from an approved service provider, this is a finding.
Configure the router configuration to use CA trust point that is a DoD or DoD-approved CA. The CA trust point configuration would look similar to the following example: crypto pki trustpoint APPROVED_CA enrollment url http://xxx.example.com
Verify that the Cisco IOS XE router is configured to send logs to a syslog server. The configuration should look similar to the example below: Logging trap information logging host x.x.x.x If the router is not configured to send log data to the syslog server, this is a finding.
Add the following commands to the router configuration to send log data to the syslog server: logging trap information logging host x.x.x.x
Verify that the Cisco IOS XE router is configured to send traps to the SNMP manager. The SNMP configuration should contain commands similar to the example below: snmp-server enable traps snmp-server host x.x.x.x version 3 auth xxxxxxxxx snmp-server user TRAP_NMS1 TRAP_GROUP v3 encrypted auth sha AAAAPPPP priv aes 128 EEEEPPPP Note: In the example above, the following values are used hypothetically: Username for SNMP Manager: TRAP_NMS1 Group for SNMP Manager: TRAP_GROUP User password for HMAC authentication: AAAAPPPP User password for encryption: EEEEPPPP AES key length: 128 If the router is not configured to send traps to the SNMP manager, this is a finding.
Configure the Cisco IOS XE router to send traps to the SNMP manager. The SNMP configuration should contain commands similar to the example below: snmp-server enable traps snmp-server host x.x.x.x version 3 auth xxxxxxxxx snmp-server user TRAP_NMS1 TRAP_GROUP v3 encrypted auth sha AAAAPPPP priv aes 128 EEEEPPPP Note: In the example above, the following values are used hypothetically: Username for SNMP Manager: TRAP_NMS1 Group for SNMP Manager: TRAP_GROUP User password for HMAC authentication: AAAAPPPP User password for encryption: EEEEPPPP AES key length: 128