Skip to main content

What is EDR (endpoint detection and response)?

EDR records process, file, and network activity on laptops and servers, detects malicious behavior, and lets responders isolate and fix hosts.

Glossary
Updated 2 min read

Definition

EDR

Also called Endpoint detection and response, Endpoint detection and threat response

EDR (endpoint detection and response) is security software that records activity on laptops, servers, and other endpoints, detects suspicious behavior in that telemetry, and gives responders tools to investigate and contain affected hosts.

How it works

An EDR agent runs on each endpoint and records system-level activity: processes starting and their parent processes, command lines, file writes, registry changes, and network connections. CrowdStrike quotes Gartner analyst Anton Chuvakin, who coined the term, defining EDR as a tool that "records and stores endpoint-system-level behaviors, uses various data analytics techniques to detect suspicious system behavior, provides contextual information, blocks malicious activity, and provides remediation suggestions to restore affected systems."

The agent streams this telemetry to a backend, where detection logic looks for malicious behavior rather than only known-bad files. When something fires, responders get a process tree and timeline, plus actions such as killing a process, quarantining a file, or isolating the host from the network. Microsoft notes that Defender for Endpoint's EDR is not meant to be an audit log of every operation: its sensor throttles high rates of repeated identical events.

Event types differ by vendor, but Microsoft's free Sysmon tool for Windows shows the kinds of telemetry an EDR sensor collects and why each matters:

Sysmon eventWhat it recordsTypical use
Event ID 1, process creationFull command line and parent processSuspicious child processes, encoded commands
Event ID 3, network connectionConnections linked to the process that made themUnexpected binaries reaching the internet
Event ID 10, process accessOne process opening anotherCredential theft from LSASS memory
Event ID 11, file createFiles created or overwrittenPayloads dropped in startup or temp folders
Event ID 22, DNS queryDNS lookups by processCommand-and-control domains

When evaluating an EDR, it's worth asking which of these it keeps, for how long, and whether the raw events can be exported to a SIEM or only the alerts.

Example

A user opens a document that launches PowerShell, which downloads a payload and writes a persistence entry. No file on its own matches a signature, but the EDR sees an office application spawning a script interpreter that reaches the internet, flags the chain, and lets the analyst isolate the laptop while they check whether the same payload ran anywhere else.

Why it matters for a SOC

Endpoints are where most intrusions execute code, so EDR alerts are often the highest-fidelity signal a SOC has, and EDR telemetry answers questions like "what ran, and what did it touch?" Its limit is scope: an EDR sees the hosts it's installed on, not identity providers, SaaS apps, or cloud control planes. Teams pair it with a SIEM or move to XDR to connect endpoint activity to the rest of an attack, and many outsource round-the-clock monitoring of it to an MDR provider.

Go deeper

FAQ

What is the difference between EDR and antivirus?
Antivirus mainly blocks known malicious files. EDR records endpoint behavior over time, detects suspicious activity that no single file signature reveals, and adds investigation and response actions such as isolating a host.

Sources

  1. What is EDR? Endpoint Detection & Response Defined | CrowdStrike · accessed November 16, 2026
  2. Overview of endpoint detection and response capabilities - Microsoft Defender for Endpoint · accessed November 16, 2026
  3. Sysmon - Sysinternals | Microsoft Learn · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo