| V-239894 | Medium | The Cisco ASA must be configured to send an alert to organization-defined personnel and/or the firewall administrator when DoS incidents are detected. | Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information.
CJCSM 6510.01B,... |
| V-239895 | Medium | The Cisco ASA must generate an alert to organization-defined personnel and/or the firewall administrator when active propagation of malware or malicious code is detected. | Without an alert, security personnel may be unaware of major detection incidents that require immediate action and this delay may result in the loss or compromise of information.
CJCSM 6510.01B,... |
| V-239892 | Medium | The Cisco ASA must be configured to send an alert to organization-defined personnel and/or the firewall administrator when intrusion events are detected. | Without an alert, security personnel may be unaware of intrusion detection incidents that require immediate action and this delay may result in the loss or compromise of information.
In... |
| V-239893 | Medium | The Cisco ASA must be configured to send an alert to organization-defined personnel and/or the firewall administrator when threats are detected. | Without an alert, security personnel may be unaware of an impending failure of the audit capability, and the ability to perform forensic analysis and detect rate-based and other anomalies will be... |
| V-239890 | Medium | The Cisco ASA must be configured to block inbound traffic containing unauthorized activities or conditions. | If inbound communications traffic is not continuously monitored for unusual/unauthorized activities or conditions, there will be times when hostile activity may not be noticed and defended... |
| V-239891 | Medium | The Cisco ASA must be configured to block outbound traffic containing unauthorized activities or conditions. | If outbound communications traffic is not continuously monitored for unusual/unauthorized activities or conditions, there will be times when hostile activity may not be noticed and defended... |
| V-239874 | Medium | The Cisco ASA must be configured to produce audit records containing information to establish when the events occurred. | Without establishing the time (date/time) an event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Associating the date and... |
| V-239875 | Medium | The Cisco ASA must be configured to produce audit records containing information to establish where the event was detected. | Associating where the event was detected with the event log entries provides a means of investigating an attack or identifying an improperly configured IDPS. This information can be used to... |
| V-239876 | Medium | The Cisco ASA must be configured to produce audit records containing information to establish the source of the event. | Associating the source of the event with detected events in the logs provides a means of investigating an attack or suspected attack.
While auditing and logging are closely related, they are not... |
| V-239877 | Medium | The Cisco ASA must be configured to produce audit records containing information to establish the outcome of events associated with detected harmful or potentially harmful traffic. | Associating event outcome with detected events in the log provides a means of investigating an attack or suspected attack.
While auditing and logging are closely related, they are not the same.... |
| V-239873 | Medium | The Cisco ASA must be configured to produce audit records containing sufficient information to establish what type of event 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. Associating an event type with each... |
| V-239878 | Medium | The Cisco ASA must be configured to log events based on policy access control rules, signatures, and anomaly analysis. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.
While... |
| V-239879 | Medium | The Cisco ASA must be configured to off-load log records to a centralized log server. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading ensures audit information does not get overwritten if the limited audit storage... |
| V-239889 | Medium | The Cisco ASA must be configured to automatically install updates to signature definitions and vendor-provided rules. | Failing to automatically update malicious code protection mechanisms, including application software files, signature definitions, and vendor-provided rules, leaves the system vulnerable to... |
| V-239888 | Medium | The Cisco ASA must be configured to send an alert to organization-defined personnel and/or the firewall administrator when malicious code is detected. | Without an alert, security personnel may be unaware of an impending failure of the audit capability, and the ability to perform forensic analysis and detect rate-based and other anomalies will be... |
| V-239881 | 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. | It is critical that when the IDPS is at risk of failing to process audit logs as required, it take action to mitigate the failure.
Audit processing failures include: software/hardware errors;... |
| V-239880 | Medium | The Cisco ASA must be configured to send log records to the syslog server for specific facility and severity level. | Without the capability to generate audit records with a severity code it is difficult to track and handle detection events.
While auditing and logging are closely related, they are not the same.... |
| V-239883 | Medium | The Cisco ASA must be configured to use Advanced Malware Protection (AMP) features to detect and block the transmission of malicious software and malware. | Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution... |
| V-239882 | Medium | The Cisco ASA must be configured to block outbound traffic containing denial-of-service (DoS) attacks by ensuring an intrusion prevention policy has been applied to outbound communications traffic. | The IDPS must include protection against DoS attacks that originate from inside the enclave which can affect either internal or external systems. These attacks may use legitimate or rogue... |
| V-239885 | Medium | The Cisco ASA must be configured to install updates for signature definitions and vendor-provided rules. | Failing to update malicious code protection mechanisms, including application software files, signature definitions, and vendor-provided rules, leaves the system vulnerable to exploitation by... |
| V-239884 | Medium | The Cisco ASA must block any prohibited mobile code at the enclave boundary when it is detected. | Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution... |
| V-239887 | Medium | The Cisco ASA must be configured to block traffic from IP addresses that have a known bad reputation based on the latest reputation intelligence. | Configuring the network element to delete and/or quarantine based on local organizational incident handling procedures minimizes the impact of this code on the network.
Malicious code includes,... |
| V-239886 | Medium | The Cisco ASA must be configured to block malicious code. | Configuring the IDPS to delete and/or quarantine based on local organizational incident handling procedures minimizes the impact of this code on the network. |
