> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/xygeni-shield/network-isolation.md).

# Network isolation

When a machine may be compromised, your security team can **isolate** it from the Xygeni dashboard: all its network traffic is blocked, except Shield's own connection to Xygeni. This contains the threat (for example, it cuts a malware's connection to its control server) while the machine can still be released remotely.

Network isolation is available on centrally managed machines (see [Activating Shield](https://docs.xygeni.io/xygeni-products/xygeni-shield/activating.md#what-your-subscription-enables)).

### Isolating and releasing a machine

In **Inventory → Endpoints**, open the machine and use its **Actions** menu:

* **Isolate endpoint**: after confirming, the machine shows **Isolating…** and becomes **Isolated**, usually within a minute.
* **Release endpoint**: restores the network, also usually within a minute.
* **Generate manual release code**: creates a single-use code, valid for 24 hours, that lets the user of the machine release it locally (see below).

A machine can also be isolated automatically when its configuration has **Paranoid mode** on and the machine raises a critical alert (see [Managing Shield from the dashboard](https://docs.xygeni.io/xygeni-products/xygeni-shield/dashboard.md#paranoid-mode)).

### What the user of an isolated machine sees

* The tray icon shows a **red padlock**, and `xygeni-fw isolate status` reports that the machine is isolated.
* **Linux**: web requests (browsers, `curl`, package managers) get an error page `503 Service Unavailable` that says that the endpoint is isolated by the security team. Any other connection is dropped.
* **Windows**: connections are refused by the Windows firewall, so tools report a connection error.
* Connections open before the isolation stop working too.
* The machine keeps resolving names and its system services keep working, so the operating system does not break. Shield itself keeps reporting to Xygeni, so the machine can be released remotely at any time.

### Releasing a machine with a manual code

If the machine cannot be released from the dashboard (for example, the release does not arrive), your security team can generate a manual release code and send it to you by phone, chat or ticket. Run:

```bash
xygeni-fw isolate off --code XXXX-XXXX
```

Shield checks the code with Xygeni and restores the network within seconds. Each code works only once.

{% hint style="info" %}
Isolation can only be started from the dashboard, and only lifted from the dashboard or with a code your security team generated. Nobody on the machine can turn it off on their own.
{% endhint %}

### Requirements

* **Linux**: `nftables`, installed by default on Ubuntu 22.04+ and Debian 12+.
* **Windows**: the Windows Defender Firewall service must be running.


---

# 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://docs.xygeni.io/xygeni-products/xygeni-shield/network-isolation.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.
