Detections
Analytics

PANW-AG-000120 - The Palo Alto Networks security platform must generate an alert to, at a minimum, the ISSO and ISSM when rootkits or other malicious software that allows unauthorized nonprivileged access is detected.

Information

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.

The device generates an alert that notifies designated personnel of the Indicators of Compromise (IOCs) that require real-time alerts. These messages should include a severity level indicator or code as an indicator of the criticality of the incident. These indicators reflect the occurrence of a compromise or a potential compromise.

Since these incidents require immediate action, these messages are assigned a critical or level 1 priority/severity, depending on the system's priority schema.

CJCSM 6510.01B, 'Cyber Incident Handling Program', lists nine Cyber Incident and Reportable Event Categories. DOD has determined that categories identified by CJCSM 6510.01B Major Indicators (category 1, 2, 4, or 7 detection events) will require an alert when an event is detected.

Alerts may be transmitted, for example, telephonically, by electronic mail messages, or by text messaging. The Palo Alto Networks security platform must either send the alert to a management console that is actively monitored by authorized personnel or use a messaging capability to send the alert directly to designated personnel.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

This requires the use of an Antivirus Profile, an Anti-spyware Profile, and a Vulnerability Protection Profile.
1. Configure a Server Profile for use with Log Forwarding Profile(s); if email is used, the ISSO and ISSM must be recipients.
2. Configure a Log Forwarding Profile:
Go to Objects >> Log Forwarding.
3. Configure an Antivirus Profile, an Anti-spyware Profile, and a Vulnerability Protection Profile in turn.

Note: A custom Anti-spyware Profile or the Strict Anti-spyware Profile must be used instead of the Default Anti-spyware Profile. The selected Anti-spyware Profile must use the block action at the critical, high, and medium severity threat levels.

Use the Antivirus Profile, Anti-spyware Profile, and Vulnerability Protection Profile in a Security Policy that filters traffic to Internal and DMZ zones:
1. Go to Policies >> Security.
2. Select an existing policy rule or select 'Add' to create a new one.
3. In the 'Actions' tab in the 'Profile Setting' section, in the 'Profile Type' field, select 'Profiles'. The window will change to display the different categories of Profiles.
4. In the 'Actions' tab in the 'Profile Setting' section, in the 'Antivirus' field, select the configured Antivirus Profile.
5. In the 'Actions' tab in the 'Profile Setting' section, in the 'Anti-spyware' field, select the configured or Strict Anti-spyware Profile.
6. In the 'Actions' tab in the 'Profile Setting' section, in the 'Vulnerability Protection' field, select the configured Vulnerability Protection Profile.
7. In the 'Actions' tab in the 'Log Setting' section, select 'Log At Session End'. This generates a traffic log entry for the end of a session and logs drop and deny entries.
8. In the 'Actions' tab in the 'Log Setting' section, in the 'Log Forwarding' field, select the log forwarding profile from the drop-down list.
9. Select 'OK'.
10. Commit changes by selecting 'Commit' in the upper-right corner of the screen.
11. Select 'OK' when the confirmation dialog appears.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_PAN_Y25M04_STIG.zip

Item Details

Category: SYSTEM AND INFORMATION INTEGRITY

References: 800-53|SI-4(5), CAT|II, CCI|CCI-002664, Rule-ID|SV-228872r1056123_rule, STIG-ID|PANW-AG-000120, STIG-Legacy|SV-77115, STIG-Legacy|V-62625, Vuln-ID|V-228872

Plugin: Palo_Alto

Control ID: 560fd62d121cb212d37b2f8025dc72823c6c74347a6cf86f4295ba1690f12c8c