
EDR vs XDR, or MDR: when the next step pays off
Most EDR vs XDR comparisons are about products, when the real question is about your own environment. If EDR is already running, there are two ways forward: connect more sources (XDR) or have more people watching (MDR). Which one you need is written in the alerts of the past few months.
XDR and MDR fix two different shortages: XDR a lack of connection between sources, MDR a lack of people to act on alerts.
Your last few incidents tell you which one you have: was the clue there but somewhere else, or was there an alert nobody saw in time?
Before switching, run a month’s trial on a defined group, with a simulated attack and an agreed definition of “better”.
First, check that your EDR does its job
What EDR is, and how it differs from antivirus, is covered in What is EDR, and is antivirus enough?. This piece starts where that one ends: EDR is in place, and the question is whether something should be added. Answer four questions about where you stand before any vendor meeting, because the answers decide which step makes sense.
- Coverage. On how many devices is the agent actually running, and which are missing: servers, Macs, laptops that have not been in the office for months?
- Volume. How many alerts came in over the last three months, and how many were genuine?
- Response time. How long between an alert and someone looking at it, during office hours and outside them?
- Outcome. Of the genuine alerts, how often did you find out afterwards where it started?
If coverage has gaps, neither next step is the answer. XDR and MDR both work on the data EDR supplies, and a gap in coverage does not shrink because there is a more expensive layer on top.
EDR vs XDR: the question XDR actually answers
EDR sees what happens on a single device. XDR puts that alongside other sources, usually email, accounts and sign-ins, and cloud applications, and turns separate alerts into one incident. So the question XDR answers is how do these signals fit together? Not: is this device infected?
Whether you have that question shows in your recent incidents. Go through them one by one and look at where the first clue was. Did it begin with a sign-in from an unknown location, a forwarding rule to an outside address, or an email someone opened anyway, and did you only see that later or not at all? Then the answer was in a source EDR does not read. If it started on the device every time, XDR adds little.
Two flavours appear in proposals. Native XDR connects one vendor’s products and works best when email, identity and endpoints already sit there. Open XDR also ingests other brands, but needs more set-up and upkeep of integrations. If you want to keep and search logs from any system, you are looking at a SIEM; the difference is in our piece on SIEM and SOAR.
MDR: when the shortage is people, not sources
MDR changes nothing about what is seen and everything about who looks at it. A team at the provider reviews alerts day and night, filters out false positives and steps in. It solves a different problem from XDR: not that signals are disconnected, but that nobody is there to act on them in time.
Put your situation on two axes and the choice usually becomes clear:
- Few sources, someone watching: EDR is still enough; invest in better rules and fewer false alarms.
- Few sources, nobody watching: MDR on your existing EDR. This is the most common situation in smaller organisations.
- Many sources, someone watching: XDR, with time for that person to investigate linked incidents properly.
- Many sources, nobody watching: MDR that takes in XDR sources. Start with the people; a better dashboard nobody reads helps no one.
“Someone watching” means evenings, weekends and that one colleague’s holiday too. If it is one person, the honest answer is usually “nobody”.
What to ask an XDR or MDR provider
Data sheets look alike. The differences are in details that only surface after signing:
- Which sources are in the licence? Endpoints are often included while email, cloud or extra logs sit in a higher tier. Ask for each source whether it is in.
- How long is data kept? If an attack is found weeks later, you want to look back to the start.
- Who manages the detection rules? Can you tune or disable a rule that raises a false alarm every day, and who carries the risk if that misses a real attack?
- How is response time measured? From the alert, or from when an analyst picks it up? That difference rarely makes the brochure.
- What happens when you leave? Can you take your data and incident history, and does the EDR agent keep working when the service ends?
Three pitfalls when making the move
Connecting everything at once. Plug in every source on day one and you get a flood of alerts in week one and a team ignoring them by week three. Add one source at a time, usually identity and email first, and tune the rules before the next one goes in.
Paying twice. An XDR or MDR package often includes its own agent or email scanner. Leave the old product running alongside and you pay twice while the two get in each other’s way. Agree beforehand what gets switched off, and when.
Assuming “response” means recovery. An MDR team isolates a laptop or blocks an account. After that, the device has to be rebuilt, the password reset and the user back at work. Agree who does that and how the MDR provider and your IT support reach each other, at night too.
How to test the step before you sign
A trial only tells you something if you know in advance what you are measuring. A set-up that works:
- Pick a defined group: one department or one site, with ordinary laptops and at least one server.
- Record the baseline: alert volume, share of false alarms and response time from the first section.
- Simulate an attack: run a harmless test combining a suspicious sign-in, a forwarding rule and a script on a laptop, and see whether it arrives as one incident and how fast someone calls.
- Judge on points agreed upfront: fewer false alarms, a quicker view of the cause, or an alert nobody saw before. Pick one or two, not all three.
If the result disappoints, that is an outcome too. Often it shows the gain was in better configured EDR, not in another layer.
Where our work stops
What we do. We map how your EDR works today, set up EDR and XDR, connect sources and tune the rules, and follow up alerts within the agreed hours as part of our support or of managed security. If you work with an MDR provider, we make sure isolation and recovery join up.
What we don’t do. We don’t make security software: how well a product detects is the vendor’s work, and no product stops everything. We don’t carry out forensic investigations that must stand as evidence or that an insurer or regulator requires; a specialist firm does that, and we supply the data. Whether an incident must be reported to the ICO or another regulator is for you to decide with your lawyer and insurer.
Questions we get about this
The five that come up once EDR is running.
What is the difference between EDR and XDR?
EDR looks at what happens on laptops and servers. XDR puts that data alongside other sources, such as email, accounts and cloud applications, and turns separate alerts into one incident. XDR builds on EDR rather than replacing it.
Is XDR better than EDR?
Only if you see attacks that start outside the device, such as a compromised account or a mailbox forwarding rule, and someone is there to investigate linked incidents. If everything starts on the device and nobody is watching, XDR mainly gives you a bigger view of the same problem.
Do I need XDR if I have MDR?
Not necessarily. MDR is a service with people who act on alerts, and it runs on EDR as well as XDR. For most smaller organisations, MDR on existing EDR is the first step, and extra sources only come in once incidents are shown to start there.
What is the difference between native and open XDR?
Native XDR connects one vendor’s products and works best when email, identity and endpoints already sit with that vendor. Open XDR also takes in other brands’ sources, but needs more set-up and maintenance of the integrations.
Do you also do forensic investigations or regulator reports?
No. We isolate, recover and get people working again, and we supply the data from the console. A forensic investigation that must stand as evidence is done by a specialist firm, and whether an incident must be reported is for you to decide with your lawyer and insurer.
Further reading
The groundwork underneath, and who is watching.
Shall we go through last quarter’s alerts together?
Tell us which EDR product you use and who reads the alerts now. We will help you see whether the gap is in the sources or in the follow-up, and what the smallest step is that closes it.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.