Skip to content
atlas

Endpoint detection and response (EDR)

Also known as: EDR

Software on each computer and phone that watches for signs of an attack and can stop it on the spot.

Draft - this entry has not been reviewed yet.

Formal

A tool installed on every endpoint that records what programs and users do, flags behaviour that matches known attack patterns, and lets defenders cut the device off, end a process or undo changes from one central screen.

In plain English

Like a guard posted inside every room of a building rather than only at the front door - they notice odd behaviour and can lock the room at once.

In practice

A laptop in a pension fund's customer department suddenly starts locking hundreds of files; the EDR tool spots the pattern, stops the process and cuts the laptop off the network before the IT operations manager has even seen the alarm.

Why it matters

Attackers who slip past the outer defences still have to act on some device, so watching every device closely is often the last real chance to catch them early.

Technical deep dive

The category was named in 2013 by Gartner analyst Anton Chuvakin as "endpoint threat detection and response", later shortened to EDR. Its defining shift from classic antivirus (now usually called EPP, endpoint protection platform) is continuous telemetry recording rather than file scanning alone. On Windows an EDR sensor typically combines a kernel-mode driver registering process, thread, image-load and registry callbacks (PsSetCreateProcessNotifyRoutineEx and related APIs), a file-system minifilter, network filtering, Event Tracing for Windows providers including the Microsoft-Windows-Threat-Intelligence provider, and the Antimalware Scan Interface (AMSI) for script content. On macOS and Linux the equivalents are Apple's Endpoint Security framework and eBPF or audit subsystems respectively.

Telemetry - process trees with command lines, parent/child relationships, network connections, file and registry writes, module loads - is streamed to a cloud or on-premises backend. Detection combines local machine-learning classifiers, behavioural rules (for example Office spawning a PowerShell process that downloads and executes content), indicators of compromise and analytics mapped to MITRE ATT&CK techniques. Response actions include network containment (the host can reach only the EDR backend), process kill, file quarantine, remote shell for live forensics and, on some platforms, rollback of changes. Retained telemetry enables threat hunting and retrospective queries when a new indicator is published.

EDR has well-known limits. Attackers disable or blind sensors through "bring your own vulnerable driver" (BYOVD) techniques that load a legitimately signed but vulnerable kernel driver to kill protected processes, through unhooking of user-mode hooks, or by operating from assets without a sensor - hypervisors, network appliances, OT and IoT devices, unmanaged machines. Tamper protection and alerting on sensor silence are therefore essential. Kernel presence is also an availability risk: on 19 July 2024 a faulty content update to CrowdStrike Falcon crashed roughly 8.5 million Windows machines, prompting Microsoft to work with vendors on moving security functionality out of the kernel.

Neighbouring terms: XDR extends the same detection-and-response model across email, identity, cloud and network sources; MDR is a managed service in which an external SOC operates the EDR; a SIEM ingests EDR alerts for correlation with other logs but is not a replacement for the sensor. EDR supports CIS Controls v8 Control 10 (Malware Defenses) and ISO/IEC 27002:2022 controls 8.7 (protection against malware) and 8.16 (monitoring activities). An EDR deployment is only as good as its coverage and triage: the metric that matters is the share of endpoints with a healthy sensor and the time from alert to containment.

What to learn first

Everything this builds on, foundations first.

  1. Operating system
  2. →Endpoint
  3. →Endpoint detection and response (EDR)

Relationships

Requires
Endpoint

Sources & further reading

Standards & official texts

  • CIS Controls v8 - Control 10 (Malware Defenses) and Control 13 (Network Monitoring and Defense) · Center for Internet Security
  • NIST SP 800-83 Rev. 1 - Guide to Malware Incident Prevention and Handling · NIST

Where this data comes from

This entry was drafted by an AI from the sources above and has not yet been checked by a person. Treat it as a starting point, and check anything important against the sources.

See the review queueSuggest a correction on GitHubThis term as JSON

Mentioned in

Check yourself

Loading…

Atlas is in beta.