An endpoint has been isolated via the Cortex XDR console due to a suspected ransomware outbreak. The incident responder needs to allow one specific management server to communicate with this isolated endpoint for forensics collection. What is the correct procedure?
Trap 1: Delete the endpoint from the Cortex XDR asset list and re-add it.
Deleting the asset does not remove network isolation enforced by the active agent driver.
Trap 2: Modify the endpoint routing table locally via a startup script.
Network isolation blocks packets before routing logic takes effect on the host.
Trap 3: Temporarily disable the Host Firewall module on the endpoint via…
Host firewall is separate from network isolation, which operates at the driver level to drop all non-excepted traffic.
- A
Configure IP-based isolation exceptions in the Cortex XDR profile to allow traffic from the designated forensic server IP.
Isolation exceptions allow targeted connectivity to specific IPs while keeping the rest of the network cut off.
- B
Delete the endpoint from the Cortex XDR asset list and re-add it.
Why wrong: Deleting the asset does not remove network isolation enforced by the active agent driver.
- C
Modify the endpoint routing table locally via a startup script.
Why wrong: Network isolation blocks packets before routing logic takes effect on the host.
- D
Temporarily disable the Host Firewall module on the endpoint via the CLI.
Why wrong: Host firewall is separate from network isolation, which operates at the driver level to drop all non-excepted traffic.