> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/security-operations-and-response/remediation-actions.md).

# Remediation actions

Use Cortex XDR remediation actions to restore files, scan endpoints, isolate devices, and automate recovery workflows.

After you contain a threat, use the following actions to clean up and recover.

| Action                           | Description                                                                                                                                                                                                                                                                                                     |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Restore quarantined files        | Restore a file, or all files with the same SHA256, from **Action Center** → **File Quarantine**. See [Manage quarantined files](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-files/manage-quarantined-files). |
| Scan for malware                 | Run an on-demand scan. See [Scan an endpoint for malware](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/investigate-endpoints/scan-an-endpoint-for-malware).                                                               |
| Run scripts                      | Run a predefined or custom script on one or many endpoints.                                                                                                                                                                                                                                                     |
| Un-isolate                       | Restore network access after remediation.                                                                                                                                                                                                                                                                       |
| Remediation suggestions          | Where supported, review suggested actions to delete, restore, or rename files, revert registry values, and terminate processes or causality chains.                                                                                                                                                             |
| Block indicators                 | Add hashes to the block list. Add IP addresses and domains to an external dynamic list (EDL) for your firewalls.                                                                                                                                                                                                |
| Identity and third-party actions | Disable users, reset passwords, block senders, or open tickets using Marketplace integrations and playbooks.                                                                                                                                                                                                    |

### Automated remediation and failure handling

When you run remediation from a playbook, configure error handling on each task: retries, **Stop**, **Continue**, or **Continue on error path**. Use an error path to run undo steps, notify an analyst, or open a ticket. Actions on external systems through APIs aren't rolled back automatically, so build the reverse action into your error path where needed. See [Configure script error handling in a playbook](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/playbooks/build-your-playbook/configure-script-error-handling-in-a-playbook).

Who can run each action depends on the user's response permissions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr/insights-and-tips-cortex-xdr/security-operations-and-response/remediation-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.