Isolate host
Since v3.45.0 you can cut a Windows, Linux or macOS computer off the network when you suspect malware. It then talks only to Control: no internet, no other computers in the local network. Remote control, shell, files, processes and event viewer keep working, as does Wazuh (same server). You can investigate an infected machine without it leaking data or infecting others.
Isolating
Host detail panel > … > Isolate host …. A reason is required, the host name is typed to confirm. Options:
| Option | Effect |
|---|---|
| Notice to signed-in users | shown on screen (Windows: msg.exe, Linux: wall), prefilled with a default text |
| Allow Defender updates (Windows) | Defender (MsMpEng, MpCmdRun, Defender for Endpoint) may reach out via HTTPS, plus DNS. Signatures come directly from Microsoft (MMPC), the update is triggered when isolating. Windows Update itself stays blocked. Default: off |
On the computer:
- Forensic snapshot – running processes with command line, network connections with process, autostarts, non-Microsoft services and scheduled tasks, recent logons, Defender detections. See Show forensics in the panel.
- Dead man's switch – a scheduled task lifts the isolation by itself after 10 minutes.
- Lock down – only the Control address (from
server_urlin the agent config, plus the proxy if set) and DHCP stay allowed. The address is pinned in the hosts file, DNS is no longer needed.- Windows: Windows Firewall block rules (group DATAZONE Isolation), which take precedence over all allow rules.
- Linux: nftables table
dz_isolation(else iptables chainsDZISO_*), also blocks forwarded traffic (containers). - macOS: pf anchor
com.apple/dz-isolation.
- Confirmation – when the agent reports back through the isolated connection, Control disarms the dead man's switch. If it does not come back, the computer is reachable normally again after 10 minutes and the isolation shows rolled back.
Existing connections may persist until they are re-established. For a clean cut, reboot the computer via Control – the isolation survives the reboot.
Releasing
Detail panel > … > Lift isolation (release). Rules, hosts entries and the dead man's switch are removed, firewall profiles are restored. Signed-in users see a short notice.
Display and alerts
- Isolated hosts are marked red in lists and the panel and listed at the top of the Overview.
- Isolating and releasing are sent as alert / all-clear to the notification channels.
- Every step is in the audit log.
Automatically on a critical check
The check editor has Isolate host on critical result (off by default), e.g. for Defender without detections. A host is isolated only once; releasing is manual.
From v3.48.2, Control isolates only after the check was critical as many times in a row as set under Alert only after … failures in a row. A timeout or a script that does not start never counts as a reason to isolate.
Permissions
Permission Isolate host per module (e.g. windows.isolate). Administrators always may. Not via MCP tokens.