How to Run a Managed Detection and Response RFP: A 12-Step Buyer Playbook
Most MDR RFPs end up scoring sales slides instead of how fast the provider contains an attack. This 12-step playbook covers weighted scoring, SLAs with defined clocks, a scripted proof-of-value test, the contract clauses to negotiate and how to check the provider against your cyber insurer's panel.
Lock Scope and Ownership Before Any Vendor Sees the RFP
Most managed detection and response RFPs go wrong in week one. The buyer sends a generic questionnaire and gets back six polished answers that all promise a "24/7 SOC." With nothing to tell them apart, the decision comes down to price. Settle your own scope and decision owners before any vendor sees the document.
Step 1: Inventory what the provider must watch
Count endpoints, servers, cloud accounts (AWS, Azure, Google Cloud), identity platforms (Entra ID, Okta, Google Workspace), email, firewalls and business-critical SaaS apps. Write down which EDR you already own, if any. That one fact shapes the whole shortlist. Some providers work only with their own agent. Others will run on top of an existing CrowdStrike, Microsoft Defender or SentinelOne deployment.
Step 2: Name the decision owners and set the timeline
Make one person accountable, usually the CISO or head of IT. Bring in finance, legal or procurement, and whoever manages your cyber insurance. Allow about 10 to 14 weeks from RFP release to signature: roughly three weeks for responses, two for scoring, four to six for proof of value and two to three for negotiation. The proof of value is the part teams most often cut short, and it's the one stage that exposes weak after-hours staffing.
Shortlist Four to Six Providers and Ask Questions That Force Specifics
Step 3: Build a shortlist that fits your geography
Providers with international reach include CrowdStrike Falcon Complete, Arctic Wolf, Sophos MDR, Rapid7, Expel, eSentire, Red Canary and Microsoft Defender Experts. Regional MSSPs in Europe, India, the Gulf, Southeast Asia, Latin America and Africa deserve a place on the list if you need in-country analysts, local-language support or local data storage. Check availability and pricing in your market, because neither is the same everywhere. Six providers is the most you can evaluate properly. Four is better, because every serious contender costs your engineers time in scoring and testing.
Step 4: Write questions that can't be answered with a brochure
Phrase your MDR vendor selection criteria so that a vague answer is obvious:
- Which telemetry sources are included in the base price, and which cost extra?
- Where are your analysts located, and does a human review every high-severity alert at all hours?
- Walk us through a recent ransomware containment, anonymized, with timestamps.
- What do you not do? List the response actions that are excluded.
- How many customers does each analyst cover, and how do you staff for surges?
Score Responses With Weights You Agree On in Advance
Step 5: Fix the scoring model before responses arrive
If you set the weights after reading the proposals, the team's favorite vendor usually wins. Agree on the weights internally first. Score each criterion from 1 to 5, and have at least two people score every response independently. The weights below suit most mid-size buyers. Regulated firms, such as banks, insurers and healthcare providers, should give data residency and compliance more weight.
| Criterion | Weight | What a 5 looks like |
|---|---|---|
| Detection coverage across your stack | 20% | Native coverage of endpoint, identity, cloud and email with no extra connector fees |
| Response capability and authority | 20% | Contains threats on the host and in identity without waiting for your call |
| Measured SLAs with remedies | 15% | Defined start and stop points for each clock, backed by service credits |
| Proof-of-value results | 20% | Detected and contained the agreed test scenarios within SLA |
| Data residency and compliance | 10% | In-region storage option plus current audit reports such as ISO 27001 or SOC 2 |
| Commercials and contract terms | 15% | Transparent unit pricing and fair exit terms |
Any vendor that scores 1 on response capability or data residency is out, whatever its total score. A high total can't make up for a provider that can't contain an attack or can't legally hold your data.
Define Response Times So the Clock Can't Be Gamed
Step 6: Write MDR SLA requirements with exact start and stop points
"Mean time to respond: 30 minutes" tells you nothing until you know when the clock starts. Some providers start it when an analyst picks up the alert, not when the alert fires, and alerts can sit in a queue for a long time first. Define each metric in the RFP:
- Time to detect: from the first malicious telemetry event to alert creation.
- Time to triage: from alert creation to an analyst's severity decision.
- Time to notify: from the severity decision to a clear written notice to your named contacts.
- Time to contain: from the severity decision to host isolation, account disablement or session revocation.
Ask for each metric as a median and a 90th percentile, broken out by severity. An average hides the slowest incidents, and those slow incidents are the ones that turn into breaches. For critical incidents, ask top-tier providers to commit to containment within roughly 15 to 30 minutes. Anything beyond an hour should trigger service credits.
Settle Active-Response Authority and Where Your Data Lives
Step 7: Put containment authority in writing
Agree in advance on what the provider may do without calling you first: isolate a laptop, disable a user, revoke tokens, block a file hash, quarantine an email. A common setup gives full authority on workstations, requires approval for production servers and excludes a short list of critical systems entirely. Record these decisions in a signed response matrix. If a provider needs a phone call before isolating a host at 3 a.m., you're buying monitoring, not MDR.
Step 8: Confirm data residency and transfer mechanisms
Data rules vary a lot by jurisdiction. In the EU, and in the UK under its own version of GDPR, you need a lawful transfer basis when analysts outside the region can access your logs. India's DPDP Act, Saudi Arabia's PDPL, Brazil's LGPD and Singapore's PDPA each set their own conditions. Some sectors, financial services in particular, add data localization requirements in a number of Gulf and Asian markets. Ask each provider where telemetry is stored, where analysts work from, how long data is kept and which subprocessors handle it. Then have privacy counsel confirm that the arrangement meets your obligations in every country where you operate.
Run a Proof of Value That Tests Response, Not Dashboards
Step 9: Use a scripted MDR proof of value
Take your top two providers into a four- to six-week proof of value on a representative slice of your environment. That's typically 5 to 10% of endpoints plus your identity tenant. Write the test plan yourself and share it in advance. Give each provider the test window, but not the exact timing of each test.
- Run harmless attack simulations mapped to MITRE ATT&CK, such as credential dumping, lateral movement and suspicious PowerShell. Use a tool like Atomic Red Team or a purple-team exercise.
- Stage an identity attack: a sign-in from an impossible location followed by an MFA-fatigue pattern.
- Set off at least one alert overnight on a weekend to check that 24/7 staffing is real.
- Measure every Step 6 clock against your own timestamps, not the provider's report.
- Grade each notification: could your on-call engineer act on it without a follow-up call?
Hypothetical example: a 400-person company tests two providers. Provider A detects all eight scenarios but contains them only after getting approval by phone. Provider B misses one scenario but isolates hosts automatically within 12 minutes. B is the better choice for most companies of that size, because fast containment limits damage more than one extra detection does.
Negotiate the Contract Clauses That Matter When Things Break
Step 10: Benchmark pricing
The figures below are typical 2026 market ranges. They vary by contract, region, volume and scope, so confirm with each vendor. Local pricing can differ significantly from USD list prices.
| Model | Indicative price | Watch for |
|---|---|---|
| MDR on your existing EDR | About $8–$20 per endpoint per month | Fees for each extra log source |
| Bundled EDR plus MDR | About $15–$40 per endpoint per month | Being locked into the vendor's agent at renewal |
| Mid-size program (500–1,500 endpoints, plus identity and cloud) | About $60,000–$300,000 per year | Data ingestion caps and overage charges |
Step 11: Negotiate MDR contract terms
- Service credits tied to the Step 6 definitions, increasing with each repeated miss.
- The right to terminate without penalty for chronic SLA failure.
- Incident response hours either included or priced in advance, not billed at emergency rates.
- Return of your data in a usable format, plus certified deletion within an agreed period after exit.
- A cap on renewal price increases. Buyers often negotiate low-to-mid single digits per year.
- Liability caps well above the vendor's starting position. Have counsel review the limitation-of-liability clause, since standard caps are often small compared with the cost of an incident.
Line Up the MDR With Your Cyber Insurer Before You Sign
Step 12: Check the provider against your breach panel
Many cyber policies cover incident response costs only if you use the insurer's panel firms or get the insurer's consent first. If your MDR provider's IR team isn't on that panel, a serious incident can become a coverage dispute while you're still containing it. Before signing:
- Send the shortlist to your broker and ask which providers are on the panel or pre-approved.
- If your preferred provider isn't, write a handoff runbook: the MDR contains the threat, preserves evidence and hands over cleanly to the panel firm.
- Ask whether your insurer gives underwriting credit for 24/7 MDR. Many applications ask about it, but how much it affects terms varies by insurer and market.
- Confirm that the MDR's logs and incident timelines will meet the insurer's evidence and notification requirements.
Decision rule: don't sign until your broker confirms in writing that the chosen provider is on the panel or that the handoff runbook is approved. Have a licensed broker or coverage counsel confirm what your policy wording actually requires.
Questions buyers ask
How long should a managed detection and response RFP take?
Plan for about 10 to 14 weeks from release to signature: around three weeks for responses, two for scoring, four to six for the proof of value and two to three for contract negotiation. The proof of value is the stage not to rush, because a shorter test is less likely to expose weak weekend and overnight staffing.
Should we choose an MDR that works on our existing EDR or switch to its bundled agent?
If your current EDR is well deployed and has more than a year left on its contract, adding MDR on top is usually cheaper and less disruptive. A bundled agent can give tighter response integration, but it makes switching harder at renewal. During the proof of value, test how far each provider's response actions actually go on your own agent.
What is a reasonable SLA for containing a critical incident?
For critical alerts, ask top-tier providers for containment within roughly 15 to 30 minutes of the severity decision. The clock definition matters more than the headline number, and so does whether missed targets trigger service credits. Ask for 90th-percentile figures as well as medians.
Do we need our MDR provider to be on our insurer's breach panel?
Not always. But many policies require panel firms or the insurer's consent before they'll cover incident response costs. If your provider isn't on the panel, document a handoff process and get your broker's written confirmation. A licensed broker or coverage counsel should review your specific policy wording.
How do we handle data residency if the provider's analysts are in another country?
Ask where telemetry is stored, where analysts access it from and which legal transfer mechanism applies. Requirements differ under GDPR and UK GDPR, India's DPDP Act, Saudi Arabia's PDPL, Brazil's LGPD, Singapore's PDPA and sector-specific rules. Some providers offer in-region storage or regional analyst teams. Your privacy counsel should confirm that the setup meets your obligations.
How many MDR providers should we take into a proof of value?
Two. Running a proper scripted test uses a lot of engineering time, and testing more than two providers in parallel usually means testing each one less thoroughly. Use the weighted written scores to narrow the field to two, then let the proof of value decide.
Written by the Auditvault Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.