acceptedCisco IOS XE Router NDM Security Technical Implementation GuideThis 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.DISASTIG.DOD.MILRelease: 5 Benchmark Date: 27 Oct 20223.4.0.342221.10.02I - Mission Critical Classified<ProfileDescription></ProfileDescription>I - Mission Critical Public<ProfileDescription></ProfileDescription>I - Mission Critical Sensitive<ProfileDescription></ProfileDescription>II - Mission Support Classified<ProfileDescription></ProfileDescription>II - Mission Support Public<ProfileDescription></ProfileDescription>II - Mission Support Sensitive<ProfileDescription></ProfileDescription>III - Administrative Classified<ProfileDescription></ProfileDescription>III - Administrative Public<ProfileDescription></ProfileDescription>III - Administrative Sensitive<ProfileDescription></ProfileDescription>SRG-APP-000001-NDM-000200<GroupDescription></GroupDescription>CISC-ND-000010The Cisco router must be configured to limit the number of concurrent management sessions to an organization-defined number.<VulnDiscussion>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 denial-of-service (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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105327V-96189CCI-000054Configure the router to limit the number of concurrent management sessions to an organization-defined number as shown in the example below.
R4(config)#ip http max-connections 2
R4(config)#line vty 0 1
R4(config-line)#transport input ssh
R4(config-line)#exit
R4(config)#line vty 2 4
R4(config-line)# transport input none
R4(config-line)#endNote: This requirement is not applicable to file transfer actions such as FTP, SCP, and SFTP.
Review the router configuration to determine if concurrent management sessions are limited as shown in the example below:
ip http secure-server
ip http max-connections 2
…
…
…
line vty 0 1
transport input ssh
line vty 2 4
transport input none
If the router is not configured to limit the number of concurrent management sessions, this is a finding.SRG-APP-000026-NDM-000208<GroupDescription></GroupDescription>CISC-ND-000090The Cisco router must be configured to automatically audit account creation.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105335V-96197CCI-000018Configure the router to log account creation using the following commands:
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the router configuration to determine if it automatically audits account creation. The configuration should look similar to the example below:
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If account creation is not automatically audited, this is a finding.SRG-APP-000027-NDM-000209<GroupDescription></GroupDescription>CISC-ND-000100The Cisco router must be configured to automatically audit account modification.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105337V-96199CCI-001403Configure the router to log account modification using the following commands:
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the router configuration to determine if it automatically audits account modification. The configuration should look similar to the example below:
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If account modification is not automatically audited, this is a finding.SRG-APP-000028-NDM-000210<GroupDescription></GroupDescription>CISC-ND-000110The Cisco router must be configured to automatically audit account disabling actions.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105339V-96201CCI-001404Configure the router to log account disabling using the following commands:
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the router configuration to determine if it automatically audits account disabling. The configuration should look similar to the example below:
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If account disabling is not automatically audited, this is a finding.SRG-APP-000029-NDM-000211<GroupDescription></GroupDescription>CISC-ND-000120The Cisco router must be configured to automatically audit account removal actions.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105341V-96203CCI-001405Configure the router to log account removal using the following commands:
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the router configuration to determine if it automatically audits account removal. The configuration should look similar to the example below:
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If account removal is not automatically audited, this is a finding.SRG-APP-000038-NDM-000213<GroupDescription></GroupDescription>CISC-ND-000140The Cisco router must be configured to enforce approved authorizations for controlling the flow of management information within the device based on control policies.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105343V-96205CCI-001368Configure the Cisco router to restrict management access to specific IP addresses via SSH as shown in the example below.
SW2(config)#ip access-list standard MANAGEMENT_NET
SW2(config-std-nacl)#permit x.x.x.0 0.0.0.255
SW2(config-std-nacl)#exit
SW2(config)#line vty 0 1
SW2(config-line)#transport input ssh
SW2(config-line)#access-class MANAGEMENT_NET in
SW2(config-line)#endReview the Cisco router 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 0 1
access-class MANAGEMENT_NET in
transport input ssh
Step 2: Verify that the ACL permits only hosts from the management network to access the router.
ip access-list extended MANAGEMENT_NET
permit ip x.x.x.0 0.0.0.255 any
deny ip any any log-input
If the Cisco router 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.SRG-APP-000065-NDM-000214<GroupDescription></GroupDescription>CISC-ND-000150The Cisco router must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105345V-96207CCI-000044Configure the Cisco router to enforce the limit of three consecutive invalid logon attempts as shown in the example below.
R2(config)#login block-for 900 attempts 3 within 120Review the Cisco router configuration to verify that it enforces the limit of three consecutive invalid logon attempts as shown in the example below.
login block-for 900 attempts 3 within 120
Note: The configuration example above will block any login attempt for 15 minutes after three consecutive invalid logon attempts within a two-minute period.
If the Cisco router is not configured to enforce the limit of three consecutive invalid logon attempts, this is a finding.SRG-APP-000068-NDM-000215<GroupDescription></GroupDescription>CISC-ND-000160The Cisco router must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105347V-96209CCI-000048Configure the Cisco router to display the Standard Mandatory DoD Notice and Consent Banner before granting access as shown in the following example:
R1(config)#banner login #
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. #
R1(config)#endReview the Cisco router configuration to verify that it is compliant with this requirement as shown in 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 Cisco router is not configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device, this is a finding.SRG-APP-000080-NDM-000220<GroupDescription></GroupDescription>CISC-ND-000210The Cisco device must be configured to audit all administrator activity.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105355V-96217CCI-000166CCI-002234CCI-000172Configure the router to log administrator activity as shown in the example below.
R1(config)#logging userinfo
R1(config)#archive
R1(config-archive)#log config
R1(config-archive-log-cfg)#logging enable
R1(config-archive-log-cfg)#endReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
hostname R1
!
logging userinfo
!
…
…
…
archive
log config
logging enable
!
Note: The logging userinfo global configuration command will generate a log when a user increases his or her privilege level.
If logging of administrator activity is not configured, this is a finding.SRG-APP-000096-NDM-000226<GroupDescription></GroupDescription>CISC-ND-000280The Cisco router must produce audit records containing information to establish when (date and time) the events occurred.<VulnDiscussion>It is essential for security personnel to know what is being done, what was attempted, where it was done, when it was done, and by whom it was done in order to compile an accurate risk assessment. Logging the date and time of each detected event provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured network device. In order to establish and correlate the series of events leading up to an outage or attack, it is imperative the date and time are recorded in all log records.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105361V-96223CCI-000131Configure the router to include the date and time on all log records as shown in the example below.
R1(config)#service timestamps log datetime localtimeVerify that the router is configured to include the date and time on all log records as shown in the configuration example below.
service timestamps log datetime localtime
If time stamps are not configured, this is a finding.SRG-APP-000097-NDM-000227<GroupDescription></GroupDescription>CISC-ND-000290The Cisco router must produce audit records containing information to establish where the events occurred.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105363V-96225CCI-000132Configure the log-input parameter after any deny statements to provide the location as to where packets have been dropped via an ACL.
R1(config)#ip access-list extended BLOCK_INBOUND
R1(config-ext-nacl)#deny icmp any any log-inputReview the deny statements in all ACLs to determine if the log-input parameter has been configured as shown in the example below.
ip access-list extended BLOCK_INBOUND
deny icmp any any log-input
If the router is not configured with the log-input parameter after any deny statements to note where packets have been dropped via an ACL, this is a finding.SRG-APP-000101-NDM-000231<GroupDescription></GroupDescription>CISC-ND-000330The Cisco router must be configured to generate audit records containing the full-text recording of privileged commands.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105365V-96227CCI-000135Configure the Cisco router to log all configuration changes as shown in the example below.
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the Cisco router configuration to verify that it is compliant with this requirement. The configuration example below will log all configuration changes.
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If the Cisco router is not configured to generate audit records of configuration changes, this is a finding.SRG-APP-000119-NDM-000236<GroupDescription></GroupDescription>CISC-ND-000380The Cisco router must be configured to protect audit information from unauthorized modification.<VulnDiscussion>Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit network device activity.
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit data, the network device must protect audit information from unauthorized modification.
This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include ensuring log files receive the proper file system permissions and limiting log data locations.
Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105369V-96231CCI-000163If persistent logging is enabled, configure the router to only allow administrators with privilege level "15" access to the file system as shown in the example below.
R4(config)#file privilege 15Review the Cisco router configuration to verify that it is compliant with this requirement.
Step 1: If persistent logging is enabled as shown in the example below, go to step 2. Otherwise, this requirement is not applicable.
logging persistent url disk0:/logfile size 134217728 filesize 16384
Step 2: Verify that the router is not configured with a privilege level other than "15" to allow access to the file system as shown in the example below.
file privilege 10
Note: The default privilege level required for access to the file system is "15"; hence, the command file privilege "15" will not be shown in the configuration.
If the router is configured with a privilege level other than "15" to allow access to the file system, this is a finding.SRG-APP-000120-NDM-000237<GroupDescription></GroupDescription>CISC-ND-000390The Cisco router must be configured to protect audit information from unauthorized deletion.<VulnDiscussion>Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.
If audit data were to become compromised, then forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.
To ensure the veracity of audit data, the network device must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods, which will depend upon system architecture and design. Some commonly employed methods include: ensuring log files receive the proper file system permissions utilizing file system protections, restricting access, and backing up log data to ensure log data is retained.
Network devices providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order to make access decisions regarding the deletion of audit data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105371V-96233CCI-000164If persistent logging is enabled, configure the router to only allow administrators with privilege level "15" access to the file system as shown in the example below.
R4(config)#file privilege 15Review the Cisco router configuration to verify that it is compliant with this requirement.
Step 1: If persistent logging is enabled as shown in the example below, go to step 2. Otherwise, this requirement is not applicable.
logging persistent url disk0:/logfile size 134217728 filesize 16384
Step 2: Verify that the router is not configured with a privilege level other than "15" to allow access to the file system as shown in the example below.
file privilege 10
Note: The default privilege level required for access to the file system is "15"; hence, the command file privilege "15" will not be shown in the configuration.
If the router is configured with a privilege level other than "15" to allow access to the file system, this is a finding.SRG-APP-000133-NDM-000244<GroupDescription></GroupDescription>CISC-ND-000460The Cisco router must be configured to limit privileges to change the software resident within software libraries.<VulnDiscussion>Changes to any software components of the network device can have significant effects on the overall security of the network. Therefore, only qualified and authorized individuals should be allowed administrative access to the network device for implementing any changes or upgrades. If the network device were to enable non-authorized users to make changes to software libraries, those changes could be implemented without undergoing testing, validation, and approval.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105375V-96237CCI-001499Configure the router to only allow administrators with privilege level "15" access to the file system as shown in the example below.
R4(config)#file privilege 15Verify that the router is not configured with a privilege level other than "15" to allow access to the file system as shown in the example below.
file privilege 10
Note: The default privilege level required for access to the file system is "15"; hence, the command file privilege "15" will not be shown in the configuration.
If the router is configured with a privilege level other than "15" to allow access to the file system, this is a finding.SRG-APP-000142-NDM-000245<GroupDescription></GroupDescription>CISC-ND-000470The Cisco router must be configured to prohibit the use of all unnecessary and nonsecure functions and services.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105377V-96239CCI-000382Disable the following services if enabled as shown in the example below.
R2(config)#no boot network
R2(config)#no ip boot server
R2(config)#no ip bootp server
R2(config)#no ip dns server
R2(config)#no ip identd
R2(config)#no ip finger
R2(config)#no ip http server
R2(config)#no ip rcmd rcp-enable
R2(config)#no ip rcmd rsh-enable
R2(config)#no service config
R2(config)#no service finger
R2(config)#no service tcp-small-servers
R2(config)#no service udp-small-servers
R2(config)#no service pad
R2(config)#endVerify that the 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:
boot network
ip boot server
ip bootp server
ip dns server
ip identd
ip finger
ip http server
ip rcmd rcp-enable
ip rcmd rsh-enable
service config
service finger
service tcp-small-servers
service udp-small-servers
If any unnecessary or non-secure ports, protocols, or services are enabled, this is a finding.SRG-APP-000148-NDM-000346<GroupDescription></GroupDescription>CISC-ND-000490The Cisco router 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.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105381V-96243CCI-001358CCI-002111Step 1: Configure a local account as shown in the example below.
R2(config)#username xxxxxxxxx privilege nn secret xxxxxxx
Step 2: Configure the authentication order to use the local account if the authentication server is not reachable as shown in the following example:
R2(config)#aaa authentication login default group tacacs+ localStep 1: Review the Cisco router configuration to verify that a local account for last resort has been configured.
username xxxxxxxxxxx privilege nn common-criteria-policy PASSWORD_POLICY password xxxxxxxxxx
Note: The configured Common Criteria policy must be used when creating or changing the local account password as shown in the example above.
Step 2: Verify that local is defined after radius or tacas+ in the authentication order as shown in the example below.
aaa authentication login default group tacacs+ local
If the Cisco router 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.SRG-APP-000164-NDM-000252<GroupDescription></GroupDescription>CISC-ND-000550The Cisco router must be configured to enforce a minimum 15-character password length.<VulnDiscussion>Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a password.
The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Use of more characters in a password helps to exponentially increase the time and/or resources required to compromise the password.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105391V-96253CCI-000205Configure the Cisco router to enforce a minimum 15-character password length as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#min-length 15
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
min-length 15
If the Cisco router is not configured to enforce a minimum 15-character password length, this is a finding.SRG-APP-000166-NDM-000254<GroupDescription></GroupDescription>CISC-ND-000570The Cisco router must be configured to enforce password complexity by requiring that at least one upper-case character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105393V-96255CCI-000192Configure the Cisco router to enforce password complexity by requiring that at least one upper-case character be used as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#upper-case 1
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
upper-case 1
If the Cisco router is not configured to enforce password complexity by requiring that at least one upper-case character be used, this is a finding.SRG-APP-000167-NDM-000255<GroupDescription></GroupDescription>CISC-ND-000580The Cisco router must be configured to enforce password complexity by requiring that at least one lower-case character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105395V-96257CCI-000193Configure the Cisco router to enforce password complexity by requiring that at least one lower-case character be used as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#lower-case 1
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
lower-case 1
If the Cisco router is not configured to enforce password complexity by requiring that at least one lower-case character be used, this is a finding.SRG-APP-000168-NDM-000256<GroupDescription></GroupDescription>CISC-ND-000590The Cisco router must be configured to enforce password complexity by requiring that at least one numeric character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105397V-96259CCI-000194Configure the Cisco router to enforce password complexity by requiring that at least one numeric character be used as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#numeric-count 1
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
numeric-count 1
If the Cisco router is not configured to enforce password complexity by requiring that at least one numeric character be used, this is a finding.SRG-APP-000169-NDM-000257<GroupDescription></GroupDescription>CISC-ND-000600The Cisco router must be configured to enforce password complexity by requiring that at least one special character be used.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105399V-96261CCI-001619Configure the Cisco router to enforce password complexity by requiring that at least one special character be used as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#special-case 1
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
special-case 1
If the Cisco router is not configured to enforce password complexity by requiring that at least one special character be used, this is a finding.SRG-APP-000170-NDM-000329<GroupDescription></GroupDescription>CISC-ND-000610The Cisco router must be configured to require that when a password is changed, the characters are changed in at least eight of the positions within the password.<VulnDiscussion>If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks.
The number of changed characters refers to the number of changes required with respect to the total number of positions in the current password. In other words, characters may be the same within the two passwords; however, the positions of the like characters must be different.
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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105401V-96263CCI-000195Configure the Cisco router to enforce password complexity by requiring that when a password is changed, the characters are changed in at least eight of the positions within the password as shown in the example below.
R1(config)#aaa common-criteria policy PASSWORD_POLICY
R1(config-cc-policy)#char-changes 8
R1(config-cc-policy)#exitReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
aaa new-model
!
!
aaa common-criteria policy PASSWORD_POLICY
char-changes 8
If the Cisco router is not configured to require that when a password is changed, the characters are changed in at least eight of the positions within the password, this is a finding.SRG-APP-000171-NDM-000258<GroupDescription></GroupDescription>CISC-ND-000620The Cisco router must only store cryptographic representations of passwords.<VulnDiscussion>Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
Network devices must enforce cryptographic representations of passwords when storing passwords in databases, configuration files, and log files. Passwords must be protected at all times; using a strong one-way hashing encryption algorithm with a salt is the standard method for providing a means to validate a password without having to store the actual password.
Performance and time required to access are factors that must be considered, and the one way hash is the most feasible means of securing the password and providing an acceptable measure of password security. If passwords are stored in clear text, they can be plainly read and easily compromised.
In many instances, verifying the user knows a password is performed using a password verifier. In its simplest form, a password verifier is a computational function that is capable of creating a hash of a password and determining if the value provided by the user matches the stored hash.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105403V-96265CCI-000196Configure the router to encrypt all passwords.
R4(config)#service password-encryption
R4(config)#endReview the router configuration to determine if passwords are encrypted as shown in the example below.
service password-encryption
If the router is not configured to encrypt passwords, this is a finding.SRG-APP-000190-NDM-000267<GroupDescription></GroupDescription>CISC-ND-000720The Cisco router must be configured to terminate all network connections associated with device management after 10 minutes of inactivity.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105409V-96271CCI-001133Set the idle timeout value to 10 minutes or less on all configured login classes as shown in the example below.
R1(config)#line vty 0 1
R1(config-line)#exec-timeout 10 0
R1(config-line)#exit
R1(config)#line con 0
R1(config-line)#exec-timeout 10 0
R1(config-line)#exit
R2(config)#ip http timeout-policy idle 600 life nnnn requests nnReview the Cisco router configuration to verify that all network connections associated with a device management have an idle timeout value set to 10 minutes or less as shown in the following example:
ip http secure-server
ip http timeout-policy idle 600 life nnnn requests nn
…
…
…
line con 0
exec-timeout 10 0
line vty 0 1
exec-timeout 10 0
If the Cisco router is not configured to terminate all network connections associated with a device management after 10 minutes of inactivity, this is a finding.SRG-APP-000319-NDM-000283<GroupDescription></GroupDescription>CISC-ND-000880The Cisco router must be configured to automatically audit account enabling actions.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105423V-96285CCI-002130Configure the router to log account enabling using the following commands:
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the router configuration to determine if it automatically audits account enabling. The configuration should look similar to the example below:
archive
log config
logging enable
Note: Configuration changes can be viewed using the show archive log config all command.
If account enabling is not automatically audited, this is a finding.SRG-APP-000357-NDM-000293<GroupDescription></GroupDescription>CISC-ND-000980The Cisco router must be configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105435V-96297CCI-001849Configure the buffer size for logging as shown in the example below.
R2(config)#logging buffered xxxxxxxx informationalVerify that the Cisco router is configured with a logging buffer size. The configuration should look like the example below:
logging buffered xxxxxxxx informational
If a logging buffer size is not configured, this is a finding.
If the Cisco router is not configured to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements, this is a finding.SRG-APP-000360-NDM-000295<GroupDescription></GroupDescription>CISC-ND-001000The Cisco router must be configured to generate an alert for all audit failure events.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020V-96301SV-105439CCI-001858Configure the Cisco router to send critical to emergency log messages to the syslog server as shown in the example below.
R4(config)#logging trap critical
Note: The parameter "critical" can replaced with a lesser severity level (i.e., error, warning, notice, informational).Review the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
logging trap critical
Note: The parameter "critical" can replaced with a lesser severity level (i.e. error, warning, notice, informational). 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 Cisco router is not configured to generate an alert for all audit failure events, this is a finding.SRG-APP-000373-NDM-000298<GroupDescription></GroupDescription>CISC-ND-001030The Cisco router must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105441V-96303CCI-001889CCI-001890CCI-001893Configure the Cisco router to synchronize its clock with redundant authoritative time sources as shown in the example below.
R2(config)#ntp server x.x.x.x
R2(config)#ntp server y.y.y.yReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the configuration example below.
ntp server x.x.x.x
ntp server y.y.y.y
If the Cisco router is not configured to synchronize its clock with redundant authoritative time sources, this is a finding.SRG-APP-000395-NDM-000310<GroupDescription></GroupDescription>CISC-ND-001130The Cisco router must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105455V-96317CCI-001967Configure the Cisco router to authenticate SNMP messages as shown in the example below.
R4(config)#snmp-server group V3GROUP v3 auth read V3READ write V3WRITE
R4(config)#snmp-server user V3USER V3GROUP v3 auth sha xxxxxxx
R4(config)#snmp-server view V3READ iso included
R4(config)#snmp-server view V3WRITE iso included
R4(config)#snmp-server host x.x.x.x version 3 auth V3USERReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
snmp-server group V3GROUP v3 auth read V3READ write V3WRITE
snmp-server view V3READ iso included
snmp-server view V3WRITE iso included
snmp-server host x.x.x.x version 3 auth V3USER
Authentication used by the SNMP users can be viewed via the show snmp user command as shown in the example below.
R4#show snmp user
User name: V3USER
Engine ID: 800000090300C2042B540000
storage-type: nonvolatile active
Authentication Protocol: SHA
Privacy Protocol: None
Group-name: V3GROUP
If the Cisco router is not configured to authenticate SNMP messages using a FIPS-validated HMAC, this is a finding.SRG-APP-000395-NDM-000310<GroupDescription></GroupDescription>CISC-ND-001140The Cisco router must be configured to encrypt SNMP messages using a FIPS 140-2 approved algorithm.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105457V-96319CCI-000068Configure the Cisco router to encrypt SNMP messages using a FIPS 140-2 approved algorithm as shown in the example below.
R4(config)#snmp-server group V3GROUP v3 priv read V3READ write V3WRITE
R4(config)#snmp-server user V3USER V3GROUP v3 auth sha xxxxxx priv aes 256 xxxxxxReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
snmp-server group V3GROUP v3 priv read V3READ write V3WRITE
snmp-server view V3READ iso included
snmp-server view V3WRITE iso included
snmp-server host x.x.x.x version 3 auth V3USER
Encryption used by the SNMP users can be viewed via the show snmp user command as shown in the example below.
R4#show snmp user
User name: V3USER
Engine ID: 800000090300C2042B540000
storage-type: nonvolatile active
Authentication Protocol: SHA
Privacy Protocol: AES256
Group-name: V3GROUP
If the Cisco router is not configured to encrypt SNMP messages using a FIPS 140-2 approved algorithm, this is a finding.SRG-APP-000395-NDM-000347<GroupDescription></GroupDescription>CISC-ND-001150The Cisco router must be configured to authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105459V-96321CCI-001967Configure the Cisco router to authenticate NTP sources using authentication that is cryptographically based as shown in the example below.
R2(config)#ntp authenticate
R2(config)#ntp authentication-key 1 md5 xxxxxx
R2(config)#ntp trusted-key 1
R2(config)#ntp server x.x.x.x key 1
R2(config)#ntp server y.y.y.y key 1Review the Cisco router configuration to verify that it is compliant with this requirement as shown in the configuration example below.
ntp authentication-key 1 md5 121B0A151012 7
ntp authenticate
ntp trusted-key 1
ntp server x.x.x.x key 1
ntp server y.y.y.y key 1
If the Cisco router is not configured to authenticate NTP sources using authentication that is cryptographically based, this is a finding.SRG-APP-000411-NDM-000330<GroupDescription></GroupDescription>CISC-ND-001200The Cisco router must be configured to use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of remote maintenance sessions.<VulnDiscussion>Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105465V-96327CCI-002890CCI-001941Configure SSH to use FIPS-validated HMAC for remote maintenance sessions as shown in the following example:
SSH Example
R1(config)#ip ssh version 2
R1(config)#ip ssh server algorithm mac hmac-sha2-256
Review the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
NOTE: Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a compromised hashing standard and is being phased out of use by industry and Government standards. Unless required for legacy use, DoD systems should not be configured to use SHA-1 for integrity of remote access sessions.
SSH Example
ip ssh version 2
ip ssh server algorithm mac hmac-sha2-256
If the Cisco router is not configured to use FIPS-validated HMAC to protect the integrity of remote maintenance sessions, this is a finding.SRG-APP-000412-NDM-000331<GroupDescription></GroupDescription>CISC-ND-001210The Cisco router must be configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105467V-96329CCI-003123Configure the Cisco router to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm as shown in the examples below.
SSH Example
R1(config)#ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr
Review the Cisco router configuration to verify that it is compliant with this requirement.
SSH Example
ip ssh version 2
ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr
If the router is not configured to implement cryptographic mechanisms to protect the confidentiality of remote maintenance sessions using a FIPS 140-2 approved algorithm, this is a finding.SRG-APP-000435-NDM-000315<GroupDescription></GroupDescription>CISC-ND-001220The Cisco router must be configured to protect against known types of denial-of-service (DoS) attacks by employing organization-defined security safeguards.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105469V-96331CCI-002385Configure the Cisco router 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.
R1(config)#ip access-list extended CoPP_CRITICAL
R1(config-ext-nacl)#remark our control plane adjacencies are critical
R1(config-ext-nacl)#permit ospf host x.x.x.x any
R1(config-ext-nacl)#permit ospf host x.x.x.x any
R1(config-ext-nacl)#permit pim host x.x.x.x any
R1(config-ext-nacl)#permit pim host x.x.x.x any
R1(config-ext-nacl)#permit igmp any 224.0.0.0 15.255.255.255
R1(config-ext-nacl)#permit tcp host x.x.x.x eq bgp host x.x.x.x
R1(config-ext-nacl)#deny ip any any
R1(config-ext-nacl)#exit
R1(config)#ip access-list extended CoPP_IMPORTANT
R1(config-ext-nacl)#permit tcp host x.x.x.x eq tacacs any
R1(config-ext-nacl)#permit tcp x.x.x.x 0.0.0.255 any eq 22
R1(config-ext-nacl)#permit udp host x.x.x.x any eq snmp
R1(config-ext-nacl)#permit udp host x.x.x.x eq ntp any
R1(config-ext-nacl)#deny ip any any
R1(config-ext-nacl)#exit
R1(config)#ip access-list extended CoPP_NORMAL
R1(config-ext-nacl)#remark we will want to rate limit ICMP traffic
R1(config-ext-nacl)#permit icmp any any echo
R1(config-ext-nacl)#permit icmp any any echo-reply
R1(config-ext-nacl)#permit icmp any any time-exceeded
R1(config-ext-nacl)#permit icmp any any unreachable
R1(config-ext-nacl)#deny ip any any
R1(config-ext-nacl)#exit
R1(config)#ip access-list extended CoPP_UNDESIRABLE
R1(config-ext-nacl)#remark management plane traffic that should not be received
R1(config-ext-nacl)#permit udp any any eq ntp
R1(config-ext-nacl)#permit udp any any eq snmp
R1(config-ext-nacl)#permit tcp any any eq 22
R1(config-ext-nacl)#permit tcp any any eq 23
R1(config-ext-nacl)#remark control plane traffic not configured on router
R1(config-ext-nacl)#permit eigrp any any
R1(config-ext-nacl)#permit udp any any eq rip
R1(config-ext-nacl)#deny ip any any
R1(config-ext-nacl)#exit
R1(config)#ip access-list extended CoPP_DEFAULT
R1(config-ext-nacl)#permit ip any any
R1(config-ext-nacl)#exit
Step 2: Configure class maps referencing each of the ACLs.
R1(config)#class-map match-all CoPP_CRITICAL
R1(config-cmap)#match access-group name CoPP_CRITICAL
R1(config-cmap)#class-map match-any CoPP_IMPORTANT
R1(config-cmap)#match access-group name CoPP_IMPORTANT
R1(config-cmap)#match protocol arp
R1(config-cmap)#class-map match-all CoPP_NORMAL
R1(config-cmap)#match access-group name CoPP_NORMAL
R1(config-cmap)#class-map match-any CoPP_UNDESIRABLE
R1(config-cmap)#match access-group name CoPP_UNDESIRABLE
R1(config-cmap)#class-map match-all CoPP_DEFAULT
R1(config-cmap)#match access-group name CoPP_DEFAULT
R1(config-cmap)#exit
Step 3: Configure a policy map referencing the configured class maps and apply appropriate bandwidth allowance and policing attributes.
R1(config)#policy-map CONTROL_PLANE_POLICY
R1(config-pmap)#class CoPP_CRITICAL
R1(config-pmap-c)#police 512000 8000 conform-action transmit exceed-action transmit
R1(config-pmap-c-police)#class CoPP_IMPORTANT
R1(config-pmap-c)#police 256000 4000 conform-action transmit exceed-action drop
R1(config-pmap-c-police)#class CoPP_NORMAL
R1(config-pmap-c)#police 128000 2000 conform-action transmit exceed-action drop
R1(config-pmap-c-police)#class CoPP_UNDESIRABLE
R1(config-pmap-c)#police 8000 1000 conform-action drop exceed-action drop
R1(config-pmap-c-police)#class CoPP_DEFAULT
R1(config-pmap-c)#police 64000 1000 conform-action transmit exceed-action drop
R1(config-pmap-c-police)#exit
R1(config-pmap-c)#exit
R1(config-pmap)#exit
Step 4: Apply the policy map to the control plane.
R1(config)#control-plane
R1(config-cp)#service-policy input CONTROL_PLANE_POLICY
R1(config-cp)#endReview the Cisco router configuration to verify that it is compliant with this requirement.
NOTE: Starting with IOS XE version 17, the default control plane policing policy has settings to meet this requirement, and this check is Not Applicable.
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 router
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
Note: Control Plane Protection (CPPr) can be used to filter as well as police control plane traffic destined to the RP. CPPr is very similar to CoPP and has the ability to filter and police traffic using finer granularity by dividing the aggregate control plane into three separate categories: (1) host, (2) transit, and (3) CEF-exception. Hence, a separate policy-map could be configured for each traffic category.
If the Cisco router is not configured to protect against known types of DoS attacks by employing organization-defined security safeguards, this is a finding.SRG-APP-000499-NDM-000319<GroupDescription></GroupDescription>CISC-ND-001250The Cisco router must be configured to generate log records when administrator privileges are deleted.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105473V-96335CCI-000172Configure the Cisco router to generate log records when administrator privileges are deleted as shown in the example below.
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example below.
archive
log config
logging enable
If the Cisco router is not configured to generate log records when administrator privileges are deleted, this is a finding.SRG-APP-000503-NDM-000320<GroupDescription></GroupDescription>CISC-ND-001260The Cisco router must be configured to generate audit records when successful/unsuccessful logon attempts occur.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105475V-96337CCI-000172Configure the Cisco router to generate audit records when successful/unsuccessful logon attempts occur as shown in the example below.
R5(config)#login on-failure log
R5(config)#login on-success logReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the examples below.
login on-failure log
login on-success log
If the Cisco router is not configured to generate audit records when successful/unsuccessful logon attempts occur, this is a finding.SRG-APP-000504-NDM-000321<GroupDescription></GroupDescription>CISC-ND-001270The Cisco router must be configured to generate log records for privileged activities.<VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105477V-96339CCI-000172Configure the Cisco router to generate log records for privileged activities as shown in the example below.
R4(config)#archive
R4(config-archive)#log config
R4(config-archive-log-cfg)#logging enable
R4(config-archive-log-cfg)#endReview the Cisco router configuration to verify that it is compliant with this requirement as shown in the example configurations below.
archive
log config
logging enable
If the Cisco router is not configured to generate log records for privileged activities, this is a finding.SRG-APP-000516-NDM-000336<GroupDescription></GroupDescription>CISC-ND-001370The Cisco router must be configured to use an authentication server for the purpose of authenticating users prior to granting administrative access.<VulnDiscussion>Centralized management of user accounts and authentication increases the administrative access to the router. 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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105489V-96351CCI-000366CCI-000370Step 1: Configure the Cisco router to use an authentication server as shown in the following example:
R4(config)#radius host 10.1.48.2 key xxxxxx
Step 2: Configure the authentication order to use the authentication server as primary source for authentication as shown in the following example:
R4(config)#aaa authentication login LOGIN_AUTHENTICATION group radius local
Step 3: Configure all network connections associated with a device management to use an authentication server for the purpose of login authentication.
R4(config)#line vty 0 1
R4(config-line)#login authentication LOGIN_AUTHENTICATION
R4(config-line)#exit
R4(config)#line con 0
R4(config-line)#login authentication LOGIN_AUTHENTICATION
R4(config-line)#exit
R4(config)#ip http authentication aaa login-authentication LOGIN_AUTHENTICATIONReview the Cisco router configuration to verify that the device is configured to use an authentication server as primary source for authentication as shown in the following example:
aaa new-model
!
aaa authentication login LOGIN_AUTHENTICATION group radius local
…
…
…
ip http authentication aaa login-authentication LOGIN_AUTHENTICATION
ip http secure-server
…
…
…
radius-server host x.x.x.x auth-port 1645 acct-port 1646 key xxxxxxx
…
…
…
line con 0
exec-timeout 10 0
login authentication LOGIN_AUTHENTICATION
line vty 0 1
exec-timeout 10 0
login authentication LOGIN_AUTHENTICATION
If the Cisco router is not configured to use an authentication server for the purpose of authenticating users prior to granting administrative access, this is a finding.SRG-APP-000516-NDM-000340<GroupDescription></GroupDescription>CISC-ND-001410The Cisco router must be configured to back up the configuration when changes occur.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105497V-96359CCI-000366CCI-000537Configure the Cisco router to send the configuration to a TFTP or FTP server when a configuration change occurs as shown in the example below.
R4(config)#event manager applet BACKUP_CONFIG
R4(config-applet)#event syslog pattern "%SYS-5-CONFIG_I"
R4(config-applet)#action 1 cli command "enable"
R4(config-applet)#action 2 info type routername
R4(config-applet)#action 3 cli command "copy run tftp" pattern "remote host"
R4(config-applet)#action 4 cli command "x.x.x.x" pattern "filename"
R4(config-applet)#action 5 cli command "$_info_routername-config"
R4(config-applet)#action 6 syslog priority informational msg "Configuration backup was executed"
R4(config-applet)#endReview the Cisco router 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 "%SYS-5-CONFIG_I"
action 1 info type routername
action 2 cli command "enable"
action 3 cli command "copy run tftp" pattern "remote host"
action 4 cli command "x.x.x.x" pattern "filename"
action 5 cli command "$_info_routername-config"
action 6 syslog priority informational msg "Configuration backup was executed"
If the Cisco router is not configured to conduct backups of the configuration when changes occur, this is a finding.SRG-APP-000516-NDM-000344<GroupDescription></GroupDescription>CISC-ND-001440The Cisco router must be configured to obtain its public key certificates from an appropriate certificate policy through an approved service provider.<VulnDiscussion>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 (CA) at medium assurance or higher, this CA will suffice.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105501V-96363CCI-000366CCI-001159Configure the router to obtain its public key certificates from an appropriate certificate policy through an approved service provider as shown in the example below.
R2(config)# crypto pki trustpoint CA_X
R2(ca-trustpoint)#enrollment url http://trustpoint1.example.com
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. The CA trust point configuration would look similar to the example below.
crypto pki trustpoint CA_X
enrollment url http://trustpoint1.example.com
Note: 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.
Note: This requirement is not applicable if the router does not have any public key certificates.
If the Cisco router is not configured to obtain its public key certificates from an appropriate certificate policy through an approved service provider, this is a finding.SRG-APP-000516-NDM-000350<GroupDescription></GroupDescription>CISC-ND-001450The Cisco router must be configured to send log data to a syslog server for the purpose of forwarding alerts to the administrators and the ISSO.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105503V-96365CCI-001851Configure the router to send log messages to the syslog server as shown in the example below.
R4(config)#logging host x.x.x.x
Verify that the router is configured to send logs to a syslog server. The configuration should look similar to the example below:
logging x.x.x.x
If the router is not configured to send log data to the syslog server, this is a finding.SRG-APP-000516-NDM-000351<GroupDescription></GroupDescription>CISC-ND-001470The Cisco router must be running an IOS release that is currently supported by Cisco Systems.<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>DPMS Target Cisco IOS XE Router NDMDISADPMS TargetCisco IOS XE Router NDM4020SV-105507V-96369CCI-000366Upgrade the router to a supported release.Verify that the router is in compliance with this requirement by having the router 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 router is not running a supported release, this is a finding.