Palo Alto

Detection rules for Palo Alto data sources. Each rule includes its MITRE ATT&CK mapping, impact rating, and a description of what it detects. These rules analyze events with the data type firewall-paloalto, which the Palo Alto Networks integration sends.

This category contains 11 detection rules.

RuleCategoryTechniqueImpact (C/I/A)
PAN-OS Blocked Threat Category Detection (session destination)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:2
PAN-OS Blocked Threat Category Detection (session source)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:2
PAN-OS High-Severity Spyware or Vulnerability Detection (client-to-server)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:2
PAN-OS High-Severity Spyware or Vulnerability Detection (server-to-client)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:2
PAN-OS Repeated Authentication FailuresCredential AccessT1110 - Brute ForceC:3 / I:3 / A:1
PAN-OS Repeated DNS Security DetectionsIntrusion DetectionVendor threat detectionC:3 / I:2 / A:1
PAN-OS Repeated High-Severity Vulnerability Signatures (client-to-server)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:3
PAN-OS Repeated High-Severity Vulnerability Signatures (server-to-client)Intrusion DetectionVendor threat detectionC:3 / I:3 / A:3
PAN-OS Repeated Risky URL Category DetectionsIntrusion DetectionVendor threat detectionC:3 / I:2 / A:1
PAN-OS WildFire Malware Verdict (client-to-server)Malware DetectionVendor threat detectionC:3 / I:3 / A:2
PAN-OS WildFire Malware Verdict (server-to-client)Malware DetectionVendor threat detectionC:3 / I:3 / A:2

Rule Example

Below is an example of a rule definition for PAN-OS Blocked Threat Category Detection (session destination) (view in repository):

# Rule version v2.0.0

dataTypes:
- firewall-paloalto
name: PAN-OS Blocked Threat Category Detection (session destination)
impact:
  confidentiality: 3
  integrity: 3
  availability: 2
category: Intrusion Detection
technique: Vendor threat detection
adversary: target
references:
- https://docs.paloaltonetworks.com/ngfw/administration/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/threat-log-fields
description: Detects a blocked PAN-OS threat categorized as malware, command-and-control, phishing or botnet. The
  category alone does not establish membership in an external intelligence feed. Review the signature, vendor action,
  session endpoints and attack direction; a blocked event does not establish compromise. For URL-category events,
  the requested remote resource is the adversary; the request direction does not make the requesting client the
  malicious resource.
where: equals("log.paType", "THREAT") && oneOf("log.thrCategory", ["malware", "command-and-control", "phishing",
  "botnet"]) && equals("actionResult", "denied") && exists("origin.ip") && exists("target.ip") && (equals("log.paSubtype",
  "url") || equals("log.paDirection", "server-to-client"))
groupBy:
- lastEvent.dataSource
- lastEvent.log.paScope
- lastEvent.log.paVsys
- adversary.ip
- adversary.ip
- lastEvent.log.paThreatid

Rule Details

PAN-OS Blocked Threat Category Detection (session destination)

Detects a blocked PAN-OS threat categorized as malware, command-and-control, phishing or botnet. The category alone does not establish membership in an external intelligence feed. Review the signature, vendor action, session endpoints and attack direction; a blocked event does not establish compromise. For URL-category events, the requested remote resource is the adversary; the request direction does not make the requesting client the malicious resource.

PAN-OS Blocked Threat Category Detection (session source)

Detects a blocked PAN-OS threat categorized as malware, command-and-control, phishing or botnet. The category alone does not establish membership in an external intelligence feed. Review the signature, vendor action, session endpoints and attack direction; a blocked event does not establish compromise. For URL-category events, the requested remote resource is the adversary; the request direction does not make the requesting client the malicious resource.

PAN-OS High-Severity Spyware or Vulnerability Detection (client-to-server)

Detects a high or critical PAN-OS spyware or vulnerability signature. The signature does not prove successful exploitation, a public-facing target, or a particular technique. Review the threat ID, action and attack direction. Session source and destination retain their physical roles; the rule uses the documented attack direction to select the alert adversary.

PAN-OS High-Severity Spyware or Vulnerability Detection (server-to-client)

Detects a high or critical PAN-OS spyware or vulnerability signature. The signature does not prove successful exploitation, a public-facing target, or a particular technique. Review the threat ID, action and attack direction. Session source and destination retain their physical roles; the rule uses the documented attack direction to select the alert adversary.

PAN-OS Repeated Authentication Failures

Detects ten SYSTEM auth-fail events from the same observed source, collector, firewall and virtual system within fifteen minutes. The event can come from different authentication services; it does not by itself prove a management-plane login. Check the authentication profile, requested user and any subsequent successes before treating the sequence as an attack.

PAN-OS Repeated DNS Security Detections

Detects three relevant DNS security events from the same observed source, collector, firewall and virtual system within thirty minutes. Supports the legacy dns subtype and spyware sinkhole or dns-c2/dns-malware category events. A source can be a forwarding resolver rather than the original endpoint. Trace the DNS request and vendor action before attributing compromise; an alert action does not prove a successful connection.

PAN-OS Repeated High-Severity Vulnerability Signatures (client-to-server)

Detects two high or critical vulnerability/exploit detections carrying a CVE label or the legacy unknown category within thirty minutes, for the same collector, firewall, virtual system, endpoints and attack direction. Neither a known CVE nor an unknown category establishes a zero-day. The vendor action determines whether traffic was blocked; this sequence does not prove successful exploitation. Inspect the signature and target exposure. The single-event spyware/vulnerability rule can also match these events.

PAN-OS Repeated High-Severity Vulnerability Signatures (server-to-client)

Detects two high or critical vulnerability/exploit detections carrying a CVE label or the legacy unknown category within thirty minutes, for the same collector, firewall, virtual system, endpoints and attack direction. Neither a known CVE nor an unknown category establishes a zero-day. The vendor action determines whether traffic was blocked; this sequence does not prove successful exploitation. Inspect the signature and target exposure. The single-event spyware/vulnerability rule can also match these events.

PAN-OS Repeated Risky URL Category Detections

Detects five URL events in the configured malware, phishing, command-and-control, grayware or hacking categories from the same observed source, collector, firewall and virtual system within thirty minutes. Includes alert-only detections and blocked/confirmation-page requests. Grayware or hacking categorization does not prove malware, and requesting a URL does not prove execution or compromise. The requested remote resource is the alert adversary; the requesting client is its target. Inspect the URL and action; a later continue/override is a separate event.

PAN-OS WildFire Malware Verdict (client-to-server)

Detects a high or critical WildFire submission with the explicit malware verdict. A WildFire verdict is analysis of a submitted file; it does not prove file execution. Inspect the hash, action and endpoint evidence. The block action indicates a blocked file; alert alone does not establish prevention. Benign, grayware and phishing verdicts are not mislabeled as malware by this rule.

PAN-OS WildFire Malware Verdict (server-to-client)

Detects a high or critical WildFire submission with the explicit malware verdict. A WildFire verdict is analysis of a submitted file; it does not prove file execution. Inspect the hash, action and endpoint evidence. The block action indicates a blocked file; alert alone does not establish prevention. Benign, grayware and phishing verdicts are not mislabeled as malware by this rule.