Score Higher on Verified XDR-Analyst | Palo Alto Networks XDR Analyst Exam Questions with Answers

The “Respond to Malicious Causality Chains” feature in a Cortex XDR Windows Malware profile allows the agent to take automatic actions against network connections and processes that are involved in malicious activity on the endpoint. The feature has two modes: Block IP Address and Kill Process1.

The two purposes of “Respond to Malicious Causality Chains” in a Cortex XDR Windows Malware profile are:

Automatically kill the processes involved in malicious activity. This can help to stop the malware from spreading or doing any further damage.

Automatically block the IP addresses involved in malicious traffic. This can help to prevent the malware from communicating with its command and control server or other malicious hosts.

The other two options, automatically close the connections involved in malicious traffic and automatically terminate the threads involved in malicious activity, are not specific to “Respond to Malicious Causality Chains”. They are general security measures that the agent can perform regardless of the feature.

The “assigned to” field value of a new incident that was just reported to Cortex is “Unassigned”. This means that the incident has not been assigned to any analyst or group yet, and it is waiting for someone to take ownership of it. The “assigned to” field is one of the default fields that are displayed in the incident layout, and it can be used to filter and sort incidents in the incident list. The “assigned to” field can be changed manually by an analyst, or automatically by a playbook or a rule12.

Let’s briefly discuss the other options to provide a comprehensive explanation:

A. Pending: This is not the correct answer. Pending is not a valid value for the “assigned to” field. Pending is a possible value for the “status” field, which indicates the current state of the incident. The status field can have values such as “New”, “Active”, “Done”, “Closed”, or "Pending"3.

B. It is blank: This is not the correct answer. The “assigned to” field is never blank for any incident. It always has a default value of “Unassigned” for new incidents, unless a playbook or a rule assigns it to a specific analyst or group12.

D. New: This is not the correct answer. New is not a valid value for the “assigned to” field. New is a possible value for the “status” field, which indicates the current state of the incident. The status field can have values such as “New”, “Active”, “Done”, “Closed”, or "Pending"3.

In conclusion, the “assigned to” field value of a new incident that was just reported to Cortex is “Unassigned”. This field can be used to manage the ownership and responsibility of incidents, and it can be changed manually or automatically.

 The Live Terminal feature in Cortex XDR allows you to initiate a remote connection to an endpoint and perform various actions such as running commands, uploading and downloading files, and terminating processes. You can disable the ability to use the Live Terminal feature in Cortex XDR by configuring the Agent Settings Profile. The Agent Settings Profile defines the behavior and functionality of the Cortex XDR agent on the endpoint. You can create different profiles for different groups of endpoints and assign them accordingly. To disable the Live Terminal feature, you need to uncheck the Enable Live Terminal option in the Agent Settings Profile and save the changes. This will prevent the Cortex XDR agent from accepting any Live Terminal requests from the Cortex XDR management console. References:

Live Terminal: This document explains how to use the Live Terminal feature to investigate and respond to security events on Windows endpoints.

Agent Settings Profile: This document describes how to create and manage Agent Settings Profiles to define the behavior and functionality of the Cortex XDR agent on the endpoint.