- Home
- Knowledge Hub
- What is MDR and how do MSPs deliver it?
What is MDR and how do MSPs deliver it?
By Oliver Spence, CEO, CybaVerse. Last reviewed
Managed detection and response (MDR) is a service in which analysts monitor an organisation's security signals 24/7, investigate suspicious activity and contain real attacks quickly. MSPs deliver MDR by partnering with an MDR platform that includes a SOC, agreeing pre-approved response actions with each client and owning onboarding, communication and recovery.
This guide is part of the CybaVerse Knowledge Hub.
What does MDR actually do?
MDR combines technology and people. Tools collect events from endpoints, identities, cloud services and firewalls, detection rules raise alerts, and analysts decide which alerts are real. When an attack is confirmed, the service contains it, for example by isolating a device or disabling an account, then supports the follow-on response.
The NIST incident response guidance describes the same cycle of detection, analysis, containment and recovery. MDR exists because most organisations cannot staff that cycle every hour of every week. Attackers do not keep office hours, so detection that only works from nine to five leaves the riskiest hours uncovered.
How is MDR different from EDR, SIEM and a SOC?
EDR is a tool on each device. A SIEM is a tool that collects and searches logs. A SOC is the team that watches them. MDR is the outcome: a managed service that uses EDR, SIEM data and a staffed SOC to detect and respond for you, around the clock.
| Term | What it is | Who acts on it |
|---|---|---|
| EDR | Endpoint detection and response tool | Whoever watches its alerts |
| SIEM | Log collection, search and detection | Whoever watches its alerts |
| SOC | A team of security analysts | The SOC itself |
| MDR | Managed service combining all three | The MDR provider, within agreed actions |
How do MSPs deliver MDR without building a SOC?
Most MSPs partner with an MDR platform that includes a 24/7 SOC, then package the service under their own brand. The MSP sells, onboards and speaks to the client. The SOC monitors, triages and contains threats out of hours, within the actions each client has approved in advance.
-
Step 1: Choose an MDR platform built for MSPs
Look for multi-tenant management, branding options and support for the EDR tools clients already run, such as Microsoft Defender, Sophos or the other EDR tools you already use.
-
Step 2: Agree pre-approved actions with each client
Decide which containment steps the SOC can take without a call, such as isolating a laptop or revoking a session.
-
Step 3: Build a complete escalation list
Make sure someone can be reached for decisions at any hour, including weekends.
-
Step 4: Connect data sources and deploy agents
Connect identity, email and endpoint sources so the SOC can see a full attack chain.
-
Step 5: Report outcomes every month
Show clients what was detected, contained and fixed, not just how many alerts fired.
What are the biggest MDR challenges for MSPs?
The challenges we hear most from MSPs are alert fatigue, unclear responsibility after detection, slow escalation and difficulty proving value to clients. Each page in this cluster tackles one of them, with steps an MSP can apply across its client base and the public guidance behind each recommendation.
- Noise. Too many alerts and false positives bury the real attack.
- Ownership. Detection without agreed remediation leaves issues open.
- Escalation. Out-of-hours decisions stall when nobody answers the phone.
- Proof. Clients and insurers want evidence that monitoring reduces risk.
Which questions does this cluster answer?
The pages below answer the most common MDR questions from MSPs and IT teams. Each one gives a direct answer first, then steps and examples. Each guide below is available to read.
- How can an MSP offer 24/7 MDR without building its own SOC?
- How do MSPs reduce alert fatigue without missing real threats?
- What should happen in the first 60 minutes after an MDR alert fires at 2am?
- Who fixes the issue after an MDR provider detects it?
- How does an MDR provider handle false positives without missing real threats?
- What are pre-approved response actions in MDR and which should an MSP approve?
- How should an MDR provider escalate critical incidents to an MSP?
- How do you measure whether an MDR service is actually reducing risk?
- Our cyber insurer wants evidence of 24/7 monitoring. What counts?
How does CybaOps help MSPs deliver MDR?
CybaOps is the CybaVerse MDR platform, sold through MSPs, resellers and distributors, backed by our UK-based security operations centre. MSPs can run it across all their customers from one multi-tenant platform, and can see it in a CybaOps demo before they onboard any of their clients. Thinkmoney's CISO, Glenn Sproule, chose CybaVerse for its SOC.
- Our UK-based security operations centre monitors customer environments 24 hours a day, 7 days a week.
- CybaCore is our AI-enabled MDR package, with 24/7 UK cyber operators, continuous monitoring, identity threat detection and response, and a monthly allowance of incident response.
- CybaEdge adds unlimited incident response, threat hunting and premium identity threat detection and response, delivered by our UK SOC.
- CybaOne adds SIEM, an external penetration test and dark web monitoring to everything in CybaEdge.
- CybaOps works with the security tools you already have, including Microsoft Defender, Sophos and the other EDR tools you already use, so you do not have to rip and replace.
- Our SOC hunts for new threats across customer environments and alerts customers when a new attack affects tools they use.
- Incidents are worked as cases in CybaOps, so every alert, action and note sits in one record your team can see.
- Pre-approved response actions are agreed with the MSP for each client during onboarding.
MDR for MSPs
How MSPs deliver MDR to every client
Managed detection and response (MDR) is a service in which analysts monitor an organisation's security signals 24/7, investigate suspicious activity and contain real attacks quickly.
01 Your tools
MDR for MSPs
02 The 5-step path
- Role-based access
- UK-based analysts
- ISO 27001
03 Outcomes
Hover or tap any part of the diagram to see what it does.
- MDR in
- CybaCore
- CybaEdge
- CybaOne
What else do MSPs ask about MDR?
These are the follow-up questions MSPs ask most when they first look at adding MDR to their services.
Do clients need to replace their EDR to get MDR?
Usually not. Many MDR services, including CybaOps, work with the security tools a client already runs, such as Microsoft Defender, Sophos or the other EDR tools you already use. Check that the service brings in the alerts and data the SOC needs.
Does MDR include remediation?
It varies by provider. Some only alert. Others contain threats and help fix root causes. Ask who fixes the issue after detection, and how that work is recorded and verified, before you sign.
Who talks to the client during an incident?
In an MSP-delivered model the MSP usually owns client contact, and the SOC escalates to the MSP. Agree this in writing so the client hears one consistent voice during a stressful moment.
What should you do next?
See how the pieces fit together on the CybaOps platform page. MSPs can read about the CybaVerse partner model for MSPs.
See how CybaVerse MDR works an incident from alert to closure.
Book a CybaOps demo