Glossary/Detection Engineering/Managed Detection and Response (MDR)

What Is MDR (Managed Detection and Response)?

Managed detection and response (MDR) is a cybersecurity service that combines detection technology with human analysts to monitor, hunt, investigate, and respond to threats on a customer's behalf around the clock.

A mid-sized company buys a top-tier endpoint detection tool. It is well configured and it fires accurate alerts. Then a critical detection lands at 2:14 a.m. on a Sunday, and nobody sees it until Monday at 9. By then the attacker has moved from the first host to a domain controller. The tool did its job. The problem was that the alert needed a human, and there was no human awake to read it.

That gap, between a tool that detects and a team that responds around the clock, is the gap managed detection and response was built to close. MDR is not a product you install. It is a service: a provider runs detection technology on your environment and staffs it with analysts who monitor, hunt, investigate, and respond on your behalf, every hour of every day.

This guide covers what MDR is, how it works as a five-step process, what it actually delivers, and how it differs from the things people confuse it with: EDR, XDR, MXDR, an MSSP, and a managed SIEM. It is written for blue teamers and security leaders deciding whether to run detection in-house or hand part of it to a provider.

What is managed detection and response?

Managed detection and response is a cybersecurity service that combines detection technology with human expertise to identify and limit the impact of threats through monitoring, threat hunting, investigation, and response. The provider supplies the tooling, the security operations center, and the analysts. You supply the environment to defend. Gartner describes the category as remotely delivered, human-led, turnkey modern SOC functions whose end goal is threat disruption and containment.

Two words in that definition carry the weight. Managed means the provider operates it, so you consume detection and response as a service rather than building and staffing it yourself. Human-led means analysts, not just software, make the calls. Modern MDR leans heavily on automation and AI to triage volume, but the model is built on people reading the alerts the machine surfaces, deciding what is real, and acting. The technology scales the humans; it does not replace them.

The reason the service exists is staffing, not technology. Plenty of organizations can buy a good detection tool. Far fewer can hire, train, and retain enough skilled analysts to watch it 24/7, build detection content, and run incident response. A security operations center that never sleeps is expensive and hard to staff. MDR rents you one.

How MDR works

MDR · the five-step process
From raw telemetry to a contained threat
The provider runs all five steps continuously, 24/7. The value is doing them fast.
01 · AUTOMATION
Prioritization
Filter raw events down to the alerts that matter. Suppress noise.
02 · HUMAN-LED
Threat hunting
Experts hunt the evasive threats that automated detection misses.
03 · HUMAN-LED
Investigation
Enrich each alert with context until it has a verdict.
04 · RESPONSE
Guided response
Containment and remediation steps that stop the spread.
05 · RESPONSE
Remediation
Restore the environment toward its pre-attack state.
Why it matters · the window IBM put the average breach lifecycle at 258 days. A staffed loop is built to compress that window from months toward minutes.

MDR turns raw telemetry into contained threats through a consistent five-step process. The provider runs all five; the value is in doing them continuously and fast.

  1. Prioritization. Detection tooling and automation filter a flood of raw events down to the alerts that matter, suppressing noise so analysts spend their attention on signal rather than drowning in false positives.
  2. Threat hunting. Human experts proactively search for the evasive threats that automated detection misses, using hypotheses and threat intelligence to find activity that never tripped a rule.
  3. Investigation. Analysts enrich each alert with context, what host, what user, what process, what came before and after, so a lone signal becomes an understood event with a verdict.
  4. Guided response. The provider tells you exactly what to do, or does it for you: the containment and remediation steps that stop the threat from spreading.
  5. Remediation. The environment is restored toward its pre-attack state, removing the attacker's artifacts and closing the door they came through.

The point of running this as a managed service is speed. IBM's Cost of a Data Breach 2024 report put the average breach lifecycle at 258 days from identification to containment, a multi-month window in which an attacker operates freely. A staffed detection-and-response loop is built to compress that window from months toward minutes, because the difference between catching an intrusion in the prioritization step and catching it after exfiltration is the difference between an incident and a breach.

What MDR delivers

Strip away the marketing and an MDR engagement delivers a short list of concrete things in-house teams struggle to provide on their own.

  • 24/7 coverage. A staffed SOC watching your environment on nights, weekends, and holidays, which is precisely when attackers prefer to operate because they know defenders are thin.
  • Human-led detection and response. Analysts who triage, investigate, and act, not just an alert queue that piles up until someone logs in.
  • Proactive threat hunting. Skilled hunters looking for the intrusions that slipped past automated detection, before those become incidents.
  • Current threat intelligence. Detection informed by what adversaries are doing right now, applied across every customer the provider defends.
  • Faster, expert response. A team that has handled the attack you are seeing many times before, so containment is practiced rather than improvised.

