Learn how to define and manage global endpoint policy exceptions in Cortex XSIAM.
As an alternative to adding an endpoint-specific exception in policy rules, you can define and manage global exceptions that apply across all of your endpoints. On the Global Exception page, you can manage all the global exceptions in your organization for all platforms. Profiles associated with one or more targets that are beyond your defined user scope are locked and cannot be edited.
Important
Starting with version 1.3, Cortex XSIAM enables you to manage the Global Endpoint Policy exceptions from a central location and easily apply them across multiple profiles in the Legacy Agent Exceptions management page.
To manage the prevention profile exceptions from Exception Configuration, you must first migrate your existing exceptions configured via the Global exceptions.
Your migrated rules are displayed on the Settings → Exception Configurations → Legacy Agent Exceptions page. For more information about the migration, see Exception configuration.
To create new global endpoint policy exceptions using the Legacy Agent Exceptions page, see Add a legacy exception rule.
If you don't migrate the legacy exceptions, you can continue to add exceptions as described below.
Configure exception rules forCortex XSIAM protection and prevention actions in a centralized location, and apply them across multiple profiles.
Go to Endpoints → Policy Management → Policy Exceptions.
Select Process exceptions.
Select the operating system.
Enter the name of the process.
Select one or more Endpoint Protection Modules that will allow this process to run. The modules displayed on the list are the modules relevant to the operating system defined for this profile. To apply the process exception on all security modules, Select all. To apply the process exception on all exploit security modules, select Disable Injection. Click the adjacent arrow to add the exception.
After you add all exceptions, Save your changes.
The new process exception is added to the Global Exceptions in your network and will be applied across all rules and policies. To edit the exception, select it and click the edit icon. To delete it, select it and click the delete icon.
Configure support exception rules for Cortex XSIAM protection and prevention actions in a centralized location, and apply them across multiple profiles.
Go to Endpoints → Prevention → Global Exceptions.
Select Support Exceptions.
Import the JSON file you received from the Palo Alto NetworksPalo Alto Networks support team by either browsing for it in your files or by dragging and dropping the file on the page.
Click Save.
The new support exception is added to the Global Exceptions in your network and will be applied across all rules and policies.
When you view a Behavioral Threat alert in the Alerts table which you want to allow across your organization, you can create a global exception for that rule.
Right-click the BTP alert and select Create alert exception.
Review the alert data (platform and rule name) and then select from the following options as needed:
CGO hash Causality Group Owner (CGO) hash value.
CGO signer: CGO signer entity (for Windows and Mac only).
CGO process path: Directory path of the CGO process.
CGO command arguments: CGO command arguments. This option is available only if CGO process path is selected, and only if you are using Cortex XDR Agent 7.5 or later on your endpoints. After selecting this option, check the full path of each relevant command argument within quote marks. You can edit the displayed paths if needed.
From Exception Scope, select Global.
Click Create.
The relevant BTP exception is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X.
Note
You cannot edit global exceptions generated from a BTP security event.
When you view a Credential Gathering Protection alert in the Alerts table that you want to allow across your organization, you can create a global exception for that rule.
Right-click the Credential Gathering Protection alert and select Create alert exception.
Review the alert data (platform and module name) and then select from the following options as needed:
CGO hash: Causality Group Owner (CGO) hash value.
CGO signer: CGO signer entity (for Windows and Mac only).
CGO process path: Directory path of the CGO process.
CGO command arguments: CGO command arguments. This option is available only if CGO process path is selected, and only if you are using Cortex XDR agent 7.5 or later on your endpoints. After selecting this option, check the full path of each relevant command argument within quote marks. You can edit the displayed paths if needed.
From Exception Scope, select Global.
Click Create.
The relevant exception is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X.
Note
You cannot edit global exceptions generated from a Credential Gathering Protection security event.
When you view an Anti Webshell Protection alert in the Alerts table that you want to allow across your organization, you can create a global exception for that rule.
Right-click the Anti Webshell Protection alert and select Create alert exception.
Review the alert data (platform and module name) and then select from the following options as needed:
CGO hash: Causality Group Owner (CGO) hash value.
CGO signer: CGO signer entity (for Windows and Mac only).
CGO process path: Directory path of the CGO process.
CGO command arguments: CGO command arguments. This option is available only if CGO process path is selected, and only if you are using Cortex XDR Agent 7.5 or later on your endpoints. After selecting this option, check the full path of each relevant command argument within quote marks. You can edit the displayed paths if needed.
From Exception Scope, select Global.
Click Create.
The relevant exception is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X.
Note
You cannot edit global exceptions generated from an Anti Webshell Protection security event.
When you view in the Alerts table a Local Analysis alert that was triggered as a result of local analysis rules, you can create a global exception to allow the rules across your organization.
Right-click the alert and select Create alert exception.
Review the alert data (platform and rule name) and select Exception Scope:Global.
Click Add.
The relevant Local Analysis Rules exception is added to the Global Exceptions in your network and will be applied across all rules and policies. The exception allows all the rules that triggered the alert, and you cannot choose to allow only specific rules within the alert. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X. You cannot edit global exceptions generated from a local analysis security event.
With Advanced Analysis, Cortex XSIAM can provide a secondary validation of Cortex XDR agent alerts raised by exploit protection modules. To perform the additional analysis, Cortex XSIAM analyzes alert data sent by the Cortex XDR agent. If Advanced Analysis indicates an alert is benign, Cortex XSIAM can automatically create exceptions and distribute the updated security policy to your endpoints.
By enabling Cortex XSIAM to automatically create and distribute global exceptions you can minimize disruption for users when they subsequently encounter the same benign activity. To enable the automatic creation of Advanced Analysis Exceptions, configure the Advanced Analysis options in Settings → Configurations → General → Agent Configurations.
For each exception, Cortex XSIAM displays the affected platform, exception name, and the relevant alert ID for which Cortex XSIAM determined activity was benign. To drill down into the alert details, click the Generating Alert ID.
When you view in the Alerts table a Digital Signer Restriction alert for a digital signer you trust and want to allow from now on across your network, create a Global Exception for that digital signer directly from the alert.
Right-click the alert and select Create alert exception.
Review the alert data (Platform, signer, and alert ID) and select Exception Scope:Global.
Click Add.
The relevant digital signer exception is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X. You cannot edit global exceptions generated from a digital signer restriction security event.
When you view in the Alerts table a Suspicious Input Desensitization alert for a Java executable you want to allow from now on across your network, create a global exception for that executable directly from the alert of the security event that prevented it.
Right-click the alert and select Create alert exception.
Review the alert data (Platform, Process, Java executable, and alert ID) and select Exception Scope: Global.
Click Add.
The relevant digital signer exception is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X. You cannot edit global exceptions generated from a digital signer restriction security event.
When you view in the Alerts table a Local Threat Detected alert for a PHP file you want to allow from now on across your network, create a global exception for that file directly from the alert of the security event that prevented it.
Right-click the alert and select Create alert exception.
Review the alert data (Process, Path, and Hash) and select Exception Scope: Global.
Click Add.
The relevant PHP file is added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X. You cannot edit global exceptions generated from a local file threat examination exception restriction security event.
When you view a Gatekeeper Enhancement security alert in the Alerts table, you can create a global exception for this specific bundle or source-child combination only, while allowing Cortex XSIAM to continue enforcing the Gatekeeper Enhancement protection module on the source process running other child processes.
Right-click the alert and select Create alert exception.
Review the alert data (Platform, Source Process, Target Process, and Alert ID) and select Exception Scope: Global.
Click Add.
The relevant source and target processes are added to the Global Exceptions in your network and will be applied across all rules and policies. At any point, you can click the Generating Alert ID to return to the original alert from which the exception originated. To delete a specific global exception, select it and click X. You cannot edit global exceptions generated from a gatekeeper enhancement security event.
Select + Import/Export to Export your exceptions list and/or Import from File.
Note
The exported file is encoded in Base64 and cannot be edited.