Static endpoint groups have limited selection flexibility compared with dynamic groups. Their selection criteria are capped, and wildcard matching is limited to the asterisk character, making them less scalable and adaptive for complex grouping requirements.

When a Cortex XDR agent encounters an unknown Portable Executable (PE) or DLL, it can automatically upload the sample to Palo Alto Networks WildFire in the cloud for deep sandboxing and dynamic analysis.
If a specific executable must be prevented from being uploaded to the cloud (for instance, to protect highly confidential corporate proprietary software, proprietary source code compilations, or data privacy requirements), you must configure an Exclusion Rule:
How it works: Under Endpoints > Policy Management > Prevention > Profiles > Malware Profile, you can add a file or path exclusion specifically targeted at WildFire Analysis. By selecting the specific executable or directory and checking the exclusion box for cloud upload/analysis, the local agent will bypass uploading that sample while still enforcing local static analysis protections.

In Palo Alto Networks Cortex XSIAM / Cortex XDR, when you create and save an XQL query to run via API or a scheduled job, the system calculates its performance and resource impact.
Simulated Compute Units: This column in the Query Center provides an estimated or simulated value of the compute resources (Compute Units) that the query is expected to consume based on its complexity, the size of the targeted datasets, and its structure. Checking this column allows administrators to predict and manage their API consumption and credit burn before putting the query into production.

When Palo Alto Networks NGFW logs are ingested into Cortex XDR, they provide additional network and application context that enhances XDR's analytics and detection capabilities. The firewall logs can be correlated with endpoint, user, and network activity, enabling enhanced application logging and deeper analysis across the environment.

The key clue in the audit report is that Network Location Configuration is enabled, and the rule successfully blocks RDP for employees at company HQ, but fails for remote workers.
When Network Location Configuration is enabled in Cortex XDR, the agent determines whether it is inside the corporate network (Internal) or outside of it (External) based on network location rules (like connectivity to a specific internal domain controller or IP range).
Host-Based Firewall rules in Cortex XDR can be assigned to specific location profiles-Internal, External, or All. If the rule group blocking outbound RDP was accidentally assigned only to the Internal location group, the rule will instantly stop applying the moment a remote worker disconnects from the corporate network at HQ.