| V-239979 | High | The Cisco VPN remote access server must be configured to use AES encryption for the Internet Key Exchange (IKE) Phase 1 to protect confidentiality of remote access sessions. | Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Remote access is access to DoD non-public information... |
| V-239975 | High | The Cisco ASA remote access VPN server must be configured to use TLS 1.2 or higher to protect the confidentiality of remote access connections. | Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol.
NIST SP... |
| V-239957 | High | The Cisco ASA must be configured to use a Diffie-Hellman (DH) Group of 14 or greater for Internet Key Exchange (IKE) Phase 1. | Use of an approved DH algorithm ensures the Internet Key Exchange (IKE) (Phase 1) proposal uses FIPS-validated key management techniques and processes in the production, storage, and control of... |
| V-239951 | High | The Cisco ASA must be configured to use Internet Key Exchange (IKE) for all IPsec security associations. | Without IKE, the Security Parameter Index (SPI) is manually specified for each security association. IKE peers will negotiate the encryption algorithm and authentication or hashing methods as well... |
| V-239950 | High | The Cisco ASA must be configured to not accept certificates that have been revoked when using PKI for authentication. | Situations may arise in which the certificate issued by a Certificate Authority (CA) may need to be revoked before the lifetime of the certificate expires. For example, the certificate is known to... |
| V-239959 | High | The Cisco ASA must be configured to use FIPS-validated SHA-2 or higher for Internet Key Exchange (IKE) Phase 2. | Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
Although allowed by SP800-131Ar2 for some... |
| V-239980 | High | The Cisco ASA VPN remote access server must be configured to use Advanced Encryption Standard (AES) encryption for the IPsec security association to protect the confidentiality of remote access sessions. | Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session.
Remote access is access to DoD non-public information... |
| V-239968 | High | The Cisco ASA remote access VPN server must be configured to enforce certificate-based authentication before granting access to the network. | To assure accountability and prevent unauthenticated access, non-privileged users must utilize multifactor authentication to prevent potential misuse and compromise of the system.
Multifactor... |
| V-239985 | High | The Cisco ASA VPN remote access server must be configured to use an approved High Assurance Commercial Solution for Classified (CSfC) cryptographic algorithm for remote access to a classified network. | Use of improperly configured or lower assurance equipment and solutions could compromise high-value information.
The National Security Agency/Central Security Service's (NSA/CSS) CSfC program... |
| V-239962 | High | The Cisco ASA VPN gateway must use cryptographic algorithms approved by NSA to protect NSS when transporting classified traffic across an unclassified network. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The VPN gateway must implement cryptographic modules adhering to the higher standards... |
| V-239949 | Medium | The Cisco ASA must be configured to validate certificates via a trustpoint that identifies a DoD or DoD-approved certificate authority. | Without path validation, an informed trust decision by the relying party cannot be made when presented with any certificate not already explicitly trusted. To meet this requirement, the... |
| V-239978 | Medium | The Cisco ASA remote access VPN server must be configured to use SHA-2 or greater for hashing to protect the integrity of IPsec remote access sessions. | Without strong cryptographic integrity protections, information can be altered by unauthorized users without detection.
SHA-1 is considered a compromised hashing standard and is being phased out... |
| V-239974 | Medium | The Cisco ASA remote access VPN server must be configured to produce log records containing information to establish the outcome of the events. | Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the... |
| V-239977 | Medium | The Cisco ASA remote access VPN server must be configured to generate unique session identifiers using a FIPS-validated Random Number Generator (RNG) based on the Deterministic Random Bit Generators (DRBG) algorithm. | Both IPsec and TLS gateways use the RNG to strengthen the security of the protocols. Using a weak RNG will weaken the protocol and make it more vulnerable.
Use of a FIPS validated RNG that is not... |
| V-239976 | Medium | The Cisco ASA remote access VPN server must be configured to use a FIPS-validated algorithm and hash function to protect the integrity of TLS remote access sessions. | Without integrity protection, unauthorized changes may be made to the log files and reliable forensic analysis and discovery of the source of malicious system activity may be degraded.
Remote... |
| V-239971 | Medium | The Cisco ASA remote access VPN server must be configured to generate log records containing information that establishes the identity of any individual or process associated with the event. | Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine... |
| V-239970 | Medium | The Cisco ASA remote access VPN server must be configured to display the Standard Mandatory DoD Notice and Consent Banner before granting access to the network. | Display of a standardized and approved use notification before granting access to the network ensures privacy and security notification verbiage used is consistent with applicable federal laws,... |
| V-239972 | Medium | The Cisco ASA remote access VPN server must be configured to generate log records containing information to establish where the events occurred. | Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
In order to compile an accurate risk... |
| V-239956 | Medium | The Cisco ASA must be configured to use a FIPS-validated cryptographic module to implement IPsec encryption services. | FIPS 140-2 precludes the use of invalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as... |
| V-239955 | Medium | The Cisco ASA must be configured to use a FIPS-validated cryptographic module to generate cryptographic hashes. | FIPS 140-2 precludes the use of invalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as... |
| V-239954 | Medium | The Cisco ASA must be configured to specify Perfect Forward Secrecy (PFS) for the IPsec Security Association (SA) during IKE Phase 2 negotiation. | PFS generates each new encryption key independently from the previous key. Without PFS, compromise of one key will compromise all communications.
The Phase 2 (Quick Mode) Security Association... |
| V-239953 | Medium | The Cisco ASA must be configured to use NIST FIPS-validated cryptography for Internet Key Exchange (IKE) Phase 1. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The VPN gateway must implement cryptographic modules adhering to the higher standards... |
| V-239952 | Medium | The Cisco ASA must be configured to use Internet Key Exchange v2 (IKEv2) for all IPsec security associations. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types); organizations must... |
| V-239958 | Medium | The Cisco ASA must be configured to use FIPS-validated SHA-2 or higher for Internet Key Exchange (IKE) Phase 1. | Without cryptographic integrity protections, information can be altered by unauthorized users without detection.
Although allowed by SP800-131Ar2 for some applications, SHA-1 is considered a... |
| V-239981 | Medium | The Cisco VPN remote access server must be configured to accept Common Access Card (CAC) credential credentials. | The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access.
DoD has mandated the use of the CAC to support identity management and personal authentication... |
| V-239969 | Medium | The Cisco ASA remote access VPN server must be configured to map the distinguished name (DN) from the client’s certificate to entries in the authentication server to determine authorization to access the network. | Without mapping the certificate used to authenticate to the user account, the ability to determine the identity of the individual user or group will not be available for forensic analysis.
This... |
| V-239984 | Medium | The Cisco ASA VPN remote access server must be configured to validate certificates used for Transport Layer Security (TLS) functions by performing RFC 5280-compliant certification path validation. | A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to... |
| V-239963 | Medium | The Cisco ASA VPN gateway must be configured to renegotiate the IPsec Security Association after eight hours or less. | The IPsec SA and its corresponding key will expire either after the number of seconds or amount of traffic volume has exceeded the configured limit. A new SA is negotiated before the lifetime... |
| V-239960 | Medium | The Cisco ASA VPN gateway must be configured to restrict what traffic is transported via the IPsec tunnel according to flow control policies. | Unrestricted traffic may contain malicious traffic which poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network, which uses bandwidth... |
| V-239961 | Medium | The Cisco ASA VPN gateway must be configured to identify all peers before establishing a connection. | Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
For distributed architectures (e.g., service-oriented architectures), the... |
| V-239966 | Medium | The Cisco ASA remote access VPN server must be configured to use LDAP over SSL to determine authorization for granting access to the network. | Protecting authentication communications between the client, the VPN Gateway, and the authentication server keeps this critical information from being exploited.
In distributed information... |
| V-239967 | Medium | The Cisco ASA remote access VPN server must be configured to identify and authenticate users before granting access to the network. | To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.
Organizational... |
| V-239964 | Medium | The Cisco ASA VPN gateway must be configured to renegotiate the IKE security association after 24 hours or less. | When a VPN gateway creates an IPsec Security Association (SA), resources must be allocated to maintain the SA. These resources are wasted during periods of IPsec endpoint inactivity, which could... |
| V-239965 | Medium | The Cisco ASA remote access VPN server must be configured to use a separate authentication server than that used for administrative access. | The VPN interacts directly with public networks and devices and should not contain user authentication information for all users. AAA network security services provide the primary framework... |
| V-239947 | Medium | The Cisco ASA must be configured to queue log records locally in the event that the central audit server is down or not reachable. | If the system were to continue processing after audit failure, actions can be taken on the system that cannot be tracked and recorded for later forensic analysis.
Because of the importance of... |
| V-239948 | Medium | The Cisco ASA must be configured to generate an alert that can be forwarded as an alert to organization-defined personnel and/or firewall administrator of all log failure events. | 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... |
| V-239982 | Medium | The Cisco ASA VPN remote access server must be configured to disable split-tunneling for remote clients. | Split tunneling would in effect allow unauthorized external connections, making the system more vulnerable to attack and to exfiltration of organizational information.
A VPN hardware or software... |
| V-239983 | Medium | The Cisco ASA VPN remote access server must be configured to generate log records when successful and/or unsuccessful VPN connection attempts occur. | Without generating log 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... |
| V-239973 | Low | The Cisco ASA remote access VPN server must be configured to generate log records containing information to establish the source of the events. | Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk... |
| V-239945 | Low | The Cisco ASA must be configured to generate log records containing information to establish what type of VPN events occurred. | Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack.
VPN gateways often have a separate... |
| V-239946 | Low | The Cisco ASA must be configured to generate log records containing information to establish when the events occurred. | Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack.
VPN gateways often have a separate audit log for... |
