# MDR contains the first host, then incident response takes over the investigation, and the contract must say where the line sits

Guide, read 10 November 2026

**The short answer.** An MDR analyst can usually stop a threat on the endpoints it sees. Scoping the intrusion, preserving evidence, working with counsel and rebuilding belong to incident response. Some services bundle it, others sell it separately. This guide traces the hand-off hour by hour and lists what to settle before it happens.

## Where does MDR end and incident response begin?

MDR work ends where the question changes from what is this alert to how far did they get. Mandiant's Managed Defense page says attacks can be stopped and incidents resolved without a formal incident response engagement, which fits contained events. Once the attacker has moved, reached identity systems or taken data, the work is a different job with different people.

Arctic Wolf's retainer FAQ draws the line in its own words: incident response works inside the client's environment, which indicates incident response is a separate service from MDR. BlueVoyant sells its DFIR retainer on a separate page with pre-arranged response SLAs. Each is a provider's statement, read on 10 Nov 2026.

## The first hours

Within the first hours, four things happen in a set order: contain, preserve, scope, notify. The MDR analyst contains the visible hosts and accounts. Someone preserves evidence before systems are rebuilt. Responders scope the intrusion. You tell insurers, counsel and, where required, regulators.

NIST's SP 800-61 Rev. 3, published April 2025 and superseding Rev. 2 of August 2012, fits incident response into the CSF 2.0 risk management structure. The UK NCSC's incident management collection divides the work into plan, build, develop and maintain. Whether your MDR provider is also your responder is a contract matter, not a standards matter.

- Who declares an incident, and by what test?
- Who calls counsel, and who talks to the insurer?
- Who keeps the evidence log?
- Which actions need approval during an incident, and from whom?

## Published response terms

Response clocks differ by service and are not interchangeable. SentinelOne's incident readiness page states a 4-hour SLA for initial expert response and a 24-hour SLA for preliminary findings. Critical Start says its emergency line routes a report to a senior responder who contacts the caller within 15 minutes, followed by a Statement of Work. Kroll says its Responder MDR includes remote DFIR at no extra cost. Mandiant's Managed Defense datasheet says deeper response actions with Technology Partner products include host containment, file acquisition and closing out alerts. Providers are listed alphabetically and each figure is theirs.

A response clock is not a restoration clock. The board will ask how long recovery takes, so ask each provider what its contract says about recovery time, and write down the answer, including when the answer is that none is stated.

## What to settle before you need it

Decide in advance whether you will use the MDR provider as responder, a separate retainer firm, or an insurer's panel. If the insurer requires a panel firm, learn that before an incident, because privilege and cost depend on who is engaged and how.

Write a one-page hand-off: who calls whom, which systems stay isolated, which logs the MDR provider will export to responders, and how fast. Walk through it once a year with the people named in it. Keep the document where you can reach it when email is down.

## Aftercare

After a breach, ask for a written timeline from the MDR provider: first detection, first analyst action, first containment, escalation. Compare it with the contract. If a clock was missed, claim the credit. If the contract was silent, fix the contract. Also record what the analysts could not see: sources that were not onboarded, hosts without agents, accounts outside scope. Those gaps are the first items on the next quarter's list.

## Related pages

- [All guides](/guides/)
- [MDR vs MSSP, the full comparison](/mdr-vs-mssp/)
- [MDR glossary](/glossary/)
- [The MDR Service Matrix](/matrix/)
- [What to check in an MDR contract](/guides/contract-checks/)
- [How MDR is priced](/guides/how-mdr-is-priced/)
- [MDR for OT and industrial networks](/guides/mdr-for-ot/)
- [Measuring an MDR service after go-live](/guides/measuring-mdr/)

## Sources

- NIST SP 800-61 Rev. 3 publication page: https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 10 November 2026)
- NCSC, Incident management: https://www.ncsc.gov.uk/collection/incident-management (read 10 November 2026)
- Mandiant, Managed Defense page: https://cloud.google.com/security/products/managed-defense (read 10 November 2026)
- Arctic Wolf, incident response retainer FAQ: https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026)
- BlueVoyant, DFIR page: https://www.bluevoyant.com/solutions/digital-forensics-incident-response (read 10 November 2026)
- SentinelOne, incident readiness and response: https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026)
- Critical Start, emergency line: https://www.criticalstart.com/emergency (read 10 November 2026)
- Kroll, Responder page: https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026)
- Mandiant, Managed Defense technology datasheet: https://services.google.com/fh/files/misc/mandiant_managed_defense_technology_ds_en.pdf (read 10 November 2026)

Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/when-an-alert-becomes-a-breach/