The throughline is that MDR sells operational capacity, not a dashboard. The deliverable is that something is watching and someone is acting, continuously, by people who do this for a living.

MDR vs. EDR vs. XDR vs. MXDR vs. MSSP

MDR is most confused with the tools and services that sit next to it. The cleanest way to separate them is to ask, for each one, is this a tool or a service, and what does it watch.

Endpoint detection and response is a tool that watches endpoints. EDR gives deep host visibility and fires high-quality alerts, but it does not come with people to read those alerts at 2 a.m. MDR is frequently the service that operates EDR on your behalf.

XDR (extended detection and response) is also a tool, a platform that correlates telemetry across endpoint, network, identity, and cloud into one detection layer. It widens what is watched beyond the endpoint, but it is still software that needs operators.

MXDR (managed XDR) is the service wrapped around XDR: a provider runs an XDR platform and staffs it. It is essentially MDR built on a broad, multi-source detection platform rather than a narrower one, and is often positioned as the most comprehensive tier of managed detection.

MSSP (managed security service provider) is the older service model. An MSSP broadly manages security devices and monitors them, but classic MSSPs alert you to a problem and stop there; active investigation and response are not the core offering. MDR's defining difference from an MSSP is that response is built in, not handed back to you.

NameTool or serviceWatchesDefining trait
EDRToolEndpointsDeep host detection, no operators included
XDRToolEndpoint, network, identity, cloudCorrelated multi-source detection platform
MDRServiceWhatever the provider's tooling coversHuman-led 24/7 detection and response
MXDRServiceBroad, via an XDR platformMDR delivered on top of XDR
MSSPServiceManaged security devicesBroad management and alerting, response not core

The takeaway: EDR and XDR are tools you can buy and still have to operate. MDR, MXDR, and MSSP are services that operate something for you. MDR's specific promise, against an MSSP, is that it does not just tell you a threat exists; it works to stop it.

MDR vs. managed SIEM

One more comparison worth drawing, because it trips people up. A managed SIEM service operates your security information and event management (SIEM) platform: it ingests logs, runs correlation rules, and maintains the platform. That is valuable, but a managed SIEM is centered on the log platform and its rules. MDR is centered on the outcome, detecting and responding to threats, using whatever telemetry and tooling get there, often including a SIEM as one input. A managed SIEM keeps the engine running; MDR is accountable for catching the attacker.

What to look for in an MDR provider

Choosing a provider is mostly about confirming the service is what it claims to be. Five questions separate real MDR from rebadged alerting.

  1. What is the analysts' expertise, and will they transfer knowledge? You want experienced people and a relationship that makes your own team better over time, not a black box.
  2. Can they access your data in real time and integrate with your stack? Response speed depends on the provider seeing your telemetry as it happens and acting through your existing tools.
  3. How current is their threat intelligence? Detection is only as good as its picture of what adversaries are doing now, including the geopolitical and industry-specific context that shapes targeting.
  4. What are the communication and handoff protocols? When an incident hits at 3 a.m., you need to know exactly how they reach you, what they will do without waiting, and how the handback works.
  5. Is coverage genuinely 24/7? "Around the clock" must mean staffed analysts overnight and on weekends, not an automated queue that a person reviews the next business day.

The honest summary: the only thing harder to verify than detection quality is response quality, so press hardest on what the provider actually does when something fires, and how fast.

How to build the skills behind MDR

If you want to understand what an MDR analyst does, build the detection-and-response loop yourself on a smaller scale.

  1. Learn alert triage. Practice taking a raw alert and deciding fast whether it is benign, suspicious, or malicious. That judgment is the core of the prioritization step.
  2. Practice investigation. Take a single detection and reconstruct the full story around it: the host, the user, the process tree, and the timeline.
  3. Run a response playbook. Learn the containment and remediation steps for common intrusions so response is a procedure, not a panic.
  4. Develop a hunting habit. Form a hypothesis about how an attacker might be hiding and go look for it in real telemetry, which is exactly what threat hunting inside an MDR service does.

Frequently asked questions

What is managed detection and response (MDR)?

MDR is a cybersecurity service that combines detection technology with human security analysts to monitor, hunt, investigate, and respond to threats on a customer's behalf, around the clock. The provider supplies the tooling and a staffed security operations center, so the customer consumes detection and response as a managed, human-led service rather than building and staffing it in-house.

What is the difference between MDR and EDR?

