OpenControls Logo

STIG Viewer

STIGViewer Support

The Cisco ASA must be configured to send an alert to organization-defined personnel and/or the firewall administrator when malicious code is detected.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-239888CASA-IP-000280SV-239888r665977_ruleCCI-001243medium
Description
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 impeded. The IDPS generates an immediate (within seconds) alert which notifies designated personnel of the incident. Sending a message to an unattended log or console does not meet this requirement since that will not be seen immediately. These messages should include a severity level indicator or code as an indicator of the criticality of the incident. The ISSM or ISSO may designate the firewall administrator and/or other authorized personnel to receive the alert within the specified time, validate the alert, and then forward only validated alerts to the ISSM and ISSO.
STIGDate
Cisco ASA IPS Security Technical Implementation Guide2024-08-27

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (15) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
CRY-05Encrypting Data At Rest
1.00
DCH-01Data Protection
1.00
IAC-21Least Privilege
1.00
END-04Malicious Code Protection (Anti-Malware)
0.50
END-04.1Automatic Antimalware Signature Updates
0.50

+5 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (8) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
SC-7(9)Restrict Threatening Outgoing Communications Traffic
1.00
SI-3Malicious Code Protection
1.00
SI-4(1)System-wide Intrusion Detection System
1.00
SI-4(22)Unauthorized Network Services
1.00
SI-4(5)System-generated Alerts
1.00
SI-6Security and Privacy Function Verification
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.14.1
1.00
3.14.2
1.00
3.14.3
1.00
3.14.4
1.00
3.14.5
1.00
CCI1 mapping
CCI-001243
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.DS-01
1.00
PR.DS-02
1.00
PR.DS-10
1.00
DE.CM-09
0.50
ID.RA-01
0.50
ID.RA-08
0.50
PR.PS-02
0.50

Who does this work

8 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-239888r665977_chk)

Verify email server and email addresses have been defined. Step 1: Navigate to Policies >> Actions >> Alerts. Step 2: From the Create Alert drop-down menu, choose Create Email Alert. Step 3: Verify the email address is that of the system administrator. ---------------------------------------- Verify that Advanced Malware Protection is configured to generate alerts. Step 1: Navigate to Policies >> Actions >> Alerts. Step 2: Click the Advanced Malware Protections Alerts tab. Step 3: In the Alerts section, verify that an email alert has been selected. Note: The above example is using the Firepower Management Center. If the ASA is not configured to send an alert to organization-defined personnel and/or the firewall administrator when malicious code is detected, this is a finding.

Fix Text (F-43080r665976_fix)

Configure email server and email addresses to send alerts to organization-defined personnel and/or the firewall administrator. Step 1: Navigate to Policies >> Actions >> Alerts. Step 2: From the Create Alert drop-down menu, choose Create Email Alert. Step 3: Enter a Name for the alert response. In the To field, enter the email addresses where you want to send alerts, separated by commas. In the From field, enter the email address that you want to appear as the sender of the alert. Next to Relay Host, click edit to enter mail server. Step 4: Click Save. ---------------------------------------------- Configure Advanced Malware Protection to send alerts when malware is detected. Step 1: Navigate to Policies >> Actions >> Alerts. Step 2: Click the Advanced Malware Protections Alerts tab. Step 3: In the Alerts section, choose the alert response for an email alert. Step 4: Click Save.