# An MDR service investigates and acts on threats for you; an MSSP mostly watches and sends you the alert

Explainer, read 10 November 2026

**The short answer.** MDR providers sell a team that investigates alerts and acts or advises on response. MSSPs typically sell monitoring, device management and alert forwarding. Both labels are loose, so the written scope decides. This page gives the usual split, published examples from providers, and the contract lines that settle it.

## What is the difference between MDR and MSSP?

Both are outside teams that watch your systems. The difference is what happens after something looks wrong. A managed security service provider (MSSP) typically watches logs and devices and sends you the alert. A managed detection and response (MDR) provider investigates the alert, decides whether it is real, and then acts or tells you what to do. Neither label guarantees that split, because the contract defines the work.

CrowdStrike, a vendor that sells MDR, writes that MSSPs "typically provide broad monitoring of the network for events and send validated alerts to other tools or to the security team" and "generally do not actively respond to threats" (read 10 Nov 2026). Treat that as one seller's description of an older category. It matches how many buyers use the terms, and it gives a fair first test: who performs the next step?

## What an MSSP contract usually covers

The same CrowdStrike page lists technology management, upgrades, compliance and vulnerability management as typical MSSP extras. That breadth suits a team that wants one provider to run firewalls, collect logs and keep the stack patched. It is a different purchase from a team that investigates intrusions.

Before you sign an MSSP agreement, get answers to these in writing:

- Who reads the alert first, and what does the provider do when it is a false positive?
- Is the output a ticket, an email or a call, and within what time?
- What may the provider change in your systems without asking?
- Who investigates when an alert needs more than a log lookup?
- What happens at 3 a.m. on a Sunday?

## What an MDR contract usually covers

An MDR service sells detection plus a response process. Published examples show how wide the range is. Critical Start says its analysts run a customer-approved playbook that may include host isolation, process termination or account suspension in the customer's tools. Huntress says a human reviews every alert before it reaches the customer. Microsoft's Defender Experts page says its experts act on the customer's behalf only if granted Security Operator access; with the default Security Reader access, actions are left pending for the customer.

Those are three different arrangements, all sold as MDR. In the first the provider acts inside rules you approved. In the second the page describes human review before you see an alert. In the third your own permission setting decides whether the provider can act at all. Each is a statement by the provider, read on 10 Nov 2026, and each belongs in your contract if you rely on it.

## Where the labels blur

Many firms sell both. Some MSSPs now run investigation and response teams, and some MDR providers also manage devices. A managed SIEM adds a third version: CrowdStrike notes that SIEM capabilities vary widely, with some products technology-only and others closer to managed event processing and alerting. Ask what the people do, not what the product is called.

Incident response is another blur. Kroll says its Responder MDR includes remote digital forensics and incident response at no extra cost. Rapid7's pricing FAQ says its pricing is not tied to incident response hours. Sophos says critical incident response is included with no caps or additional fees. Arctic Wolf's retainer FAQ says incident response works inside the client's environment, which indicates it sells that as a separate service from MDR. These are statements by the providers, listed alphabetically, and not a comparison.

## Contract lines that settle which one you are buying

Published service levels show how differently the paper can read. Critical Start's SLA page publishes a 60-minute mean time to respond in all three tiers and service credits of 10 percent for a missed per-alert or monthly response time. ReliaQuest's incident response SLA page commits to acknowledgement in 45 minutes for critical alerts and 240 minutes for low ones. Sophos commits, for MDR Plus customers, to a time to respond within 60 minutes for 90 percent of priority investigations, measured monthly. Arctic Wolf's company FAQ says its team contacts the customer within minutes of a threat; no minute-level SLA found on the pages read on 10 Nov 2026.

Compare the definitions before the numbers. One provider counts from alert creation, another from analyst assignment, another from confirmed detection. A figure with no stated start point cannot be set beside another.

- Named response actions (isolate host, disable account, block address) and who authorizes each.
- A start and stop point for every time commitment.
- Credits or remedies for a missed commitment, and whether they are capped.
- Whether incident response hours are included, capped or billed.
- Which of your data sources are in scope, and which are excluded.

## A working rule

If your team cannot act at night, buy a service whose paper says the provider acts, and read the list of actions it may take. If your team can act and wants a second pair of eyes, an alert-forwarding service may be enough. Either way, run a test alert in the first two weeks and see who does what.

## Related pages

- [Home: MDR vs MSSP in short](/)
- [MDR vs XDR: a service against a platform](/mdr-vs-xdr/)
- [MDR vs SOC: renting a team against building one](/mdr-vs-soc/)
- [The six kinds of managed detection service](/guides/kinds-of-managed-detection/)
- [MDR glossary](/glossary/)
- [The MDR Service Matrix](/matrix/)

## Sources

- CrowdStrike, MDR explainer (vendor's definition): https://www.crowdstrike.com/en-us/cybersecurity-101/managed-security/managed-detection-and-response-mdr/ (read 10 November 2026)
- Critical Start, MDR page: https://www.criticalstart.com/mdr (read 10 November 2026)
- Huntress, Managed EDR page: https://www.huntress.com/platform/managed-edr (read 10 November 2026)
- Microsoft, Defender Experts managed response: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026)
- Kroll, Responder page: https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026)
- Rapid7, MDR FAQ: https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026)
- Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026)
- Arctic Wolf, incident response retainer FAQ: https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026)
- Critical Start, SLA page: https://www.criticalstart.com/sla-commitment (read 10 November 2026)
- ReliaQuest, GreyMatter IR SLA: https://reliaquest.com/greymatter-ir-sla/ (read 10 November 2026)
- Sophos, MDR service description: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026)
- Arctic Wolf, company FAQ: https://arcticwolf.com/company/faq/ (read 10 November 2026)

Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/mdr-vs-mssp/