EDR (endpoint detection and response) is a tool that monitors endpoints and produces alerts. MDR is a service that operates detection tooling, often including EDR, and adds the human analysts, processes, and 24/7 staffing to investigate and respond to what it finds. In short, EDR detects, and MDR is the team and operation that acts on the detections. Many organizations buy MDR specifically because they own an EDR tool but cannot staff it around the clock.

What is the difference between MDR and an MSSP?

A managed security service provider (MSSP) broadly manages and monitors security devices and typically alerts the customer when something looks wrong, leaving the investigation and response to them. MDR is built around active detection and response: it does not just notify you of a threat, it investigates and works to contain it. The defining difference is that response is a core part of MDR and is generally not core to a classic MSSP.

What is the difference between MDR, XDR, and MXDR?

XDR is a tool, a platform that correlates telemetry across endpoint, network, identity, and cloud. MDR is a service that operates detection tooling with human analysts. MXDR (managed XDR) is the service version of XDR: a provider runs an XDR platform and staffs it, which makes MXDR essentially MDR delivered on top of a broad, multi-source detection platform and often positioned as the most comprehensive managed tier.

How does MDR reduce the time to detect and respond to threats?

MDR runs a continuous five-step loop, prioritization, threat hunting, investigation, guided response, and remediation, staffed 24/7. Because analysts are always watching and the process is practiced, detections are triaged and acted on in near real time instead of sitting in a queue. IBM's Cost of a Data Breach 2024 report put the average breach lifecycle at 258 days; a staffed detection-and-response operation is designed to compress that window dramatically.

Do I still need an in-house security team if I use MDR?

Usually yes, but a smaller and more focused one. MDR covers continuous monitoring, hunting, and response, which frees your internal team from staffing overnight shifts. You still need people to own the relationship, handle the response actions the provider hands off, manage the broader security program, and apply the context only an insider has. The best MDR engagements make an in-house team more effective rather than replacing it.

Frequently asked questions

What is managed detection and response (MDR)?

<p>MDR is a cybersecurity service that combines detection technology with human security analysts to monitor, hunt, investigate, and respond to threats on a customer's behalf, around the clock. The provider supplies the tooling and a staffed security operations center, so the customer consumes detection and response as a managed, human-led service rather than building and staffing it in-house.</p>

What is the difference between MDR and EDR?

<p>EDR (endpoint detection and response) is a tool that monitors endpoints and produces alerts. MDR is a service that operates detection tooling, often including EDR, and adds the human analysts, processes, and 24/7 staffing to investigate and respond to what it finds. In short, EDR detects, and MDR is the team and operation that acts on the detections. Many organizations buy MDR specifically because they own an EDR tool but cannot staff it around the clock.</p>

What is the difference between MDR and an MSSP?

<p>A managed security service provider (MSSP) broadly manages and monitors security devices and typically alerts the customer when something looks wrong, leaving the investigation and response to them. MDR is built around active detection and response: it does not just notify you of a threat, it investigates and works to contain it. The defining difference is that response is a core part of MDR and is generally not core to a classic MSSP.</p>

What is the difference between MDR, XDR, and MXDR?

<p>XDR is a tool, a platform that correlates telemetry across endpoint, network, identity, and cloud. MDR is a service that operates detection tooling with human analysts. MXDR (managed XDR) is the service version of XDR: a provider runs an XDR platform and staffs it, which makes MXDR essentially MDR delivered on top of a broad, multi-source detection platform and often positioned as the most comprehensive managed tier.</p>

How does MDR reduce the time to detect and respond to threats?

<p>MDR runs a continuous five-step loop, prioritization, threat hunting, investigation, guided response, and remediation, staffed 24/7. Because analysts are always watching and the process is practiced, detections are triaged and acted on in near real time instead of sitting in a queue. IBM's Cost of a Data Breach 2024 report put the average breach lifecycle at 258 days; a staffed detection-and-response operation is designed to compress that window dramatically.</p>

Do I still need an in-house security team if I use MDR?

<p>Usually yes, but a smaller and more focused one. MDR covers continuous monitoring, hunting, and response, which frees your internal team from staffing overnight shifts. You still need people to own the relationship, handle the response actions the provider hands off, manage the broader security program, and apply the context only an insider has. The best MDR engagements make an in-house team more effective rather than replacing it.</p>

Practice track
SOC Analyst Tier 1
Build your foundational skills to monitor, detect, and escalate security alerts. This track includes essential tools, basic log analysis, and introductory incident response labs.
Browse SOC Analyst Tier 1 Labs โ†’