Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

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.

To collect forensic evidence from a machine that has no network connection or no Cortex XDR agent, use offline triage collection.

Last updated

Was this helpful?