Core Alert Fields

The SHA256 value of the CGO that initiated the alert.

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

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

APP-ID category name associated with a firewall alert

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

Whether the alert is starred by starring configuration

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

Miscellaneous information about the 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 SHA256 hash value of the initiator.

Command-line arguments of the Causality Group Owner.

Name of the virtual system for the Palo Alto Networks firewall that triggered an 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.

Indicates whether a firewall alert is classified as phishing

The MD5 value of the process which initiated the alert.

A unique identifier per agent.

Unique identifier of the causality instance generated by Cortex XDR

The MD5 value of the CGO that initiated 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

OS parent thread ID.

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

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

Name of the user associated with the parent operating system

OS parent process ID

The domain on which an alert was triggered.

The source zone name of the connection for firewall alerts.

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

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

Signing status of the operating system of the activity

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

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

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

The firewall rule ID that triggered the firewall alert

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

MD5 hash value of the file.

The firewall rule ID that triggered the firewall alert

Thread ID (TID) of the initiating process.

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

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

Signer of the process that triggered the alert.

APP-ID technology name associated with a firewall alert

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 remote IP address of a network operation that triggered the alert.

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.

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

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

Path of the initiating process.

Parent operating system signer

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

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.

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

The ID that matches the rule that triggered the alert

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

SHA256 hash value of the file.

Signer of the process that triggered the alert.

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

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

Unique identifier of the Actor Process instance generated by Cortex XDR

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

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

APP-ID Sub category name associated with a firewall alert

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

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

Process ID (PID) of the initiating process.

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

Whether the alert is excluded by an exclusion configuration

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

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

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

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.

Name of firewall on which a firewall alert was raised.

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

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

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

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

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>

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

The domain name queried in the DNS request.

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

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

The destination zone of the connection for firewall alerts.

SHA256 hash value of an Microsoft Office file macro

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.

Parent operating system SHA256 hash value

Unique identifier of the Action Process instance generated by Cortex XDR

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 name of the software publishing vendor that signed the file in the causality chain that led up to the alert.

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.