MDR (managed detection and response) is a service in which an outside team watches your systems for attacks, investigates alerts, and helps you respond. Choosing a provider is less about finding the best brand than about four things: knowing what you need, asking every provider the same questions, testing before you sign, and writing the answers into the contract. This article follows that order. It does not name or rank any provider.
If you are still unsure what MDR is, read EDR, XDR and MDR: Differences and How to Choose. If you are still deciding whether to outsource at all, read SOC Models: In-House, MSSP or Hybrid Compared first.
Start with what you need
The Canadian Cyber Centre (ITSM.10.023) advises a preliminary risk assessment before choosing a managed provider. Its list covers:
- Assets: an inventory of what you have
- Protection level: how well each asset must be protected
- Access: who has access to what
- Data location: where your data is stored
- Existing controls: the security measures already in place
- Likely threats: what is most likely to be used against you
- Incident response plan: whether you already have one (see Incident Response Plan Under NIST SP 800-61 Rev. 3)
Then decide how much you want the provider to do. MDR scope differs by provider, so the service name alone tells you little. This three-level simplification is our own, not a standard:
- Alerts only: the provider tells you something is wrong, and your team does the rest
- Alerts with advice: the provider also investigates and recommends what to do, and your team acts
- Response on your behalf: the provider takes agreed actions itself, for example isolating a device from the network
Five areas to evaluate
Ask every provider the same questions on these five areas, so the answers can be compared. The grouping is our own, built from questions in the Canadian Cyber Centre, NCSC, NIST, and CISA guidance:
- Scope and coverage: which devices, accounts, cloud services, and hours are covered, and how the provider learns about new systems. The Cyber Centre says a provider may be less aware of your changes than an in-house team. Its SOC contract guide (ITSM.00.500) lists round-the-clock monitoring, actionable notifications, escalations, and written event reports as topics to cover
- Who acts: which response actions the provider takes alone, which wait for your approval, and who can approve at night. NIST says the limits on a provider, such as whether it may deactivate a service immediately, should be settled in the contract
- Service levels: the targets for detection, alerting, and resolution, and a sample service level agreement (SLA, the promised response and resolution times) to read before signing (Cyber Centre)
- Data and access: where logs are stored, whether they are encrypted, who at the provider can connect, whether you can audit access, and data residency (Cyber Centre). Also how the provider protects its own access to you, with multi-factor authentication (MFA) and only the permissions it needs (CISA, NCSC)
- Assurance and fit: certifications, references from your industry, support for forensics and emergency response, threat intelligence, fit with your tools, and the provider's own suppliers (Cyber Centre, NCSC, CISA)
Check the evidence and test before you sign
For certifications, the NCSC guide for managed service providers names Cyber Essentials Plus (a UK government baseline scheme), ISO 27001, and SOC 2. The Cyber Centre gives SOC 2 Type 2, ISO 27001, ISO 27017, and CSA STAR as examples. The NCSC states that a certification does not remove your own responsibility, so ask what a certificate actually covers. The NCSC also runs assured service schemes, such as Cyber Incident Response and CHECK penetration testing. On the page we read, no scheme was named for MDR or monitoring services, so we do not know of an NCSC assurance mark for MDR. Do not treat an assurance mark for another service as proof of MDR quality. If a provider cites MITRE ATT&CK Evaluations results, see EDR, XDR and MDR: Differences and How to Choose for how to read them.
A pilot (a short trial on a limited scope) shows what a brochure does not. This five-step design is our own view, not from a source:
- Set success criteria: write down what counts as good, such as coverage, time to notify you, and report quality
- Limit the scope: a few systems, agreed in writing, with the provider's access limited in time
- Run agreed test activity: safe, simulated activity that IT has approved in advance
- Measure: how fast and how clearly the provider tells you, whether alerts can be acted on, and whether its advice fits your environment
- Compare and decide: score every shortlisted provider against the same criteria and call its references
Set your must-haves as pass or fail before you compare the rest, for example that data stays in the country, that provider accounts use MFA, and that a named person can approve actions at night. A provider that fails a must-have is out, whatever else it scores. Treat a vague answer as a signal to ask again. This is our own view, and the figure below shows what to listen for.
Vague answer
- "We cover everything"no sources or hours named
- "Our team handles it"no word on who acts
- "Very fast response"no target numbers
Clear answer
- A list of sources and hourswhat is connected and when
- A table of actionsalone versus with approval
- Targets in a sample SLAdetect, alert, resolve
What the contract should say
NIST SP 800-61 Rev. 3 (April 2025) says that when duties move to a provider, the contract should define them clearly. The topics below come from CISA, the NCSC, and the Cyber Centre. The Cyber Centre says its guide is not legal advice, so have legal counsel review your contract:
- Roles: who owns hardening (making systems more secure by tightening settings), detection, and incident response (CISA), ideally in a responsibility matrix, a table of who does what (NCSC)
- Service levels and reports: an SLA and regular reports. The NCSC's example for general managed IT services is a response in about one business day for minor requests and under one hour for urgent issues, and it notes that faster response usually costs more. Those figures are not for detection work, so agree MDR targets with the provider
- Incident notification: how and when the provider tells you, scaled to severity, including incidents on its own systems (NCSC, CISA)
- The provider's access: MFA, only the permissions it needs, no reuse of admin credentials across customers, and accounts disabled when the contract ends (CISA)
- Data: what is captured, where it is stored, who sees it, who owns it, how it is returned at the end, and the cost and time of moving it (Cyber Centre). CISA advises keeping the most important logs for at least six months
- Liability and exit: who is liable, audit and site-visit rights, insurance coverage (Cyber Centre), and the term, renewal, and termination (NCSC)
Common mistakes
- Choosing by demo or brand name: providers answer different questions, so the answers cannot be compared (our own view)
- Reading "24/7" as "someone acts at 3 a.m.": round-the-clock watching is not the same as round-the-clock response, so ask who acts (our own view)
- Not telling the provider about new systems: the Cyber Centre says a provider may be less aware of your changes
- Believing MDR moves the risk to the provider: the Cyber Centre says the organization remains accountable for its data and systems
- Leaving provider accounts open when the contract ends: CISA notes this is often overlooked
- Skipping the pilot: signing for a long term before seeing a single real report (our own view)
- Copying a small-organization checklist for a large one: the NCSC guide is written for small and medium organisations, and it points those with more than 250 people to its cloud security guidance, so treat it as a starting point
Start today
- Write your requirements: assets, where data may be stored, the hours you need, and the tools you already run
- Pick a scope level: alerts only, alerts with advice, or response on your behalf, and name who may approve actions at night
- Prepare one question sheet: use the five areas and send the same sheet to every provider
- Fix your must-haves: the pass or fail items that remove a provider from the list
- Plan the pilot and the contract review: involve legal and procurement early, and see Writing a Security RFP, TOR and PoC Plan
To see where your security operations stand today, try the self-assessment.
Scope and accuracy
This article draws on the Canadian Cyber Centre guides ITSM.10.023 (October 2022) and ITSM.00.500 (April 2025), the NCSC guide to choosing a managed service provider (published November 2025) and its assured services page, CISA advisory AA22-131A (May 2022), and NIST SP 800-61 Rev. 3 (April 2025), read from the NIST PDF. We read these pages on 4 November 2026. The NCSC guide covers general managed IT services for small and medium organisations, not MDR specifically, so we apply it to MDR by analogy. The five areas, the three scope levels, the pilot, and the must-have approach are our own view, not from the sources. We name no provider and make no ranking. This is general guidance, not legal advice. Guidance changes, so check the current versions.
References and further reading
- Canadian Cyber Centre: Choosing the best cyber security solution (ITSM.10.023): the preliminary risk assessment and the 17 MSSP evaluation criteria
- Canadian Cyber Centre: Recommended contract clauses for SOC procurement (ITSM.00.500): topics for contracts when buying SOC services
- UK NCSC: Choosing a managed service provider (MSP): certifications, references, contract topics, and a checklist (written for small and medium organisations)
- UK NCSC: Assured services: the list of NCSC assured service schemes
- CISA AA22-131A: Protecting Against Cyber Threats to Managed Service Providers and their Customers: advice for customers on contracts, access, logs, and incident notification
- NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations: sharing duties with a provider and the limits to settle in a contract