EDR — Endpoint Detection and Response
- Software on laptops, servers, and workstations.
- Records process, file, and network activity on the device.
- Detects malicious behaviour and can isolate the host.
Concepts
These acronyms get used loosely and are easy to mix up. The quickest way to keep them straight: EDR is a tool, MDR is a service, and XDR is an approach to joining tools together. This guide unpacks each and shows how they sit around a SIEM.
Definitions
The obvious question
This is where people get stuck, because the categories overlap. A useful way to think about it: a SIEM is broad and source-agnostic — it will ingest almost anything and is strong at long-term storage, compliance, and custom detections. XDR is narrower and more opinionated, focused on tightly correlating a curated set of security signals out of the box.
In practice many SOCs run both: EDR on the endpoints, a SIEM like Splunk as the central backbone, and either an XDR layer or a SOAR tool to tie response together. They are not competitors so much as parts of a stack. For the backbone, see the SIEM architecture guide; for response, see SOAR.
For the analyst
As an analyst you will likely pivot between consoles: an alert in the SIEM points you to the EDR for endpoint detail, which you correlate back against network and identity data. Knowing which tool answers which question — and not expecting one tool to do everything — is a real day-one skill. The acronym wars matter far less than being able to follow the evidence wherever it lives.