Core Alert Fields

The command-line of the process whose creation triggered the alert.

If the alert triggered on network activity (the Event Type is Network Connection) this is the port on the endpoint that triggered the alert. If not, then N/A.

Signing status of the process that initiated the activity: Unsigned, Signed, Invalid Signature, Unknown.

Command-line used to by the parent operating system to initiate the process including any arguments

The descriptions of the reasons that contributed to the user's risk level.

The name of the process whose creation triggered the alert.

The email sender value of a firewall alerts triggered on a the content of a malicious email.

Unique identifier of the Actor Process instance generated by Cortex XDR

The SHA256 hash value of the initiator.

Signing status of the CGO: Unsigned, Signed, Invalid Signature, Unknown.

Alert category based on the alert source. An example of an XDR Agent alert category is Exploit Modules.

The descriptions of the reasons that contributed to the host's risk level.

Classifications used to map similar types of resources across different cloud providers. For example, EC2, Google Compute Engine, and Microsoft Compute are all mapped to Compute

The type of event on which the alert was triggered: File Event, Injection Event, Load Image Event, Network Event, Process Execution, Registry Event

Unique identifier of the Action Process instance generated by Cortex XDR

When the alert triggered on a file (the Event Type is File) this is the path to the file on the endpoint. If not, then N/A.

The MD5 value of the process which initiated the alert.

Displays the type of MITRE ATT&CK tactic on which the alert was triggered.

A unique identifier per agent.

Parent operating system signer

OS parent thread ID.

Represents the cloud provider folders or projects. For example, AWS Accounts and Azure Subscriptions

The email subject value of a firewall alerts triggered on a the content of a malicious email.

The fully qualified domain name (FQDN) of the Windows endpoint or server on which this alert triggered.

Unique identifier of the causality instance generated by Cortex XDR

Signing status of the operating system of the activity

Action taken by the alert sensor, either Detected or Prevented with action status displayed in parenthesis.

SHA256 hash value of the file.

Thread ID (TID) of the initiating process.

IP address of the endpoint or server on which this alert triggered.

Command-line used to initiate the process including any arguments.

Name of firewall on which a firewall alert was raised.

The SHA256 hash vale of an external DLL file that triggered the alert.

APP-ID category name associated with a firewall alert

Related App-ID for an alert. App-ID is a traffic classification system that determines what an application is irrespective of port, protocol, encryption (SSH or SSL) or any other evasive tactic used by the application. When known, you can also pivot to the Palo Alto Networks Applipedia entry that describes the detected application.

A more specific classification used to map the types of resources. For example, DISK,VPC, Subnet are all mapped to Compute

The URL destination address of the domain triggering the firewall alert.

If the alert triggered on network activity (the Event Type is Network Connection) this is the IP address of the host that triggered the alert. If not, then N/A.

The remote IP address of a network operation that triggered the alert.

Parent operating system SHA256 hash value

The remote port of a network operation that triggered the alert.

The date and time when the alert was triggered. Right-click to Show rows 30 days prior or 30 days after the selected timestamp field value

Classification used to map identity type that initiated an operation which triggered an alert. For example, Service, Application and Temporary Credentials

If the alert triggered on network activity (the Event Type is Network Connection) this is the the remote host name that triggered the alert. If not, then N/A.

Name of the virtual system for the Palo Alto Networks firewall that triggered an alert

Action taken by the alert sensor, either Detected or Prevented with action status displayed in parenthesis.

The firewall rule name that matches the network traffic that triggered the firewall alert.

A more specific classification of the identity initiated operation. For example, for Identity Type: Temporary Credentials the sub type could be Assumed Role

The name of the process that initiated an activity such as a network connection or registry change.

The domain on which an alert was triggered.

The source zone name of the connection for firewall alerts.

Signer of the process that triggered the alert.

Represents the resources that are referenced in the alert log. In most cases, the referred resource will be where the operation was initiated on

If the alert triggered on registry modifications (the Event Type is Registry) this is the full registry key that triggered the alert. If not, then N/A.

OS parent process ID

The destination zone of the connection for firewall alerts.

Command-line arguments of the Causality Group Owner.

The MD5 value of the CGO that initiated the alert.

For XDR Agent alerts, this field identifies the protection module that triggered the alert.

Name of the user associated with the parent operating system

The risk level associated with the risky user. Can be LOW, MED or HIGH.

The domain name queried in the DNS request.

Miscellaneous information about the alert.

The risk level associated with the risky host. Can be LOW, MED, or HIGH

The email recipient value of a firewall alerts triggered on a the content of a malicious email.

The serial number of the firewall that raised the firewall alert.

The hostname of the endpoint or server on which this alert triggered. The hostname is generally available for XDR agent alerts or alerts that are stitched with EDR data. When the hostname is unknown, this field is blank.

The firewall rule ID that triggered the firewall alert

The operating system subtype of the agent from which the alert was triggered.

If the alert triggered on registry modifications (the Event Type is Registry) this is the registry data that triggered the alert. If not, then N/A

The name of the software publishing vendor that signed the file in the causality chain that led up to the alert.

The name of the process that started the causality chain based on Cortex XDR causality logic.

Signer of the process that triggered the alert.

MD5 hash value of the file.

Displays the type of MITRE ATT&CK technique and sub-technique on which the alert was triggered.

Process ID (PID) of the initiating process.

The name of the cloud provider where the alert occurred: AWS/GCP/Azure/etc

Signature status of the process that triggered the alert: Unsigned, Signed, Invalid Signature, Unknown.

APP-ID Sub category name associated with a firewall alert

APP-ID technology name associated with a firewall alert

Indicates whether a firewall alert is classified as phishing

The name of the user that initiated the behavior that triggered the alert. If the user is a domain user account, this field also identifies the domain. Any alert triggered based on network, authentication, or login events, displays the User Name in the follow standardized format in the Alerts and Incidents pages.<company domain>\<username>

Whether the alert is starred by starring configuration

SHA256 hash value of an Microsoft Office file macro

The SHA256 value of the CGO that initiated the alert.

Path of the initiating process.

Whether the alert is excluded by an exclusion configuration

The ID that matches the rule that triggered the alert

The firewall rule ID that triggered the firewall alert

MAC address of the endpoint or server on which this alert triggered.