| V-242608 | | The Cisco ISE must change the password for the local CLI and web-based account when members who have access to the password leave the role and are no longer authorized access. | If shared/group account credentials are not terminated when individuals leave the group, the user that left the group can still gain access even thoug... |
| V-242609 | | For the local web-based account of last resort, the Cisco ISE must automatically audit account creation. | Upon gaining access to a network device, an attacker will often first attempt to create a persistent method of reestablishing access. One way to accom... |
| V-242610 | | For the local web-based account of last resort and the default local CLI account, the Cisco ISE must automatically audit account modification. | Since the accounts in the network device are privileged or system-level accounts, account management is vital to the security of the network device. A... |
| V-242611 | | For the local web-based account of last resort, the Cisco ISE must automatically audit account disabling actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized pers... |
| V-242612 | | For the local account of last resort, the Cisco ISE must automatically audit account removal actions. | Account management, as a whole, ensures access to the network device is being controlled in a secure manner by granting access to only authorized pers... |
| V-242614 | | The Cisco ISE must be configured with only one local web-based account to be used as the account of last resort in the event the authentication server is unavailable. | Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local da... |
| V-242616 | | The Cisco ISE must audit the execution of privileged functions. | Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromise... |
| V-242617 | | The Cisco ISE 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. | By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, ... |
| V-242618 | | For the local account of last resort, the Cisco ISE must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the device. | Display of the DoD-approved use notification before granting access to the network device ensures privacy and security notification verbiage used is c... |
| V-242619 | | The Cisco ISE must protect against an individual (or process acting on behalf of an individual) falsely denying having performed organization-defined actions to be covered by non-repudiation. | This requirement supports non-repudiation of actions taken by an administrator and is required in order to maintain the integrity of the configuration... |
| V-242620 | | The Cisco ISE must generate audit records when successful attempts to access privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242621 | | The Cisco ISE must generate audit records when successful attempts to modify administrator privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242622 | | The Cisco ISE must generate audit records when successful attempts to delete administrator privileges occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242623 | | The Cisco ISE must generate audit records when successful logon attempts occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242624 | | The Cisco ISE must generate audit records for privileged activities or other system-level access. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242625 | | The Cisco ISE must generate audit records when concurrent logons from different workstations occur. | Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlat... |
| V-242626 | | The Cisco ISE must limit audit record storage capacity for all locally stored logs. | 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 ... |
| V-242627 | | The Cisco ISE must configure a remote syslog where audit records are stored on a centralized logging target that is different from the system being audited. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Storing audit logs to a different system than th... |
| V-242628 | | The Cisco ISE must send an alarm to one or more individuals when the monitoring collector process has an error or failure. | 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 an alert, securi... |
| V-242629 | | The Cisco ISE must be configured to synchronize internal information system clocks using redundant authoritative time sources. | The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly in... |
| V-242630 | | The Cisco ISE must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-242632 | | The Cisco ISE must enforce access restrictions associated with changes to the firmware, OS, and hardware components. | Changes to the hardware or software components of the network device can have significant effects on the overall security of the network. Therefore, o... |
| V-242633 | | The Cisco ISE must be configured to use an external authentication server to authenticate administrators prior to granting administrative access. | Centralized management of authentication settings increases the security of remote and nonlocal access methods. This control is particularly important... |
| V-242634 | | The Cisco ISE must be running an operating system release that is currently supported by the vendor. | Network devices running an unsupported operating system lack current security fixes required to mitigate the risks associated with recent vulnerabilit... |
| V-242636 | | The Cisco ISE must generate log records for a locally developed list of auditable events. | Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to iden... |
| V-242639 | | The Cisco ISE must use DoD-approved PKI rather than proprietary or self-signed device certificates. | To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs.
The Cisco I... |
| V-242642 | | For accounts using password authentication, the Cisco ISE must implement replay-resistant authentication mechanisms for network access to privileged accounts. | A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the applicati... |
| V-242643 | | The Cisco ISE must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC). | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authenticati... |
| V-242644 | | The Cisco ISE must authenticate Network Time Protocol (NTP) sources using authentication that is cryptographically based. | If NTP is not authenticated, an attacker can introduce a rogue NTP server. This rogue server can then be used to send incorrect time information to ne... |
| V-242645 | | For accounts using password authentication, the Cisco ISE must enforce a minimum 15-character password length. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password ... |
| V-242646 | | For accounts using password authentication, the Cisco ISE must enforce password complexity by requiring that at least one uppercase character be used. | Use of a complex passwords helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measur... |
| V-242647 | | For accounts using password authentication, the Cisco ISE must enforce password complexity by requiring that at least one lowercase character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-242648 | | For accounts using password authentication, the Cisco ISE must enforce password complexity by requiring that at least one digit be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-242649 | | For accounts using password authentication, the Cisco ISE must enforce password complexity by requiring that at least one special character be used. | Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure... |
| V-242652 | | The Cisco ISE must prohibit the use of cached authenticators after an organization-defined time period. | Some authentication implementations can be configured to use cached authenticators.
If cached authentication information is out-of-date, the validity... |
| V-242654 | | The Cisco ISE must use FIPS-validated Keyed-Hash Message Authentication Code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications. | Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide con... |
| V-242658 | | The Cisco ISE must generate unique session identifiers using a FIPS 140-2 approved Random Number Generator (RNG) using DRGB. | Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session ident... |
| V-242660 | | The Cisco ISE must configure the control plane to protect against or limit the effects of common types of Denial of Service (DoS) attacks on the device itself by configuring applicable system options and internet-options. | DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or m... |
| V-242661 | | The Cisco ISE must be configured to send log data to at least two central log servers for the purpose of forwarding alerts to the administrators and the information system security officer (ISSO). | 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 stor... |
| V-242662 | | The Cisco ISE must initiate session auditing upon startup. | If auditing is enabled late in the startup process, the actions of some start-up processes may not be audited. Some audit systems also maintain state ... |
| V-242663 | | The Cisco ISE must generate audit records containing the full-text recording of privileged commands. | Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information.
Organizations consider lim... |
| V-242607 | | The Cisco ISE must limit the number of CLI and GUI sessions to an organization-defined number. | Device management includes the ability to control the number of management sessions that manage a device. Limiting the number of allowed sessions is h... |
| V-242613 | | The Cisco ISE must automatically audit account enabling actions. | Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way t... |
| V-242638 | | The Cisco ISE must conduct configuration and operational backups when changes are made or must schedule backups weekly, at a minimum. | If this information is not backed up and a system failure was to occur, the security settings would be difficult to reconfigure quickly and accurately... |
| V-242615 | | The Cisco ISE must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary... |
| V-242640 | | The Cisco ISE must be configured to prohibit the use of all unnecessary and/or nonsecure functions, ports, protocols, and/or services. | Changes to any software components of the network device can have significant effects on the overall security of the network. Therefore, only qualifie... |
| V-242641 | | The Cisco ISE must be configured to disable Wireless Setup for production systems. | ISE Wireless Setup is beta software so is not authorized for use in DoD.
Wireless Setup is disabled by default after fresh installation of Cisco ISE.... |
| V-242651 | | For accounts using password authentication, the Cisco ISE must use FIPS-validated SHA-2 or later protocol to protect the integrity of the password authentication process. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can ... |
| V-242653 | | The Cisco ISE must use FIPS-validated SHA-2 (or greater) to protect the integrity of hash message authentication code (HMAC), Key Derivation Functions (KDFs), Random Bit Generation, and hash-only applications. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Nonlocal maintenance and diagnostic ... |
| V-242655 | | The Cisco ISE must verify the checksum value of any software download, including install files (ISO or OVA), patch files, and upgrade bundles. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Nonlocal maintenance and diagnostic ... |
| V-242656 | | The Cisco ISE must be configured to implement cryptographic mechanisms using a FIPS 140-2 validated algorithm to protect the confidentiality of remote maintenance sessions. | This requires the use of secure protocols instead of their unsecured counterparts, such as SSH instead of telnet, SCP instead of FTP, and HTTPS instea... |
| V-242657 | | The Cisco ISE must terminate all network connections associated with a device management session at the end of the session, or the session must be terminated after five minutes of inactivity except to fulfill documented and validated mission requirements. | Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management se... |
| V-242659 | | The Cisco ISE must only allow authorized administrators to view or change the device configuration, system files, and other files stored. | This requirement is intended to address the confidentiality and integrity of system information at rest (e.g., network device rule sets) when it is lo... |
