> 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/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/response-actions/isolate-an-endpoint.md).

# Isolate an endpoint

Isolate an endpoint to contain potential threats in Cortex XDR.

Isolating an endpoint contains a compromised device to block lateral movement across your network.

When an endpoint is isolated:

* Network traffic is restricted: All inbound and outbound connectivity stops except for communication with Cortex XDR.
* Status updates: Cortex XDR marks the endpoint status as Isolated once the agent applies the action.
* Upgrades are blocked: Agent upgrades are disabled to ensure the endpoint remains safely isolated.

When isolated, the endpoint will still allow:

* DHCP and HTTPS outgoing traffic for the root user
* DNS traffic

{% hint style="info" %}
IP-based file storage protocol traffic will also be blocked. This may affect endpoint functionality if the endpoint uses such mounts.
{% endhint %}

### Network isolation requirements

Network isolation is supported for endpoints that meet the following requirements:

| Operating System | Prerequisites                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Windows          | <ul><li>Agent 6.0 or later.</li><li>(VDI) Network isolation allow list in the agent settings profile is configured to ensure VDI sessions remain uninterrupted. For more information, see <a href="https://cortex-docs.paloaltonetworks.com/cortex-xdr/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-agent-settings-profiles.md">Set up agent settings profiles</a>.</li></ul> |
| macOS            | <ul><li>Agent 7.3 or later.</li><li>macOS 10.15.4 or later.</li><li>Cortex XDR Network extension is enabled on the endpoint.</li></ul><p>Network isolation on Mac endpoints does not terminate active connections that were initiated before the agent was installed on the endpoint.</p>                                                                                                                                                                           |
| Linux            | <ul><li>iptables and ip6tables.</li><li>Agent 7.7 or later.</li><li><p>Linux kernel with the following enabled:</p><ul><li><code>CONFIG\_NETFILTER</code></li><li><code>CONFIG\_IP\_NF\_IPTABLES</code></li><li><code>CONFIG\_IP\_NF\_MATCH\_OWNER</code></li></ul></li><li>Network isolation allow list configured in the agent settings profile.</li></ul><p>Network isolation on Linux endpoints is based on the defined IP addresses and ports.</p>             |
| iOS              | Supported by the Cortex XDR agent on iOS 9.1 or later. This feature is only available on supervised iOS devices where the Network Shield is enabled.                                                                                                                                                                                                                                                                                                                |

### Isolate an endpoint in Cortex XDR

1. Go to I**nvestigation & Response → Response → Action Center**, click **Create Action,** and select **Isolate**.\
   You can also start from **Action Center → Isolated Endpoints** (**Create action**), or go to **Inventory → Endpoints → All Endpoints**, right-click one or more endpoints, and select **Security operations → Isolate endpoint**.
2. Enter a **Comment** to provide additional background or other information that explains why you isolated the endpoint.

   After you isolate an endpoint, the **Isolation Comment** appears on the **Action Center → Isolated Endpoints** page. To change it, right-click the endpoint and select **Edit isolation comment**.
3. Click **Next**.
4. Select the target endpoint that you want to isolate from your network.\
   If needed, filter the list of endpoints.
5. Click **Next**.
6. Review the action summary and click **Done** when finished.

   In the next heartbeat, the agent will receive the isolation request from Cortex XDR.
7. To track the status, go to **Action Center**. In the side panel, under **Applied Actions**, select **Isolated Endpoints**.\
   If the endpoint hasn't been isolated yet (Pending Isolation status), you can cancel the action. Go to **Action Center → All Actions**, right-click the isolate action, and select **Cancel isolate**.

{% hint style="info" %}
If file system operations become unresponsive during isolation, such as being unable to list folder content, unmount the mounted network shares.
{% endhint %}

### Cancel endpoint isolation in Cortex XSIAM

After you remediate the endpoint, cancel endpoint isolation to resume normal communication.

1. Do one of the following:
   1. Go to I**nvestigation & Response → Response → Action Center → Isolated Endpoints**, right-click the endpoint, and select **Cancel endpoint isolation.**
   2. In **Inventory → Endpoints → All Endpoints**, right-click the endpoint and select **Security operations → Cancel endpoint isolation**.

The endpoint shows a pending status until the agent receives the request in the next heartbeat. After the agent carries out the request, the endpoint no longer shows the **Isolated** status.


---

# 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/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/response-actions/isolate-an-endpoint.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.
