> 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/endpoint-and-cortex-xdr-agent-management/cortex-xdr-agent-offline-protection.md).

# Cortex XDR agent offline protection

Learn how the Cortex XDR agent protects offline endpoints and which functions resume after reconnection to Cortex XDR.

Most Cortex XDR agent prevention capabilities run locally on the endpoint, so the endpoint stays protected when it is disconnected from Cortex XDR, for example when a laptop is offline or traveling. Capabilities that depend on cloud services or the tenant resume when the Cortex XDR agent reconnects.

| Capability                                                                  | Offline? | Notes                                                                                                                         |
| --------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Local analysis (machine learning and static rules)                          | Yes      | Issues a local verdict for unknown files without connectivity.                                                                |
| WildFire verdicts                                                           | Partly   | Cached verdicts are used locally. New cloud verdicts and WildFire sandbox analysis need connectivity.                         |
| Behavioral threat protection                                                | Yes      | Runs on the endpoint and stops malicious causality chains with agent-side actions.                                            |
| Exploit protection, anti-ransomware, and credential-gathering protection    | Yes      | Enforced by the agent according to the last policy it received.                                                               |
| Endpoint hardening (host firewall, device control, disk encryption)         | Yes      | Last policy received is enforced. Location-based host firewall rules re-evaluate the network location after a network change. |
| Policy and content updates                                                  | No       | Received at the next check-in.                                                                                                |
| EDR data and issues in the tenant                                           | No       | Data reaches Cortex XDR only when the Cortex XDR agent reconnects.                                                            |
| Response actions (isolation, Live Terminal, malware scan, script execution) | No       | Delivered to the Cortex XDR agent at its next heartbeat.                                                                      |

For details of each module, see [Endpoint protection capabilities](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/endpoint-protection/endpoint-protection-capabilities) and [File analysis and protection flow](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/endpoint-protection/file-analysis-and-protection-flow).

{% hint style="info" %}
To collect forensic evidence from a machine that has no network connection or no Cortex XDR agent, use offline triage collection.
{% endhint %}


---

# 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/endpoint-and-cortex-xdr-agent-management/cortex-xdr-agent-offline-protection.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.