Eight MDR Contract Red Flags, and the Terms to Ask For Instead
Most MDR contracts promise fast detection but say little about containment, fees, data or exit. Here are eight clauses that cost buyers later, and the wording to ask for before you sign.
Where MDR Contract Terms Diverge From the Sales Demo
A demo shows you a console, a 24/7 analyst team and a mean-time-to-respond figure. It doesn't show what the provider is required to do at 3 a.m. when ransomware starts encrypting a file server. Only the MDR contract terms do that, and they're usually written to protect the provider, not you.
The eight problems below come up repeatedly in managed detection and response contract reviews, whatever the region or deal size. None of them should kill a deal. Each can be fixed with better wording, and many providers will agree when a buyer asks in writing. Use the table as a redline checklist before you open the master services agreement.
| Red flag | What to ask for instead |
|---|---|
| SLA measures only time to alert | Separate SLAs for triage, notification and containment by severity |
| Service credits capped at a token amount | Credits that escalate, plus a termination right for repeated misses |
| Ingestion or endpoint overage fees | Fixed pricing bands with a true-up only at renewal |
| No containment authority | A pre-approved list of response actions the provider can take |
| Short telemetry retention | At least 12 months of searchable or exportable data |
| No exit or data-return clause | Defined export format, timeline and transition help |
| Auto-renewal with open-ended uplift | Renewal notice, a cap on price increases and a short opt-out |
| No insurer or panel coordination | A duty to cooperate with insurer-appointed counsel and forensics |
Alert-Only SLAs and Service Credits Without Teeth
Red flag 1: the SLA stops at the alert. Many MDR service level agreements promise to "respond" within 15 or 30 minutes. Read the definitions. "Respond" often means an analyst opened a ticket or an automated email went out. That says nothing about how fast a compromised host gets isolated.
Ask for instead: an MDR response time SLA with separate, measured clocks for each stage, broken out by severity:
- Time to triage: an analyst has confirmed or dismissed the detection.
- Time to notify: a named contact has been reached by phone, not just email, for critical incidents.
- Time to contain: the agreed containment action is complete, or the provider has requested approval and recorded the request.
For critical severity, a reasonable target is 15 to 30 minutes to triage and 30 to 60 minutes to contain when pre-approval exists. Define each severity level in plain language. If you don't, the provider decides after the fact what counted as critical.
Red flag 2: credits that don't sting. A credit of a few percent of one month's fee won't change provider behavior. Push for credits that rise with each consecutive miss. Also ask for the right to terminate without penalty if critical-severity SLAs are missed in, say, two of any three months. That termination right matters more than the credit percentage.
Ingestion Overage Fees Hidden in the Pricing Metric
Red flag 3: you're quoted per endpoint but billed per gigabyte. Many providers now ingest cloud, identity, email and firewall logs on top of endpoint telemetry. The base quote may cover a set daily volume, with overage billed per GB at rates you only find in an order form appendix. Adding a SaaS platform, turning on verbose cloud logging or acquiring a company can push you over that volume fast.
Here's a hypothetical. A 300-endpoint company signs at $12 to $20 per endpoint per month, roughly $43,000 to $72,000 a year. Six months later it connects its cloud audit logs and ingestion doubles. Uncapped overage could add a large share, perhaps a fifth or more, to the annual bill before anyone notices. These are indicative 2026 market ranges that vary by contract and region, so confirm with each vendor and model your own case.
Ask for instead:
- Pricing bands, for example 250 to 350 endpoints, with no charge for growth inside the band.
- An ingestion allowance tied to named data sources rather than raw GB, or a fixed price per source.
- Overage reconciled once a year at renewal at the contracted unit rate, never billed monthly without notice.
- Written notice when you reach 80% of any allowance.
No Containment Authority When Minutes Matter
Red flag 4: the provider can watch but not act. Some contracts limit the provider to detection and advice. Others allow response actions but say nothing about authority. Analysts then wait for your approval while an attacker moves sideways through the network. At a 40-person company with no overnight IT staff, that wait can last hours.
Ask for instead: a pre-authorized response schedule attached to the contract. It should list actions the provider may take without asking, actions that need approval, and actions it may never take. A typical split:
- Pre-approved: isolate a workstation, kill a malicious process, quarantine a file, disable a compromised user account, revoke active sessions.
- Approval required: isolate servers or domain controllers, block an IP range at the firewall, reset privileged credentials.
- Prohibited: deleting data, wiping systems, contacting attackers.
Pair the schedule with an escalation tree of names and phone numbers, and a clause saying what happens if nobody answers within a set time. Have counsel review the liability wording too. Providers will want protection when a good-faith containment action disrupts operations. That's a fair request if the action followed the agreed schedule.
Retention Limits and a Missing MDR Exit Clause
Red flag 5: telemetry disappears too soon. Entry-level MDR tiers often keep only a few weeks to a few months of searchable data. Attackers can stay hidden longer than that. When forensic investigators later ask what happened four months ago, the evidence is gone. Regulators, litigants or your insurer may ask the same question.
Ask for instead: at least 12 months of retention, searchable or exportable to storage you control. Specify where the data is stored and processed. GDPR in Europe and the UK, India's Digital Personal Data Protection Act, and data-protection laws in the Gulf states and Southeast Asia can all impose cross-border transfer or localization rules. Your counsel should confirm which apply to your telemetry.
Red flag 6: no exit path. Without an MDR exit clause, you can end up locked into a proprietary agent and a data store you can't reach. Ask for:
- Export of all your telemetry, detections and case notes in a standard format within 30 days of termination.
- Transition support of around 90 days at a fixed rate, including help removing agents.
- Certified deletion of your data afterwards, confirmed in writing.
- Ownership of custom detection rules written for your environment, or a license to keep using them.
Auto-Renewal Uplifts That Arrive Unannounced
Red flag 7: evergreen renewal with uncapped increases. Some agreements renew automatically for another full term unless you cancel 60 to 90 days before the end. The renewal price can be the provider's "then-current list price." Buyers who signed at heavy first-year discounts can face large jumps.
Ask for instead:
- Written renewal notice from the provider about 120 days before the term ends, with the proposed price.
- An annual increase cap in the low single digits, or one tied to a published inflation index.
- Discounts that carry into renewal, not just year one.
- For multi-year deals, termination for convenience after year one with a defined, modest fee.
A two- or three-year term at a locked price usually beats one-year terms with uncapped renewals. That holds only if the SLA termination right from earlier is in place, so an underperforming provider can't hold you to the full term.
No Insurer-Panel Coordination, and How to Close the Gap
Red flag 8: the MDR contract ignores your cyber policy. Many cyber insurers require insureds to call a breach hotline, then appoint panel counsel and a panel forensics firm. If your MDR provider isn't on that panel, its incident response hours may not be reimbursed. Uncoordinated work can also complicate legal privilege where it applies, or break the chain of evidence. Panel rules differ between insurers and markets, from London and continental Europe to Singapore, the Gulf and North America.
Ask for instead: a clause requiring the provider to:
- Cooperate with insurer-appointed counsel and forensics firms, including working under counsel's direction where you request it.
- Preserve and hand over raw telemetry and case records within 24 to 48 hours of a request.
- Support your regulatory deadlines, which can be short. Examples include GDPR's 72-hour notification to a supervisory authority, NIS2's 24-hour early warning, and CERT-In's six-hour reporting window in India. Confirm which apply to you.
Before you sign, send the draft to your broker. Ask whether the provider is on your insurer's panel or can be pre-approved, and whether running MDR affects your premium or retention.
Decision rule: if a provider won't agree to containment authority, data export on exit and insurer cooperation, move to the next vendor on your shortlist. The other five terms are normal negotiation points. Those three decide whether the service protects you during an incident. Have a licensed attorney in your jurisdiction review the final redlines.
Quick answers
What is a reasonable MDR response time SLA for critical incidents?
For critical severity, buyers commonly negotiate 15 to 30 minutes to triage and 30 to 60 minutes to contain, provided pre-approved containment actions are in place. Measure triage, notification and containment separately. One vague "response" figure can hide long delays.
Should our MDR provider be on our cyber insurer's panel?
Ideally yes, or pre-approved in writing by the insurer. Otherwise incident response costs may not be reimbursed and you may have to coordinate two firms during a breach. Ask your broker to check before you sign the MDR contract.
How much telemetry retention do we actually need?
Twelve months of searchable or exportable data is a sensible baseline for most mid-size companies. Attackers can stay hidden longer than the few weeks or months many entry-level tiers keep. Regulated sectors and some jurisdictions may require longer, so confirm with counsel.
Are MDR prices negotiable, and what drives the cost?
Yes. Endpoint count, ingestion volume, extra data sources, retention length, response scope and term length are the main cost drivers. Typical 2026 market ranges run roughly $8 to $25 per endpoint per month, but local pricing and bundles vary widely, so get written quotes for your own environment.
What should an MDR exit clause include?
It should cover export of all telemetry, detections and case notes in a standard format within a set period, often 30 days. It should also include paid transition support, help removing agents, and certified deletion of your data afterwards. Ideally you also keep custom detection rules built for your environment.
Written by the Breach Underwrite Group editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.