# MDR vs MSSP: every page as markdown A reference on managed detection and response services: sixteen services listed alphabetically, with what each says it will do on the customer's behalf and on which data, the MDR Service Matrix and the MDR Question Sheet. Every fact sourced and dated. --- # MDR vs MSSP: MDR investigates and acts on alerts, an MSSP mostly monitors and forwards them Reference, read 10 November 2026 **The short answer.** An MDR provider sells a team that investigates alerts and acts or advises on response. An MSSP typically sells monitoring, device management and alert forwarding. Both labels are loose, so the written scope decides. XDR is software rather than a service, and a SOC is a function that MDR can deliver in part or in full. The data each service watches, and the full method, are on [the matrix page](/matrix/). The [Question Sheet](/questions/) puts fifteen questions to every provider and prints the answers found. ## Four things to settle before any shortlist ### Who is watching: Who watches the environment around the clock, and who handles a major incident? The people on the night shift and the people called for a breach are often different teams with different contracts. [Read the answers found](/questions/q01/) ### What they may do: What may the provider do without asking first? Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. [Read the answers found](/questions/q02/) ### Whose agent: Is the provider's own endpoint agent required? A required agent means replacing or running next to the tools already in place. [Read the answers found](/questions/q04/) ### When it becomes a breach: Are incident response hours included, or is a retainer needed? IR billed separately changes the cost of the worst week of the year. [Read the answers found](/questions/q06/) ## What each service says it does well - **Arctic Wolf:** Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. - **BlueVoyant:** BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. - **Critical Start:** Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. - **CrowdStrike:** CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. - **Deepwatch:** Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. - **eSentire:** eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. - **Expel:** Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. - **Huntress:** Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. - **Kroll:** Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. - **Mandiant:** Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. - **Microsoft:** Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. - **Rapid7:** Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. - **Red Canary:** Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. - **SentinelOne:** SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. - **Sophos:** Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. - **Sygnia:** Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. ## What is managed detection and response? Managed detection and response (MDR) is a service: an outside team watches the customer's environment around the clock, investigates what its detections find, and acts to contain a threat, within limits the customer sets in writing. It differs from an MSSP, which mostly monitors and forwards alerts, and from XDR, which is software. - [MDR vs MSSP](/mdr-vs-mssp/) - [MDR vs XDR](/mdr-vs-xdr/) - [MDR vs SOC](/mdr-vs-soc/) - [The six kinds of managed detection service](/guides/kinds-of-managed-detection/) ## Guides and glossary - [Authority to act in an MDR service](/guides/authority-to-act/) - [The first 30 days of an MDR service](/guides/first-30-days/) - [What to check in an MDR contract](/guides/contract-checks/) - [How MDR is priced](/guides/how-mdr-is-priced/) - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/) - [Glossary, 36 terms](/glossary/) - [30 questions answered](/faq/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/ --- # MDR vs MSSP lists sixteen services and ranks none of them Method, read 10 November 2026 **In short.** MDR vs MSSP lists sixteen managed detection and response services alphabetically and gives each the same fields in the same order. Every fact comes from a source read on 10 November 2026, with its address. What a provider says about itself is labelled as the provider's. No page carries a verdict. ## Is there a list of MDR providers? Sixteen managed detection and response services are listed alphabetically on every page. Each gets the same fields in the same order, and none is ranked. ## What the site does and does not do - It lists. Services appear in alphabetical order on every page; dated records appear by date; measurements appear by the measured value. - It does not rank, rate or choose. No page names a pick, and side-by-side pages end without a verdict. - Every service gets the same fields in the same order: what it is, what it says it will do on your behalf, on which data, the answers found to the fifteen questions, what it does well and where it is limited, each with a source and read date. ## How facts are sourced and labelled - Sources: the providers' own service descriptions, datasheets and terms; analyst reports (IDC MarketScape Worldwide MDR 2024); MITRE ATT&CK Evaluations for managed services (participation only: MITRE publishes no comparative result); customers' own published statements; regulators. - A provider's claim about itself is labelled as the provider's. Analyst text published by a provider on its own site counts as the provider's. - Where nothing was found the page says "none found on 10 Nov 2026", which records what was searched, not what the provider offers. - Facts are re-read monthly; anything older than 60 days is re-read before it is used again. ## The matrix marks - **Stated:** A source (the provider's own page, or an analyst's text about the service) says plainly that the service does this. - **Stated with limits:** It is said with a condition (customer approval each time, a named tier or add-on, a scenario list, another company's product) or only as an aim, such as "aims to", or only on an archived page. - **None found:** No source on file says it, read 10 November 2026. One grading rule applies to every provider: Stated means a source (the provider's own page, or an analyst's text about the service) says plainly that the service does this; Stated with limits means it is said with a condition (approval each time, a tier or add-on, a scenario list, another company's product) or as an aim ("aims to"), or only on a page the provider has archived; None found means no source on file says it. Who said it is a separate label, shown in each cell's note and on the service page: a provider's own claim is marked as the provider's, and analyst text hosted on a provider's site is labelled as that provider's publication of it. ## Related pages - [MDR vs MSSP in short](/) - [How the MDR Service Matrix was read](/matrix/method/) - [Editorial policy](/editorial-policy/) - [About this reference](/about/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) ## Sources - MITRE ATT&CK Evaluations: https://evals.mitre.org/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/method/ --- # Sixteen MDR services, from A to Z Services, read 10 November 2026 **In short.** Sixteen managed detection and response services, from Arctic Wolf to Sygnia, each with one page in the same format: what it says it will do on your behalf, on which data, the answers found to fifteen buyer questions, what it does well and where it is limited. - [Arctic Wolf](/services/arctic-wolf/): Arctic Wolf Aurora Managed Detection and Response - [BlueVoyant](/services/bluevoyant/): BlueVoyant Managed Detection & Response (MDR) - [Critical Start](/services/critical-start/): Critical Start Managed Detection & Response (MDR) - [CrowdStrike](/services/crowdstrike/): Falcon Complete (Falcon Complete MDR, described on the page as Agentic MDR) - [Deepwatch](/services/deepwatch/): Deepwatch Managed Detection and Response (Guardian MDR Platform) - [eSentire](/services/esentire/): eSentire Managed Detection and Response (Atlas MDR) - [Expel](/services/expel/): Expel Managed Detection and Response (MDR) - [Huntress](/services/huntress/): Huntress Managed EDR (within the Huntress Agentic Security Platform, with Managed ITDR and Managed SIEM) - [Kroll](/services/kroll/): Kroll Responder MDR - [Mandiant](/services/mandiant/): Mandiant Managed Defense (also shown on the incident response page as Mandiant Threat Defense) - [Microsoft](/services/microsoft/): Microsoft Defender Experts MDR (formerly Defender Experts for XDR), with Defender Experts Hunting - [Rapid7](/services/rapid7/): Rapid7 MDR (Managed Detection and Response; "Preemptive MDR") - [Red Canary](/services/red-canary/): Red Canary Managed Detection and Response (now Zscaler Managed Detection & Response) - [SentinelOne](/services/sentinelone/): Wayfinder Managed Detection & Response (MDR), within Wayfinder Threat Detection and Response (TDR), with Wayfinder Threat Hunting and Wayfinder Incident Readiness & Response (IRR) - [Sophos](/services/sophos/): Sophos Managed Detection and Response (MDR) - [Sygnia](/services/sygnia/): Sygnia Managed Detection and Response (MDR), powered by Velocity TDIR ## Related pages - [Home: MDR vs MSSP in short](/) - [The MDR Service Matrix](/matrix/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [How this site lists services](/method/) - [Glossary](/glossary/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/ --- # Arctic Wolf: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Arctic Wolf says its Aurora MDR contains threats with humans in the loop, and its timeline example records endpoint containment and password resets under predefined customer instructions. IDC says it aims for visibility across endpoint, network, cloud and identity. None found on 10 Nov 2026: IP or hash blocking, process kill, email or OT coverage. ## What does Arctic Wolf do on the customer's behalf? On 10 November 2026, Arctic Wolf's public pages show, across six actions, 0 stated, 3 with limits, 3 none found. No action is stated without conditions. | Action | What was found | | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | ## Arctic Wolf at a glance - **Service:** Arctic Wolf Aurora Managed Detection and Response - **Company status:** Arctic Wolf is listed under its own name on arcticwolf.com (Arctic Wolf Networks, Eden Prairie, Minnesota); no acquisition or rename was found on the pages read. - **Does well:** Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. - **Limited:** Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. ## The data Arctic Wolf watches | Data | What was found | | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | | Network | Stated with limits IDC says it aims for visibility across network. | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | | [What may the provider do without asking first?](/questions/q02/) | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | | [Which data sources does the service monitor?](/questions/q03/) | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | | [What response-time commitments are published?](/questions/q07/) | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | | [Is the pricing model published?](/questions/q08/) | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Stated strength: The firm says it wants to be the first call in a breach and that its full-service IR team can stop an attack and restore pre-incident operations. (the provider's claim) - Who does the work: The MDR service delivery list on the MDR page includes Incident Response items (business restoration, severe incident remediation, digital forensics) within the Aurora Agentic SOC delivery model. (the provider's claim) - Who does the work: IDC says the Arctic Wolf Concierge Security Team learns each customer's business context to tune detection and response guidelines for that customer. - Tools and data it works on: The MDR page says the platform has an open XDR architecture and supports over 200 integrations. (the provider's claim) - Tools and data it works on: The technology partners page says the service is compatible with other security tools and does not require ripping and replacing products. (the provider's claim) - What it may do on your behalf: The retainer page FAQ says the MDR service performs triage, containment, analytics, investigations and guided remediation. (the provider's claim) - What it may do on your behalf: The MDR page says threats are contained through Agentic SOC response with humans in the loop. (the provider's claim) - Coverage: The MDR page says it provides visibility across all attack surfaces with integrated telemetry and 24x7 detection. (the provider's claim) - Coverage: IDC says Arctic Wolf aims to gain broad visibility across endpoint, network, cloud, identity and the human element. - When an alert becomes a breach: The retainer page FAQ distinguishes MDR from IR, saying IR works inside the client's environment, which indicates IR is a separate service from MDR. (the provider's claim) - When an alert becomes a breach: The MDR page says the firm's Security Operations Warranty offers up to 3 million dollars in financial assistance for incidents, tied to a Total Security Operations Bundle with Aurora Managed Endpoint Defense on a three-year term (MDR page text). (the provider's claim) - Published scope, commitments and pricing: The firm's home page says pricing is flat and predictable with no additional token costs; no price figures appear. (the provider's claim) - Published scope, commitments and pricing: Its MDR FAQ states a pricing model: coverage is based on the number of users, servers and internet egress points, not event or log volume; no prices are printed. (the provider's claim) - Breadth: The home page says the firm is trusted by over 10,000 customers worldwide. (the provider's claim) ## The provider's own pages - [Arctic Wolf service page 1 (arcticwolf.com)](https://arcticwolf.com/solutions/managed-detection-and-response/) - [Arctic Wolf service page 2 (arcticwolf.com)](https://arcticwolf.com/partners/technology-integrations/) - [Arctic Wolf service page 3 (arcticwolf.com)](https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/) ## Side by side - [Arctic Wolf and BlueVoyant](/side-by-side/arctic-wolf-and-bluevoyant/) - [Arctic Wolf and Critical Start](/side-by-side/arctic-wolf-and-critical-start/) - [Arctic Wolf and CrowdStrike](/side-by-side/arctic-wolf-and-crowdstrike/) - [Arctic Wolf and Deepwatch](/side-by-side/arctic-wolf-and-deepwatch/) - [Arctic Wolf and eSentire](/side-by-side/arctic-wolf-and-esentire/) - [Arctic Wolf and Expel](/side-by-side/arctic-wolf-and-expel/) - [Arctic Wolf and Huntress](/side-by-side/arctic-wolf-and-huntress/) - [Arctic Wolf and Kroll](/side-by-side/arctic-wolf-and-kroll/) - [Arctic Wolf and Mandiant](/side-by-side/arctic-wolf-and-mandiant/) - [Arctic Wolf and Microsoft](/side-by-side/arctic-wolf-and-microsoft/) - [Arctic Wolf and Rapid7](/side-by-side/arctic-wolf-and-rapid7/) - [Arctic Wolf and Red Canary](/side-by-side/arctic-wolf-and-red-canary/) - [Arctic Wolf and SentinelOne](/side-by-side/arctic-wolf-and-sentinelone/) - [Arctic Wolf and Sophos](/side-by-side/arctic-wolf-and-sophos/) - [Arctic Wolf and Sygnia](/side-by-side/arctic-wolf-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Arctic Wolf, "Technology integrations" page (the firm's own page): https://arcticwolf.com/partners/technology-integrations/ (read 10 November 2026) - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/company/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response retainer" page (the firm's own page): https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Arctic Wolf, "Incident response" page (the firm's own page): https://arcticwolf.com/solutions/incident-response/ (read 10 November 2026) - Arctic Wolf, home page (the firm's own page): https://arcticwolf.com/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/arctic-wolf/ --- # BlueVoyant: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** BlueVoyant says its MDR protects network, cloud, containers and endpoints with 24x7 in-regional SOC monitoring across Europe and the US, and that its Microsoft module includes unlimited remote incident response lifecycle support. It states automated blocking and containment on endpoints. None found on 10 Nov 2026: SLA minutes, pricing model, OT coverage. ## What does BlueVoyant do on the customer's behalf? On 10 November 2026, BlueVoyant's public pages show, across six actions, 2 stated, 0 with limits, 4 none found. Stated without conditions: isolate a host; block an ip, domain, hash or email. | Action | What was found | | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | ## BlueVoyant at a glance - **Service:** BlueVoyant Managed Detection & Response (MDR) - **Company status:** BlueVoyant still trades under this name (archived 2026 pages show copyright 2026 BlueVoyant and a New York address); its press page features a new CEO, John Hernandez. No rename or acquisition found. The live site is behind a bot challenge so pages were read from web.archive.org. - **Does well:** BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. - **Limited:** BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. ## The data BlueVoyant watches | Data | What was found | | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | | Network | Stated BlueVoyant says its MDR protects network. | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | | [What may the provider do without asking first?](/questions/q02/) | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | [Which data sources does the service monitor?](/questions/q03/) | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | | [Is the provider's own endpoint agent required?](/questions/q04/) | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | | [Is threat hunting included, and what output is published?](/questions/q05/) | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | [What response-time commitments are published?](/questions/q07/) | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | | [Is the pricing model published?](/questions/q08/) | None found on 10 Nov 2026 | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The firm says its digital forensics and incident response page lists forensics examiners with FBI Cyber, Fortune 100 and legal backgrounds. (the provider's claim) - Who does the work: The firm says it has physical forensic laboratories in EMEA and the Americas. (the provider's claim) - Tools and data it works on: The firm says its MDR is meant to strengthen use of existing EDR, SIEM and cloud security tools. (the provider's claim) - Tools and data it works on: The firm's MDR for Microsoft module is built around Microsoft Security technology. (the provider's claim) - Coverage: The firm says its MDR protects network, cloud, containers and endpoints, and runs 24x7 in-regional SOC monitoring across Europe and the US. (the provider's claim) - Coverage: The firm lists Agentic Identity Services among its MDR for Microsoft solutions menu. (the provider's claim) - When an alert becomes a breach: The firm says its DFIR retainer carries pre-arranged rapid response SLAs, sold on a separate DFIR page. (the provider's claim) - When an alert becomes a breach: The firm says 99% of its DFIR retainer clients get first-time threat actor eviction (its own statistic). (the provider's claim) - Published scope, commitments and pricing: The firm says its DFIR retainer has pre-arranged response SLAs. (the provider's claim) - Published scope, commitments and pricing: MITRE Engenuity lists BlueVoyant among the organizations that took part in ATT&CK Evaluations: Managed Services, OilRig (2022); MITRE says the round was not a product evaluation and has no named, and its post does not say which of the company's services was evaluated. - Breadth: The firm says it has more than 1,000 customers in 45 countries. (the provider's claim) - Breadth: The firm says it has 1,200+ successful Microsoft Sentinel deployments. (the provider's claim) - Stated strength: The firm says it has been recognized by Microsoft ten times, including Worldwide Security Partner of the Year. (the provider's claim) - Company status: The firm's press releases page features John Hernandez joining BlueVoyant as CEO. (the provider's claim) ## The provider's own pages - [BlueVoyant service page 1 (bluevoyant.com)](https://www.bluevoyant.com/solutions/digital-forensics-incident-response) - [BlueVoyant service page 2 (bluevoyant.com)](https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft) - [BlueVoyant service page 3 (bluevoyant.com)](https://www.bluevoyant.com/) ## Side by side - [Arctic Wolf and BlueVoyant](/side-by-side/arctic-wolf-and-bluevoyant/) - [BlueVoyant and Critical Start](/side-by-side/bluevoyant-and-critical-start/) - [BlueVoyant and CrowdStrike](/side-by-side/bluevoyant-and-crowdstrike/) - [BlueVoyant and Deepwatch](/side-by-side/bluevoyant-and-deepwatch/) - [BlueVoyant and eSentire](/side-by-side/bluevoyant-and-esentire/) - [BlueVoyant and Expel](/side-by-side/bluevoyant-and-expel/) - [BlueVoyant and Huntress](/side-by-side/bluevoyant-and-huntress/) - [BlueVoyant and Kroll](/side-by-side/bluevoyant-and-kroll/) - [BlueVoyant and Mandiant](/side-by-side/bluevoyant-and-mandiant/) - [BlueVoyant and Microsoft](/side-by-side/bluevoyant-and-microsoft/) - [BlueVoyant and Rapid7](/side-by-side/bluevoyant-and-rapid7/) - [BlueVoyant and Red Canary](/side-by-side/bluevoyant-and-red-canary/) - [BlueVoyant and SentinelOne](/side-by-side/bluevoyant-and-sentinelone/) - [BlueVoyant and Sophos](/side-by-side/bluevoyant-and-sophos/) - [BlueVoyant and Sygnia](/side-by-side/bluevoyant-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - BlueVoyant, "Digital forensics incident response" page (the firm's own page): https://www.bluevoyant.com/solutions/digital-forensics-incident-response (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - BlueVoyant, "Managed detection and response" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/bluevoyant/ --- # Critical Start: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Critical Start lists response actions by domain: isolate host and block hash on endpoints, reset password and disable account on identity, block IP on network, quarantine message on email. Customers approve or reject containment. It says cloud response is advisory and detection only, and OT is read-only monitoring. Prices are not published. ## What does Critical Start do on the customer's behalf? On 10 November 2026, Critical Start's public pages show, across six actions, 3 stated, 2 with limits, 1 none found. Stated without conditions: isolate a host; disable or reset an account; block an ip, domain, hash or email. | Action | What was found | | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | ## Critical Start at a glance - **Service:** Critical Start Managed Detection & Response (MDR) - **Company status:** Critical Start still trades under this name; its July 2026 press release is datelined Plano, Texas and quotes a Vista Equity Partners managing director, and its own page describes it as an independent MDR specialist. No rename or acquisition found. - **Does well:** Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. - **Limited:** Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. ## The data Critical Start watches | Data | What was found | | --- | --- | | Endpoint | Stated Lists endpoint response actions. | | Identity | Stated Lists identity response actions. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | | Network | Stated Lists network response actions such as block IP. | | Email | Stated Lists email actions such as quarantine message. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | | [What may the provider do without asking first?](/questions/q02/) | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | [Which data sources does the service monitor?](/questions/q03/) | Critical Start says CORR supports 100+ integrations across seven security domains. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | [What response-time commitments are published?](/questions/q07/) | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | [Is the pricing model published?](/questions/q08/) | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | | [Is OT covered?](/questions/q09/) | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | | [What cloud and identity coverage is stated?](/questions/q10/) | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The firm says its emergency page connects an active incident to its own cyber incident response team, available 24/7. (the provider's claim) - Who does the work: The firm says that because of the MDR relationship its incident response team (CIRT) already has context on the customer environment. (the provider's claim) - Tools and data it works on: The firm says it has 100+ integrations, 30+ of them bidirectional, and requires no proprietary agents. (the provider's claim) - Tools and data it works on: The firm says its CORR platform connects to the customer's existing stack by API with no agents to deploy. (the provider's claim) - What it may do on your behalf: The firm's MDR page describes its analyst isolating a host in CrowdStrike and disabling an account in Entra ID, with notice ahead of action available if the customer prefers. (the provider's claim) - What it may do on your behalf: The firm says that on a confirmed threat its analysts run the customer-approved playbook, which may include host isolation, process termination, or account suspension in the customer's tools. (the provider's claim) - Hunting: The firm says threat hunting engagements are one of the services customers can buy with the service credits included in every managed service contract; its page does not describe hunting as a standing part of MDR. (the provider's claim) - Hunting: The firm's Cyber Research Unit published an H1 2026 threat intelligence report built from alert investigations (a research report, not described as hunt findings). (the provider's claim) - Coverage: The firm says its CORR platform supports 100+ integrations across seven security domains, with 30+ advanced integrations that can contain threats directly in customer tools. (the provider's claim) - Coverage: The firm lists cloud response as advisory and detection only, and OT/ICS as escalation, advisory and read-only monitoring. (the provider's claim) - When an alert becomes a breach: The firm's services page shows Incident Response as an available add-on to every MDR tier. (the provider's claim) - When an alert becomes a breach: The firm says unused IR retainer hours convert to service credits at 3 hours per credit. (the provider's claim) - Published scope, commitments and pricing: The firm's SLA page publishes a 60-minute mean time to respond in all three tiers and a 60-minute per-alert time to respond for critical and high alerts in Signature. (the provider's claim) - Published scope, commitments and pricing: The firm publishes service credit remedies for missed SLAs: 10% per-alert, 10% monthly MTTR, 50% for uptime below 98%. (the provider's claim) ## The provider's own pages - [Critical Start service page 1 (criticalstart.com)](https://www.criticalstart.com/emergency) - [Critical Start service page 2 (criticalstart.com)](https://www.criticalstart.com/service-credits) - [Critical Start service page 3 (criticalstart.com)](https://www.criticalstart.com/mdr) ## Side by side - [Arctic Wolf and Critical Start](/side-by-side/arctic-wolf-and-critical-start/) - [BlueVoyant and Critical Start](/side-by-side/bluevoyant-and-critical-start/) - [Critical Start and CrowdStrike](/side-by-side/critical-start-and-crowdstrike/) - [Critical Start and Deepwatch](/side-by-side/critical-start-and-deepwatch/) - [Critical Start and eSentire](/side-by-side/critical-start-and-esentire/) - [Critical Start and Expel](/side-by-side/critical-start-and-expel/) - [Critical Start and Huntress](/side-by-side/critical-start-and-huntress/) - [Critical Start and Kroll](/side-by-side/critical-start-and-kroll/) - [Critical Start and Mandiant](/side-by-side/critical-start-and-mandiant/) - [Critical Start and Microsoft](/side-by-side/critical-start-and-microsoft/) - [Critical Start and Rapid7](/side-by-side/critical-start-and-rapid7/) - [Critical Start and Red Canary](/side-by-side/critical-start-and-red-canary/) - [Critical Start and SentinelOne](/side-by-side/critical-start-and-sentinelone/) - [Critical Start and Sophos](/side-by-side/critical-start-and-sophos/) - [Critical Start and Sygnia](/side-by-side/critical-start-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Critical Start, "SLA commitment" page (the firm's own page): https://www.criticalstart.com/sla-commitment (read 10 November 2026) - Critical Start, "Why critical start" page (the firm's own page): https://www.criticalstart.com/why-critical-start (read 10 November 2026) - Critical Start, "Platform" page (the firm's own page): https://www.criticalstart.com/platform (read 10 November 2026) - Critical Start, "Emergency" page (the firm's own page): https://www.criticalstart.com/emergency (read 10 November 2026) - Critical Start, "Service credits" page (the firm's own page): https://www.criticalstart.com/service-credits (read 10 November 2026) - Critical Start, "Rapid detection and containment of a qilin ransomware attack" page (the firm's own page): https://www.criticalstart.com/resources/rapid-detection-and-containment-of-a-qilin-ransomware-attack (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/critical-start/ --- # CrowdStrike: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** CrowdStrike says Falcon Complete experts own every outcome, with playbooks executing containment and analysts delivering remediation on the customer's behalf. It states a median time-to-contain of 1 minute on an endpoint and warranty coverage up to $2 million. Telemetry covers endpoint, identity, cloud, SaaS and third-party data. Pricing is Contact sales. Each fact below carries its source and read date. ## What does CrowdStrike do on the customer's behalf? On 10 November 2026, CrowdStrike's public pages show, across six actions, 1 stated, 1 with limits, 4 none found. Stated without conditions: isolate a host. | Action | What was found | | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | ## CrowdStrike at a glance - **Service:** Falcon Complete (Falcon Complete MDR, described on the page as Agentic MDR) - **Company status:** CrowdStrike's own About Us page describes the company under the CrowdStrike name and no rename or acquisition appears on the pages read. Its services pages list Incident Response, Services Retainer and Falcon Complete. - **Does well:** CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. - **Limited:** CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. ## The data CrowdStrike watches | Data | What was found | | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | | Network | None found on 10 November 2026 | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | [What may the provider do without asking first?](/questions/q02/) | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | [Which data sources does the service monitor?](/questions/q03/) | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | [Is the provider's own endpoint agent required?](/questions/q04/) | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | [Is threat hunting included, and what output is published?](/questions/q05/) | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | [What response-time commitments are published?](/questions/q07/) | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | [Is the pricing model published?](/questions/q08/) | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The Falcon Complete page says experts own every outcome, validating decisions and remediation in real time. (the provider's claim) - Who does the work: The firm quotes Forrester as saying the core of CrowdStrike's MDR service is deep expertise in threat intelligence and incident response. (the provider's claim) - Tools and data it works on: The Falcon Complete page says analysts correlate Falcon platform telemetry across endpoints, identities, AI agents, cloud, SaaS and third-party data. (the provider's claim) - Tools and data it works on: IDC says CrowdStrike's MDR offering is Falcon Complete Managed XDR with endpoint at the core, and that practitioners keep tight control over the Falcon agent in customer environments. - What it may do on your behalf: The Falcon Complete page says response playbooks execute containment actions. (the provider's claim) - What it may do on your behalf: The page says analysts deliver full-cycle remediation on the customer's behalf. (the provider's claim) - Coverage: The page says Falcon Complete combines Falcon Shield visibility with expert response across the SaaS stack. (the provider's claim) - Coverage: IDC says CrowdStrike adds managed cloud workload protection and a managed identity threat protection service (Falcon Complete Identity Threat Protection) to its MDR offering. - Hunting: CrowdStrike publishes a 2026 Threat Hunting Report (the page does not state that hunting is part of Falcon Complete). (the provider's claim) - Hunting: The firm quotes Forrester as saying organizations wanting advanced threat hunting and response capabilities should consider CrowdStrike, and says it received the highest possible results in threat hunting in the Forrester MDR Europe Wave Q4 2023. (the provider's claim) - Published scope, commitments and pricing: The page states a median time-to-contain of 1 minute for Falcon Complete. (the provider's claim) - Published scope, commitments and pricing: The page footnote defines MTTC as the time from initial detection to successful containment on an endpoint and says results may vary. (the provider's claim) - When an alert becomes a breach: The Falcon Complete page says the service is backed by warranty coverage of up to $2 million. (the provider's claim) - When an alert becomes a breach: IDC says public sector organizations needing a FedRAMP-certified SOC with strong threat intelligence and incident response capabilities should consider CrowdStrike. ## The provider's own pages - [CrowdStrike service page 1 (crowdstrike.com)](https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/) - [CrowdStrike service page 2 (crowdstrike.com)](https://www.crowdstrike.com/en-us/blog/crowdstrike-leader-with-stellar-mdr-in-forrester-wave-mdr-services/) ## Side by side - [Arctic Wolf and CrowdStrike](/side-by-side/arctic-wolf-and-crowdstrike/) - [BlueVoyant and CrowdStrike](/side-by-side/bluevoyant-and-crowdstrike/) - [Critical Start and CrowdStrike](/side-by-side/critical-start-and-crowdstrike/) - [CrowdStrike and Deepwatch](/side-by-side/crowdstrike-and-deepwatch/) - [CrowdStrike and eSentire](/side-by-side/crowdstrike-and-esentire/) - [CrowdStrike and Expel](/side-by-side/crowdstrike-and-expel/) - [CrowdStrike and Huntress](/side-by-side/crowdstrike-and-huntress/) - [CrowdStrike and Kroll](/side-by-side/crowdstrike-and-kroll/) - [CrowdStrike and Mandiant](/side-by-side/crowdstrike-and-mandiant/) - [CrowdStrike and Microsoft](/side-by-side/crowdstrike-and-microsoft/) - [CrowdStrike and Rapid7](/side-by-side/crowdstrike-and-rapid7/) - [CrowdStrike and Red Canary](/side-by-side/crowdstrike-and-red-canary/) - [CrowdStrike and SentinelOne](/side-by-side/crowdstrike-and-sentinelone/) - [CrowdStrike and Sophos](/side-by-side/crowdstrike-and-sophos/) - [CrowdStrike and Sygnia](/side-by-side/crowdstrike-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - CrowdStrike, "Pricing" page (the firm's own page): https://www.crowdstrike.com/en-us/pricing/ (read 10 November 2026) - CrowdStrike, "Threat hunting report" page (the firm's own page): https://www.crowdstrike.com/en-us/resources/reports/threat-hunting-report/ (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/crowdstrike/ --- # Deepwatch: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Deepwatch says its Active Response is opt-in: the customer sets, through a Response Intent Matrix, which detections are eligible and whether actions run automatically, with analyst approval, or monitor-only. Actions include host isolation, process termination, session revocation and password reset. It works with existing SIEM, EDR, cloud and identity tools. IR hours were none found on 10 Nov 2026. ## What does Deepwatch do on the customer's behalf? On 10 November 2026, Deepwatch's public pages show, across six actions, 4 stated, 0 with limits, 2 none found. Stated without conditions: isolate a host; disable or reset an account; kill a process or remove a file; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | ## Deepwatch at a glance - **Service:** Deepwatch Managed Detection and Response (Guardian MDR Platform) - **Company status:** Deepwatch still trades under this name; its press release list shows a May 2026 CEO appointment (Brian Dhatt) and a February 2025 acquisition by Deepwatch of Dassana. No rename or acquisition of Deepwatch itself found on its pages. - **Does well:** Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. - **Limited:** Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. ## The data Deepwatch watches | Data | What was found | | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | | Identity | Stated Platform page shows identity. | | Cloud | Stated Platform page shows cloud. | | Network | Stated Platform page shows network. | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | [What may the provider do without asking first?](/questions/q02/) | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | [Which data sources does the service monitor?](/questions/q03/) | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | [What response-time commitments are published?](/questions/q07/) | None found on 10 Nov 2026 | | [Is the pricing model published?](/questions/q08/) | None found on 10 Nov 2026 | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The firm says its Adversary Tactics and Intelligence (ATI) group is made up of intelligence and DFIR professionals. (the provider's claim) - Who does the work: The firm's ATI page lists incident management and forensics (24/7/365 response, forensic collection and analysis, an emergency operations center, containment and remediation strategies) under adversary response. (the provider's claim) - Tools and data it works on: The firm calls itself an agnostic security provider that orchestrates tools from multiple vendors. (the provider's claim) - Tools and data it works on: The firm says its platform uses a Bring Your Own Tech approach that integrates with existing infrastructure. (the provider's claim) - What it may do on your behalf: The firm lists identity response actions for Active Response as session revocation, password reset and account control actions. (the provider's claim) - What it may do on your behalf: The firm lists endpoint response actions for Active Response as process termination and host isolation. (the provider's claim) - Hunting: The firm's MDR datasheet page says the service includes proactive threat hunting. (the provider's claim) - Hunting: The firm says it publishes Deepwatch Labs threat reports weekly that include targeted and general threat hunts. (the provider's claim) - Coverage: The firm's platform page shows the existing environment it works with as SIEM, endpoint, cloud, identity and network. (the provider's claim) - Coverage: The firm says Active Response covers identities and endpoints and that other response domains will be added over time. (the provider's claim) - When an alert becomes a breach: The firm's ATI page lists 24/7/365 response and an emergency operations center, but the pages read do not state whether IR hours or a retainer come with MDR. (the provider's claim) - Published scope, commitments and pricing: The firm says customers see what it sees, with no black box of anonymous alerts or events. (the provider's claim) - Published scope, commitments and pricing: The firm says its Security Center gives a consolidated view of alert volume, incidents and actions. (the provider's claim) - Breadth: The firm lists headquarters in Palo Alto, CA, an office in Tampa, FL and one in Bengaluru, India. (the provider's claim) ## The provider's own pages - [Deepwatch service page 1 (deepwatch.com)](https://www.deepwatch.com/ati/) - [Deepwatch service page 2 (deepwatch.com)](https://www.deepwatch.com/deepwatch-experts/) - [Deepwatch service page 3 (deepwatch.com)](https://www.deepwatch.com/use-existing-tools/) ## Side by side - [Arctic Wolf and Deepwatch](/side-by-side/arctic-wolf-and-deepwatch/) - [BlueVoyant and Deepwatch](/side-by-side/bluevoyant-and-deepwatch/) - [Critical Start and Deepwatch](/side-by-side/critical-start-and-deepwatch/) - [CrowdStrike and Deepwatch](/side-by-side/crowdstrike-and-deepwatch/) - [Deepwatch and eSentire](/side-by-side/deepwatch-and-esentire/) - [Deepwatch and Expel](/side-by-side/deepwatch-and-expel/) - [Deepwatch and Huntress](/side-by-side/deepwatch-and-huntress/) - [Deepwatch and Kroll](/side-by-side/deepwatch-and-kroll/) - [Deepwatch and Mandiant](/side-by-side/deepwatch-and-mandiant/) - [Deepwatch and Microsoft](/side-by-side/deepwatch-and-microsoft/) - [Deepwatch and Rapid7](/side-by-side/deepwatch-and-rapid7/) - [Deepwatch and Red Canary](/side-by-side/deepwatch-and-red-canary/) - [Deepwatch and SentinelOne](/side-by-side/deepwatch-and-sentinelone/) - [Deepwatch and Sophos](/side-by-side/deepwatch-and-sophos/) - [Deepwatch and Sygnia](/side-by-side/deepwatch-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Deepwatch, "Ati" page (the firm's own page): https://www.deepwatch.com/ati/ (read 10 November 2026) - Deepwatch, "Deepwatch platform" page (the firm's own page): https://www.deepwatch.com/deepwatch-platform/ (read 10 November 2026) - Deepwatch, "Leverage existing tools" page (the firm's own page): https://www.deepwatch.com/use-existing-tools/ (read 10 November 2026) - Deepwatch, "Technology partners" page (the firm's own page): https://www.deepwatch.com/technology-partners/ (read 10 November 2026) - Deepwatch, home page (the firm's own page): https://www.deepwatch.com/ (read 10 November 2026) - Deepwatch, "Deepwatch experts" page (the firm's own page): https://www.deepwatch.com/deepwatch-experts/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/deepwatch/ --- # eSentire: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** eSentire says its standard MDR response includes isolating attackers, suspending accounts, quarantining files, terminating processes and disrupting network connections, with policy-bounded, reversible actions. Atlas ingests endpoint, network, cloud and identity signals; IDC places identity and cloud in a higher tier. It states IT and OT coverage in manufacturing. Prices sit on an online shop. ## What does eSentire do on the customer's behalf? On 10 November 2026, eSentire's public pages show, across six actions, 6 stated, 0 with limits, 0 none found. Stated without conditions: isolate a host; disable or reset an account; block an ip, domain, hash or email; kill a process or remove a file; act in a cloud or saas console; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## eSentire at a glance - **Service:** eSentire Managed Detection and Response (Atlas MDR) - **Company status:** eSentire still operates under this name; its about page says it was founded in 2001, and no acquirer is named on the pages read. The home page announces eSentire acquiring an AI security startup. - **Does well:** eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. - **Limited:** eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. ## The data eSentire watches | Data | What was found | | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | Stated Atlas ingests network signals. | | Email | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | [What may the provider do without asking first?](/questions/q02/) | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | [Which data sources does the service monitor?](/questions/q03/) | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | [Is the provider's own endpoint agent required?](/questions/q04/) | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | [Is threat hunting included, and what output is published?](/questions/q05/) | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | [What response-time commitments are published?](/questions/q07/) | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | [Is the pricing model published?](/questions/q08/) | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | [Is OT covered?](/questions/q09/) | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | [What cloud and identity coverage is stated?](/questions/q10/) | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The firm says its MDR response is staffed by a 24/7 SOC and that root cause analysis is delivered under both MDR and DFIR in its response comparison table. (the provider's claim) - Who does the work: The firm says its DFIR incident responders and its MDR share the eSentire Agent, combining MDR and DFIR capabilities in one tool. (the provider's claim) - Tools and data it works on: The firm says its Atlas platform connects to any signal across any vendor stack. (the provider's claim) - Tools and data it works on: The firm says its MDR does not require replacing an existing stack. (the provider's claim) - What it may do on your behalf: The firm says its standard MDR response includes isolating attackers and suspending accounts and user access. (the provider's claim) - What it may do on your behalf: The firm lists suspending accounts and user access to stop compromised users as a standard MDR response procedure. (the provider's claim) - Hunting: The firm says its MDR includes 24/7 Elite Threat Hunters and unlimited threat hunting in its SOC-as-a-service. (the provider's claim) - Hunting: The firm says its Threat Response Unit works with its threat hunters and SOC analysts to hunt threats, and that it does original threat research. (the provider's claim) - Coverage: The firm says Atlas ingests signals from endpoint, network, log, cloud, identity, AI sessions and vulnerability data. (the provider's claim) - Coverage: The firm says it supports correcting critical misconfigurations across multi-cloud environments and purging emails organization-wide. (the provider's claim) - When an alert becomes a breach: The firm says its Incident Response Retainer provides unlimited incident response with a threat suppression guarantee, delivered remotely. (the provider's claim) - When an alert becomes a breach: The firm says it will respond and engage within one hour under its incident response retainer. (the provider's claim) - Published scope, commitments and pricing: The firm publishes three MDR packages (Professional, Enhanced, Elite) with prices on an online shop, not on the page read. (the provider's claim) - Published scope, commitments and pricing: The firm says its MDR packages are priced by endpoints, third-party technology, service engagement and add-ons. (the provider's claim) ## The provider's own pages - [eSentire service page 1 (esentire.com)](https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation) - [eSentire service page 2 (esentire.com)](https://www.esentire.com/how-we-do-it/signals/mdr-for-endpoint/mdr-for-endpoint-esentire-agent) - [eSentire service page 3 (esentire.com)](https://www.esentire.com/) ## Side by side - [Arctic Wolf and eSentire](/side-by-side/arctic-wolf-and-esentire/) - [BlueVoyant and eSentire](/side-by-side/bluevoyant-and-esentire/) - [Critical Start and eSentire](/side-by-side/critical-start-and-esentire/) - [CrowdStrike and eSentire](/side-by-side/crowdstrike-and-esentire/) - [Deepwatch and eSentire](/side-by-side/deepwatch-and-esentire/) - [eSentire and Expel](/side-by-side/esentire-and-expel/) - [eSentire and Huntress](/side-by-side/esentire-and-huntress/) - [eSentire and Kroll](/side-by-side/esentire-and-kroll/) - [eSentire and Mandiant](/side-by-side/esentire-and-mandiant/) - [eSentire and Microsoft](/side-by-side/esentire-and-microsoft/) - [eSentire and Rapid7](/side-by-side/esentire-and-rapid7/) - [eSentire and Red Canary](/side-by-side/esentire-and-red-canary/) - [eSentire and SentinelOne](/side-by-side/esentire-and-sentinelone/) - [eSentire and Sophos](/side-by-side/esentire-and-sophos/) - [eSentire and Sygnia](/side-by-side/esentire-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - eSentire, "Pricing packaging" page (the firm's own page): https://www.esentire.com/pricing-packaging (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - eSentire, "Incident response retainer" page (the firm's own page): https://www.esentire.com/what-we-do/digital-forensics-and-incident-response/incident-response-retainer (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - eSentire, "Manufacturing cybersecurity" page (the firm's own page): https://www.esentire.com/how-we-do-it/industries/manufacturing-cybersecurity (read 10 November 2026) - eSentire, "24 7 security operations for manufacturing" page (the firm's own page): https://www.esentire.com/24-7-security-operations-for-manufacturing (read 10 November 2026) - eSentire, home page (the firm's own page): https://www.esentire.com/ (read 10 November 2026) - eSentire, "MDR for endpoint esentire agent" page (the firm's own page): https://www.esentire.com/how-we-do-it/signals/mdr-for-endpoint/mdr-for-endpoint-esentire-agent (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/esentire/ --- # Expel: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Expel says its analysts take auto remediation actions on the customer's behalf once its SOC validates a threat, and customers choose what, how and when it acts. It states coverage of endpoints, identity, cloud, SaaS and networks from 160+ integrations with no agents to deploy. Included IR hours and a retainer were none found on 10 Nov 2026. ## What does Expel do on the customer's behalf? On 10 November 2026, Expel's public pages show, across six actions, 1 stated, 0 with limits, 5 none found. Stated without conditions: acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | None found on 10 November 2026 | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Expel at a glance - **Service:** Expel Managed Detection and Response (MDR) - **Company status:** Expel still operates under this name; its own about and home pages present it as an independent company with no acquirer named on the pages read. - **Does well:** Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. - **Limited:** Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. ## The data Expel watches | Data | What was found | | --- | --- | | Endpoint | Stated Packages page lists endpoints. | | Identity | Stated Packages page lists identity. | | Cloud | Stated Packages page lists cloud workloads and control planes. | | Network | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | [What may the provider do without asking first?](/questions/q02/) | Expel says customers can let it press the respond button or choose what, how and when it acts. | | [Which data sources does the service monitor?](/questions/q03/) | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Expel says no agents need to be deployed and it plugs into the existing stack. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | [What response-time commitments are published?](/questions/q07/) | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | [Is the pricing model published?](/questions/q08/) | Expel says pricing is by request, with Starter, Select and Premium packages. | | [Is OT covered?](/questions/q09/) | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | [What cloud and identity coverage is stated?](/questions/q10/) | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Expel says customers see every alert, investigation and action in its Workbench platform. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | Expel says customers see every alert, investigation and action in Workbench. | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The firm says its Global Response Team leads critical incident investigations such as active attackers and ransomware. (the provider's claim) - Who does the work: The firm lists SOC Threat Analysts, Threat Hunters, Detection Engineers and the Global Response Team as parts of one 24x7 security operations team. (the provider's claim) - Tools and data it works on: The firm says no agents need to be deployed and that Expel plugs into the customer's existing security stack. (the provider's claim) - Tools and data it works on: The firm says it pulls telemetry from more than 160 integrated tools. (the provider's claim) - What it may do on your behalf: The firm says its analysts take auto remediation actions on the customer's behalf once its SOC validates a threat. (the provider's claim) - What it may do on your behalf: The firm says customers can let it press the respond button or choose what, how and when it acts. (the provider's claim) - Hunting: The firm sells a Threat Hunting service with monthly hunts on customers' existing tools, paired with MDR. (the provider's claim) - Hunting: The firm says all hunt findings and gaps are shared in a monthly report. (the provider's claim) - Coverage: The firm says it unifies signals across ten attack surfaces. (the provider's claim) - Coverage: The firm's MDR packages page says coverage spans cloud workloads, control planes, identity, SaaS, endpoints and networks. (the provider's claim) - When an alert becomes a breach: The firm lists a Global Response Team within the MDR service; the pages read do not state included IR hours or a retainer. (the provider's claim) - When an alert becomes a breach: The firm runs an Incident Response Partner Program, in which IR firms use Expel's platform to support their customers after a breach. (the provider's claim) - Published scope, commitments and pricing: The firm says pricing is by request, with Starter, Select and Premium packages. (the provider's claim) - Published scope, commitments and pricing: The firm publishes response metrics of 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. (the provider's claim) ## The provider's own pages - [Expel service page 1 (expel.com)](https://expel.com/meet-the-soc-experts/) - [Expel service page 2 (expel.com)](https://expel.com/about/) - [Expel service page 3 (expel.com)](https://expel.com/services/managed-detection-response/) ## Side by side - [Arctic Wolf and Expel](/side-by-side/arctic-wolf-and-expel/) - [BlueVoyant and Expel](/side-by-side/bluevoyant-and-expel/) - [Critical Start and Expel](/side-by-side/critical-start-and-expel/) - [CrowdStrike and Expel](/side-by-side/crowdstrike-and-expel/) - [Deepwatch and Expel](/side-by-side/deepwatch-and-expel/) - [eSentire and Expel](/side-by-side/esentire-and-expel/) - [Expel and Huntress](/side-by-side/expel-and-huntress/) - [Expel and Kroll](/side-by-side/expel-and-kroll/) - [Expel and Mandiant](/side-by-side/expel-and-mandiant/) - [Expel and Microsoft](/side-by-side/expel-and-microsoft/) - [Expel and Rapid7](/side-by-side/expel-and-rapid7/) - [Expel and Red Canary](/side-by-side/expel-and-red-canary/) - [Expel and SentinelOne](/side-by-side/expel-and-sentinelone/) - [Expel and Sophos](/side-by-side/expel-and-sophos/) - [Expel and Sygnia](/side-by-side/expel-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Expel, "About" page (the firm's own page): https://expel.com/about/ (read 10 November 2026) - Expel, "MDR packages" page (the firm's own page): https://expel.com/mdr-packages/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Expel, home page (the firm's own page): https://expel.com/ (read 10 November 2026) - Expel, "Managed detection response" page (the firm's own page): https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Expel, "Meet the SOC experts" page (the firm's own page): https://expel.com/meet-the-soc-experts/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/expel/ --- # Huntress: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Huntress sells Managed EDR at $8.99 per endpoint per month and Managed ITDR at $4.80 per identity per month, both run by a 24/7 human SOC. It says the SOC contains threats and removes the attacker's foothold. Identity and SIEM coverage are separate products. Included IR hours were none found on 10 Nov 2026. ## What does Huntress do on the customer's behalf? On 10 November 2026, Huntress's public pages show, across six actions, 1 stated, 2 with limits, 3 none found. Stated without conditions: isolate a host. | Action | What was found | | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | ## Huntress at a glance - **Service:** Huntress Managed EDR (within the Huntress Agentic Security Platform, with Managed ITDR and Managed SIEM) - **Company status:** Huntress is sold under its own name; its Series D page (read) describes it as a privately held company valued at $1.55B and its history page lists acquisitions Huntress made (Curricula, Level Effect). No sale of Huntress itself appeared on the pages read. - **Does well:** Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. - **Limited:** Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. ## The data Huntress watches | Data | What was found | | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | [What may the provider do without asking first?](/questions/q02/) | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | [Which data sources does the service monitor?](/questions/q03/) | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | [What response-time commitments are published?](/questions/q07/) | None found on 10 Nov 2026 | | [Is the pricing model published?](/questions/q08/) | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: Its Managed EDR page says a 24/7 AI-centric, human-led SOC investigates and acts on suspicious activity. (the provider's claim) - Who does the work: Its Managed EDR page says a human reviews every alert before it reaches the customer. (the provider's claim) - Tools and data it works on: Its Managed EDR page says it does not rely on other vendors' EDR tools and owns and builds its own technology. (the provider's claim) - Tools and data it works on: Its Managed EDR page says the service pairs a lightweight Huntress agent with its SOC, and runs alongside existing AV including Microsoft Defender. (the provider's claim) - What it may do on your behalf: Its Managed EDR page says the SOC contains the threat, removes the attacker's foothold and actively remediates threats to evict them from endpoints. (the provider's claim) - What it may do on your behalf: Its Managed EDR page says that on ransomware indicators it takes action fast and contains the threat. (the provider's claim) - Hunting: Its Managed EDR page says the EDR integrates 24/7 AI-assisted SOC and threat hunters. (the provider's claim) - Hunting: Its Managed SIEM page says Huntress experts hunt for evidence of malicious activity across supported security sources. (the provider's claim) - Coverage: Its platform page says the platform fabric covers endpoints, identities, logs and learners. (the provider's claim) - Coverage: Its platform page says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace. (the provider's claim) - When an alert becomes a breach: Its Managed EDR page criticizes competitors for separate SKUs for "real incident response", implying response is included in its own price (the page does not name included IR hours). (the provider's claim) - When an alert becomes a breach: Its Managed EDR page says its EDR includes everything in one price with no add-ons or service tiers. (the provider's claim) - Published scope, commitments and pricing: Its pricing page publishes $8.99 per endpoint per month for Managed EDR. (the provider's claim) - Published scope, commitments and pricing: Its pricing page publishes $4.80 per licensed identity per month for Managed ITDR, with volume pricing on request. (the provider's claim) ## The provider's own pages - [Huntress service page 1 (huntress.com)](https://www.huntress.com/platform/managed-edr) - [Huntress service page 2 (huntress.com)](https://www.huntress.com/platform/siem) - [Huntress service page 3 (huntress.com)](https://www.huntress.com/pricing) ## Side by side - [Arctic Wolf and Huntress](/side-by-side/arctic-wolf-and-huntress/) - [BlueVoyant and Huntress](/side-by-side/bluevoyant-and-huntress/) - [Critical Start and Huntress](/side-by-side/critical-start-and-huntress/) - [CrowdStrike and Huntress](/side-by-side/crowdstrike-and-huntress/) - [Deepwatch and Huntress](/side-by-side/deepwatch-and-huntress/) - [eSentire and Huntress](/side-by-side/esentire-and-huntress/) - [Expel and Huntress](/side-by-side/expel-and-huntress/) - [Huntress and Kroll](/side-by-side/huntress-and-kroll/) - [Huntress and Mandiant](/side-by-side/huntress-and-mandiant/) - [Huntress and Microsoft](/side-by-side/huntress-and-microsoft/) - [Huntress and Rapid7](/side-by-side/huntress-and-rapid7/) - [Huntress and Red Canary](/side-by-side/huntress-and-red-canary/) - [Huntress and SentinelOne](/side-by-side/huntress-and-sentinelone/) - [Huntress and Sophos](/side-by-side/huntress-and-sophos/) - [Huntress and Sygnia](/side-by-side/huntress-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Platform" page (the firm's own page): https://www.huntress.com/platform (read 10 November 2026) - Huntress, "SIEM" page (the firm's own page): https://www.huntress.com/platform/siem (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/huntress/ --- # Kroll: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Kroll says Responder MDR uses the DFIR team behind its breach investigations, extended remotely at no additional cost, and includes a $1 million incident protection warranty for qualifying clients. Stated containment includes isolating endpoints, updating WAFs and firewalls, and revoking access. Its newer pages describe a move to CrowdStrike Falcon. SLA minutes were none found on 10 Nov 2026. ## What does Kroll do on the customer's behalf? On 10 November 2026, Kroll's public pages show, across six actions, 2 stated, 3 with limits, 1 none found. Stated without conditions: isolate a host; kill a process or remove a file. | Action | What was found | | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | ## Kroll at a glance - **Service:** Kroll Responder MDR - **Company status:** Kroll still operates under this name. Its December 2025 press release says its MDR is migrating to CrowdStrike Falcon Complete Next-Gen MDR, and an August 2026 case study says the global MDR client base was migrated to the new Kroll Responder MDR service. - **Does well:** Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. - **Limited:** Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. ## The data Kroll watches | Data | What was found | | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | | Identity | Stated Case study says visibility across identity. | | Cloud | Stated Case study says visibility across cloud. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | [What may the provider do without asking first?](/questions/q02/) | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | [Which data sources does the service monitor?](/questions/q03/) | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | [Is threat hunting included, and what output is published?](/questions/q05/) | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | [What response-time commitments are published?](/questions/q07/) | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | [Is the pricing model published?](/questions/q08/) | None found on 10 Nov 2026 | | [Is OT covered?](/questions/q09/) | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | [What cloud and identity coverage is stated?](/questions/q10/) | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | [How long does onboarding take?](/questions/q11/) | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | [What reporting does the customer receive?](/questions/q12/) | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The Responder page says the service uses the same DFIR team that conducts high-profile breach investigations and extends remote DFIR to MDR customers at no additional cost. (the provider's claim) - Who does the work: The Responder page lists forensic capabilities of the responders: collecting additional forensic evidence including from virtual machines, reverse engineering malware, and validating remediation. (the provider's claim) - Tools and data it works on: The firm's December 2025 press release says it is migrating more than half a million endpoints of MDR protection to the CrowdStrike Falcon platform via Falcon Complete Next-Gen MDR. (the provider's claim) - Tools and data it works on: The firm's August 2026 case study says its previous MDR model let clients choose from multiple platforms but required detection engineering across five EDR and three SIEM platforms, and that it consolidated to CrowdStrike Falcon. (the provider's claim) - What it may do on your behalf: The Responder page says that on containment the team will isolate compromised endpoints, update WAFs and firewalls, and interact with authentication platforms, revoking access to compromised systems. (the provider's claim) - What it may do on your behalf: The Responder page says that after containment it will eradicate malware or bad actors from endpoints, remove persistence and assist with recovery. (the provider's claim) - Hunting: The Responder page says detection feeds proactive hunting and that potential threats and IOCs are sent to investigators who go live in customer systems. (the provider's claim) - Hunting: The Responder for Microsoft page says investigators conduct root-cause analysis and hunt for additional indicators of compromise; it lists weekly and out-of-band threat intelligence reports, not hunt findings. (the provider's claim) - Coverage: The August 2026 case study says clients get visibility across endpoint, identity, SIEM and cloud on the CrowdStrike foundation. (the provider's claim) - Coverage: Kroll's OT Security page describes 24/7 OT security monitoring and rapid incident response as a separate OT security service; it does not say OT is part of Responder MDR. (the provider's claim) - When an alert becomes a breach: The firm says Responder MDR includes remote DFIR at no extra cost and a complimentary $1 million incident protection warranty for qualifying clients with endpoint protection in their package. (the provider's claim) - When an alert becomes a breach: The Responder for Microsoft page says a 1 million dollar incident protection warranty is included at no extra cost if the service includes EDR, covering ransomware and business email compromise costs. (the provider's claim) - Published scope, commitments and pricing: The firm cites a 10x reduction in mean time to respond and 98% customer satisfaction (2024) on the Responder page; no SLA minutes were found on that page. (the provider's claim) - Breadth: The case study says Kroll migrated over 270 client environments to the new MDR service in under eight months, with nearly 300,000 contracted endpoints as of July 2026. (the provider's claim) ## The provider's own pages - [Kroll service page 1 (kroll.com)](https://www.kroll.com/en/services/cyber/kroll-responder) - [Kroll service page 2 (kroll.com)](https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr) - [Kroll service page 3 (kroll.com)](https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike) ## Side by side - [Arctic Wolf and Kroll](/side-by-side/arctic-wolf-and-kroll/) - [BlueVoyant and Kroll](/side-by-side/bluevoyant-and-kroll/) - [Critical Start and Kroll](/side-by-side/critical-start-and-kroll/) - [CrowdStrike and Kroll](/side-by-side/crowdstrike-and-kroll/) - [Deepwatch and Kroll](/side-by-side/deepwatch-and-kroll/) - [eSentire and Kroll](/side-by-side/esentire-and-kroll/) - [Expel and Kroll](/side-by-side/expel-and-kroll/) - [Huntress and Kroll](/side-by-side/huntress-and-kroll/) - [Kroll and Mandiant](/side-by-side/kroll-and-mandiant/) - [Kroll and Microsoft](/side-by-side/kroll-and-microsoft/) - [Kroll and Rapid7](/side-by-side/kroll-and-rapid7/) - [Kroll and Red Canary](/side-by-side/kroll-and-red-canary/) - [Kroll and SentinelOne](/side-by-side/kroll-and-sentinelone/) - [Kroll and Sophos](/side-by-side/kroll-and-sophos/) - [Kroll and Sygnia](/side-by-side/kroll-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Incident protection warranty" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/incident-protection-warranty (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Kroll, "Kroll MDR services migrate to crowdstrike falcon complete next gen MDR" page (the firm's own page): https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Kroll, "OT security" page (the firm's own page): https://www.kroll.com/en/services/cyber/cybersecurity-transformation/ot-security (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Kroll, "Incident response" page (the firm's own page): https://www.kroll.com/en/services/cyber/reactive-services/incident-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/kroll/ --- # Mandiant: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Mandiant says Managed Defense experts monitor the customer's security technology, hunt continually, and can contain impacted hosts and investigate, so incidents may be resolved without a formal incident response engagement. It names endpoint, network and multicloud monitoring and supported EDR partners. None found on 10 Nov 2026: account disable, IP block, pricing, SLA minutes, OT. ## What does Mandiant do on the customer's behalf? On 10 November 2026, Mandiant's public pages show, across six actions, 0 stated, 1 with limits, 5 none found. No action is stated without conditions. | Action | What was found | | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | ## Mandiant at a glance - **Service:** Mandiant Managed Defense (also shown on the incident response page as Mandiant Threat Defense) - **Company status:** Google completed its acquisition of Mandiant on 12 September 2022 and Mandiant joined Google Cloud, where its pages are now hosted. The Mandiant Retainer was formerly called Expertise on Demand, and the incident response page now lists Mandiant Threat Defense alongside the Managed Defense page. - **Does well:** Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. - **Limited:** Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. ## The data Mandiant watches | Data | What was found | | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | | Identity | None found on 10 November 2026 | | Cloud | Stated Full-stack monitoring across multicloud environments. | | Network | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | [What may the provider do without asking first?](/questions/q02/) | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | [Which data sources does the service monitor?](/questions/q03/) | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | [What response-time commitments are published?](/questions/q07/) | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | [Is the pricing model published?](/questions/q08/) | None found on 10 Nov 2026 | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The Managed Defense page says the service gives access to frontline experts who monitor the customer's security technology, and customers benefit from the collective knowledge of Mandiant. (the provider's claim) - Who does the work: The incident response page says Mandiant Threat Defense prioritizes critical cases, leads rapid incident response and applies AI-assisted threat hunting. (the provider's claim) - What it may do on your behalf: The Managed Defense page says its experts can contain impacted hosts and investigate, and provide actionable guidance. (the provider's claim) - What it may do on your behalf: The Managed Defense datasheet says that, with Technology Partner products, deeper response actions taken on behalf of customers include host containment, file acquisition and closing out alerts. (the provider's claim) - When an alert becomes a breach: The Managed Defense page says attacks can be stopped and incidents resolved without a formal incident response engagement. (the provider's claim) - Hunting: The Managed Defense page says Mandiant threat hunters hunt continually and map results to MITRE ATT&CK. (the provider's claim) - Hunting: The Managed Defense page links published output from the service, titled Tales from the Trenches, on attack and malware trends observed over Q2 2024. (the provider's claim) - Tools and data it works on: The Managed Defense page says the service supports hunting, triage, investigation and response for the customer's technology stack and points to a supported technology partners list. (the provider's claim) - Tools and data it works on: The Managed Defense datasheet lists supported EDR partners including CrowdStrike Falcon Insight XDR, SentinelOne Singularity XDR and Microsoft Defender for Endpoint, ingested via Google SecOps. (the provider's claim) - Coverage: The incident response page says Mandiant Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. (the provider's claim) - Published scope, commitments and pricing: The Managed Defense page says alerts are triaged and prioritized by a Mandiant expert within minutes. (the provider's claim) - Company status: Google announced on 12 September 2022 that it completed its acquisition of Mandiant, which joined Google Cloud. (the provider's claim) - Stated strength: The firm says Mandiant helps organizations prepare for and respond to incidents from technical investigation through recovery and crisis management. (the provider's claim) ## The provider's own pages - [Mandiant service page 1 (cloud.google.com)](https://cloud.google.com/security/products/managed-defense) - [Mandiant service page 2 (cloud.google.com)](https://cloud.google.com/security/consulting/mandiant-incident-response-services) - [Mandiant service page 3 (services.google.com)](https://services.google.com/fh/files/misc/mandiant_managed_defense_technology_ds_en.pdf) ## Side by side - [Arctic Wolf and Mandiant](/side-by-side/arctic-wolf-and-mandiant/) - [BlueVoyant and Mandiant](/side-by-side/bluevoyant-and-mandiant/) - [Critical Start and Mandiant](/side-by-side/critical-start-and-mandiant/) - [CrowdStrike and Mandiant](/side-by-side/crowdstrike-and-mandiant/) - [Deepwatch and Mandiant](/side-by-side/deepwatch-and-mandiant/) - [eSentire and Mandiant](/side-by-side/esentire-and-mandiant/) - [Expel and Mandiant](/side-by-side/expel-and-mandiant/) - [Huntress and Mandiant](/side-by-side/huntress-and-mandiant/) - [Kroll and Mandiant](/side-by-side/kroll-and-mandiant/) - [Mandiant and Microsoft](/side-by-side/mandiant-and-microsoft/) - [Mandiant and Rapid7](/side-by-side/mandiant-and-rapid7/) - [Mandiant and Red Canary](/side-by-side/mandiant-and-red-canary/) - [Mandiant and SentinelOne](/side-by-side/mandiant-and-sentinelone/) - [Mandiant and Sophos](/side-by-side/mandiant-and-sophos/) - [Mandiant and Sygnia](/side-by-side/mandiant-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Mandiant, "Mandiant managed defense technology ds en" page (the firm's own page): https://services.google.com/fh/files/misc/mandiant_managed_defense_technology_ds_en.pdf (read 10 November 2026) - Mandiant, "Mandiant incident response services" page (the firm's own page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/mandiant/ --- # Microsoft: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Microsoft says Defender Experts MDR experts can isolate a device, quarantine a file, restrict app execution and disable a user, but only if granted Security Operator access; the default leaves actions pending. It excludes incident response for an active compromise, a separate service. Plan 2 needs Sentinel and 1,500 seats. Prices were none found on 10 Nov 2026. ## What does Microsoft do on the customer's behalf? On 10 November 2026, Microsoft's public pages show, across six actions, 0 stated, 5 with limits, 1 none found. No action is stated without conditions. | Action | What was found | | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Microsoft at a glance - **Service:** Microsoft Defender Experts MDR (formerly Defender Experts for XDR), with Defender Experts Hunting - **Company status:** Microsoft's incident response page now carries the name Microsoft Defender Experts Cybersecurity Incident Response (page title still Microsoft Incident Response), and Learn documentation says Defender Experts for XDR was renamed Defender Experts MDR. - **Does well:** Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. - **Limited:** Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. ## The data Microsoft watches | Data | What was found | | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated MDR page says it protects identities. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | [What may the provider do without asking first?](/questions/q02/) | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | [Which data sources does the service monitor?](/questions/q03/) | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | [What response-time commitments are published?](/questions/q07/) | Microsoft's overview prints no price or response-time commitment. | | [Is the pricing model published?](/questions/q08/) | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | [Is OT covered?](/questions/q09/) | Microsoft's FAQ excludes IoT devices and does not mention OT. | | [What cloud and identity coverage is stated?](/questions/q10/) | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: The Learn overview says Defender Experts MDR does not provide incident response for an active compromise and points to the separate Defender Experts Cybersecurity Incident Response. (the provider's claim) - Who does the work: The Defender Experts MDR FAQ says Defender Experts MDR does not provide incident response; customers are directed to the separate Defender Experts Cybersecurity Incident Response offering. (the provider's claim) - Tools and data it works on: The Learn overview says Plan 1 covers Microsoft Defender workloads and Plan 2 extends to selected non-Microsoft telemetry collected in Microsoft Sentinel, and that Plan 2 requires Sentinel. (the provider's claim) - Tools and data it works on: The Learn overview lists Plan 2 third-party sources: Okta, Proofpoint TAP, AWS CloudTrail, AWS GuardDuty, Palo Alto PAN-OS, Cisco ASA/Meraki, Zscaler ZIA/ZPA and Fortinet FortiGate. (the provider's claim) - What it may do on your behalf: The managed-response page lists one-click actions: isolate device, quarantine file, restrict app execution, release from isolation, remove app restriction and disable user. (the provider's claim) - What it may do on your behalf: The page says experts act on the customer's behalf only if granted Security Operator access; with the default Security Reader access, actions are left as pending for the customer. (the provider's claim) - Hunting: The overview says proactive threat hunting is built in to both plans via Microsoft Defender Experts Hunting. (the provider's claim) - Hunting: The Hunting page says customers receive interactive reports on scope, impact and analysis for each hunt conducted. (the provider's claim) - Coverage: The MDR page says it protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure across Microsoft and third-party sources. (the provider's claim) - Coverage: The overview says neither plan covers Microsoft Defender for Cloud workloads such as storage, containers and databases. (the provider's claim) - When an alert becomes a breach: The overview and IR page present incident response as a separate Defender Experts service, offered under Defender Experts Service Terms. (the provider's claim) - Published scope, commitments and pricing: The overview publishes plan scope, capabilities and boundaries, and says the service is sold separately; no price or response-time commitment appears on it. (the provider's claim) - Published scope, commitments and pricing: The service gives customers live dashboards and reports of the work done on their behalf. (the provider's claim) - Company status: The overview says Plan 1 is the service previously offered as Defender Experts for XDR, later renamed Defender Experts MDR. (the provider's claim) ## The provider's own pages - [Microsoft service page 1 (learn.microsoft.com)](https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview) - [Microsoft service page 2 (learn.microsoft.com)](https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response) - [Microsoft service page 3 (learn.microsoft.com)](https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq) ## Side by side - [Arctic Wolf and Microsoft](/side-by-side/arctic-wolf-and-microsoft/) - [BlueVoyant and Microsoft](/side-by-side/bluevoyant-and-microsoft/) - [Critical Start and Microsoft](/side-by-side/critical-start-and-microsoft/) - [CrowdStrike and Microsoft](/side-by-side/crowdstrike-and-microsoft/) - [Deepwatch and Microsoft](/side-by-side/deepwatch-and-microsoft/) - [eSentire and Microsoft](/side-by-side/esentire-and-microsoft/) - [Expel and Microsoft](/side-by-side/expel-and-microsoft/) - [Huntress and Microsoft](/side-by-side/huntress-and-microsoft/) - [Kroll and Microsoft](/side-by-side/kroll-and-microsoft/) - [Mandiant and Microsoft](/side-by-side/mandiant-and-microsoft/) - [Microsoft and Rapid7](/side-by-side/microsoft-and-rapid7/) - [Microsoft and Red Canary](/side-by-side/microsoft-and-red-canary/) - [Microsoft and SentinelOne](/side-by-side/microsoft-and-sentinelone/) - [Microsoft and Sophos](/side-by-side/microsoft-and-sophos/) - [Microsoft and Sygnia](/side-by-side/microsoft-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Microsoft, "Microsoft defender experts hunting" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-hunting (read 10 November 2026) - Microsoft, "Defender experts MDR FAQ" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq (read 10 November 2026) - Microsoft, "Microsoft defender experts MDR" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-mdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/microsoft/ --- # Rapid7: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Rapid7 says its MDR SOC and IR team investigate, contain and eradicate threats, with unlimited incident response in the subscription and no cap on hours. It states contain-remotely actions aligned to the customer's approved policies, coverage of endpoint, cloud, identity, email and network, and asset-based pricing. Dollar prices and OT coverage were none found on 10 Nov 2026. ## What does Rapid7 do on the customer's behalf? On 10 November 2026, Rapid7's public pages show, across six actions, 2 stated, 0 with limits, 4 none found. Stated without conditions: isolate a host; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says response actions follow the customer's approved policies. | ## Rapid7 at a glance - **Service:** Rapid7 MDR (Managed Detection and Response; "Preemptive MDR") - **Company status:** Rapid7 MDR is still sold under this name on Rapid7's own site. A Rapid7 press-release listing shows Rapid7 announcing its own acquisition of Kenzo Security; no sale of Rapid7 itself appears on the page read. - **Does well:** Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. - **Limited:** Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. ## The data Rapid7 watches | Data | What was found | | --- | --- | | Endpoint | Stated MDR page lists endpoint. | | Identity | Stated MDR page lists identity. | | Cloud | Stated MDR page lists cloud. | | Network | Stated MDR page lists network. | | Email | Stated MDR page lists email. | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | [What may the provider do without asking first?](/questions/q02/) | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | [Which data sources does the service monitor?](/questions/q03/) | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | [What response-time commitments are published?](/questions/q07/) | None found on 10 Nov 2026 | | [Is the pricing model published?](/questions/q08/) | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 | | [What cloud and identity coverage is stated?](/questions/q10/) | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Rapid7 says every action in the SOC is logged, explainable and auditable. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: Its MDR page states that Rapid7 analysts and advisors investigate, contain, remediate and strategize as an extension of the customer team. (the provider's claim) - Who does the work: Its MDR FAQ says the SOC and the Incident Response team both act when a threat is detected, and that the team performs forensic analysis to determine scope and impact. (the provider's claim) - Tools and data it works on: Its MDR FAQ says the service provides SOC support for third-party tools across endpoint, identity, cloud and email, with 190+ integrations for telemetry, and that SOC-managed monitoring applies to supported tools. (the provider's claim) - Tools and data it works on: Its MDR for Microsoft page says the service operationalizes Microsoft Defender across endpoint, identity, cloud and email. (the provider's claim) - What it may do on your behalf: Its MDR FAQ says the team notifies the customer, contains affected assets remotely and takes response actions aligned to the customer's approved policies. (the provider's claim) - What it may do on your behalf: Its package comparison lists "Active response for remote containment" and "Active remediation with Velociraptor" as service rows. (the provider's claim) - Hunting: Its package page lists "Threat hunting" among the Essentials package inclusions and "Proactive threat hunting" in the full comparison. (the provider's claim) - Hunting: Its MDR page says 20% of annual revenue is reinvested in research delivered through Rapid7 Intelligence and Emergent Threat Response, included in the MDR service; the research hub publishes a Quarterly Threat Landscape Report. (the provider's claim) - Coverage: Its MDR page says native multi-vector telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. (the provider's claim) - Coverage: Its MDR for Enterprise page says custom event source integration extends detection to business-critical systems, vertical-specific tools or in-house applications, beyond endpoints. (the provider's claim) - When an alert becomes a breach: Its MDR FAQ says incident response is unlimited and Rapid7 remains engaged until remediation is complete. (the provider's claim) - When an alert becomes a breach: Its pricing page lists "Unlimited incident and breach response" as a service row and "Breach protection warranty" as a separate row. (the provider's claim) - Published scope, commitments and pricing: Its MDR FAQ states an asset-based pricing model, paid by number of assets protected. (the provider's claim) - Published scope, commitments and pricing: Its pricing page publishes three named packages (Essentials, Advanced, Ultimate) with feature lists; no dollar prices appear on the page read. (the provider's claim) ## The provider's own pages - [Rapid7 service page 1 (rapid7.com)](https://www.rapid7.com/services/managed-detection-and-response-mdr/) - [Rapid7 service page 2 (rapid7.com)](https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq) - [Rapid7 service page 3 (rapid7.com)](https://www.rapid7.com/services/managed-detection-and-response-mdr/microsoft/) ## Side by side - [Arctic Wolf and Rapid7](/side-by-side/arctic-wolf-and-rapid7/) - [BlueVoyant and Rapid7](/side-by-side/bluevoyant-and-rapid7/) - [Critical Start and Rapid7](/side-by-side/critical-start-and-rapid7/) - [CrowdStrike and Rapid7](/side-by-side/crowdstrike-and-rapid7/) - [Deepwatch and Rapid7](/side-by-side/deepwatch-and-rapid7/) - [eSentire and Rapid7](/side-by-side/esentire-and-rapid7/) - [Expel and Rapid7](/side-by-side/expel-and-rapid7/) - [Huntress and Rapid7](/side-by-side/huntress-and-rapid7/) - [Kroll and Rapid7](/side-by-side/kroll-and-rapid7/) - [Mandiant and Rapid7](/side-by-side/mandiant-and-rapid7/) - [Microsoft and Rapid7](/side-by-side/microsoft-and-rapid7/) - [Rapid7 and Red Canary](/side-by-side/rapid7-and-red-canary/) - [Rapid7 and SentinelOne](/side-by-side/rapid7-and-sentinelone/) - [Rapid7 and Sophos](/side-by-side/rapid7-and-sophos/) - [Rapid7 and Sygnia](/side-by-side/rapid7-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Rapid7, "Pricing" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/pricing/ (read 10 November 2026) - Rapid7, "Microsoft" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/microsoft/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/rapid7/ --- # Red Canary: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Red Canary, now Zscaler Managed Detection and Response, says automated playbooks isolate endpoints via EDR, suspend users via the customer's IDP and block URLs and IoCs via ZIA, with customers choosing human oversight or automation. It states identity, endpoint, cloud, email and network coverage. IR comes from partner firms. Prices were none found on 10 Nov 2026. ## What does Red Canary do on the customer's behalf? On 10 November 2026, Red Canary's public pages show, across six actions, 4 stated, 1 with limits, 1 none found. Stated without conditions: isolate a host; disable or reset an account; block an ip, domain, hash or email; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Red Canary at a glance - **Service:** Red Canary Managed Detection and Response (now Zscaler Managed Detection & Response) - **Company status:** redcanary.com now redirects to a Zscaler page that says Red Canary is now part of Zscaler; a Red Canary co-founder's post on zscaler.com says Zscaler signed a definitive agreement to acquire Red Canary. The service is now presented as Zscaler Managed Detection & Response. - **Does well:** Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. - **Limited:** Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. ## The data Red Canary watches | Data | What was found | | --- | --- | | Endpoint | Stated Page lists endpoint as a key domain. | | Identity | Stated Page lists identity. | | Cloud | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Page lists network. | | Email | Stated Page lists email. | | OT | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | [What may the provider do without asking first?](/questions/q02/) | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | [Which data sources does the service monitor?](/questions/q03/) | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | [What response-time commitments are published?](/questions/q07/) | None found on 10 Nov 2026 | | [Is the pricing model published?](/questions/q08/) | None found on 10 Nov 2026 | | [Is OT covered?](/questions/q09/) | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | [What cloud and identity coverage is stated?](/questions/q10/) | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | Red Canary says reporting shows speed and accuracy of detection and response over time. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Company status: The Zscaler MDR page that redcanary.com now redirects to states that Red Canary is now part of Zscaler. (the provider's claim) - Company status: A Red Canary co-founder's post on Zscaler's site says Zscaler signed a definitive agreement to acquire Red Canary. (the provider's claim) - Who does the work: The page says MDR taps in-house experts to detect, manage, respond to and remediate threats. (the provider's claim) - Who does the work: The Active Remediation post says detection engineers who confirmed a threat escalate to the firm's Incident Handling Team, which does hands-on endpoint remediation. (the provider's claim) - Tools and data it works on: The Active Remediation post says the service is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto Networks or SentinelOne as EDR. (the provider's claim) - Tools and data it works on: The page says MDR integrates with a wide range of security tools and can integrate with Zscaler Internet Access for enrichment and response. (the provider's claim) - What it may do on your behalf: The page says automated playbooks block URLs and IoCs via ZIA, isolate endpoints via EDR, and suspend users via the customer's IDP. (the provider's claim) - What it may do on your behalf: The page says customers can keep human oversight on specific response actions or choose to automate. (the provider's claim) - Hunting: The page says the service includes threat hunting across clouds, endpoints and identities with scoped findings. (the provider's claim) - Hunting: The page says customers can view writeups of every threat hunt's hypothesis, observations, recommendations and findings. (the provider's claim) - Coverage: The page lists key domains of identity, endpoint, cloud, email and network. (the provider's claim) - Coverage: The page says Zscaler MDR unifies data from AWS, GCP, Azure and cloud security tools like Wiz. (the provider's claim) - When an alert becomes a breach: The page says MDR can remediate threats and that incident response partners are part of its partner ecosystem; it states no included IR hours. (the provider's claim) - When an alert becomes a breach: Its partner page (archived snapshot) says IR consulting firms can attach Red Canary to a case in a 45-day short-term engagement, i.e. IR is delivered by partner firms, not bundled in the MDR service. (the provider's claim) ## The provider's own pages - [Red Canary service page 1 (zscaler.com)](https://www.zscaler.com/products-and-solutions/managed-detection-and-response) - [Red Canary service page 2 (zscaler.com)](https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation) ## Side by side - [Arctic Wolf and Red Canary](/side-by-side/arctic-wolf-and-red-canary/) - [BlueVoyant and Red Canary](/side-by-side/bluevoyant-and-red-canary/) - [Critical Start and Red Canary](/side-by-side/critical-start-and-red-canary/) - [CrowdStrike and Red Canary](/side-by-side/crowdstrike-and-red-canary/) - [Deepwatch and Red Canary](/side-by-side/deepwatch-and-red-canary/) - [eSentire and Red Canary](/side-by-side/esentire-and-red-canary/) - [Expel and Red Canary](/side-by-side/expel-and-red-canary/) - [Huntress and Red Canary](/side-by-side/huntress-and-red-canary/) - [Kroll and Red Canary](/side-by-side/kroll-and-red-canary/) - [Mandiant and Red Canary](/side-by-side/mandiant-and-red-canary/) - [Microsoft and Red Canary](/side-by-side/microsoft-and-red-canary/) - [Rapid7 and Red Canary](/side-by-side/rapid7-and-red-canary/) - [Red Canary and SentinelOne](/side-by-side/red-canary-and-sentinelone/) - [Red Canary and Sophos](/side-by-side/red-canary-and-sophos/) - [Red Canary and Sygnia](/side-by-side/red-canary-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Red Canary, "Redcanary joining zscaler" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/redcanary-joining-zscaler (read 10 November 2026) - Red Canary, "Incident response" page (the firm's own page): https://redcanary.com/partners/incident-response/ (read 10 November 2026) - Red Canary, "Manufacturing services" page (the firm's own page): https://redcanary.com/solutions/industry/manufacturing-services/ (read 10 November 2026) - Red Canary, "Introducing red canary active threat remediation" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/red-canary/ --- # SentinelOne: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** SentinelOne says Wayfinder MDR contains confirmed threats by killing malicious processes, isolating endpoints and rolling back unauthorized changes per the configured response policy. It names endpoint, cloud and identity coverage and an IR retainer pool of expert hours with a 4-hour initial response SLA. MDR price was none found on 10 Nov 2026. ## What does SentinelOne do on the customer's behalf? On 10 November 2026, SentinelOne's public pages show, across six actions, 3 stated, 0 with limits, 3 none found. Stated without conditions: isolate a host; kill a process or remove a file; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says confirmed threats are contained according to the configured response policy. | ## SentinelOne at a glance - **Service:** Wayfinder Managed Detection & Response (MDR), within Wayfinder Threat Detection and Response (TDR), with Wayfinder Threat Hunting and Wayfinder Incident Readiness & Response (IRR) - **Company status:** SentinelOne's current pages name its managed services Wayfinder MDR, Wayfinder Threat Hunting and Wayfinder IRR under Wayfinder TDR; the former Vigilance MDR product URL (/platform/vigilance-mdr/) returns a 404 page. No page read states the rename in words. SentinelOne is itself publicly traded (NYSE: S) per its company page. - **Does well:** SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. - **Limited:** SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. ## The data SentinelOne watches | Data | What was found | | --- | --- | | Endpoint | Stated Core detection coverage includes endpoint. | | Identity | Stated Core detection coverage includes identity. | | Cloud | Stated Core detection coverage includes cloud. | | Network | None found on 10 November 2026 | | Email | None found on 10 November 2026 | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | [What may the provider do without asking first?](/questions/q02/) | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | [Which data sources does the service monitor?](/questions/q03/) | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | [Is the provider's own endpoint agent required?](/questions/q04/) | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | [Is threat hunting included, and what output is published?](/questions/q05/) | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | [What response-time commitments are published?](/questions/q07/) | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | [Is the pricing model published?](/questions/q08/) | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | [Is OT covered?](/questions/q09/) | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | [What cloud and identity coverage is stated?](/questions/q10/) | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Who does the work: Its MDR page says certified analysts investigate every alert and that DFIR experts are available for critical incidents. (the provider's claim) - Who does the work: Its MDR page says that for critical incidents, DFIR experts are available for rapid containment and forensic recovery. (the provider's claim) - Tools and data it works on: Its MDR page lists core detection coverage as endpoint, cloud, identity and supported third-party integrations. (the provider's claim) - Tools and data it works on: Its MDR page describes the service as built into the Singularity Platform. (the provider's claim) - What it may do on your behalf: Its MDR page says confirmed threats are contained: malicious processes are killed, endpoints isolated and unauthorized changes rolled back, according to the configured response policy. (the provider's claim) - What it may do on your behalf: Its MDR page lists "Managed Response & Mitigation" among the Detection & Response rows of its service levels. (the provider's claim) - Hunting: Its MDR page says Wayfinder TDR includes proactive, intelligence-led hunting by analysts using Google Threat Intelligence. (the provider's claim) - Hunting: Its MDR service-level table lists "Behavioral & Periodic Threat Hunts on EDR" and "Advanced Proactive Hunting" rows. (the provider's claim) - Coverage: Its MDR page says 24/7 monitoring runs across endpoints, cloud and identity. (the provider's claim) - Coverage: Its site navigation (on the MDR page) lists an industry page ("Defend OT, IT, IIOT, and Supply Chains at Scale"), but the MDR page itself lists only endpoint, cloud and identity as core coverage. (the provider's claim) - When an alert becomes a breach: Its IR page says Wayfinder IRR retainer gives a renewable pool of expert hours consumed across readiness, assessments and response. (the provider's claim) - When an alert becomes a breach: Its IR page states a 4-hour SLA for initial expert response and a 24-hour SLA for preliminary findings. (the provider's claim) - Published scope, commitments and pricing: Its MDR page says Wayfinder MDR mean time to detect averages 3.3 minutes across customer environments. (the provider's claim) - Published scope, commitments and pricing: Its MDR page names three service levels (Threat Hunting, MDR Essentials, MDR Elite) and offers up to a $1M breach response warranty. (the provider's claim) ## The provider's own pages - [SentinelOne service page 1 (sentinelone.com)](https://www.sentinelone.com/global-services/managed-detection-and-response/) - [SentinelOne service page 2 (sentinelone.com)](https://www.sentinelone.com/global-services/incident-readiness-and-response/) - [SentinelOne service page 3 (sentinelone.com)](https://www.sentinelone.com/pricing/) ## Side by side - [Arctic Wolf and SentinelOne](/side-by-side/arctic-wolf-and-sentinelone/) - [BlueVoyant and SentinelOne](/side-by-side/bluevoyant-and-sentinelone/) - [Critical Start and SentinelOne](/side-by-side/critical-start-and-sentinelone/) - [CrowdStrike and SentinelOne](/side-by-side/crowdstrike-and-sentinelone/) - [Deepwatch and SentinelOne](/side-by-side/deepwatch-and-sentinelone/) - [eSentire and SentinelOne](/side-by-side/esentire-and-sentinelone/) - [Expel and SentinelOne](/side-by-side/expel-and-sentinelone/) - [Huntress and SentinelOne](/side-by-side/huntress-and-sentinelone/) - [Kroll and SentinelOne](/side-by-side/kroll-and-sentinelone/) - [Mandiant and SentinelOne](/side-by-side/mandiant-and-sentinelone/) - [Microsoft and SentinelOne](/side-by-side/microsoft-and-sentinelone/) - [Rapid7 and SentinelOne](/side-by-side/rapid7-and-sentinelone/) - [Red Canary and SentinelOne](/side-by-side/red-canary-and-sentinelone/) - [SentinelOne and Sophos](/side-by-side/sentinelone-and-sophos/) - [SentinelOne and Sygnia](/side-by-side/sentinelone-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - SentinelOne, "Pricing" page (the firm's own page): https://www.sentinelone.com/pricing/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/sentinelone/ --- # Sophos: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Sophos defines Response Actions it may take as host isolation, process termination, quarantine, blocking indicators, disabling users and revoking sessions. The customer picks a mode, Authorize or Collaborate. Coverage spans endpoint, network, cloud, identity and email. MDR Plus commits to 60 minutes Time to Respond for 90 percent of priority investigations. OT was none found on 10 Nov 2026. ## What does Sophos do on the customer's behalf? On 10 November 2026, Sophos's public pages show, across six actions, 5 stated, 0 with limits, 1 none found. Stated without conditions: isolate a host; disable or reset an account; block an ip, domain, hash or email; kill a process or remove a file; acts without asking first (pre-approved). | Action | What was found | | --- | --- | | Isolate a host | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Sophos at a glance - **Service:** Sophos Managed Detection and Response (MDR) - **Company status:** Sophos MDR exists under this name. Its MDR page offers Taegis MDR, powered by Secureworks, within the Sophos portfolio; the acquisition completion page could not be loaded (404 on tried URLs), so ownership of Secureworks by Sophos rests on that product page only. - **Does well:** Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. - **Limited:** Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. ## The data Sophos watches | Data | What was found | | --- | --- | | Endpoint | Stated MDR page states endpoint coverage. | | Identity | Stated MDR page states identity coverage. | | Cloud | Stated MDR page states cloud coverage. | | Network | Stated MDR page states network coverage. | | Email | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | [What may the provider do without asking first?](/questions/q02/) | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | [Which data sources does the service monitor?](/questions/q03/) | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | [What response-time commitments are published?](/questions/q07/) | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | [Is the pricing model published?](/questions/q08/) | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | [Is OT covered?](/questions/q09/) | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | [What cloud and identity coverage is stated?](/questions/q10/) | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 | | [What reporting does the customer receive?](/questions/q12/) | None found on 10 Nov 2026 | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Tools and data it works on: Its MDR page states the service is vendor-agnostic, with analysts working across diverse vendor environments. (the provider's claim) - Tools and data it works on: Its MDR page states 500+ integrations are included across endpoint, network, cloud, identity, email and business applications; its FAQ gives a figure of more than 350 third-party tools. (the provider's claim) - What it may do on your behalf: Its MDR page states confirmed threats are fully contained and removed with no limits or extra fees; the page does not list individual actions such as isolate or disable account. (the provider's claim) - What it may do on your behalf: Its MDR page cites an average of 89 seconds from alert to automated response where AI can act alone. (the provider's claim) - Hunting: Its MDR page describes proactive threat hunting powered by autonomous agents and threat intelligence. (the provider's claim) - Hunting: Its service description includes Threat Hunting in both MDR tiers, limited to data in Sophos Fusion for covered endpoints and supported integrated systems; hunting findings open an Investigation Case. It does not describe hunt reports. (the provider's claim) - Coverage: Its MDR page states coverage across endpoint, network, cloud, identity, email and business applications; OT is not mentioned. (the provider's claim) - Coverage: Its MDR page describes the service as fully managed, 24/7 detection and response, and the FAQ cites nine regional security operations teams. (the provider's claim) - When an alert becomes a breach: Its MDR page states critical incident response is included with no caps or additional fees, including root cause analysis and a dedicated incident response advisor. (the provider's claim) - When an alert becomes a breach: Its service description puts Incident Response in the MDR Plus tier only, performed remotely, with an assigned Incident Response Advisor. (the provider's claim) - Who does the work: Its MDR page says incident response with a dedicated advisor is part of the MDR service, which implies escalation within the same service; it does not state forensic depth. (the provider's claim) - Who does the work: Its service description says the Incident Response Advisor provides coordination and communication support only and does not manage the overall incident lifecycle or take operational control. (the provider's claim) - Published scope, commitments and pricing: Its MDR page mentions flexible service tiers and response modes and lists no prices. (the provider's claim) - Published scope, commitments and pricing: Its service description commits, for MDR Plus customers, to a Time to Respond within 60 minutes for 90 percent of Priority Investigations, measured monthly, with a service credit. (the provider's claim) ## The provider's own pages - [Sophos service page 1 (sophos.com)](https://www.sophos.com/en-us/products/managed-detection-and-response) - [Sophos service page 2 (sophos.com)](https://www.sophos.com/en-us/legal/mdr-description) ## Side by side - [Arctic Wolf and Sophos](/side-by-side/arctic-wolf-and-sophos/) - [BlueVoyant and Sophos](/side-by-side/bluevoyant-and-sophos/) - [Critical Start and Sophos](/side-by-side/critical-start-and-sophos/) - [CrowdStrike and Sophos](/side-by-side/crowdstrike-and-sophos/) - [Deepwatch and Sophos](/side-by-side/deepwatch-and-sophos/) - [eSentire and Sophos](/side-by-side/esentire-and-sophos/) - [Expel and Sophos](/side-by-side/expel-and-sophos/) - [Huntress and Sophos](/side-by-side/huntress-and-sophos/) - [Kroll and Sophos](/side-by-side/kroll-and-sophos/) - [Mandiant and Sophos](/side-by-side/mandiant-and-sophos/) - [Microsoft and Sophos](/side-by-side/microsoft-and-sophos/) - [Rapid7 and Sophos](/side-by-side/rapid7-and-sophos/) - [Red Canary and Sophos](/side-by-side/red-canary-and-sophos/) - [SentinelOne and Sophos](/side-by-side/sentinelone-and-sophos/) - [Sophos and Sygnia](/side-by-side/sophos-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/sophos/ --- # Sygnia: what it says it will do on your behalf, and on which data MDR service, read 10 November 2026 **In short.** Sygnia says its MDR detects, investigates, contains and remediates threats, with client-authorized automated containment for defined scenarios and human approval for actions that affect the environment. It states data from endpoint, identity, network, cloud, application, email and OT, with over 250 integrations. None found on 10 Nov 2026: account disable, IP block, process kill, or SLA minutes. ## What does Sygnia do on the customer's behalf? On 10 November 2026, Sygnia's public pages show, across six actions, 0 stated, 2 with limits, 4 none found. No action is stated without conditions. | Action | What was found | | --- | --- | | Isolate a host | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Sygnia at a glance - **Service:** Sygnia Managed Detection and Response (MDR), powered by Velocity TDIR - **Company status:** Sygnia exists under this name; it says it has been a Temasek International company since 2018 and part of the ISTARI Collective, and CNBC reported the 2018 acquisition by Temasek. - **Does well:** Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. - **Limited:** Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. Sygnia's MDR has fewer analyst placements than the largest MDR providers (it is not among the seven services profiled in IDC's 2024 MDR assessment and took part in neither MITRE managed services evaluation), and no published price (none found on 10 Nov 2026). ## The data Sygnia watches | Data | What was found | | --- | --- | | Endpoint | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Velocity ingests network data, per Sygnia. | | Email | Stated Alternate MDR page lists email among data sources. | | OT | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions, with the answers found | Question | Answer found | | --- | --- | | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | [What may the provider do without asking first?](/questions/q02/) | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | [Which data sources does the service monitor?](/questions/q03/) | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | [Is the provider's own endpoint agent required?](/questions/q04/) | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | [Is threat hunting included, and what output is published?](/questions/q05/) | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | [What response-time commitments are published?](/questions/q07/) | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | [Is the pricing model published?](/questions/q08/) | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | [Is OT covered?](/questions/q09/) | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | [What cloud and identity coverage is stated?](/questions/q10/) | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | [How long does onboarding take?](/questions/q11/) | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | [What reporting does the customer receive?](/questions/q12/) | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | [Where is customer data kept, and for how long?](/questions/q13/) | None found on 10 Nov 2026 | | [Can the customer's analysts see what the provider sees?](/questions/q14/) | None found on 10 Nov 2026 | | [What are the exit and data-return terms?](/questions/q15/) | None found on 10 Nov 2026 | ## Evidence on file, by topic - Company status: Sygnia says it has been a Temasek International company since 2018 and is a member of the ISTARI Collective. (the provider's claim) - Company status: CNBC reported on 2018-10-16 that Sygnia said it would be acquired by Temasek Holdings and would keep its operational independence. - Breadth: The firm's home page states 500 clients, 60 countries and 12 years of frontline experience. (the provider's claim) - Breadth: The firm's August 2026 release says Velocity has 250+ integrations and 750+ detection scenarios. (the provider's claim) - Stated strength: The firm says it combines global reach with a boutique, engaged approach and over a decade of frontline incident response experience. (the provider's claim) - Who does the work: The firm's MDR page says MDR uses the same technology as its IR, so moving to IR is as simple as flipping a switch, and analysts are tied closely to IR teams. (the provider's claim) - Who does the work: The firm's MDR page says each client has a named team of 8 experts, all analysts are seasoned, and they stay current through integration with IR teams. (the provider's claim) - Tools and data it works on: The firm's MDR page says Sygnia MDR integrates with existing network, endpoint, cloud, firewall, email gateway and application technologies. (the provider's claim) - Tools and data it works on: A January 2023 press release says Sygnia's MXDR has hundreds of integrations and a proprietary light-weight agent for faster deployment. (the provider's claim) - What it may do on your behalf: The firm's MDR service description says it detects, investigates, contains and remediates threats, with rapid transition from detection to containment and remediation. (the provider's claim) - What it may do on your behalf: The firm's August 2026 AWS Marketplace release says the MDR helps organizations detect, investigate, contain and remediate threats. (the provider's claim) - Hunting: The firm's MDR page says Velocity provides forensics collection, threat detection, triage, analysis and mitigation (its home page also lists threat hunting in Velocity's role). (the provider's claim) - Hunting: Sygnia lists Threat Hunting as a separate service that delivers a comprehensive report of analyses, findings and recommendations; the MDR pages read do not state hunting as an included MDR component. (the provider's claim) - Coverage: The firm's MDR page says Velocity ingests endpoint, cloud, network and application data for visibility across IT, OT and hybrid cloud. (the provider's claim) ## The provider's own pages - [Sygnia managed detection and response](https://sygnia.co/solutions/managed-detection-and-response/?utm_source=mdrvsmssp.com&utm_medium=referral&utm_campaign=service) - [Sygnia Velocity platform](https://sygnia.co/velocity/?utm_source=mdrvsmssp.com&utm_medium=referral&utm_campaign=service) - [Sygnia home page](https://sygnia.co/?utm_source=mdrvsmssp.com&utm_medium=referral&utm_campaign=service) ## Side by side - [Arctic Wolf and Sygnia](/side-by-side/arctic-wolf-and-sygnia/) - [BlueVoyant and Sygnia](/side-by-side/bluevoyant-and-sygnia/) - [Critical Start and Sygnia](/side-by-side/critical-start-and-sygnia/) - [CrowdStrike and Sygnia](/side-by-side/crowdstrike-and-sygnia/) - [Deepwatch and Sygnia](/side-by-side/deepwatch-and-sygnia/) - [eSentire and Sygnia](/side-by-side/esentire-and-sygnia/) - [Expel and Sygnia](/side-by-side/expel-and-sygnia/) - [Huntress and Sygnia](/side-by-side/huntress-and-sygnia/) - [Kroll and Sygnia](/side-by-side/kroll-and-sygnia/) - [Mandiant and Sygnia](/side-by-side/mandiant-and-sygnia/) - [Microsoft and Sygnia](/side-by-side/microsoft-and-sygnia/) - [Rapid7 and Sygnia](/side-by-side/rapid7-and-sygnia/) - [Red Canary and Sygnia](/side-by-side/red-canary-and-sygnia/) - [SentinelOne and Sygnia](/side-by-side/sentinelone-and-sygnia/) - [Sophos and Sygnia](/side-by-side/sophos-and-sygnia/) ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Sixteen MDR services, A to Z](/services/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [All side-by-side pages](/side-by-side/) ## Sources - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) - Sygnia, "MDR integrations" page (the firm's own page): https://www.sygnia.co/mdr-integrations/ (read 10 November 2026) - Sygnia, "Our story" page (the firm's own page): https://www.sygnia.co/our-story/ (read 10 November 2026) - cnbc.com, "Singapore firm temasek to acquire israeli cybersecurity firmsygnia": https://www.cnbc.com/2018/10/16/singapore-firm-temasek-to-acquire-israeli-cybersecurity-firmsygnia-.html (read 10 November 2026) - Sygnia, "Sygnia uncovers active chinese nexus 080000889" page (the firm's own page): https://finance.yahoo.com/news/sygnia-uncovers-active-chinese-nexus-080000889.html (read 10 November 2026) - Sygnia, "Threat reports and advisories" page (the firm's own page): https://www.sygnia.co/threat-reports-and-advisories/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/services/sygnia/ --- # 120 pairs of MDR services, set out row by row Side by side, read 10 November 2026 **In short.** Each side-by-side page puts the published facts of two MDR services in the same rows: the actions each says it will take, the data each watches, and the answers found to fifteen buyer questions. The pages end without a verdict. ### Arctic Wolf - [Arctic Wolf and BlueVoyant](/side-by-side/arctic-wolf-and-bluevoyant/) - [Arctic Wolf and Critical Start](/side-by-side/arctic-wolf-and-critical-start/) - [Arctic Wolf and CrowdStrike](/side-by-side/arctic-wolf-and-crowdstrike/) - [Arctic Wolf and Deepwatch](/side-by-side/arctic-wolf-and-deepwatch/) - [Arctic Wolf and eSentire](/side-by-side/arctic-wolf-and-esentire/) - [Arctic Wolf and Expel](/side-by-side/arctic-wolf-and-expel/) - [Arctic Wolf and Huntress](/side-by-side/arctic-wolf-and-huntress/) - [Arctic Wolf and Kroll](/side-by-side/arctic-wolf-and-kroll/) - [Arctic Wolf and Mandiant](/side-by-side/arctic-wolf-and-mandiant/) - [Arctic Wolf and Microsoft](/side-by-side/arctic-wolf-and-microsoft/) - [Arctic Wolf and Rapid7](/side-by-side/arctic-wolf-and-rapid7/) - [Arctic Wolf and Red Canary](/side-by-side/arctic-wolf-and-red-canary/) - [Arctic Wolf and SentinelOne](/side-by-side/arctic-wolf-and-sentinelone/) - [Arctic Wolf and Sophos](/side-by-side/arctic-wolf-and-sophos/) - [Arctic Wolf and Sygnia](/side-by-side/arctic-wolf-and-sygnia/) ### BlueVoyant - [Arctic Wolf and BlueVoyant](/side-by-side/arctic-wolf-and-bluevoyant/) - [BlueVoyant and Critical Start](/side-by-side/bluevoyant-and-critical-start/) - [BlueVoyant and CrowdStrike](/side-by-side/bluevoyant-and-crowdstrike/) - [BlueVoyant and Deepwatch](/side-by-side/bluevoyant-and-deepwatch/) - [BlueVoyant and eSentire](/side-by-side/bluevoyant-and-esentire/) - [BlueVoyant and Expel](/side-by-side/bluevoyant-and-expel/) - [BlueVoyant and Huntress](/side-by-side/bluevoyant-and-huntress/) - [BlueVoyant and Kroll](/side-by-side/bluevoyant-and-kroll/) - [BlueVoyant and Mandiant](/side-by-side/bluevoyant-and-mandiant/) - [BlueVoyant and Microsoft](/side-by-side/bluevoyant-and-microsoft/) - [BlueVoyant and Rapid7](/side-by-side/bluevoyant-and-rapid7/) - [BlueVoyant and Red Canary](/side-by-side/bluevoyant-and-red-canary/) - [BlueVoyant and SentinelOne](/side-by-side/bluevoyant-and-sentinelone/) - [BlueVoyant and Sophos](/side-by-side/bluevoyant-and-sophos/) - [BlueVoyant and Sygnia](/side-by-side/bluevoyant-and-sygnia/) ### Critical Start - [Arctic Wolf and Critical Start](/side-by-side/arctic-wolf-and-critical-start/) - [BlueVoyant and Critical Start](/side-by-side/bluevoyant-and-critical-start/) - [Critical Start and CrowdStrike](/side-by-side/critical-start-and-crowdstrike/) - [Critical Start and Deepwatch](/side-by-side/critical-start-and-deepwatch/) - [Critical Start and eSentire](/side-by-side/critical-start-and-esentire/) - [Critical Start and Expel](/side-by-side/critical-start-and-expel/) - [Critical Start and Huntress](/side-by-side/critical-start-and-huntress/) - [Critical Start and Kroll](/side-by-side/critical-start-and-kroll/) - [Critical Start and Mandiant](/side-by-side/critical-start-and-mandiant/) - [Critical Start and Microsoft](/side-by-side/critical-start-and-microsoft/) - [Critical Start and Rapid7](/side-by-side/critical-start-and-rapid7/) - [Critical Start and Red Canary](/side-by-side/critical-start-and-red-canary/) - [Critical Start and SentinelOne](/side-by-side/critical-start-and-sentinelone/) - [Critical Start and Sophos](/side-by-side/critical-start-and-sophos/) - [Critical Start and Sygnia](/side-by-side/critical-start-and-sygnia/) ### CrowdStrike - [Arctic Wolf and CrowdStrike](/side-by-side/arctic-wolf-and-crowdstrike/) - [BlueVoyant and CrowdStrike](/side-by-side/bluevoyant-and-crowdstrike/) - [Critical Start and CrowdStrike](/side-by-side/critical-start-and-crowdstrike/) - [CrowdStrike and Deepwatch](/side-by-side/crowdstrike-and-deepwatch/) - [CrowdStrike and eSentire](/side-by-side/crowdstrike-and-esentire/) - [CrowdStrike and Expel](/side-by-side/crowdstrike-and-expel/) - [CrowdStrike and Huntress](/side-by-side/crowdstrike-and-huntress/) - [CrowdStrike and Kroll](/side-by-side/crowdstrike-and-kroll/) - [CrowdStrike and Mandiant](/side-by-side/crowdstrike-and-mandiant/) - [CrowdStrike and Microsoft](/side-by-side/crowdstrike-and-microsoft/) - [CrowdStrike and Rapid7](/side-by-side/crowdstrike-and-rapid7/) - [CrowdStrike and Red Canary](/side-by-side/crowdstrike-and-red-canary/) - [CrowdStrike and SentinelOne](/side-by-side/crowdstrike-and-sentinelone/) - [CrowdStrike and Sophos](/side-by-side/crowdstrike-and-sophos/) - [CrowdStrike and Sygnia](/side-by-side/crowdstrike-and-sygnia/) ### Deepwatch - [Arctic Wolf and Deepwatch](/side-by-side/arctic-wolf-and-deepwatch/) - [BlueVoyant and Deepwatch](/side-by-side/bluevoyant-and-deepwatch/) - [Critical Start and Deepwatch](/side-by-side/critical-start-and-deepwatch/) - [CrowdStrike and Deepwatch](/side-by-side/crowdstrike-and-deepwatch/) - [Deepwatch and eSentire](/side-by-side/deepwatch-and-esentire/) - [Deepwatch and Expel](/side-by-side/deepwatch-and-expel/) - [Deepwatch and Huntress](/side-by-side/deepwatch-and-huntress/) - [Deepwatch and Kroll](/side-by-side/deepwatch-and-kroll/) - [Deepwatch and Mandiant](/side-by-side/deepwatch-and-mandiant/) - [Deepwatch and Microsoft](/side-by-side/deepwatch-and-microsoft/) - [Deepwatch and Rapid7](/side-by-side/deepwatch-and-rapid7/) - [Deepwatch and Red Canary](/side-by-side/deepwatch-and-red-canary/) - [Deepwatch and SentinelOne](/side-by-side/deepwatch-and-sentinelone/) - [Deepwatch and Sophos](/side-by-side/deepwatch-and-sophos/) - [Deepwatch and Sygnia](/side-by-side/deepwatch-and-sygnia/) ### eSentire - [Arctic Wolf and eSentire](/side-by-side/arctic-wolf-and-esentire/) - [BlueVoyant and eSentire](/side-by-side/bluevoyant-and-esentire/) - [Critical Start and eSentire](/side-by-side/critical-start-and-esentire/) - [CrowdStrike and eSentire](/side-by-side/crowdstrike-and-esentire/) - [Deepwatch and eSentire](/side-by-side/deepwatch-and-esentire/) - [eSentire and Expel](/side-by-side/esentire-and-expel/) - [eSentire and Huntress](/side-by-side/esentire-and-huntress/) - [eSentire and Kroll](/side-by-side/esentire-and-kroll/) - [eSentire and Mandiant](/side-by-side/esentire-and-mandiant/) - [eSentire and Microsoft](/side-by-side/esentire-and-microsoft/) - [eSentire and Rapid7](/side-by-side/esentire-and-rapid7/) - [eSentire and Red Canary](/side-by-side/esentire-and-red-canary/) - [eSentire and SentinelOne](/side-by-side/esentire-and-sentinelone/) - [eSentire and Sophos](/side-by-side/esentire-and-sophos/) - [eSentire and Sygnia](/side-by-side/esentire-and-sygnia/) ### Expel - [Arctic Wolf and Expel](/side-by-side/arctic-wolf-and-expel/) - [BlueVoyant and Expel](/side-by-side/bluevoyant-and-expel/) - [Critical Start and Expel](/side-by-side/critical-start-and-expel/) - [CrowdStrike and Expel](/side-by-side/crowdstrike-and-expel/) - [Deepwatch and Expel](/side-by-side/deepwatch-and-expel/) - [eSentire and Expel](/side-by-side/esentire-and-expel/) - [Expel and Huntress](/side-by-side/expel-and-huntress/) - [Expel and Kroll](/side-by-side/expel-and-kroll/) - [Expel and Mandiant](/side-by-side/expel-and-mandiant/) - [Expel and Microsoft](/side-by-side/expel-and-microsoft/) - [Expel and Rapid7](/side-by-side/expel-and-rapid7/) - [Expel and Red Canary](/side-by-side/expel-and-red-canary/) - [Expel and SentinelOne](/side-by-side/expel-and-sentinelone/) - [Expel and Sophos](/side-by-side/expel-and-sophos/) - [Expel and Sygnia](/side-by-side/expel-and-sygnia/) ### Huntress - [Arctic Wolf and Huntress](/side-by-side/arctic-wolf-and-huntress/) - [BlueVoyant and Huntress](/side-by-side/bluevoyant-and-huntress/) - [Critical Start and Huntress](/side-by-side/critical-start-and-huntress/) - [CrowdStrike and Huntress](/side-by-side/crowdstrike-and-huntress/) - [Deepwatch and Huntress](/side-by-side/deepwatch-and-huntress/) - [eSentire and Huntress](/side-by-side/esentire-and-huntress/) - [Expel and Huntress](/side-by-side/expel-and-huntress/) - [Huntress and Kroll](/side-by-side/huntress-and-kroll/) - [Huntress and Mandiant](/side-by-side/huntress-and-mandiant/) - [Huntress and Microsoft](/side-by-side/huntress-and-microsoft/) - [Huntress and Rapid7](/side-by-side/huntress-and-rapid7/) - [Huntress and Red Canary](/side-by-side/huntress-and-red-canary/) - [Huntress and SentinelOne](/side-by-side/huntress-and-sentinelone/) - [Huntress and Sophos](/side-by-side/huntress-and-sophos/) - [Huntress and Sygnia](/side-by-side/huntress-and-sygnia/) ### Kroll - [Arctic Wolf and Kroll](/side-by-side/arctic-wolf-and-kroll/) - [BlueVoyant and Kroll](/side-by-side/bluevoyant-and-kroll/) - [Critical Start and Kroll](/side-by-side/critical-start-and-kroll/) - [CrowdStrike and Kroll](/side-by-side/crowdstrike-and-kroll/) - [Deepwatch and Kroll](/side-by-side/deepwatch-and-kroll/) - [eSentire and Kroll](/side-by-side/esentire-and-kroll/) - [Expel and Kroll](/side-by-side/expel-and-kroll/) - [Huntress and Kroll](/side-by-side/huntress-and-kroll/) - [Kroll and Mandiant](/side-by-side/kroll-and-mandiant/) - [Kroll and Microsoft](/side-by-side/kroll-and-microsoft/) - [Kroll and Rapid7](/side-by-side/kroll-and-rapid7/) - [Kroll and Red Canary](/side-by-side/kroll-and-red-canary/) - [Kroll and SentinelOne](/side-by-side/kroll-and-sentinelone/) - [Kroll and Sophos](/side-by-side/kroll-and-sophos/) - [Kroll and Sygnia](/side-by-side/kroll-and-sygnia/) ### Mandiant - [Arctic Wolf and Mandiant](/side-by-side/arctic-wolf-and-mandiant/) - [BlueVoyant and Mandiant](/side-by-side/bluevoyant-and-mandiant/) - [Critical Start and Mandiant](/side-by-side/critical-start-and-mandiant/) - [CrowdStrike and Mandiant](/side-by-side/crowdstrike-and-mandiant/) - [Deepwatch and Mandiant](/side-by-side/deepwatch-and-mandiant/) - [eSentire and Mandiant](/side-by-side/esentire-and-mandiant/) - [Expel and Mandiant](/side-by-side/expel-and-mandiant/) - [Huntress and Mandiant](/side-by-side/huntress-and-mandiant/) - [Kroll and Mandiant](/side-by-side/kroll-and-mandiant/) - [Mandiant and Microsoft](/side-by-side/mandiant-and-microsoft/) - [Mandiant and Rapid7](/side-by-side/mandiant-and-rapid7/) - [Mandiant and Red Canary](/side-by-side/mandiant-and-red-canary/) - [Mandiant and SentinelOne](/side-by-side/mandiant-and-sentinelone/) - [Mandiant and Sophos](/side-by-side/mandiant-and-sophos/) - [Mandiant and Sygnia](/side-by-side/mandiant-and-sygnia/) ### Microsoft - [Arctic Wolf and Microsoft](/side-by-side/arctic-wolf-and-microsoft/) - [BlueVoyant and Microsoft](/side-by-side/bluevoyant-and-microsoft/) - [Critical Start and Microsoft](/side-by-side/critical-start-and-microsoft/) - [CrowdStrike and Microsoft](/side-by-side/crowdstrike-and-microsoft/) - [Deepwatch and Microsoft](/side-by-side/deepwatch-and-microsoft/) - [eSentire and Microsoft](/side-by-side/esentire-and-microsoft/) - [Expel and Microsoft](/side-by-side/expel-and-microsoft/) - [Huntress and Microsoft](/side-by-side/huntress-and-microsoft/) - [Kroll and Microsoft](/side-by-side/kroll-and-microsoft/) - [Mandiant and Microsoft](/side-by-side/mandiant-and-microsoft/) - [Microsoft and Rapid7](/side-by-side/microsoft-and-rapid7/) - [Microsoft and Red Canary](/side-by-side/microsoft-and-red-canary/) - [Microsoft and SentinelOne](/side-by-side/microsoft-and-sentinelone/) - [Microsoft and Sophos](/side-by-side/microsoft-and-sophos/) - [Microsoft and Sygnia](/side-by-side/microsoft-and-sygnia/) ### Rapid7 - [Arctic Wolf and Rapid7](/side-by-side/arctic-wolf-and-rapid7/) - [BlueVoyant and Rapid7](/side-by-side/bluevoyant-and-rapid7/) - [Critical Start and Rapid7](/side-by-side/critical-start-and-rapid7/) - [CrowdStrike and Rapid7](/side-by-side/crowdstrike-and-rapid7/) - [Deepwatch and Rapid7](/side-by-side/deepwatch-and-rapid7/) - [eSentire and Rapid7](/side-by-side/esentire-and-rapid7/) - [Expel and Rapid7](/side-by-side/expel-and-rapid7/) - [Huntress and Rapid7](/side-by-side/huntress-and-rapid7/) - [Kroll and Rapid7](/side-by-side/kroll-and-rapid7/) - [Mandiant and Rapid7](/side-by-side/mandiant-and-rapid7/) - [Microsoft and Rapid7](/side-by-side/microsoft-and-rapid7/) - [Rapid7 and Red Canary](/side-by-side/rapid7-and-red-canary/) - [Rapid7 and SentinelOne](/side-by-side/rapid7-and-sentinelone/) - [Rapid7 and Sophos](/side-by-side/rapid7-and-sophos/) - [Rapid7 and Sygnia](/side-by-side/rapid7-and-sygnia/) ### Red Canary - [Arctic Wolf and Red Canary](/side-by-side/arctic-wolf-and-red-canary/) - [BlueVoyant and Red Canary](/side-by-side/bluevoyant-and-red-canary/) - [Critical Start and Red Canary](/side-by-side/critical-start-and-red-canary/) - [CrowdStrike and Red Canary](/side-by-side/crowdstrike-and-red-canary/) - [Deepwatch and Red Canary](/side-by-side/deepwatch-and-red-canary/) - [eSentire and Red Canary](/side-by-side/esentire-and-red-canary/) - [Expel and Red Canary](/side-by-side/expel-and-red-canary/) - [Huntress and Red Canary](/side-by-side/huntress-and-red-canary/) - [Kroll and Red Canary](/side-by-side/kroll-and-red-canary/) - [Mandiant and Red Canary](/side-by-side/mandiant-and-red-canary/) - [Microsoft and Red Canary](/side-by-side/microsoft-and-red-canary/) - [Rapid7 and Red Canary](/side-by-side/rapid7-and-red-canary/) - [Red Canary and SentinelOne](/side-by-side/red-canary-and-sentinelone/) - [Red Canary and Sophos](/side-by-side/red-canary-and-sophos/) - [Red Canary and Sygnia](/side-by-side/red-canary-and-sygnia/) ### SentinelOne - [Arctic Wolf and SentinelOne](/side-by-side/arctic-wolf-and-sentinelone/) - [BlueVoyant and SentinelOne](/side-by-side/bluevoyant-and-sentinelone/) - [Critical Start and SentinelOne](/side-by-side/critical-start-and-sentinelone/) - [CrowdStrike and SentinelOne](/side-by-side/crowdstrike-and-sentinelone/) - [Deepwatch and SentinelOne](/side-by-side/deepwatch-and-sentinelone/) - [eSentire and SentinelOne](/side-by-side/esentire-and-sentinelone/) - [Expel and SentinelOne](/side-by-side/expel-and-sentinelone/) - [Huntress and SentinelOne](/side-by-side/huntress-and-sentinelone/) - [Kroll and SentinelOne](/side-by-side/kroll-and-sentinelone/) - [Mandiant and SentinelOne](/side-by-side/mandiant-and-sentinelone/) - [Microsoft and SentinelOne](/side-by-side/microsoft-and-sentinelone/) - [Rapid7 and SentinelOne](/side-by-side/rapid7-and-sentinelone/) - [Red Canary and SentinelOne](/side-by-side/red-canary-and-sentinelone/) - [SentinelOne and Sophos](/side-by-side/sentinelone-and-sophos/) - [SentinelOne and Sygnia](/side-by-side/sentinelone-and-sygnia/) ### Sophos - [Arctic Wolf and Sophos](/side-by-side/arctic-wolf-and-sophos/) - [BlueVoyant and Sophos](/side-by-side/bluevoyant-and-sophos/) - [Critical Start and Sophos](/side-by-side/critical-start-and-sophos/) - [CrowdStrike and Sophos](/side-by-side/crowdstrike-and-sophos/) - [Deepwatch and Sophos](/side-by-side/deepwatch-and-sophos/) - [eSentire and Sophos](/side-by-side/esentire-and-sophos/) - [Expel and Sophos](/side-by-side/expel-and-sophos/) - [Huntress and Sophos](/side-by-side/huntress-and-sophos/) - [Kroll and Sophos](/side-by-side/kroll-and-sophos/) - [Mandiant and Sophos](/side-by-side/mandiant-and-sophos/) - [Microsoft and Sophos](/side-by-side/microsoft-and-sophos/) - [Rapid7 and Sophos](/side-by-side/rapid7-and-sophos/) - [Red Canary and Sophos](/side-by-side/red-canary-and-sophos/) - [SentinelOne and Sophos](/side-by-side/sentinelone-and-sophos/) - [Sophos and Sygnia](/side-by-side/sophos-and-sygnia/) ### Sygnia - [Arctic Wolf and Sygnia](/side-by-side/arctic-wolf-and-sygnia/) - [BlueVoyant and Sygnia](/side-by-side/bluevoyant-and-sygnia/) - [Critical Start and Sygnia](/side-by-side/critical-start-and-sygnia/) - [CrowdStrike and Sygnia](/side-by-side/crowdstrike-and-sygnia/) - [Deepwatch and Sygnia](/side-by-side/deepwatch-and-sygnia/) - [eSentire and Sygnia](/side-by-side/esentire-and-sygnia/) - [Expel and Sygnia](/side-by-side/expel-and-sygnia/) - [Huntress and Sygnia](/side-by-side/huntress-and-sygnia/) - [Kroll and Sygnia](/side-by-side/kroll-and-sygnia/) - [Mandiant and Sygnia](/side-by-side/mandiant-and-sygnia/) - [Microsoft and Sygnia](/side-by-side/microsoft-and-sygnia/) - [Rapid7 and Sygnia](/side-by-side/rapid7-and-sygnia/) - [Red Canary and Sygnia](/side-by-side/red-canary-and-sygnia/) - [SentinelOne and Sygnia](/side-by-side/sentinelone-and-sygnia/) - [Sophos and Sygnia](/side-by-side/sophos-and-sygnia/) ## Related pages - [Home: MDR vs MSSP in short](/) - [The MDR Service Matrix](/matrix/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [How this site lists services](/method/) - [Glossary](/glossary/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/ --- # Arctic Wolf and BlueVoyant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and BlueVoyant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; BlueVoyant 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Arctic Wolf and BlueVoyant differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and BlueVoyant has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and BlueVoyant has 4 stated, 1 with limits, 2 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | BlueVoyant | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated The provider says its MDR does threat containment across endpoints. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated The provider says its MDR does automated blocking across endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | None found on 10 November 2026 | ## Data watched | Data | Arctic Wolf | BlueVoyant | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated BlueVoyant says its MDR protects endpoints. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated BlueVoyant says its MDR protects cloud and containers. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated BlueVoyant says its MDR protects network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | ## The fifteen questions | Question | Arctic Wolf | BlueVoyant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | BlueVoyant | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [BlueVoyant, all published facts](/services/bluevoyant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-bluevoyant/ --- # Arctic Wolf and Critical Start, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Critical Start, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Critical Start 3 stated, 2 with limits, 1 none found. The page gives no verdict. ## How do Arctic Wolf and Critical Start differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Critical Start has 3 stated, 2 with limits, 1 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Critical Start has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Critical Start | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Lists endpoint response actions including isolate host. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated Lists identity actions including disable account and reset password. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists block file hash, block IP and block sender. | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider says its customer-approved playbook may include process termination. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | ## Data watched | Data | Arctic Wolf | Critical Start | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Lists endpoint response actions. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Lists identity response actions. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated The provider says cloud is covered by detection; its cloud response is advisory. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Lists network response actions such as block IP. | | Email | None found on 10 November 2026 | Stated Lists email actions such as quarantine message. | | OT | None found on 10 November 2026 | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Says 100+ integrations and no proprietary agents required. | ## The fifteen questions | Question | Arctic Wolf | Critical Start | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Critical Start says CORR supports 100+ integrations across seven security domains. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | | Is OT covered? | None found on 10 Nov 2026 | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Critical Start | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Critical Start, all published facts](/services/critical-start/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-critical-start/ --- # Arctic Wolf and CrowdStrike, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and CrowdStrike, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; CrowdStrike 1 stated, 1 with limits, 4 none found. The page gives no verdict. ## How do Arctic Wolf and CrowdStrike differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and CrowdStrike has 1 stated, 1 with limits, 4 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and CrowdStrike has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | CrowdStrike | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | None found on 10 November 2026 | ## Data watched | Data | Arctic Wolf | CrowdStrike | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Time to contain is defined on an endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Telemetry includes identities; a managed identity service is added. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Telemetry includes cloud; managed cloud workload protection is added. | | Network | Stated with limits IDC says it aims for visibility across network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | ## The fifteen questions | Question | Arctic Wolf | CrowdStrike | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | CrowdStrike | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [CrowdStrike, all published facts](/services/crowdstrike/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-crowdstrike/ --- # Arctic Wolf and Deepwatch, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Deepwatch, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Deepwatch 4 stated, 0 with limits, 2 none found. The page gives no verdict. ## How do Arctic Wolf and Deepwatch differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Deepwatch has 4 stated, 0 with limits, 2 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Deepwatch has 5 stated, 0 with limits, 2 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Deepwatch | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Active Response lists host isolation for endpoints. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated Active Response lists password reset and account control actions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Active Response lists process termination for endpoints. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | ## Data watched | Data | Arctic Wolf | Deepwatch | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Platform page shows endpoint in the environment it works with. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Platform page shows identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Platform page shows cloud. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Platform page shows network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Calls itself agnostic with a Bring Your Own Tech approach. | ## The fifteen questions | Question | Arctic Wolf | Deepwatch | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | None found on 10 Nov 2026 | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Deepwatch | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Deepwatch, all published facts](/services/deepwatch/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-deepwatch/ --- # Arctic Wolf and eSentire, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and eSentire, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; eSentire 6 stated, 0 with limits, 0 none found. The page gives no verdict. ## How do Arctic Wolf and eSentire differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and eSentire has 6 stated, 0 with limits, 0 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and eSentire has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | eSentire | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## Data watched | Data | Arctic Wolf | eSentire | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Atlas ingests endpoint signals. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Atlas ingests network signals. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions | Question | Arctic Wolf | eSentire | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | Is OT covered? | None found on 10 Nov 2026 | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | eSentire | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [eSentire, all published facts](/services/esentire/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-esentire/ --- # Arctic Wolf and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do Arctic Wolf and Expel differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Expel | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | None found on 10 November 2026 | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | Arctic Wolf | Expel | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Packages page lists endpoints. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Packages page lists identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Packages page lists cloud workloads and control planes. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | Arctic Wolf | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | None found on 10 Nov 2026 | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Expel | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-expel/ --- # Arctic Wolf and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do Arctic Wolf and Huntress differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Huntress | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | None found on 10 November 2026 | ## Data watched | Data | Arctic Wolf | Huntress | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | Arctic Wolf | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | None found on 10 Nov 2026 | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Huntress | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-huntress/ --- # Arctic Wolf and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do Arctic Wolf and Kroll differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Kroll | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | None found on 10 November 2026 | ## Data watched | Data | Arctic Wolf | Kroll | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Case study says visibility across endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Case study says visibility across identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Case study says visibility across cloud. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | Arctic Wolf | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | None found on 10 Nov 2026 | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Kroll | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-kroll/ --- # Arctic Wolf and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Arctic Wolf and Mandiant differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Mandiant | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | None found on 10 November 2026 | ## Data watched | Data | Arctic Wolf | Mandiant | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Full-stack monitoring across endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | None found on 10 November 2026 | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Arctic Wolf | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Mandiant | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-mandiant/ --- # Arctic Wolf and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Arctic Wolf and Microsoft differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Microsoft | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Arctic Wolf | Microsoft | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated MDR page says it protects identities. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Arctic Wolf | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Microsoft | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-microsoft/ --- # Arctic Wolf and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Arctic Wolf and Rapid7 differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Rapid7 | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Arctic Wolf | Rapid7 | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated MDR page lists endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated MDR page lists identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated MDR page lists cloud. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Arctic Wolf | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | None found on 10 Nov 2026 | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Rapid7 | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-rapid7/ --- # Arctic Wolf and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Arctic Wolf and Red Canary differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Red Canary | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Arctic Wolf | Red Canary | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Page lists endpoint as a key domain. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Page lists identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Arctic Wolf | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | None found on 10 Nov 2026 | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Red Canary | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-red-canary/ --- # Arctic Wolf and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Arctic Wolf and SentinelOne differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | SentinelOne | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Arctic Wolf | SentinelOne | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Core detection coverage includes endpoint. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Core detection coverage includes identity. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Core detection coverage includes cloud. | | Network | Stated with limits IDC says it aims for visibility across network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Arctic Wolf | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | SentinelOne | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-sentinelone/ --- # Arctic Wolf and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Arctic Wolf and Sophos differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Sophos | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Arctic Wolf | Sophos | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated MDR page states endpoint coverage. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated MDR page states identity coverage. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated MDR page states cloud coverage. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Arctic Wolf | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Sophos | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-sophos/ --- # Arctic Wolf and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Arctic Wolf and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Arctic Wolf 0 stated, 3 with limits, 3 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Arctic Wolf and Sygnia differ? On the six actions read, Arctic Wolf has 0 stated, 3 with limits, 3 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Arctic Wolf has 1 stated, 4 with limits, 2 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Arctic Wolf | Sygnia | | --- | --- | --- | | Isolate a host | Stated with limits Managed Containment workflow isolates the threat at network and host level, started with the customer. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated with limits Its own timeline example records password resets for compromised admin and service accounts. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Example shows endpoint containment under predefined customer instructions; page says humans stay in the loop. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Arctic Wolf | Sygnia | | --- | --- | --- | | Endpoint | Stated with limits IDC says Arctic Wolf aims for visibility across endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated with limits IDC says it aims for visibility across identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated with limits IDC says it aims for visibility across cloud. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated with limits IDC says it aims for visibility across network. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated The provider says it works with other security tools; IDC says it ingests telemetry from existing tooling. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Arctic Wolf | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Arctic Wolf | Sygnia | | --- | --- | --- | | Does well | Arctic Wolf says its open XDR platform supports over 200 integrations without ripping and replacing products. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Arctic Wolf prints no minute-level SLA and no prices; it separates IR from MDR, and OT coverage was none found on 10 Nov 2026. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Arctic Wolf, all published facts](/services/arctic-wolf/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Incident response timeline ransomware attack containment" page (the firm's own page): https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/arctic-wolf-and-sygnia/ --- # BlueVoyant and Critical Start, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Critical Start, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Critical Start 3 stated, 2 with limits, 1 none found. The page gives no verdict. ## How do BlueVoyant and Critical Start differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Critical Start has 3 stated, 2 with limits, 1 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Critical Start has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Critical Start | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Lists endpoint response actions including isolate host. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists identity actions including disable account and reset password. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | Stated Lists block file hash, block IP and block sender. | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider says its customer-approved playbook may include process termination. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | ## Data watched | Data | BlueVoyant | Critical Start | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Lists endpoint response actions. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Lists identity response actions. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated The provider says cloud is covered by detection; its cloud response is advisory. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Lists network response actions such as block IP. | | Email | None found on 10 November 2026 | Stated Lists email actions such as quarantine message. | | OT | None found on 10 November 2026 | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Says 100+ integrations and no proprietary agents required. | ## The fifteen questions | Question | BlueVoyant | Critical Start | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Critical Start says CORR supports 100+ integrations across seven security domains. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | Is the pricing model published? | None found on 10 Nov 2026 | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | | Is OT covered? | None found on 10 Nov 2026 | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Critical Start | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Critical Start, all published facts](/services/critical-start/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-critical-start/ --- # BlueVoyant and CrowdStrike, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and CrowdStrike, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; CrowdStrike 1 stated, 1 with limits, 4 none found. The page gives no verdict. ## How do BlueVoyant and CrowdStrike differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and CrowdStrike has 1 stated, 1 with limits, 4 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and CrowdStrike has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | BlueVoyant | CrowdStrike | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | BlueVoyant | CrowdStrike | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Time to contain is defined on an endpoint. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Telemetry includes identities; a managed identity service is added. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Telemetry includes cloud; managed cloud workload protection is added. | | Network | Stated BlueVoyant says its MDR protects network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | ## The fifteen questions | Question | BlueVoyant | CrowdStrike | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | Is the pricing model published? | None found on 10 Nov 2026 | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | CrowdStrike | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [CrowdStrike, all published facts](/services/crowdstrike/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-crowdstrike/ --- # BlueVoyant and Deepwatch, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Deepwatch, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Deepwatch 4 stated, 0 with limits, 2 none found. The page gives no verdict. ## How do BlueVoyant and Deepwatch differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Deepwatch has 4 stated, 0 with limits, 2 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Deepwatch has 5 stated, 0 with limits, 2 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Deepwatch | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Active Response lists host isolation for endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated Active Response lists password reset and account control actions. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Active Response lists process termination for endpoints. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | ## Data watched | Data | BlueVoyant | Deepwatch | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Platform page shows endpoint in the environment it works with. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Platform page shows identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Platform page shows cloud. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Platform page shows network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Calls itself agnostic with a Bring Your Own Tech approach. | ## The fifteen questions | Question | BlueVoyant | Deepwatch | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Deepwatch | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Deepwatch, all published facts](/services/deepwatch/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-deepwatch/ --- # BlueVoyant and eSentire, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and eSentire, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; eSentire 6 stated, 0 with limits, 0 none found. The page gives no verdict. ## How do BlueVoyant and eSentire differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and eSentire has 6 stated, 0 with limits, 0 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and eSentire has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | eSentire | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | None found on 10 November 2026 | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## Data watched | Data | BlueVoyant | eSentire | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Atlas ingests endpoint signals. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Atlas ingests network signals. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions | Question | BlueVoyant | eSentire | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | Is the pricing model published? | None found on 10 Nov 2026 | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | Is OT covered? | None found on 10 Nov 2026 | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | eSentire | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [eSentire, all published facts](/services/esentire/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-esentire/ --- # BlueVoyant and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do BlueVoyant and Expel differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Expel | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | None found on 10 November 2026 | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | BlueVoyant | Expel | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Packages page lists endpoints. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Packages page lists identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Packages page lists cloud workloads and control planes. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | BlueVoyant | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | None found on 10 Nov 2026 | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | None found on 10 Nov 2026 | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Expel | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-expel/ --- # BlueVoyant and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do BlueVoyant and Huntress differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Huntress | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | BlueVoyant | Huntress | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated BlueVoyant says its MDR protects network. | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | BlueVoyant | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Huntress | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-huntress/ --- # BlueVoyant and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do BlueVoyant and Kroll differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Kroll | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | BlueVoyant | Kroll | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Case study says visibility across endpoint. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Case study says visibility across identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Case study says visibility across cloud. | | Network | Stated BlueVoyant says its MDR protects network. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | BlueVoyant | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | None found on 10 Nov 2026 | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Kroll | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-kroll/ --- # BlueVoyant and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do BlueVoyant and Mandiant differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Mandiant | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | BlueVoyant | Mandiant | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Full-stack monitoring across endpoint. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | None found on 10 November 2026 | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | BlueVoyant | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Mandiant | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-mandiant/ --- # BlueVoyant and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do BlueVoyant and Microsoft differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Microsoft | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | BlueVoyant | Microsoft | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated MDR page says it protects identities. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | BlueVoyant | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | None found on 10 Nov 2026 | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Microsoft | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-microsoft/ --- # BlueVoyant and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do BlueVoyant and Rapid7 differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Rapid7 | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | BlueVoyant | Rapid7 | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated MDR page lists endpoint. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated MDR page lists identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated MDR page lists cloud. | | Network | Stated BlueVoyant says its MDR protects network. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | BlueVoyant | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Rapid7 | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-rapid7/ --- # BlueVoyant and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do BlueVoyant and Red Canary differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Red Canary | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | None found on 10 November 2026 | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | BlueVoyant | Red Canary | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Page lists endpoint as a key domain. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Page lists identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | BlueVoyant | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Red Canary | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-red-canary/ --- # BlueVoyant and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do BlueVoyant and SentinelOne differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | BlueVoyant | SentinelOne | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | BlueVoyant | SentinelOne | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Core detection coverage includes endpoint. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Core detection coverage includes identity. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Core detection coverage includes cloud. | | Network | Stated BlueVoyant says its MDR protects network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | BlueVoyant | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | None found on 10 Nov 2026 | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | SentinelOne | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-sentinelone/ --- # BlueVoyant and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do BlueVoyant and Sophos differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Sophos | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | BlueVoyant | Sophos | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated MDR page states endpoint coverage. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated MDR page states identity coverage. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated MDR page states cloud coverage. | | Network | Stated BlueVoyant says its MDR protects network. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | BlueVoyant | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | None found on 10 Nov 2026 | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Sophos | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-sophos/ --- # BlueVoyant and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** BlueVoyant and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: BlueVoyant 2 stated, 0 with limits, 4 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do BlueVoyant and Sygnia differ? On the six actions read, BlueVoyant has 2 stated, 0 with limits, 4 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, BlueVoyant has 4 stated, 1 with limits, 2 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | BlueVoyant | Sygnia | | --- | --- | --- | | Isolate a host | Stated The provider says its MDR does threat containment across endpoints. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated The provider says its MDR does automated blocking across endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | BlueVoyant | Sygnia | | --- | --- | --- | | Endpoint | Stated BlueVoyant says its MDR protects endpoints. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated with limits Agentic Identity Services appear in its MDR for Microsoft menu. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated BlueVoyant says its MDR protects cloud and containers. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated BlueVoyant says its MDR protects network. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated The provider says its MDR strengthens existing EDR, SIEM and cloud tools. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | BlueVoyant | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | None found on 10 Nov 2026 | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | BlueVoyant | Sygnia | | --- | --- | --- | | Does well | BlueVoyant says its MDR for Microsoft includes unlimited remote incident response lifecycle support and runs 24x7 in-regional SOCs. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | BlueVoyant's pages read print no response commitments or pricing model for MDR, and its DFIR retainer is sold on a separate page. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [BlueVoyant, all published facts](/services/bluevoyant/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/bluevoyant-and-sygnia/ --- # Critical Start and CrowdStrike, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and CrowdStrike, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; CrowdStrike 1 stated, 1 with limits, 4 none found. The page gives no verdict. ## How do Critical Start and CrowdStrike differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and CrowdStrike has 1 stated, 1 with limits, 4 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and CrowdStrike has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Critical Start | CrowdStrike | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | None found on 10 November 2026 | ## Data watched | Data | Critical Start | CrowdStrike | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Time to contain is defined on an endpoint. | | Identity | Stated Lists identity response actions. | Stated Telemetry includes identities; a managed identity service is added. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Telemetry includes cloud; managed cloud workload protection is added. | | Network | Stated Lists network response actions such as block IP. | None found on 10 November 2026 | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | ## The fifteen questions | Question | Critical Start | CrowdStrike | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | CrowdStrike | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [CrowdStrike, all published facts](/services/crowdstrike/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-crowdstrike/ --- # Critical Start and Deepwatch, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Deepwatch, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Deepwatch 4 stated, 0 with limits, 2 none found. The page gives no verdict. ## How do Critical Start and Deepwatch differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Deepwatch has 4 stated, 0 with limits, 2 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Deepwatch has 5 stated, 0 with limits, 2 none found. ## Actions on the customer's behalf | Action | Critical Start | Deepwatch | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Active Response lists host isolation for endpoints. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated Active Response lists password reset and account control actions. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated Active Response lists process termination for endpoints. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | ## Data watched | Data | Critical Start | Deepwatch | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Platform page shows endpoint in the environment it works with. | | Identity | Stated Lists identity response actions. | Stated Platform page shows identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Platform page shows cloud. | | Network | Stated Lists network response actions such as block IP. | Stated Platform page shows network. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Calls itself agnostic with a Bring Your Own Tech approach. | ## The fifteen questions | Question | Critical Start | Deepwatch | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | None found on 10 Nov 2026 | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | None found on 10 Nov 2026 | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Deepwatch | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Deepwatch, all published facts](/services/deepwatch/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-deepwatch/ --- # Critical Start and eSentire, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and eSentire, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; eSentire 6 stated, 0 with limits, 0 none found. The page gives no verdict. ## How do Critical Start and eSentire differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and eSentire has 6 stated, 0 with limits, 0 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and eSentire has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | eSentire | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## Data watched | Data | Critical Start | eSentire | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Atlas ingests endpoint signals. | | Identity | Stated Lists identity response actions. | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | Stated Lists network response actions such as block IP. | Stated Atlas ingests network signals. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions | Question | Critical Start | eSentire | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | eSentire | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [eSentire, all published facts](/services/esentire/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-esentire/ --- # Critical Start and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do Critical Start and Expel differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | Expel | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | None found on 10 November 2026 | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | Critical Start | Expel | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Packages page lists endpoints. | | Identity | Stated Lists identity response actions. | Stated Packages page lists identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Packages page lists cloud workloads and control planes. | | Network | Stated Lists network response actions such as block IP. | Stated Packages page lists networks. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | Critical Start | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Expel | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-expel/ --- # Critical Start and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do Critical Start and Huntress differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | Critical Start | Huntress | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | None found on 10 November 2026 | ## Data watched | Data | Critical Start | Huntress | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated Lists identity response actions. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated Lists network response actions such as block IP. | Stated with limits Managed SIEM page says it connects network activity. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | Critical Start | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | None found on 10 Nov 2026 | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Huntress | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-huntress/ --- # Critical Start and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do Critical Start and Kroll differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | Kroll | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | None found on 10 November 2026 | ## Data watched | Data | Critical Start | Kroll | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Case study says visibility across endpoint. | | Identity | Stated Lists identity response actions. | Stated Case study says visibility across identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Case study says visibility across cloud. | | Network | Stated Lists network response actions such as block IP. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | Critical Start | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | None found on 10 Nov 2026 | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Kroll | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-kroll/ --- # Critical Start and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Critical Start and Mandiant differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Critical Start | Mandiant | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | None found on 10 November 2026 | ## Data watched | Data | Critical Start | Mandiant | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Full-stack monitoring across endpoint. | | Identity | Stated Lists identity response actions. | None found on 10 November 2026 | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated Lists network response actions such as block IP. | Stated Full-stack monitoring across network. | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Critical Start | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | None found on 10 Nov 2026 | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Mandiant | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-mandiant/ --- # Critical Start and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Critical Start and Microsoft differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | Microsoft | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Critical Start | Microsoft | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated Lists identity response actions. | Stated MDR page says it protects identities. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Lists network response actions such as block IP. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | Stated Lists email actions such as quarantine message. | Stated MDR page says it protects email. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Critical Start | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Microsoft | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-microsoft/ --- # Critical Start and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Critical Start and Rapid7 differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | Rapid7 | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Critical Start | Rapid7 | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated MDR page lists endpoint. | | Identity | Stated Lists identity response actions. | Stated MDR page lists identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated MDR page lists cloud. | | Network | Stated Lists network response actions such as block IP. | Stated MDR page lists network. | | Email | Stated Lists email actions such as quarantine message. | Stated MDR page lists email. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Critical Start | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | None found on 10 Nov 2026 | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Rapid7 | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-rapid7/ --- # Critical Start and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Critical Start and Red Canary differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Critical Start | Red Canary | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Critical Start | Red Canary | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Page lists endpoint as a key domain. | | Identity | Stated Lists identity response actions. | Stated Page lists identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Lists network response actions such as block IP. | Stated Page lists network. | | Email | Stated Lists email actions such as quarantine message. | Stated Page lists email. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Critical Start | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | None found on 10 Nov 2026 | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | None found on 10 Nov 2026 | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Red Canary | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-red-canary/ --- # Critical Start and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Critical Start and SentinelOne differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Critical Start | SentinelOne | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Critical Start | SentinelOne | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Core detection coverage includes endpoint. | | Identity | Stated Lists identity response actions. | Stated Core detection coverage includes identity. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Core detection coverage includes cloud. | | Network | Stated Lists network response actions such as block IP. | None found on 10 November 2026 | | Email | Stated Lists email actions such as quarantine message. | None found on 10 November 2026 | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Critical Start | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | SentinelOne | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-sentinelone/ --- # Critical Start and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Critical Start and Sophos differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Critical Start | Sophos | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Critical Start | Sophos | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated MDR page states endpoint coverage. | | Identity | Stated Lists identity response actions. | Stated MDR page states identity coverage. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated MDR page states cloud coverage. | | Network | Stated Lists network response actions such as block IP. | Stated MDR page states network coverage. | | Email | Stated Lists email actions such as quarantine message. | Stated MDR page states email coverage. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Critical Start | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Sophos | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-sophos/ --- # Critical Start and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Critical Start and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Critical Start 3 stated, 2 with limits, 1 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Critical Start and Sygnia differ? On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Critical Start | Sygnia | | --- | --- | --- | | Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Critical Start | Sygnia | | --- | --- | --- | | Endpoint | Stated Lists endpoint response actions. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Lists identity response actions. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Lists network response actions such as block IP. | Stated Velocity ingests network data, per Sygnia. | | Email | Stated Lists email actions such as quarantine message. | Stated Alternate MDR page lists email among data sources. | | OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Critical Start | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Critical Start | Sygnia | | --- | --- | --- | | Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Critical Start, all published facts](/services/critical-start/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-sygnia/ --- # CrowdStrike and Deepwatch, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Deepwatch, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Deepwatch 4 stated, 0 with limits, 2 none found. The page gives no verdict. ## How do CrowdStrike and Deepwatch differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Deepwatch has 4 stated, 0 with limits, 2 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Deepwatch has 5 stated, 0 with limits, 2 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Deepwatch | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Active Response lists host isolation for endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated Active Response lists password reset and account control actions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Active Response lists process termination for endpoints. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | ## Data watched | Data | CrowdStrike | Deepwatch | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Platform page shows endpoint in the environment it works with. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Platform page shows identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Platform page shows cloud. | | Network | None found on 10 November 2026 | Stated Platform page shows network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated Calls itself agnostic with a Bring Your Own Tech approach. | ## The fifteen questions | Question | CrowdStrike | Deepwatch | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | None found on 10 Nov 2026 | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Deepwatch | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Deepwatch, all published facts](/services/deepwatch/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-deepwatch/ --- # CrowdStrike and eSentire, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and eSentire, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; eSentire 6 stated, 0 with limits, 0 none found. The page gives no verdict. ## How do CrowdStrike and eSentire differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and eSentire has 6 stated, 0 with limits, 0 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and eSentire has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | eSentire | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | None found on 10 November 2026 | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## Data watched | Data | CrowdStrike | eSentire | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Atlas ingests endpoint signals. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | None found on 10 November 2026 | Stated Atlas ingests network signals. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions | Question | CrowdStrike | eSentire | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | Is OT covered? | None found on 10 Nov 2026 | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | eSentire | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [eSentire, all published facts](/services/esentire/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-esentire/ --- # CrowdStrike and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do CrowdStrike and Expel differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Expel | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | None found on 10 November 2026 | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | CrowdStrike | Expel | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Packages page lists endpoints. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Packages page lists identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Packages page lists cloud workloads and control planes. | | Network | None found on 10 November 2026 | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | CrowdStrike | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | None found on 10 Nov 2026 | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Expel | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-expel/ --- # CrowdStrike and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do CrowdStrike and Huntress differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Huntress | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | CrowdStrike | Huntress | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | None found on 10 November 2026 | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | CrowdStrike | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | None found on 10 Nov 2026 | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Huntress | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-huntress/ --- # CrowdStrike and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do CrowdStrike and Kroll differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Kroll | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | CrowdStrike | Kroll | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Case study says visibility across endpoint. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Case study says visibility across identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Case study says visibility across cloud. | | Network | None found on 10 November 2026 | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | CrowdStrike | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | None found on 10 Nov 2026 | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Kroll | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-kroll/ --- # CrowdStrike and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do CrowdStrike and Mandiant differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Mandiant | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | CrowdStrike | Mandiant | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Full-stack monitoring across endpoint. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | None found on 10 November 2026 | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Full-stack monitoring across multicloud environments. | | Network | None found on 10 November 2026 | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | CrowdStrike | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Mandiant | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-mandiant/ --- # CrowdStrike and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do CrowdStrike and Microsoft differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Microsoft | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | CrowdStrike | Microsoft | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated MDR page says it protects identities. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | None found on 10 November 2026 | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | CrowdStrike | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Microsoft | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-microsoft/ --- # CrowdStrike and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do CrowdStrike and Rapid7 differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Rapid7 | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | CrowdStrike | Rapid7 | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated MDR page lists endpoint. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated MDR page lists identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated MDR page lists cloud. | | Network | None found on 10 November 2026 | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | CrowdStrike | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | None found on 10 Nov 2026 | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Rapid7 | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-rapid7/ --- # CrowdStrike and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do CrowdStrike and Red Canary differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Red Canary | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | None found on 10 November 2026 | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | CrowdStrike | Red Canary | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Page lists endpoint as a key domain. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Page lists identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Page unifies AWS, GCP and Azure data. | | Network | None found on 10 November 2026 | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | CrowdStrike | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | None found on 10 Nov 2026 | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Red Canary | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-red-canary/ --- # CrowdStrike and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do CrowdStrike and SentinelOne differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | CrowdStrike | SentinelOne | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | CrowdStrike | SentinelOne | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Core detection coverage includes endpoint. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Core detection coverage includes identity. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Core detection coverage includes cloud. | | Network | None found on 10 November 2026 | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | CrowdStrike | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | SentinelOne | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-sentinelone/ --- # CrowdStrike and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do CrowdStrike and Sophos differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Sophos | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | CrowdStrike | Sophos | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated MDR page states endpoint coverage. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated MDR page states identity coverage. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated MDR page states cloud coverage. | | Network | None found on 10 November 2026 | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | CrowdStrike | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Sophos | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-sophos/ --- # CrowdStrike and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** CrowdStrike and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: CrowdStrike 1 stated, 1 with limits, 4 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do CrowdStrike and Sygnia differ? On the six actions read, CrowdStrike has 1 stated, 1 with limits, 4 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, CrowdStrike has 3 stated, 1 with limits, 3 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | CrowdStrike | Sygnia | | --- | --- | --- | | Isolate a host | Stated The provider says Falcon Complete playbooks execute containment; its time-to-contain measure is on an endpoint. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Page says expert response across the SaaS stack with Falcon Shield visibility. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | CrowdStrike | Sygnia | | --- | --- | --- | | Endpoint | Stated Time to contain is defined on an endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Telemetry includes identities; a managed identity service is added. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Telemetry includes cloud; managed cloud workload protection is added. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | None found on 10 November 2026 | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Page lists third-party data in telemetry; IDC says endpoint is at the core with the Falcon agent. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | CrowdStrike | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | CrowdStrike | Sygnia | | --- | --- | --- | | Does well | CrowdStrike publishes a median time-to-contain of 1 minute for Falcon Complete, with the measure defined in a footnote. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | CrowdStrike lists Falcon Complete as Contact sales, names no individual response actions, and the page does not state that hunting is part of it. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [CrowdStrike, all published facts](/services/crowdstrike/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/crowdstrike-and-sygnia/ --- # Deepwatch and eSentire, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and eSentire, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; eSentire 6 stated, 0 with limits, 0 none found. The page gives no verdict. ## How do Deepwatch and eSentire differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and eSentire has 6 stated, 0 with limits, 0 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and eSentire has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | eSentire | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated Standard response includes isolating attackers and host isolation. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated Standard response includes suspending accounts and user access. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists preventing devices from communicating with known bad actors. | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | Stated Lists quarantining malicious files and terminating processes. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | ## Data watched | Data | Deepwatch | eSentire | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Atlas ingests endpoint signals. | | Identity | Stated Platform page shows identity. | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | | Cloud | Stated Platform page shows cloud. | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | | Network | Stated Platform page shows network. | Stated Atlas ingests network signals. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated Says Atlas connects to any signal across any vendor stack. | ## The fifteen questions | Question | Deepwatch | eSentire | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | What response-time commitments are published? | None found on 10 Nov 2026 | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | Is the pricing model published? | None found on 10 Nov 2026 | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | Is OT covered? | None found on 10 Nov 2026 | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | eSentire | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [eSentire, all published facts](/services/esentire/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-esentire/ --- # Deepwatch and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do Deepwatch and Expel differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | Expel | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | None found on 10 November 2026 | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | Deepwatch | Expel | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Packages page lists endpoints. | | Identity | Stated Platform page shows identity. | Stated Packages page lists identity. | | Cloud | Stated Platform page shows cloud. | Stated Packages page lists cloud workloads and control planes. | | Network | Stated Platform page shows network. | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | Deepwatch | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | None found on 10 Nov 2026 | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | None found on 10 Nov 2026 | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | None found on 10 Nov 2026 | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Expel | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-expel/ --- # Deepwatch and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do Deepwatch and Huntress differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | Deepwatch | Huntress | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | None found on 10 November 2026 | ## Data watched | Data | Deepwatch | Huntress | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated Platform page shows identity. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated Platform page shows cloud. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated Platform page shows network. | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | Deepwatch | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Huntress | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-huntress/ --- # Deepwatch and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do Deepwatch and Kroll differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | Kroll | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | None found on 10 November 2026 | ## Data watched | Data | Deepwatch | Kroll | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Case study says visibility across endpoint. | | Identity | Stated Platform page shows identity. | Stated Case study says visibility across identity. | | Cloud | Stated Platform page shows cloud. | Stated Case study says visibility across cloud. | | Network | Stated Platform page shows network. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | Deepwatch | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | None found on 10 Nov 2026 | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Kroll | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-kroll/ --- # Deepwatch and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Deepwatch and Mandiant differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Deepwatch | Mandiant | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | None found on 10 November 2026 | ## Data watched | Data | Deepwatch | Mandiant | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Full-stack monitoring across endpoint. | | Identity | Stated Platform page shows identity. | None found on 10 November 2026 | | Cloud | Stated Platform page shows cloud. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated Platform page shows network. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Deepwatch | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | None found on 10 Nov 2026 | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Mandiant | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-mandiant/ --- # Deepwatch and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Deepwatch and Microsoft differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | Microsoft | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Deepwatch | Microsoft | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated Platform page shows identity. | Stated MDR page says it protects identities. | | Cloud | Stated Platform page shows cloud. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Platform page shows network. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Deepwatch | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | None found on 10 Nov 2026 | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | None found on 10 Nov 2026 | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Microsoft | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-microsoft/ --- # Deepwatch and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Deepwatch and Rapid7 differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | Rapid7 | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Deepwatch | Rapid7 | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated MDR page lists endpoint. | | Identity | Stated Platform page shows identity. | Stated MDR page lists identity. | | Cloud | Stated Platform page shows cloud. | Stated MDR page lists cloud. | | Network | Stated Platform page shows network. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Deepwatch | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Rapid7 | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-rapid7/ --- # Deepwatch and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Deepwatch and Red Canary differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Deepwatch | Red Canary | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Deepwatch | Red Canary | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Page lists endpoint as a key domain. | | Identity | Stated Platform page shows identity. | Stated Page lists identity. | | Cloud | Stated Platform page shows cloud. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Platform page shows network. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Deepwatch | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Red Canary | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-red-canary/ --- # Deepwatch and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Deepwatch and SentinelOne differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Deepwatch | SentinelOne | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Deepwatch | SentinelOne | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Core detection coverage includes endpoint. | | Identity | Stated Platform page shows identity. | Stated Core detection coverage includes identity. | | Cloud | Stated Platform page shows cloud. | Stated Core detection coverage includes cloud. | | Network | Stated Platform page shows network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Deepwatch | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | None found on 10 Nov 2026 | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | None found on 10 Nov 2026 | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | SentinelOne | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-sentinelone/ --- # Deepwatch and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Deepwatch and Sophos differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Deepwatch | Sophos | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Deepwatch | Sophos | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated MDR page states endpoint coverage. | | Identity | Stated Platform page shows identity. | Stated MDR page states identity coverage. | | Cloud | Stated Platform page shows cloud. | Stated MDR page states cloud coverage. | | Network | Stated Platform page shows network. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Deepwatch | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | None found on 10 Nov 2026 | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Sophos | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-sophos/ --- # Deepwatch and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Deepwatch and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Deepwatch 4 stated, 0 with limits, 2 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Deepwatch and Sygnia differ? On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Deepwatch | Sygnia | | --- | --- | --- | | Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Deepwatch | Sygnia | | --- | --- | --- | | Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Platform page shows identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Platform page shows cloud. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Platform page shows network. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Deepwatch | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | None found on 10 Nov 2026 | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Deepwatch | Sygnia | | --- | --- | --- | | Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Deepwatch says other response domains will be added over time, and none found on 10 Nov 2026 for IR hours, a retainer, prices or SLA minutes. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Deepwatch, all published facts](/services/deepwatch/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/deepwatch-and-sygnia/ --- # eSentire and Expel, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Expel, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Expel 1 stated, 0 with limits, 5 none found. The page gives no verdict. ## How do eSentire and Expel differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Expel has 1 stated, 0 with limits, 5 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Expel has 6 stated, 0 with limits, 1 none found. ## Actions on the customer's behalf | Action | eSentire | Expel | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | None found on 10 November 2026 | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | ## Data watched | Data | eSentire | Expel | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Packages page lists endpoints. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated Packages page lists identity. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Packages page lists cloud workloads and control planes. | | Network | Stated Atlas ingests network signals. | Stated Packages page lists networks. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | Stated The provider's site navigation lists OT among its coverage attack surfaces. | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | ## The fifteen questions | Question | eSentire | Expel | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Expel says customers can let it press the respond button or choose what, how and when it acts. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Expel says no agents need to be deployed and it plugs into the existing stack. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Expel says pricing is by request, with Starter, Select and Premium packages. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in its Workbench platform. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Expel says customers see every alert, investigation and action in Workbench. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Expel | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Expel, all published facts](/services/expel/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-expel/ --- # eSentire and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do eSentire and Huntress differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | eSentire | Huntress | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | None found on 10 November 2026 | ## Data watched | Data | eSentire | Huntress | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated Atlas ingests network signals. | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | eSentire | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | None found on 10 Nov 2026 | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Huntress | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-huntress/ --- # eSentire and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do eSentire and Kroll differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | eSentire | Kroll | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | None found on 10 November 2026 | ## Data watched | Data | eSentire | Kroll | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Case study says visibility across endpoint. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated Case study says visibility across identity. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Case study says visibility across cloud. | | Network | Stated Atlas ingests network signals. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | eSentire | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | None found on 10 Nov 2026 | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | None found on 10 Nov 2026 | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Kroll | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-kroll/ --- # eSentire and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do eSentire and Mandiant differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | eSentire | Mandiant | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | None found on 10 November 2026 | ## Data watched | Data | eSentire | Mandiant | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Full-stack monitoring across endpoint. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | None found on 10 November 2026 | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated Atlas ingests network signals. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | eSentire | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | None found on 10 Nov 2026 | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Mandiant | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-mandiant/ --- # eSentire and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do eSentire and Microsoft differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | eSentire | Microsoft | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | eSentire | Microsoft | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated MDR page says it protects identities. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Atlas ingests network signals. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | eSentire | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Microsoft | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-microsoft/ --- # eSentire and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do eSentire and Rapid7 differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | eSentire | Rapid7 | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | eSentire | Rapid7 | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated MDR page lists endpoint. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated MDR page lists identity. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated MDR page lists cloud. | | Network | Stated Atlas ingests network signals. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | eSentire | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | None found on 10 Nov 2026 | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Rapid7 | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-rapid7/ --- # eSentire and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do eSentire and Red Canary differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | eSentire | Red Canary | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | eSentire | Red Canary | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Page lists endpoint as a key domain. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated Page lists identity. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Atlas ingests network signals. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | eSentire | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | None found on 10 Nov 2026 | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | None found on 10 Nov 2026 | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Red Canary | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-red-canary/ --- # eSentire and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do eSentire and SentinelOne differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | eSentire | SentinelOne | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | eSentire | SentinelOne | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Core detection coverage includes endpoint. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated Core detection coverage includes identity. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Core detection coverage includes cloud. | | Network | Stated Atlas ingests network signals. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | eSentire | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | SentinelOne | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-sentinelone/ --- # eSentire and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do eSentire and Sophos differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | eSentire | Sophos | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | eSentire | Sophos | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated MDR page states endpoint coverage. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated MDR page states identity coverage. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated MDR page states cloud coverage. | | Network | Stated Atlas ingests network signals. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | eSentire | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Sophos | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-sophos/ --- # eSentire and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** eSentire and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: eSentire 6 stated, 0 with limits, 0 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do eSentire and Sygnia differ? On the six actions read, eSentire has 6 stated, 0 with limits, 0 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, eSentire has 3 stated, 3 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | eSentire | Sygnia | | --- | --- | --- | | Isolate a host | Stated Standard response includes isolating attackers and host isolation. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated Standard response includes suspending accounts and user access. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists preventing devices from communicating with known bad actors. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists quarantining malicious files and terminating processes. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated The provider says it supports correcting critical multi-cloud misconfigurations. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says it isolates, suspends and disrupts on every incident, with policy-bounded, reversible actions. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | eSentire | Sygnia | | --- | --- | --- | | Endpoint | Stated Atlas ingests endpoint signals. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated with limits The provider says Atlas ingests identity signals; IDC says identity comes with the next tier. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated with limits The provider says Atlas ingests cloud signals; IDC says cloud coverage comes with the next tier. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Atlas ingests network signals. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | Stated with limits The provider says its manufacturing MDR covers threats moving across IT and OT. | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Says Atlas connects to any signal across any vendor stack. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | eSentire | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | eSentire | Sygnia | | --- | --- | --- | | Does well | eSentire lists named response procedures (isolate, suspend accounts, terminate processes, disrupt connections) and states a mean time to engage of 30 seconds. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | eSentire says round-the-clock hunting is added at the Enhanced package, IDC places identity and cloud coverage above the entry tier, and IR is an add-on or retainer. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [eSentire, all published facts](/services/esentire/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/esentire-and-sygnia/ --- # Expel and Huntress, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Huntress, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict. ## How do Expel and Huntress differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Huntress has 1 stated, 4 with limits, 2 none found. ## Actions on the customer's behalf | Action | Expel | Huntress | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated The provider says its SOC contains threats and evicts them from endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | None found on 10 November 2026 | ## Data watched | Data | Expel | Huntress | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Native agents cover Windows, macOS and Linux. | | Identity | Stated Packages page lists identity. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated with limits Managed SIEM page says it connects cloud services activity. | | Network | Stated Packages page lists networks. | Stated with limits Managed SIEM page says it connects network activity. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | ## The fifteen questions | Question | Expel | Huntress | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | None found on 10 Nov 2026 | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Huntress | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Huntress, all published facts](/services/huntress/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-huntress/ --- # Expel and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do Expel and Kroll differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Expel | Kroll | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | None found on 10 November 2026 | ## Data watched | Data | Expel | Kroll | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Case study says visibility across endpoint. | | Identity | Stated Packages page lists identity. | Stated Case study says visibility across identity. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated Case study says visibility across cloud. | | Network | Stated Packages page lists networks. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | Expel | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | None found on 10 Nov 2026 | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Kroll | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-kroll/ --- # Expel and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Expel and Mandiant differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Expel | Mandiant | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | None found on 10 November 2026 | ## Data watched | Data | Expel | Mandiant | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Full-stack monitoring across endpoint. | | Identity | Stated Packages page lists identity. | None found on 10 November 2026 | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated Packages page lists networks. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Expel | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | None found on 10 Nov 2026 | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Mandiant | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-mandiant/ --- # Expel and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Expel and Microsoft differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Expel | Microsoft | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Expel | Microsoft | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated Packages page lists identity. | Stated MDR page says it protects identities. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Packages page lists networks. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Expel | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Microsoft | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-microsoft/ --- # Expel and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Expel and Rapid7 differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Expel | Rapid7 | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Expel | Rapid7 | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated MDR page lists endpoint. | | Identity | Stated Packages page lists identity. | Stated MDR page lists identity. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated MDR page lists cloud. | | Network | Stated Packages page lists networks. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Expel | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | None found on 10 Nov 2026 | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Rapid7 | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-rapid7/ --- # Expel and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Expel and Red Canary differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Expel | Red Canary | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | None found on 10 November 2026 | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Expel | Red Canary | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Page lists endpoint as a key domain. | | Identity | Stated Packages page lists identity. | Stated Page lists identity. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Packages page lists networks. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Expel | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | None found on 10 Nov 2026 | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | None found on 10 Nov 2026 | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Red Canary | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-red-canary/ --- # Expel and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Expel and SentinelOne differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Expel | SentinelOne | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Expel | SentinelOne | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Core detection coverage includes endpoint. | | Identity | Stated Packages page lists identity. | Stated Core detection coverage includes identity. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated Core detection coverage includes cloud. | | Network | Stated Packages page lists networks. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Expel | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | SentinelOne | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-sentinelone/ --- # Expel and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Expel and Sophos differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Expel | Sophos | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Expel | Sophos | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated MDR page states endpoint coverage. | | Identity | Stated Packages page lists identity. | Stated MDR page states identity coverage. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated MDR page states cloud coverage. | | Network | Stated Packages page lists networks. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Expel | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Sophos | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-sophos/ --- # Expel and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Expel and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Expel 1 stated, 0 with limits, 5 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Expel and Sygnia differ? On the six actions read, Expel has 1 stated, 0 with limits, 5 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Expel has 6 stated, 0 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Expel | Sygnia | | --- | --- | --- | | Isolate a host | None found on 10 November 2026 | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Customers can let Expel act once its SOC validates a threat, or choose what, how and when. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Expel | Sygnia | | --- | --- | --- | | Endpoint | Stated Packages page lists endpoints. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Packages page lists identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Packages page lists cloud workloads and control planes. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Packages page lists networks. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | Stated The provider's site navigation lists OT among its coverage attack surfaces. | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Says no agents need to be deployed; pulls telemetry from 160+ tools. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Expel | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Expel says customers can let it press the respond button or choose what, how and when it acts. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Expel says no agents need to be deployed and it plugs into the existing stack. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Expel says pricing is by request, with Starter, Select and Premium packages. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Expel says customers see every alert, investigation and action in its Workbench platform. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Expel says customers see every alert, investigation and action in Workbench. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Expel | Sygnia | | --- | --- | --- | | Does well | Expel publishes response metrics of 5 minutes to detect, 13 to respond on high severity and 14 to remediate, and shows every action in Workbench. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Expel prices by request in three packages, and none found on 10 Nov 2026 for included IR hours or a retainer or named response actions. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Expel, all published facts](/services/expel/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/expel-and-sygnia/ --- # Huntress and Kroll, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Kroll, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Kroll 2 stated, 3 with limits, 1 none found. The page gives no verdict. ## How do Huntress and Kroll differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Kroll has 2 stated, 3 with limits, 1 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Kroll has 3 stated, 3 with limits, 1 none found. ## Actions on the customer's behalf | Action | Huntress | Kroll | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated Says on containment the team will isolate compromised endpoints. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | | Kill a process or remove a file | None found on 10 November 2026 | Stated The provider says it will eradicate malware from endpoints and remove persistence. | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | Huntress | Kroll | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Case study says visibility across endpoint. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated Case study says visibility across identity. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated Case study says visibility across cloud. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | ## The fifteen questions | Question | Huntress | Kroll | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | What response-time commitments are published? | None found on 10 Nov 2026 | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | What reporting does the customer receive? | None found on 10 Nov 2026 | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Kroll | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Kroll, all published facts](/services/kroll/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-kroll/ --- # Huntress and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Huntress and Mandiant differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Huntress | Mandiant | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | Huntress | Mandiant | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Full-stack monitoring across endpoint. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | None found on 10 November 2026 | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Huntress | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | None found on 10 Nov 2026 | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Mandiant | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-mandiant/ --- # Huntress and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Huntress and Microsoft differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Huntress | Microsoft | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Huntress | Microsoft | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated MDR page says it protects identities. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Huntress | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | None found on 10 Nov 2026 | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Microsoft | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-microsoft/ --- # Huntress and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Huntress and Rapid7 differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Huntress | Rapid7 | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Huntress | Rapid7 | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated MDR page lists endpoint. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated MDR page lists identity. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated MDR page lists cloud. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Huntress | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Rapid7 | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-rapid7/ --- # Huntress and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Huntress and Red Canary differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Huntress | Red Canary | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Huntress | Red Canary | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Page lists endpoint as a key domain. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated Page lists identity. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Huntress | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Red Canary | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-red-canary/ --- # Huntress and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Huntress and SentinelOne differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Huntress | SentinelOne | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Huntress | SentinelOne | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Core detection coverage includes endpoint. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated Core detection coverage includes identity. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated Core detection coverage includes cloud. | | Network | Stated with limits Managed SIEM page says it connects network activity. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Huntress | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | None found on 10 Nov 2026 | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | SentinelOne | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-sentinelone/ --- # Huntress and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Huntress and Sophos differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Huntress | Sophos | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Huntress | Sophos | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated MDR page states endpoint coverage. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated MDR page states identity coverage. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated MDR page states cloud coverage. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Huntress | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Sophos | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-sophos/ --- # Huntress and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Huntress and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Huntress 1 stated, 2 with limits, 3 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Huntress and Sygnia differ? On the six actions read, Huntress has 1 stated, 2 with limits, 3 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Huntress has 1 stated, 4 with limits, 2 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Huntress | Sygnia | | --- | --- | --- | | Isolate a host | Stated The provider says its SOC contains threats and evicts them from endpoints. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Huntress | Sygnia | | --- | --- | --- | | Endpoint | Stated Native agents cover Windows, macOS and Linux. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated with limits Managed SIEM page says it connects cloud services activity. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated with limits Managed SIEM page says it connects network activity. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Huntress | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Huntress says its price includes everything with no add-ons; included IR hours not stated. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Huntress | Sygnia | | --- | --- | --- | | Does well | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours or OT. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Huntress, all published facts](/services/huntress/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/huntress-and-sygnia/ --- # Kroll and Mandiant, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Mandiant, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Mandiant 0 stated, 1 with limits, 5 none found. The page gives no verdict. ## How do Kroll and Mandiant differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Mandiant has 0 stated, 1 with limits, 5 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Mandiant has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Kroll | Mandiant | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | None found on 10 November 2026 | ## Data watched | Data | Kroll | Mandiant | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated Full-stack monitoring across endpoint. | | Identity | Stated Case study says visibility across identity. | None found on 10 November 2026 | | Cloud | Stated Case study says visibility across cloud. | Stated Full-stack monitoring across multicloud environments. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated Full-stack monitoring across network. | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | ## The fifteen questions | Question | Kroll | Mandiant | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Mandiant | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Mandiant, all published facts](/services/mandiant/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-mandiant/ --- # Kroll and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Kroll and Microsoft differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Kroll | Microsoft | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Kroll | Microsoft | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | Stated Case study says visibility across identity. | Stated MDR page says it protects identities. | | Cloud | Stated Case study says visibility across cloud. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Kroll | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | None found on 10 Nov 2026 | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Microsoft | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-microsoft/ --- # Kroll and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Kroll and Rapid7 differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Kroll | Rapid7 | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Kroll | Rapid7 | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated MDR page lists endpoint. | | Identity | Stated Case study says visibility across identity. | Stated MDR page lists identity. | | Cloud | Stated Case study says visibility across cloud. | Stated MDR page lists cloud. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Kroll | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Rapid7 | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-rapid7/ --- # Kroll and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Kroll and Red Canary differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Kroll | Red Canary | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Kroll | Red Canary | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated Page lists endpoint as a key domain. | | Identity | Stated Case study says visibility across identity. | Stated Page lists identity. | | Cloud | Stated Case study says visibility across cloud. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Kroll | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Red Canary | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-red-canary/ --- # Kroll and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Kroll and SentinelOne differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Kroll | SentinelOne | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Kroll | SentinelOne | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated Core detection coverage includes endpoint. | | Identity | Stated Case study says visibility across identity. | Stated Core detection coverage includes identity. | | Cloud | Stated Case study says visibility across cloud. | Stated Core detection coverage includes cloud. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Kroll | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | None found on 10 Nov 2026 | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | SentinelOne | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-sentinelone/ --- # Kroll and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Kroll and Sophos differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Kroll | Sophos | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Kroll | Sophos | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated MDR page states endpoint coverage. | | Identity | Stated Case study says visibility across identity. | Stated MDR page states identity coverage. | | Cloud | Stated Case study says visibility across cloud. | Stated MDR page states cloud coverage. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Kroll | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | None found on 10 Nov 2026 | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Sophos | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-sophos/ --- # Kroll and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Kroll and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Kroll 2 stated, 3 with limits, 1 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Kroll and Sygnia differ? On the six actions read, Kroll has 2 stated, 3 with limits, 1 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Kroll has 3 stated, 3 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Kroll | Sygnia | | --- | --- | --- | | Isolate a host | Stated Says on containment the team will isolate compromised endpoints. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated with limits The provider says it revokes access through authentication platforms; its Microsoft page lists revoking sessions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated with limits Says it updates WAFs and firewalls and, for Microsoft, blocks malicious files on endpoints. | None found on 10 November 2026 | | Kill a process or remove a file | Stated The provider says it will eradicate malware from endpoints and remove persistence. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Microsoft service lists deleting mailbox rules and revoking sessions. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Kroll | Sygnia | | --- | --- | --- | | Endpoint | Stated Case study says visibility across endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Case study says visibility across identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Case study says visibility across cloud. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated with limits IDC says NDR with Darktrace detects attacks on IoT or OT devices. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | Stated with limits OT security monitoring is a separate Kroll service; IDC cites NDR for OT devices. | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits 2025-2026 pages describe consolidation on CrowdStrike Falcon; an older page still says tech-agnostic. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Kroll | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | None found on 10 Nov 2026 | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Kroll | Sygnia | | --- | --- | --- | | Does well | Kroll says Responder MDR includes remote DFIR at no additional cost and a $1 million warranty, with weekly hunting and a monthly report per IDC. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Kroll's newer pages describe consolidating on CrowdStrike Falcon, its OT monitoring is a separate service, and no SLA minutes were found. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Kroll, all published facts](/services/kroll/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Managed XDR microsoft" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder/managed-xdr-microsoft (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/kroll-and-sygnia/ --- # Mandiant and Microsoft, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and Microsoft, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; Microsoft 0 stated, 5 with limits, 1 none found. The page gives no verdict. ## How do Mandiant and Microsoft differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and Microsoft has 0 stated, 5 with limits, 1 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and Microsoft has 4 stated, 2 with limits, 1 none found. ## Actions on the customer's behalf | Action | Mandiant | Microsoft | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | | Disable or reset an account | None found on 10 November 2026 | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | ## Data watched | Data | Mandiant | Microsoft | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | | Identity | None found on 10 November 2026 | Stated MDR page says it protects identities. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | | Network | Stated Full-stack monitoring across network. | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | | Email | None found on 10 November 2026 | Stated MDR page says it protects email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | ## The fifteen questions | Question | Mandiant | Microsoft | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | Microsoft's overview prints no price or response-time commitment. | | Is the pricing model published? | None found on 10 Nov 2026 | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | Is OT covered? | None found on 10 Nov 2026 | Microsoft's FAQ excludes IoT devices and does not mention OT. | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | Microsoft | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [Microsoft, all published facts](/services/microsoft/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-microsoft/ --- # Mandiant and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Mandiant and Rapid7 differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Mandiant | Rapid7 | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Mandiant | Rapid7 | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated MDR page lists endpoint. | | Identity | None found on 10 November 2026 | Stated MDR page lists identity. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated MDR page lists cloud. | | Network | Stated Full-stack monitoring across network. | Stated MDR page lists network. | | Email | None found on 10 November 2026 | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Mandiant | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | Rapid7 | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-rapid7/ --- # Mandiant and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Mandiant and Red Canary differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Mandiant | Red Canary | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | None found on 10 November 2026 | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Mandiant | Red Canary | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated Page lists endpoint as a key domain. | | Identity | None found on 10 November 2026 | Stated Page lists identity. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Full-stack monitoring across network. | Stated Page lists network. | | Email | None found on 10 November 2026 | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Mandiant | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | None found on 10 Nov 2026 | | Is the pricing model published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | Red Canary | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-red-canary/ --- # Mandiant and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Mandiant and SentinelOne differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Mandiant | SentinelOne | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Mandiant | SentinelOne | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated Core detection coverage includes endpoint. | | Identity | None found on 10 November 2026 | Stated Core detection coverage includes identity. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated Core detection coverage includes cloud. | | Network | Stated Full-stack monitoring across network. | None found on 10 November 2026 | | Email | None found on 10 November 2026 | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Mandiant | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | None found on 10 Nov 2026 | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | SentinelOne | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-sentinelone/ --- # Mandiant and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Mandiant and Sophos differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Mandiant | Sophos | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Mandiant | Sophos | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated MDR page states endpoint coverage. | | Identity | None found on 10 November 2026 | Stated MDR page states identity coverage. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated MDR page states cloud coverage. | | Network | Stated Full-stack monitoring across network. | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Mandiant | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | None found on 10 Nov 2026 | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | Sophos | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-sophos/ --- # Mandiant and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Mandiant and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Mandiant 0 stated, 1 with limits, 5 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Mandiant and Sygnia differ? On the six actions read, Mandiant has 0 stated, 1 with limits, 5 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Mandiant has 3 stated, 1 with limits, 3 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Mandiant | Sygnia | | --- | --- | --- | | Isolate a host | Stated with limits The provider says experts can contain impacted hosts; its datasheet ties containment to Technology Partner products. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | None found on 10 November 2026 | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Mandiant | Sygnia | | --- | --- | --- | | Endpoint | Stated Full-stack monitoring across endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | None found on 10 November 2026 | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Full-stack monitoring across multicloud environments. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Full-stack monitoring across network. | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Supports the customer's technology stack via a partner list; deeper response needs Technology Partner products. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Mandiant | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | None found on 10 Nov 2026 | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Mandiant | Sygnia | | --- | --- | --- | | Does well | Mandiant says its experts can contain impacted hosts and triage alerts within minutes, with supported EDR partners including CrowdStrike, SentinelOne and Microsoft. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Mandiant's pages list host containment, file acquisition and closing alerts, and none found on 10 Nov 2026 for accounts, blocking, pricing, SLA minutes or OT. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Mandiant, all published facts](/services/mandiant/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/mandiant-and-sygnia/ --- # Microsoft and Rapid7, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Microsoft and Rapid7, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Microsoft 0 stated, 5 with limits, 1 none found; Rapid7 2 stated, 0 with limits, 4 none found. The page gives no verdict. ## How do Microsoft and Rapid7 differ? On the six actions read, Microsoft has 0 stated, 5 with limits, 1 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Microsoft has 4 stated, 2 with limits, 1 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Microsoft | Rapid7 | | --- | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | Stated The provider says response actions follow the customer's approved policies. | ## Data watched | Data | Microsoft | Rapid7 | | --- | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | Stated MDR page lists endpoint. | | Identity | Stated MDR page says it protects identities. | Stated MDR page lists identity. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | Stated MDR page lists cloud. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | Stated MDR page lists network. | | Email | Stated MDR page says it protects email. | Stated MDR page lists email. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | ## The fifteen questions | Question | Microsoft | Rapid7 | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | What may the provider do without asking first? | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | Which data sources does the service monitor? | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | Is the provider's own endpoint agent required? | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | Is threat hunting included, and what output is published? | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | Are incident response hours included, or is a retainer needed? | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | What response-time commitments are published? | Microsoft's overview prints no price or response-time commitment. | None found on 10 Nov 2026 | | Is the pricing model published? | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | Is OT covered? | Microsoft's FAQ excludes IoT devices and does not mention OT. | None found on 10 Nov 2026 | | What cloud and identity coverage is stated? | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | Rapid7 says every action in the SOC is logged, explainable and auditable. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Microsoft | Rapid7 | | --- | --- | --- | | Does well | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | | Limited | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Microsoft, all published facts](/services/microsoft/) - [Rapid7, all published facts](/services/rapid7/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/microsoft-and-rapid7/ --- # Microsoft and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Microsoft and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Microsoft 0 stated, 5 with limits, 1 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Microsoft and Red Canary differ? On the six actions read, Microsoft has 0 stated, 5 with limits, 1 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Microsoft has 4 stated, 2 with limits, 1 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Microsoft | Red Canary | | --- | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Microsoft | Red Canary | | --- | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | Stated Page lists endpoint as a key domain. | | Identity | Stated MDR page says it protects identities. | Stated Page lists identity. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | Stated Page lists network. | | Email | Stated MDR page says it protects email. | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Microsoft | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | Microsoft's overview prints no price or response-time commitment. | None found on 10 Nov 2026 | | Is the pricing model published? | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | None found on 10 Nov 2026 | | Is OT covered? | Microsoft's FAQ excludes IoT devices and does not mention OT. | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Microsoft | Red Canary | | --- | --- | --- | | Does well | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Microsoft, all published facts](/services/microsoft/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/microsoft-and-red-canary/ --- # Microsoft and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Microsoft and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Microsoft 0 stated, 5 with limits, 1 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Microsoft and SentinelOne differ? On the six actions read, Microsoft has 0 stated, 5 with limits, 1 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Microsoft has 4 stated, 2 with limits, 1 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Microsoft | SentinelOne | | --- | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Microsoft | SentinelOne | | --- | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | Stated Core detection coverage includes endpoint. | | Identity | Stated MDR page says it protects identities. | Stated Core detection coverage includes identity. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | Stated Core detection coverage includes cloud. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | None found on 10 November 2026 | | Email | Stated MDR page says it protects email. | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Microsoft | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | Microsoft's overview prints no price or response-time commitment. | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | Microsoft's FAQ excludes IoT devices and does not mention OT. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Microsoft | SentinelOne | | --- | --- | --- | | Does well | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Microsoft, all published facts](/services/microsoft/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/microsoft-and-sentinelone/ --- # Microsoft and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Microsoft and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Microsoft 0 stated, 5 with limits, 1 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Microsoft and Sophos differ? On the six actions read, Microsoft has 0 stated, 5 with limits, 1 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Microsoft has 4 stated, 2 with limits, 1 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Microsoft | Sophos | | --- | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Microsoft | Sophos | | --- | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | Stated MDR page states endpoint coverage. | | Identity | Stated MDR page says it protects identities. | Stated MDR page states identity coverage. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | Stated MDR page states cloud coverage. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | Stated MDR page states network coverage. | | Email | Stated MDR page says it protects email. | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Microsoft | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | Microsoft's overview prints no price or response-time commitment. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | Microsoft's FAQ excludes IoT devices and does not mention OT. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Microsoft | Sophos | | --- | --- | --- | | Does well | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Microsoft, all published facts](/services/microsoft/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/microsoft-and-sophos/ --- # Microsoft and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Microsoft and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Microsoft 0 stated, 5 with limits, 1 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Microsoft and Sygnia differ? On the six actions read, Microsoft has 0 stated, 5 with limits, 1 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Microsoft has 4 stated, 2 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Microsoft | Sygnia | | --- | --- | --- | | Isolate a host | Stated with limits The provider lists isolate device; experts act only if granted Security Operator access, otherwise actions stay pending. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated with limits The provider lists disable user; experts act only with Security Operator access, otherwise actions stay pending. | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated with limits The provider lists quarantine file and restrict app execution; experts act only with Security Operator access. | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Experts take action or guide for Defender workloads; guidance only for supported third-party products. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated with limits Experts act only if granted Security Operator access; default Security Reader leaves actions pending. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Microsoft | Sygnia | | --- | --- | --- | | Endpoint | Stated Covers Windows, Linux and macOS devices at High and Medium severity. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated MDR page says it protects identities. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated with limits Covers cloud apps and workloads; neither plan covers Defender for Cloud storage, containers, databases. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Microsoft says its MDR page covers network infrastructure across Microsoft and third-party sources. | Stated Velocity ingests network data, per Sygnia. | | Email | Stated MDR page says it protects email. | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Plan 2 adds listed third-party sources through Sentinel; Plan 2 requires Sentinel and 1,500 seats. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Microsoft | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Microsoft's overview prints no price or response-time commitment. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | Microsoft's FAQ excludes IoT devices and does not mention OT. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | Microsoft says customers get live dashboards and reports of the work done on their behalf. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Microsoft | Sygnia | | --- | --- | --- | | Does well | Microsoft lists named one-click response actions and publishes plan scope, capabilities and boundaries, with interactive hunting reports. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Microsoft says MDR does not provide incident response for an active compromise, excludes IoT, iOS, Android and Defender for Cloud workloads, and Plan 2 needs 1,500 seats. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Microsoft, all published facts](/services/microsoft/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/microsoft-and-sygnia/ --- # Rapid7 and Red Canary, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Rapid7 and Red Canary, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Rapid7 2 stated, 0 with limits, 4 none found; Red Canary 4 stated, 1 with limits, 1 none found. The page gives no verdict. ## How do Rapid7 and Red Canary differ? On the six actions read, Rapid7 has 2 stated, 0 with limits, 4 none found, and Red Canary has 4 stated, 1 with limits, 1 none found. On the seven data sources read, Rapid7 has 5 stated, 1 with limits, 1 none found, and Red Canary has 6 stated, 1 with limits, 0 none found. ## Actions on the customer's behalf | Action | Rapid7 | Red Canary | | --- | --- | --- | | Isolate a host | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | Stated Automated playbooks isolate endpoints via EDR. | | Disable or reset an account | None found on 10 November 2026 | Stated Automated playbooks suspend users via the customer's IDP. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | | Acts without asking first (pre-approved) | Stated The provider says response actions follow the customer's approved policies. | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | ## Data watched | Data | Rapid7 | Red Canary | | --- | --- | --- | | Endpoint | Stated MDR page lists endpoint. | Stated Page lists endpoint as a key domain. | | Identity | Stated MDR page lists identity. | Stated Page lists identity. | | Cloud | Stated MDR page lists cloud. | Stated Page unifies AWS, GCP and Azure data. | | Network | Stated MDR page lists network. | Stated Page lists network. | | Email | Stated MDR page lists email. | Stated Page lists email. | | OT | None found on 10 November 2026 | Stated with limits An archived manufacturing page states it protects OT and IT environments. | | Works on other vendors' tools | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | ## The fifteen questions | Question | Rapid7 | Red Canary | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | What may the provider do without asking first? | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | Which data sources does the service monitor? | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | Is the provider's own endpoint agent required? | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | Is threat hunting included, and what output is published? | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | Are incident response hours included, or is a retainer needed? | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Is the pricing model published? | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | None found on 10 Nov 2026 | | Is OT covered? | None found on 10 Nov 2026 | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | What cloud and identity coverage is stated? | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Rapid7 says every action in the SOC is logged, explainable and auditable. | Red Canary says reporting shows speed and accuracy of detection and response over time. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Rapid7 | Red Canary | | --- | --- | --- | | Does well | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | | Limited | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Rapid7, all published facts](/services/rapid7/) - [Red Canary, all published facts](/services/red-canary/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/rapid7-and-red-canary/ --- # Rapid7 and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Rapid7 and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Rapid7 2 stated, 0 with limits, 4 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Rapid7 and SentinelOne differ? On the six actions read, Rapid7 has 2 stated, 0 with limits, 4 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Rapid7 has 5 stated, 1 with limits, 1 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Rapid7 | SentinelOne | | --- | --- | --- | | Isolate a host | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says response actions follow the customer's approved policies. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Rapid7 | SentinelOne | | --- | --- | --- | | Endpoint | Stated MDR page lists endpoint. | Stated Core detection coverage includes endpoint. | | Identity | Stated MDR page lists identity. | Stated Core detection coverage includes identity. | | Cloud | Stated MDR page lists cloud. | Stated Core detection coverage includes cloud. | | Network | Stated MDR page lists network. | None found on 10 November 2026 | | Email | Stated MDR page lists email. | None found on 10 November 2026 | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Rapid7 | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | None found on 10 Nov 2026 | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | None found on 10 Nov 2026 | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Rapid7 says every action in the SOC is logged, explainable and auditable. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Rapid7 | SentinelOne | | --- | --- | --- | | Does well | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Rapid7, all published facts](/services/rapid7/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/rapid7-and-sentinelone/ --- # Rapid7 and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Rapid7 and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Rapid7 2 stated, 0 with limits, 4 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Rapid7 and Sophos differ? On the six actions read, Rapid7 has 2 stated, 0 with limits, 4 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Rapid7 has 5 stated, 1 with limits, 1 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Rapid7 | Sophos | | --- | --- | --- | | Isolate a host | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says response actions follow the customer's approved policies. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Rapid7 | Sophos | | --- | --- | --- | | Endpoint | Stated MDR page lists endpoint. | Stated MDR page states endpoint coverage. | | Identity | Stated MDR page lists identity. | Stated MDR page states identity coverage. | | Cloud | Stated MDR page lists cloud. | Stated MDR page states cloud coverage. | | Network | Stated MDR page lists network. | Stated MDR page states network coverage. | | Email | Stated MDR page lists email. | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Rapid7 | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Rapid7 says every action in the SOC is logged, explainable and auditable. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Rapid7 | Sophos | | --- | --- | --- | | Does well | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Rapid7, all published facts](/services/rapid7/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/rapid7-and-sophos/ --- # Rapid7 and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Rapid7 and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Rapid7 2 stated, 0 with limits, 4 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Rapid7 and Sygnia differ? On the six actions read, Rapid7 has 2 stated, 0 with limits, 4 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Rapid7 has 5 stated, 1 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Rapid7 | Sygnia | | --- | --- | --- | | Isolate a host | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says response actions follow the customer's approved policies. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Rapid7 | Sygnia | | --- | --- | --- | | Endpoint | Stated MDR page lists endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated MDR page lists identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated MDR page lists cloud. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated MDR page lists network. | Stated Velocity ingests network data, per Sygnia. | | Email | Stated MDR page lists email. | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Rapid7 | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Rapid7 says every action in the SOC is logged, explainable and auditable. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Rapid7 | Sygnia | | --- | --- | --- | | Does well | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Rapid7, all published facts](/services/rapid7/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/rapid7-and-sygnia/ --- # Red Canary and SentinelOne, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Red Canary and SentinelOne, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Red Canary 4 stated, 1 with limits, 1 none found; SentinelOne 3 stated, 0 with limits, 3 none found. The page gives no verdict. ## How do Red Canary and SentinelOne differ? On the six actions read, Red Canary has 4 stated, 1 with limits, 1 none found, and SentinelOne has 3 stated, 0 with limits, 3 none found. On the seven data sources read, Red Canary has 6 stated, 1 with limits, 0 none found, and SentinelOne has 3 stated, 1 with limits, 3 none found. ## Actions on the customer's behalf | Action | Red Canary | SentinelOne | | --- | --- | --- | | Isolate a host | Stated Automated playbooks isolate endpoints via EDR. | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | | Disable or reset an account | Stated Automated playbooks suspend users via the customer's IDP. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | Stated Says malicious processes are killed per the configured response policy. | | Act in a cloud or SaaS console | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | Stated The provider says confirmed threats are contained according to the configured response policy. | ## Data watched | Data | Red Canary | SentinelOne | | --- | --- | --- | | Endpoint | Stated Page lists endpoint as a key domain. | Stated Core detection coverage includes endpoint. | | Identity | Stated Page lists identity. | Stated Core detection coverage includes identity. | | Cloud | Stated Page unifies AWS, GCP and Azure data. | Stated Core detection coverage includes cloud. | | Network | Stated Page lists network. | None found on 10 November 2026 | | Email | Stated Page lists email. | None found on 10 November 2026 | | OT | Stated with limits An archived manufacturing page states it protects OT and IT environments. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | ## The fifteen questions | Question | Red Canary | SentinelOne | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | What may the provider do without asking first? | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | Which data sources does the service monitor? | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | Is the provider's own endpoint agent required? | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | Is threat hunting included, and what output is published? | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | Are incident response hours included, or is a retainer needed? | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | What response-time commitments are published? | None found on 10 Nov 2026 | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | Is the pricing model published? | None found on 10 Nov 2026 | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | Is OT covered? | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | What cloud and identity coverage is stated? | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Red Canary says reporting shows speed and accuracy of detection and response over time. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Red Canary | SentinelOne | | --- | --- | --- | | Does well | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | | Limited | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Red Canary, all published facts](/services/red-canary/) - [SentinelOne, all published facts](/services/sentinelone/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/red-canary-and-sentinelone/ --- # Red Canary and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Red Canary and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Red Canary 4 stated, 1 with limits, 1 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do Red Canary and Sophos differ? On the six actions read, Red Canary has 4 stated, 1 with limits, 1 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, Red Canary has 6 stated, 1 with limits, 0 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | Red Canary | Sophos | | --- | --- | --- | | Isolate a host | Stated Automated playbooks isolate endpoints via EDR. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | Stated Automated playbooks suspend users via the customer's IDP. | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | Stated Lists blocking indicators. | | Kill a process or remove a file | None found on 10 November 2026 | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | Red Canary | Sophos | | --- | --- | --- | | Endpoint | Stated Page lists endpoint as a key domain. | Stated MDR page states endpoint coverage. | | Identity | Stated Page lists identity. | Stated MDR page states identity coverage. | | Cloud | Stated Page unifies AWS, GCP and Azure data. | Stated MDR page states cloud coverage. | | Network | Stated Page lists network. | Stated MDR page states network coverage. | | Email | Stated Page lists email. | Stated MDR page states email coverage. | | OT | Stated with limits An archived manufacturing page states it protects OT and IT environments. | None found on 10 November 2026 | | Works on other vendors' tools | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | Red Canary | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | None found on 10 Nov 2026 | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | Red Canary says reporting shows speed and accuracy of detection and response over time. | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Red Canary | Sophos | | --- | --- | --- | | Does well | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Red Canary, all published facts](/services/red-canary/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/red-canary-and-sophos/ --- # Red Canary and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Red Canary and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Red Canary 4 stated, 1 with limits, 1 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Red Canary and Sygnia differ? On the six actions read, Red Canary has 4 stated, 1 with limits, 1 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Red Canary has 6 stated, 1 with limits, 0 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Red Canary | Sygnia | | --- | --- | --- | | Isolate a host | Stated Automated playbooks isolate endpoints via EDR. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated Automated playbooks suspend users via the customer's IDP. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Playbooks block URLs and IoCs via ZIA and add IPs to deny lists. | None found on 10 November 2026 | | Kill a process or remove a file | None found on 10 November 2026 | None found on 10 November 2026 | | Act in a cloud or SaaS console | Stated with limits Lists ZIA responses such as browser isolation and conditional access policies. | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says customers can keep human oversight on specific actions or choose to automate. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Red Canary | Sygnia | | --- | --- | --- | | Endpoint | Stated Page lists endpoint as a key domain. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Page lists identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Page unifies AWS, GCP and Azure data. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated Page lists network. | Stated Velocity ingests network data, per Sygnia. | | Email | Stated Page lists email. | Stated Alternate MDR page lists email among data sources. | | OT | Stated with limits An archived manufacturing page states it protects OT and IT environments. | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated Available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne EDR. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Red Canary | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | None found on 10 Nov 2026 | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | None found on 10 Nov 2026 | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | Red Canary says reporting shows speed and accuracy of detection and response over time. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Red Canary | Sygnia | | --- | --- | --- | | Does well | Red Canary lists named actions across endpoint, identity and network, lets customers choose oversight or automation, and publishes hunt writeups. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Red Canary states no included IR hours (IR comes through partner firms), and no price or response commitment, and OT rests on an archived page. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Red Canary, all published facts](/services/red-canary/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/red-canary-and-sygnia/ --- # SentinelOne and Sophos, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** SentinelOne and Sophos, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: SentinelOne 3 stated, 0 with limits, 3 none found; Sophos 5 stated, 0 with limits, 1 none found. The page gives no verdict. ## How do SentinelOne and Sophos differ? On the six actions read, SentinelOne has 3 stated, 0 with limits, 3 none found, and Sophos has 5 stated, 0 with limits, 1 none found. On the seven data sources read, SentinelOne has 3 stated, 1 with limits, 3 none found, and Sophos has 5 stated, 1 with limits, 1 none found. ## Actions on the customer's behalf | Action | SentinelOne | Sophos | | --- | --- | --- | | Isolate a host | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | Stated Service description lists host isolation as a Response Action. | | Disable or reset an account | None found on 10 November 2026 | Stated Lists disabling users and revoking sessions. | | Block an IP, domain, hash or email | None found on 10 November 2026 | Stated Lists blocking indicators. | | Kill a process or remove a file | Stated Says malicious processes are killed per the configured response policy. | Stated Lists process termination and quarantine of malicious artifacts. | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says confirmed threats are contained according to the configured response policy. | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | ## Data watched | Data | SentinelOne | Sophos | | --- | --- | --- | | Endpoint | Stated Core detection coverage includes endpoint. | Stated MDR page states endpoint coverage. | | Identity | Stated Core detection coverage includes identity. | Stated MDR page states identity coverage. | | Cloud | Stated Core detection coverage includes cloud. | Stated MDR page states cloud coverage. | | Network | None found on 10 November 2026 | Stated MDR page states network coverage. | | Email | None found on 10 November 2026 | Stated MDR page states email coverage. | | OT | None found on 10 November 2026 | None found on 10 November 2026 | | Works on other vendors' tools | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | ## The fifteen questions | Question | SentinelOne | Sophos | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | What may the provider do without asking first? | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | Which data sources does the service monitor? | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | Is the provider's own endpoint agent required? | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | Is threat hunting included, and what output is published? | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | Are incident response hours included, or is a retainer needed? | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | What response-time commitments are published? | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | Is the pricing model published? | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | Is OT covered? | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | What cloud and identity coverage is stated? | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What reporting does the customer receive? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | SentinelOne | Sophos | | --- | --- | --- | | Does well | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | | Limited | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [SentinelOne, all published facts](/services/sentinelone/) - [Sophos, all published facts](/services/sophos/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/sentinelone-and-sophos/ --- # SentinelOne and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** SentinelOne and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: SentinelOne 3 stated, 0 with limits, 3 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do SentinelOne and Sygnia differ? On the six actions read, SentinelOne has 3 stated, 0 with limits, 3 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, SentinelOne has 3 stated, 1 with limits, 3 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | SentinelOne | Sygnia | | --- | --- | --- | | Isolate a host | Stated Says confirmed threats are contained: endpoints isolated per the configured response policy. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | None found on 10 November 2026 | None found on 10 November 2026 | | Block an IP, domain, hash or email | None found on 10 November 2026 | None found on 10 November 2026 | | Kill a process or remove a file | Stated Says malicious processes are killed per the configured response policy. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated The provider says confirmed threats are contained according to the configured response policy. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | SentinelOne | Sygnia | | --- | --- | --- | | Endpoint | Stated Core detection coverage includes endpoint. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated Core detection coverage includes identity. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated Core detection coverage includes cloud. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | None found on 10 November 2026 | Stated Velocity ingests network data, per Sygnia. | | Email | None found on 10 November 2026 | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Lists supported third-party integrations; MDR is an add-on to Singularity plans. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | SentinelOne | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | SentinelOne | Sygnia | | --- | --- | --- | | Does well | SentinelOne states a 4-hour SLA for initial IR response, a 40-hour on-demand DFIR block, and an up to $1M breach response warranty. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | SentinelOne shows no MDR price (an add-on to Singularity plans), and none found on 10 Nov 2026 for OT on the MDR page or whether its agent is required. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [SentinelOne, all published facts](/services/sentinelone/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/sentinelone-and-sygnia/ --- # Sophos and Sygnia, side by side: what each says it will do, and on which data Side by side, read 10 November 2026 **In short.** Sophos and Sygnia, read from public pages on 10 November 2026 and set out in the same rows. Actions on the customer's behalf: Sophos 5 stated, 0 with limits, 1 none found; Sygnia 0 stated, 2 with limits, 4 none found. The page gives no verdict. ## How do Sophos and Sygnia differ? On the six actions read, Sophos has 5 stated, 0 with limits, 1 none found, and Sygnia has 0 stated, 2 with limits, 4 none found. On the seven data sources read, Sophos has 5 stated, 1 with limits, 1 none found, and Sygnia has 7 stated, 0 with limits, 0 none found. ## Actions on the customer's behalf | Action | Sophos | Sygnia | | --- | --- | --- | | Isolate a host | Stated Service description lists host isolation as a Response Action. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. | | Disable or reset an account | Stated Lists disabling users and revoking sessions. | None found on 10 November 2026 | | Block an IP, domain, hash or email | Stated Lists blocking indicators. | None found on 10 November 2026 | | Kill a process or remove a file | Stated Lists process termination and quarantine of malicious artifacts. | None found on 10 November 2026 | | Act in a cloud or SaaS console | None found on 10 November 2026 | None found on 10 November 2026 | | Acts without asking first (pre-approved) | Stated Authorize mode means pre-authorized action with notice after; Collaborate needs written consent. | Stated with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. | ## Data watched | Data | Sophos | Sygnia | | --- | --- | --- | | Endpoint | Stated MDR page states endpoint coverage. | Stated Sygnia says Velocity ingests endpoint data. | | Identity | Stated MDR page states identity coverage. | Stated Alternate MDR page lists identity among integrated data sources. | | Cloud | Stated MDR page states cloud coverage. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. | | Network | Stated MDR page states network coverage. | Stated Velocity ingests network data, per Sygnia. | | Email | Stated MDR page states email coverage. | Stated Alternate MDR page lists email among data sources. | | OT | None found on 10 November 2026 | Stated Sygnia states OT monitoring, including legacy OT systems. | | Works on other vendors' tools | Stated with limits Covers third-party endpoints agentless; IR applies only to Sophos XDR endpoints; Complete needs Sophos XDR. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. | ## The fifteen questions | Question | Sophos | Sygnia | | --- | --- | --- | | Who watches the environment around the clock, and who handles a major incident? | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | | What may the provider do without asking first? | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | | Which data sources does the service monitor? | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | | Is the provider's own endpoint agent required? | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | | Is threat hunting included, and what output is published? | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | | Are incident response hours included, or is a retainer needed? | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | | What response-time commitments are published? | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | | Is the pricing model published? | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | | Is OT covered? | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | | What cloud and identity coverage is stated? | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | | How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | | What reporting does the customer receive? | None found on 10 Nov 2026 | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | | Where is customer data kept, and for how long? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | Can the customer's analysts see what the provider sees? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | | What are the exit and data-return terms? | None found on 10 Nov 2026 | None found on 10 Nov 2026 | ## What each does well, and where each is limited | Field | Sophos | Sygnia | | --- | --- | --- | | Does well | Sophos publishes a defined list of Response Actions, customer-chosen response modes, and a 60-minute SLA with a service credit for MDR Plus. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. | | Limited | Sophos limits IR to MDR Plus on Sophos XDR endpoints, excludes disk forensics and on-site work, and OT was none found on 10 Nov 2026. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. | ## What to check in each situation - A mid-size company with no retainer and no in-house responders: ask both providers "What may the provider do without asking first?" and "Are incident response hours included, or is a retainer needed?" in writing. - A Global 2000 company with OT, several regions and a board that asks about readiness: ask both providers "Which data sources does the service monitor?" and "Is OT covered?" in writing. - A company under attack today: ask both providers "Who watches the environment around the clock, and who handles a major incident?" and "What may the provider do without asking first?" in writing. - A cyber-insured company whose policy names a panel of firms: ask both providers "Are incident response hours included, or is a retainer needed?" and "What response-time commitments are published?" in writing. - A security team that has tools and alerts but no one awake at 2 a.m.: ask both providers "Is the provider's own endpoint agent required?" and "What may the provider do without asking first?" in writing. ## Related pages - [Sophos, all published facts](/services/sophos/) - [Sygnia, all published facts](/services/sygnia/) - [The MDR Service Matrix](/matrix/) - [All side-by-side pages](/side-by-side/) ## Sources - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/sophos-and-sygnia/ --- # 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/ --- # MDR is a team you hire to watch and respond; XDR is software that gathers and correlates signals Explainer, read 10 November 2026 **The short answer.** XDR is a product category: a platform that collects telemetry from endpoints, network, cloud and identity and correlates it. MDR is a service in which people monitor, investigate and respond. A provider may run XDR to deliver MDR, or you may run XDR yourself. This page sets out the difference and the questions that follow. ## What is the difference between MDR and XDR? XDR stands for extended detection and response. It is software. MDR stands for managed detection and response. It is a service. The two sit at different layers, which is why a purchase can include both and why comparing them as rivals confuses a selection. Palo Alto Networks, an XDR vendor, writes that XDR "is a security technology platform that integrates and correlates threat data across endpoints, networks, cloud environments, and identity systems to improve detection and automate response", while MDR "is a managed security service that combines technology with human expertise to provide continuous threat monitoring, investigation, and response." It adds that XDR can be used on its own or combined with MDR. That is the vendor's definition, read on 10 Nov 2026. ## What XDR does and does not do for a small team IBM's explainer says XDR is typically consumed as a cloud-based or software-as-a-service product and can integrate point tools, layer-specific tools such as EDR and network detection and response (NDR), and data-collection tools such as SIEM and SOAR. It also says XDR may be the core technology behind a provider's MDR offering. The same page says XDR collects log data and telemetry from the integrated tools, including log-ins, network connections and traffic (read 10 Nov 2026). What software cannot supply is someone awake at 2 a.m. to read the result. If you buy XDR alone, your team triages, investigates and decides on every alert. If your team already does that on days and cannot at night, the gap is staffing, and a platform will not close it. ## What MDR adds MDR adds analysts, a triage process and a response procedure. Published examples show the range. Expel says its team monitors the customer's environment 24x7, investigates alerts, conducts root-cause analysis and alerts the customer when attention is needed. Huntress says a 24/7 human-led SOC investigates and acts. SentinelOne says every alert is investigated by certified analysts and that DFIR experts are available for critical incidents. Each statement is the provider's, read on 10 Nov 2026, and the providers are listed alphabetically. Notice what is missing from all three: a promise about outcomes. They describe work done, and a contract should do the same. What matters for your selection is not the adjective but the verb list: investigate, contain, remediate, advise. ## Three ways the two combine The pairing takes one of three forms, and the form changes what you own. - Provider platform: the provider supplies its own agent and console and runs the service on it. You own little of the tooling and the contract usually ends the access when the service ends. Arctic Wolf, for example, describes an open XDR architecture with over 200 integrations on its own platform. - Your platform: you license an XDR or EDR product and the provider's analysts work inside it. Microsoft's Defender Experts MDR works on Microsoft Defender workloads, and its overview says that for supported third-party products Plan 2 provides response guidance. - Mixed: the provider ingests several of your tools. Sophos says its service includes 500+ integrations across endpoint, network, cloud, identity, email and business applications, and Expel says it plugs into an existing stack with no agents to deploy. ## Questions that settle the choice Start with who owns the data and the detections. If the provider's platform holds the telemetry, ask how long it keeps it and whether you can export it. NCSC advises storing your most important logs for at least 6 months, so a provider that holds your telemetry for less needs a copy sent to you. Next, ask which actions the analysts may take on their own. MDR layered over XDR only reduces risk when someone is allowed to isolate a host or disable an account at night. Last, ask what is out of scope. Microsoft's overview, for instance, says neither plan covers Defender for Cloud workloads such as storage, containers and databases. - Which sources feed detection, and which are excluded? - Who writes and tunes detections: the provider, you, or both? - Where is telemetry stored, for how long, and can you export it? - What happens to access, data and agents at contract end? - Who pays for added integrations? ## A fair way to run the selection Decide the platform question and the staffing question separately, because mixing them is how selections stall. A platform question sounds like this: which telemetry do we already collect, and which product holds it? A staffing question sounds like this: which hours do we need covered, and who may act in them? If you already own an XDR or EDR product you like, restrict the list to services that work inside it. If you do not, accept that the service and the platform arrive together and read the exit terms with care. ## Related pages - [Home: MDR vs MSSP in short](/) - [MDR vs MSSP: who takes the next step after an alert](/mdr-vs-mssp/) - [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 - Palo Alto Networks, XDR explainer (vendor's definition): https://www.paloaltonetworks.com/cyberpedia/what-is-xdr (read 10 November 2026) - IBM, XDR explainer (vendor's definition): https://www.ibm.com/think/topics/xdr (read 10 November 2026) - NCSC, 10 Steps: Logging and monitoring: https://www.ncsc.gov.uk/collection/10-steps/logging-and-monitoring (read 10 November 2026) - Expel, meet the SOC experts: https://expel.com/meet-the-soc-experts/ (read 10 November 2026) - Huntress, Managed EDR page: https://www.huntress.com/platform/managed-edr (read 10 November 2026) - SentinelOne, MDR page: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Arctic Wolf, MDR page: https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Microsoft, Defender Experts MDR overview: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Expel, MDR service page: https://expel.com/services/managed-detection-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/mdr-vs-xdr/ --- # A SOC is the team and tools that watch your systems; MDR is a way to get that team from an outside provider Explainer, read 10 November 2026 **The short answer.** A security operations center (SOC) is a function: people, process and tools that detect and respond to attacks. MDR delivers part or all of that function as a service. The choice is between building, buying or sharing it. This page lays out what the UK NCSC says a SOC is for and what to hand over. ## What is the difference between MDR and a SOC? A SOC is not a product and not a vendor. It is a function inside an organization, or outsourced for one: the people and process that watch for attacks and respond to them. MDR is a service that supplies some or all of that function. So the comparison is between three ways of getting a SOC: build it, buy it as MDR, or split it. The UK National Cyber Security Centre says SOCs vary widely in scope but most are responsible for detecting and responding to cyber attacks, and that their role is to limit the damage from attacks that get past preventive controls. It adds that a SOC can include activities such as vulnerability assessment, compliance and system configuration (NCSC, read 10 Nov 2026). That wide scope is why a SOC and an MDR service rarely match one for one. ## What the NCSC lists as SOC work The NCSC guidance is organized around an operating model, onboarding systems and log sources, threat modeling, detection approaches, detection practices, threat intelligence and incident management. It describes onboarding as adding systems to the scope of the SOC so their logs are collected and monitored, and it notes that no IT estate stays the same, so onboarding never finishes. Read that list as a checklist of jobs. For each one, decide whether your team keeps it, the provider takes it or you share it. Most small teams keep the business context and hand over the night shift. ## What a provider takes over Published service descriptions show typical hand-offs. Expel lists SOC threat analysts, threat hunters, detection engineers and a global response team as parts of one 24x7 operation. Service tiers differ by provider: SentinelOne names three service levels, Threat Hunting, MDR Essentials and MDR Elite. Sophos lists service level targets of 2 minutes to create a case and 30 minutes from case creation to first outreach, evidence collection or response action, and says these are targets and not an SLA. Each of these is a provider's statement, read on 10 Nov 2026. None of them says the provider replaces your side of the work. Someone in your company still decides what is critical, approves response actions, talks to counsel and runs recovery. - Usually handed over: alert triage, 24x7 monitoring, first investigation, containment within agreed limits. - Often shared: detection tuning, threat hunting, incident communications. - Usually kept: asset knowledge, business priority, approvals, recovery, legal and regulatory decisions. ## Three models for the same function Build: you hire analysts, license tools and run shifts. A week has 168 hours, and one analyst works about 40 of them before leave and sickness, so continuous coverage needs several people before you count a manager. The cost lands in salaries before any tool is bought. Buy: you contract MDR for the night shift, or for the whole function. The provider owns the shift pattern and you own the escalation path. Share: your analysts work days, the provider works nights and weekends, and both read the same cases. Deepwatch, for example, says it connects to the customer's existing SIEM, EDR, cloud, identity and SaaS tools, and that its response actions run automatically, with analyst approval or in monitor-only mode, as the customer sets. That is the vendor's description of a shared arrangement. The seam between day and night is where cases get dropped, so agree how a case opened at 6 p.m. reaches your analyst at 8 a.m., and who owns it in between. Put the hand-off in the runbook and test it with a drill alert in the first month. ## What to settle before you decide Count the hours your team can actually cover and the incidents it has handled alone. Write both down for the past year, with dates, so the provider sees the same picture you do. Then write the escalation path: who gets the call, in what order, with what authority. Agree what the provider may do without a call. The NIST incident response publication, SP 800-61 Rev. 3 (April 2025), places incident response inside CSF 2.0 risk management, which fits this view: response is a governance matter as well as a technical one. Finally, plan the exit. If the provider is your SOC, ask how you would run detections, cases and history on the day the contract ends. - Hours covered by your own staff, by week. - Actions the provider may take without calling anyone. - Data and case history you can export. - Who owns detection rules written for you. - Escalation contacts and their back-ups. ## Related pages - [Home: MDR vs MSSP in short](/) - [MDR vs MSSP: who takes the next step after an alert](/mdr-vs-mssp/) - [MDR vs XDR: a service against a platform](/mdr-vs-xdr/) - [The six kinds of managed detection service](/guides/kinds-of-managed-detection/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) ## Sources - NCSC, Building a Security Operations Centre: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre (read 10 November 2026) - NCSC, Onboarding systems and log sources: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre/onboarding-systems-and-log-sources (read 10 November 2026) - NIST SP 800-61 Rev. 3 publication page: https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 10 November 2026) - Expel, meet the SOC experts: https://expel.com/meet-the-soc-experts/ (read 10 November 2026) - SentinelOne, MDR page: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, MDR service description: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Deepwatch, home page: https://www.deepwatch.com/ (read 10 November 2026) - Deepwatch, Active Response: https://www.deepwatch.com/active-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/mdr-vs-soc/ --- # Five buyer situations, and what each should check first Situations, read 10 November 2026 **In short.** Five situations a buyer is usually in: no retainer and no responders, a Global 2000 estate with OT, under attack today, a cyber policy with a panel, and tools with no one awake at night. Each page names the questions that matter most there and prints every provider's published answer. - [A mid-size company with no retainer and no in-house responders](/situations/mid-size-no-retainer/): With nobody inside to take over, the service must act on its own and carry the breach through to response. - [A Global 2000 company with OT, several regions and a board that asks about readiness](/situations/global-2000-with-ot/): The estate spans IT, cloud, identity and plants, and runs tools from many vendors. - [A company under attack today](/situations/under-attack-today/): What counts is who investigates, what they may do right now, and whether response is part of the service. - [A cyber-insured company whose policy names a panel of firms](/situations/insurer-panel/): The insurer wants response attached and terms in writing. Panel membership found in public sources is printed as a fact. - [A security team that has tools and alerts but no one awake at 2 a.m.](/situations/no-night-shift/): The service has to work on the tools already bought and be allowed to act at night without waking anyone. ## Related pages - [Home: MDR vs MSSP in short](/) - [The MDR Service Matrix](/matrix/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [How this site lists services](/method/) - [Glossary](/glossary/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/ --- # A mid-size company with no retainer and no in-house responders: the four questions to settle first Situation, read 10 November 2026 **In short.** With nobody inside to take over, the service must act on its own and carry the breach through to response. The four questions that matter most here: what may the provider do without asking first; are incident response hours included, or is a retainer needed; what response-time commitments are published; is the pricing model published. ## Why these questions With nobody inside to take over, the service must act on its own and carry the breach through to response. ## What may the provider do without asking first? Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | [Deepwatch](/services/deepwatch/) | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | [eSentire](/services/esentire/) | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | [Expel](/services/expel/) | Expel says customers can let it press the respond button or choose what, how and when it acts. | | [Huntress](/services/huntress/) | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | [Kroll](/services/kroll/) | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | [Microsoft](/services/microsoft/) | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | [Rapid7](/services/rapid7/) | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | [Red Canary](/services/red-canary/) | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | [SentinelOne](/services/sentinelone/) | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | [Sophos](/services/sophos/) | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | [Sygnia](/services/sygnia/) | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | Alphabetical. 16 of 16 answered in public pages. ## Are incident response hours included, or is a retainer needed? IR billed separately changes the cost of the worst week of the year. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | [Critical Start](/services/critical-start/) | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | [eSentire](/services/esentire/) | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | [Expel](/services/expel/) | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | [Huntress](/services/huntress/) | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | [Kroll](/services/kroll/) | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | [Mandiant](/services/mandiant/) | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | [Rapid7](/services/rapid7/) | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | [Red Canary](/services/red-canary/) | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | [SentinelOne](/services/sentinelone/) | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | [Sophos](/services/sophos/) | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | [Sygnia](/services/sygnia/) | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | Alphabetical. 16 of 16 answered in public pages. ## What response-time commitments are published? A stated number with a credit is something a contract can enforce. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | [Expel](/services/expel/) | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | [Microsoft](/services/microsoft/) | Microsoft's overview prints no price or response-time commitment. | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | [Sophos](/services/sophos/) | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | [Sygnia](/services/sygnia/) | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | Alphabetical. 12 of 16 answered in public pages. ## Is the pricing model published? Knowing what is priced (endpoints, users, data volume) tells you how the bill grows. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | [Expel](/services/expel/) | Expel says pricing is by request, with Starter, Select and Premium packages. | | [Huntress](/services/huntress/) | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | [Rapid7](/services/rapid7/) | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | [Sophos](/services/sophos/) | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | [Sygnia](/services/sygnia/) | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | Alphabetical. 11 of 16 answered in public pages. ## Related pages - [All five buyer situations](/situations/) - [MDR for a Global 2000 company with OT, several regions and a board that asks about readiness](/situations/global-2000-with-ot/) - [MDR for a company under attack today](/situations/under-attack-today/) - [MDR for a cyber-insured company whose policy names a panel of firms](/situations/insurer-panel/) - [MDR for a security team that has tools and alerts but no one awake at 2 a.m.](/situations/no-night-shift/) - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Arctic Wolf, "Incident response retainer" page (the firm's own page): https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/company/faq/ (read 10 November 2026) - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - BlueVoyant, "Digital forensics incident response" page (the firm's own page): https://www.bluevoyant.com/solutions/digital-forensics-incident-response (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Critical Start, "Services" page (the firm's own page): https://www.criticalstart.com/services (read 10 November 2026) - Critical Start, "SLA commitment" page (the firm's own page): https://www.criticalstart.com/sla-commitment (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - CrowdStrike, "Pricing" page (the firm's own page): https://www.crowdstrike.com/en-us/pricing/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Deepwatch, "Ati" page (the firm's own page): https://www.deepwatch.com/ati/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - eSentire, "Incident response retainer" page (the firm's own page): https://www.esentire.com/what-we-do/digital-forensics-and-incident-response/incident-response-retainer (read 10 November 2026) - eSentire, "Pricing packaging" page (the firm's own page): https://www.esentire.com/pricing-packaging (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Expel, "MDR packages" page (the firm's own page): https://expel.com/mdr-packages/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Red Canary, "Redcanary joining zscaler" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/redcanary-joining-zscaler (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - SentinelOne, "Pricing" page (the firm's own page): https://www.sentinelone.com/pricing/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) - Sygnia, "Sygnia brings expert led managed 130000486" page (the firm's own page): https://finance.yahoo.com/technology/ai/articles/sygnia-brings-expert-led-managed-130000486.html (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) - Sygnia, "Prodview mjvsalxozaiuk" page (the firm's own page): https://aws.amazon.com/marketplace/pp/prodview-mjvsalxozaiuk (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/mid-size-no-retainer/ --- # A Global 2000 company with OT, several regions and a board that asks about readiness: the four questions to settle first Situation, read 10 November 2026 **In short.** The estate spans IT, cloud, identity and plants, and runs tools from many vendors. The four questions that matter most here: which data sources does the service monitor; is OT covered; what cloud and identity coverage is stated; is the provider's own endpoint agent required. The first two: which data sources does the service monitor; and is OT covered. ## Why these questions The estate spans IT, cloud, identity and plants, and runs tools from many vendors. ## Which data sources does the service monitor? Detection only works on the data the provider actually ingests. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | | [Critical Start](/services/critical-start/) | Critical Start says CORR supports 100+ integrations across seven security domains. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | [Deepwatch](/services/deepwatch/) | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | [eSentire](/services/esentire/) | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | [Expel](/services/expel/) | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | [Huntress](/services/huntress/) | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | [Kroll](/services/kroll/) | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | [Mandiant](/services/mandiant/) | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | [Microsoft](/services/microsoft/) | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | [Rapid7](/services/rapid7/) | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | [Red Canary](/services/red-canary/) | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | [SentinelOne](/services/sentinelone/) | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | [Sophos](/services/sophos/) | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | [Sygnia](/services/sygnia/) | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | Alphabetical. 16 of 16 answered in public pages. ## Is OT covered? Plant and building systems often cannot run an agent and need different monitoring. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | [Expel](/services/expel/) | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft's FAQ excludes IoT devices and does not mention OT. | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | [SentinelOne](/services/sentinelone/) | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | [Sygnia](/services/sygnia/) | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | Alphabetical. 8 of 16 answered in public pages. ## What cloud and identity coverage is stated? Many intrusions now move through accounts and cloud consoles, not hosts. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | | [Critical Start](/services/critical-start/) | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | [Deepwatch](/services/deepwatch/) | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | [eSentire](/services/esentire/) | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | [Expel](/services/expel/) | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | [Huntress](/services/huntress/) | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | [Kroll](/services/kroll/) | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | [Mandiant](/services/mandiant/) | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | [Rapid7](/services/rapid7/) | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | [Red Canary](/services/red-canary/) | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | [SentinelOne](/services/sentinelone/) | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | [Sophos](/services/sophos/) | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | [Sygnia](/services/sygnia/) | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | Alphabetical. 16 of 16 answered in public pages. ## Is the provider's own endpoint agent required? A required agent means replacing or running next to the tools already in place. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | | [Critical Start](/services/critical-start/) | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | [CrowdStrike](/services/crowdstrike/) | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | [eSentire](/services/esentire/) | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | [Expel](/services/expel/) | Expel says no agents need to be deployed and it plugs into the existing stack. | | [Huntress](/services/huntress/) | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | [Kroll](/services/kroll/) | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | [Mandiant](/services/mandiant/) | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | [Microsoft](/services/microsoft/) | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | [Rapid7](/services/rapid7/) | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | [Red Canary](/services/red-canary/) | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | [SentinelOne](/services/sentinelone/) | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | [Sophos](/services/sophos/) | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | [Sygnia](/services/sygnia/) | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | Alphabetical. 16 of 16 answered in public pages. ## Related pages - [All five buyer situations](/situations/) - [MDR for a mid-size company with no retainer and no in-house responders](/situations/mid-size-no-retainer/) - [MDR for a company under attack today](/situations/under-attack-today/) - [MDR for a cyber-insured company whose policy names a panel of firms](/situations/insurer-panel/) - [MDR for a security team that has tools and alerts but no one awake at 2 a.m.](/situations/no-night-shift/) - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Arctic Wolf, "Technology integrations" page (the firm's own page): https://arcticwolf.com/partners/technology-integrations/ (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Critical Start, "Why critical start" page (the firm's own page): https://www.criticalstart.com/why-critical-start (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Deepwatch platform" page (the firm's own page): https://www.deepwatch.com/deepwatch-platform/ (read 10 November 2026) - Deepwatch, "Leverage existing tools" page (the firm's own page): https://www.deepwatch.com/use-existing-tools/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - eSentire, "Manufacturing cybersecurity" page (the firm's own page): https://www.esentire.com/how-we-do-it/industries/manufacturing-cybersecurity (read 10 November 2026) - Expel, "Detection coverage" page (the firm's own page): https://expel.com/detection-coverage/ (read 10 November 2026) - Expel, home page (the firm's own page): https://expel.com/ (read 10 November 2026) - Expel, "MDR packages" page (the firm's own page): https://expel.com/mdr-packages/ (read 10 November 2026) - Expel, "Managed detection response" page (the firm's own page): https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Huntress, "Platform" page (the firm's own page): https://www.huntress.com/platform (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Kroll, "OT security" page (the firm's own page): https://www.kroll.com/en/services/cyber/cybersecurity-transformation/ot-security (read 10 November 2026) - Kroll, "Kroll MDR services migrate to crowdstrike falcon complete next gen MDR" page (the firm's own page): https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr (read 10 November 2026) - Mandiant, "Mandiant incident response services" page (the firm's own page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Microsoft defender experts MDR" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-mdr (read 10 November 2026) - Microsoft, "Defender experts MDR FAQ" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Red Canary, "Manufacturing services" page (the firm's own page): https://redcanary.com/solutions/industry/manufacturing-services/ (read 10 November 2026) - Red Canary, "Introducing red canary active threat remediation" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/global-2000-with-ot/ --- # A company under attack today: the four questions to settle first Situation, read 10 November 2026 **In short.** What counts is who investigates, what they may do right now, and whether response is part of the service. The first two: who watches the environment around the clock, and who handles a major incident; and what may the provider do without asking first. Public answers were found for between 1 and 16 of sixteen providers. ## Why these questions What counts is who investigates, what they may do right now, and whether response is part of the service. ## Who watches the environment around the clock, and who handles a major incident? The people on the night shift and the people called for a breach are often different teams with different contracts. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | | [Critical Start](/services/critical-start/) | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | [Deepwatch](/services/deepwatch/) | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | [eSentire](/services/esentire/) | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | [Expel](/services/expel/) | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | [Huntress](/services/huntress/) | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | [Kroll](/services/kroll/) | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | [Mandiant](/services/mandiant/) | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | [Microsoft](/services/microsoft/) | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | [Rapid7](/services/rapid7/) | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | [Red Canary](/services/red-canary/) | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | [SentinelOne](/services/sentinelone/) | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | [Sophos](/services/sophos/) | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | [Sygnia](/services/sygnia/) | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | Alphabetical. 16 of 16 answered in public pages. ## What may the provider do without asking first? Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | [Deepwatch](/services/deepwatch/) | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | [eSentire](/services/esentire/) | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | [Expel](/services/expel/) | Expel says customers can let it press the respond button or choose what, how and when it acts. | | [Huntress](/services/huntress/) | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | [Kroll](/services/kroll/) | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | [Microsoft](/services/microsoft/) | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | [Rapid7](/services/rapid7/) | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | [Red Canary](/services/red-canary/) | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | [SentinelOne](/services/sentinelone/) | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | [Sophos](/services/sophos/) | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | [Sygnia](/services/sygnia/) | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | Alphabetical. 16 of 16 answered in public pages. ## Are incident response hours included, or is a retainer needed? IR billed separately changes the cost of the worst week of the year. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | [Critical Start](/services/critical-start/) | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | [eSentire](/services/esentire/) | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | [Expel](/services/expel/) | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | [Huntress](/services/huntress/) | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | [Kroll](/services/kroll/) | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | [Mandiant](/services/mandiant/) | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | [Rapid7](/services/rapid7/) | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | [Red Canary](/services/red-canary/) | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | [SentinelOne](/services/sentinelone/) | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | [Sophos](/services/sophos/) | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | [Sygnia](/services/sygnia/) | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | Alphabetical. 16 of 16 answered in public pages. ## How long does onboarding take? Time to full coverage is time exposed during the change. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | None found on 10 Nov 2026 | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | None found on 10 Nov 2026 | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | Alphabetical. 1 of 16 answered in public pages. ## Related pages - [All five buyer situations](/situations/) - [MDR for a mid-size company with no retainer and no in-house responders](/situations/mid-size-no-retainer/) - [MDR for a Global 2000 company with OT, several regions and a board that asks about readiness](/situations/global-2000-with-ot/) - [MDR for a cyber-insured company whose policy names a panel of firms](/situations/insurer-panel/) - [MDR for a security team that has tools and alerts but no one awake at 2 a.m.](/situations/no-night-shift/) - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Arctic Wolf, "Incident response retainer" page (the firm's own page): https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Critical Start, "Services" page (the firm's own page): https://www.criticalstart.com/services (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Deepwatch experts" page (the firm's own page): https://www.deepwatch.com/deepwatch-experts/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Deepwatch, "Ati" page (the firm's own page): https://www.deepwatch.com/ati/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - eSentire, "Incident response retainer" page (the firm's own page): https://www.esentire.com/what-we-do/digital-forensics-and-incident-response/incident-response-retainer (read 10 November 2026) - Expel, "Meet the SOC experts" page (the firm's own page): https://expel.com/meet-the-soc-experts/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Red Canary, "Redcanary joining zscaler" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/redcanary-joining-zscaler (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) - Sygnia, "Sygnia brings expert led managed 130000486" page (the firm's own page): https://finance.yahoo.com/technology/ai/articles/sygnia-brings-expert-led-managed-130000486.html (read 10 November 2026) - Sygnia, "Sygnia expands incident response and proactive security services to include managed extended detection and response service 301724165" page (the firm's own page): https://www.prnewswire.com/news-releases/sygnia-expands-incident-response-and-proactive-security-services-to-include-managed-extended-detection-and-response-service-301724165.html (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/under-attack-today/ --- # A cyber-insured company whose policy names a panel of firms: the four questions to settle first Situation, read 10 November 2026 **In short.** The insurer wants response attached and terms in writing. Panel membership found in public sources is printed as a fact. The four questions that matter most here: are incident response hours included, or is a retainer needed; what response-time commitments are published; what reporting does the customer receive; what are the exit and data-return terms. ## Why these questions The insurer wants response attached and terms in writing. Panel membership found in public sources is printed as a fact. ## Are incident response hours included, or is a retainer needed? IR billed separately changes the cost of the worst week of the year. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | [Critical Start](/services/critical-start/) | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | [eSentire](/services/esentire/) | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | [Expel](/services/expel/) | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | [Huntress](/services/huntress/) | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | [Kroll](/services/kroll/) | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | [Mandiant](/services/mandiant/) | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | [Rapid7](/services/rapid7/) | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | [Red Canary](/services/red-canary/) | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | [SentinelOne](/services/sentinelone/) | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | [Sophos](/services/sophos/) | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | [Sygnia](/services/sygnia/) | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | Alphabetical. 16 of 16 answered in public pages. ## What response-time commitments are published? A stated number with a credit is something a contract can enforce. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | [Expel](/services/expel/) | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | [Microsoft](/services/microsoft/) | Microsoft's overview prints no price or response-time commitment. | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | [Sophos](/services/sophos/) | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | [Sygnia](/services/sygnia/) | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | Alphabetical. 12 of 16 answered in public pages. ## What reporting does the customer receive? Regular reports are how the security lead shows the board what was done. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | Expel says customers see every alert, investigation and action in its Workbench platform. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [Rapid7](/services/rapid7/) | Rapid7 says every action in the SOC is logged, explainable and auditable. | | [Red Canary](/services/red-canary/) | Red Canary says reporting shows speed and accuracy of detection and response over time. | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | Alphabetical. 8 of 16 answered in public pages. ## What are the exit and data-return terms? Leaving a provider is easier when data return is agreed before signing. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | None found on 10 Nov 2026 | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | None found on 10 Nov 2026 | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 | Alphabetical. 0 of 16 answered in public pages. ## Related pages - [All five buyer situations](/situations/) - [MDR for a mid-size company with no retainer and no in-house responders](/situations/mid-size-no-retainer/) - [MDR for a Global 2000 company with OT, several regions and a board that asks about readiness](/situations/global-2000-with-ot/) - [MDR for a company under attack today](/situations/under-attack-today/) - [MDR for a security team that has tools and alerts but no one awake at 2 a.m.](/situations/no-night-shift/) - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - Arctic Wolf, "Incident response retainer" page (the firm's own page): https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/company/faq/ (read 10 November 2026) - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - BlueVoyant, "Digital forensics incident response" page (the firm's own page): https://www.bluevoyant.com/solutions/digital-forensics-incident-response (read 10 November 2026) - Critical Start, "Services" page (the firm's own page): https://www.criticalstart.com/services (read 10 November 2026) - Critical Start, "SLA commitment" page (the firm's own page): https://www.criticalstart.com/sla-commitment (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Ati" page (the firm's own page): https://www.deepwatch.com/ati/ (read 10 November 2026) - Deepwatch, "Transparency and accountability" page (the firm's own page): https://www.deepwatch.com/transparency-and-accountability/ (read 10 November 2026) - eSentire, "Incident response retainer" page (the firm's own page): https://www.esentire.com/what-we-do/digital-forensics-and-incident-response/incident-response-retainer (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Expel, "About" page (the firm's own page): https://expel.com/about/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Redcanary joining zscaler" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/redcanary-joining-zscaler (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Sygnia brings expert led managed 130000486" page (the firm's own page): https://finance.yahoo.com/technology/ai/articles/sygnia-brings-expert-led-managed-130000486.html (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/insurer-panel/ --- # A security team that has tools and alerts but no one awake at 2 a.m.: the four questions to settle first Situation, read 10 November 2026 **In short.** The service has to work on the tools already bought and be allowed to act at night without waking anyone. The four questions that matter most here: is the provider's own endpoint agent required; what may the provider do without asking first; which data sources does the service monitor; can the customer's analysts see what the provider sees. ## Why these questions The service has to work on the tools already bought and be allowed to act at night without waking anyone. ## Is the provider's own endpoint agent required? A required agent means replacing or running next to the tools already in place. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | | [Critical Start](/services/critical-start/) | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | [CrowdStrike](/services/crowdstrike/) | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | [eSentire](/services/esentire/) | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | [Expel](/services/expel/) | Expel says no agents need to be deployed and it plugs into the existing stack. | | [Huntress](/services/huntress/) | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | [Kroll](/services/kroll/) | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | [Mandiant](/services/mandiant/) | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | [Microsoft](/services/microsoft/) | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | [Rapid7](/services/rapid7/) | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | [Red Canary](/services/red-canary/) | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | [SentinelOne](/services/sentinelone/) | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | [Sophos](/services/sophos/) | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | [Sygnia](/services/sygnia/) | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | Alphabetical. 16 of 16 answered in public pages. ## What may the provider do without asking first? Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | [Deepwatch](/services/deepwatch/) | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | [eSentire](/services/esentire/) | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | [Expel](/services/expel/) | Expel says customers can let it press the respond button or choose what, how and when it acts. | | [Huntress](/services/huntress/) | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | [Kroll](/services/kroll/) | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | [Microsoft](/services/microsoft/) | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | [Rapid7](/services/rapid7/) | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | [Red Canary](/services/red-canary/) | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | [SentinelOne](/services/sentinelone/) | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | [Sophos](/services/sophos/) | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | [Sygnia](/services/sygnia/) | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | Alphabetical. 16 of 16 answered in public pages. ## Which data sources does the service monitor? Detection only works on the data the provider actually ingests. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | | [Critical Start](/services/critical-start/) | Critical Start says CORR supports 100+ integrations across seven security domains. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | [Deepwatch](/services/deepwatch/) | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | [eSentire](/services/esentire/) | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | [Expel](/services/expel/) | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | [Huntress](/services/huntress/) | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | [Kroll](/services/kroll/) | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | [Mandiant](/services/mandiant/) | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | [Microsoft](/services/microsoft/) | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | [Rapid7](/services/rapid7/) | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | [Red Canary](/services/red-canary/) | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | [SentinelOne](/services/sentinelone/) | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | [Sophos](/services/sophos/) | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | [Sygnia](/services/sygnia/) | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | Alphabetical. 16 of 16 answered in public pages. ## Can the customer's analysts see what the provider sees? Shared access lets your team check the work and take over an investigation. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | Expel says customers see every alert, investigation and action in Workbench. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [Rapid7](/services/rapid7/) | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | [Red Canary](/services/red-canary/) | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 | Alphabetical. 5 of 16 answered in public pages. ## Related pages - [All five buyer situations](/situations/) - [MDR for a mid-size company with no retainer and no in-house responders](/situations/mid-size-no-retainer/) - [MDR for a Global 2000 company with OT, several regions and a board that asks about readiness](/situations/global-2000-with-ot/) - [MDR for a company under attack today](/situations/under-attack-today/) - [MDR for a cyber-insured company whose policy names a panel of firms](/situations/insurer-panel/) - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - Arctic Wolf, "Technology integrations" page (the firm's own page): https://arcticwolf.com/partners/technology-integrations/ (read 10 November 2026) - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Critical Start, "Why critical start" page (the firm's own page): https://www.criticalstart.com/why-critical-start (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Leverage existing tools" page (the firm's own page): https://www.deepwatch.com/use-existing-tools/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Deepwatch, "Deepwatch platform" page (the firm's own page): https://www.deepwatch.com/deepwatch-platform/ (read 10 November 2026) - Deepwatch, "Transparency and accountability" page (the firm's own page): https://www.deepwatch.com/transparency-and-accountability/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Managed detection response" page (the firm's own page): https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Expel, "Detection coverage" page (the firm's own page): https://expel.com/detection-coverage/ (read 10 November 2026) - Expel, "About" page (the firm's own page): https://expel.com/about/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Huntress, "Platform" page (the firm's own page): https://www.huntress.com/platform (read 10 November 2026) - Kroll, "Kroll MDR services migrate to crowdstrike falcon complete next gen MDR" page (the firm's own page): https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Mandiant, "Mandiant incident response services" page (the firm's own page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Microsoft defender experts MDR" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-mdr (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Introducing red canary active threat remediation" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/situations/no-night-shift/ --- # What sixteen MDR services say they will do on your behalf, and on which data MDR Service Matrix, edition 10 November 2026 **In short.** Read from public service descriptions on 10 November 2026, sixteen services, alphabetical. Isolate a host: 11 state it without conditions, 4 with limits, 1 none found. Act in a cloud or SaaS console: 1 state it without conditions, 5 with limits, 10 none found. Monitor OT: 3 state it without conditions, 3 with limits, 10 none found. ## What do MDR services do on the customer's behalf? Isolating a host: 11 state it without conditions, 4 with limits, 1 none found. Disabling or resetting an account: 5 state it without conditions, 4 with limits, 7 none found. | Service | Isolate a host | Disable or reset an account | Block an IP, domain, hash or email | Kill a process or remove a file | Act in a cloud or SaaS console | Acts without asking first (pre-approved) | | --- | --- | --- | --- | --- | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Stated with limits | Stated with limits | None found | None found | None found | Stated with limits | | [BlueVoyant](/services/bluevoyant/) | Stated | None found | Stated | None found | None found | None found | | [Critical Start](/services/critical-start/) | Stated | Stated | Stated | Stated with limits | None found | Stated with limits | | [CrowdStrike](/services/crowdstrike/) | Stated | None found | None found | None found | Stated with limits | None found | | [Deepwatch](/services/deepwatch/) | Stated | Stated | None found | Stated | None found | Stated | | [eSentire](/services/esentire/) | Stated | Stated | Stated | Stated | Stated | Stated | | [Expel](/services/expel/) | None found | None found | None found | None found | None found | Stated | | [Huntress](/services/huntress/) | Stated | Stated with limits | None found | None found | Stated with limits | None found | | [Kroll](/services/kroll/) | Stated | Stated with limits | Stated with limits | Stated | Stated with limits | None found | | [Mandiant](/services/mandiant/) | Stated with limits | None found | None found | None found | None found | None found | | [Microsoft](/services/microsoft/) | Stated with limits | Stated with limits | None found | Stated with limits | Stated with limits | Stated with limits | | [Rapid7](/services/rapid7/) | Stated | None found | None found | None found | None found | Stated | | [Red Canary](/services/red-canary/) | Stated | Stated | Stated | None found | Stated with limits | Stated | | [SentinelOne](/services/sentinelone/) | Stated | None found | None found | Stated | None found | Stated | | [Sophos](/services/sophos/) | Stated | Stated | Stated | Stated | None found | Stated | | [Sygnia](/services/sygnia/) | Stated with limits | None found | None found | None found | None found | Stated with limits | Alphabetical. Stated: a source says so plainly. Stated with limits: said with a condition or only as an aim. None found: no source on file on 10 November 2026, which does not mean the service cannot do it. Each cell's source is on the service page. No asking records pre-approval of whatever actions a service takes, even where no specific action was found. Expel, acts without asking first: Customers can let Expel act once its SOC validates a threat, or choose what, how and when. ## Data each service watches | Service | Endpoint | Identity | Cloud | Network | Email | OT | Works on other vendors' tools | | --- | --- | --- | --- | --- | --- | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Stated with limits | Stated with limits | Stated with limits | Stated with limits | None found | None found | Stated | | [BlueVoyant](/services/bluevoyant/) | Stated | Stated with limits | Stated | Stated | None found | None found | Stated | | [Critical Start](/services/critical-start/) | Stated | Stated | Stated | Stated | Stated | Stated | Stated | | [CrowdStrike](/services/crowdstrike/) | Stated | Stated | Stated | None found | None found | None found | Stated with limits | | [Deepwatch](/services/deepwatch/) | Stated | Stated | Stated | Stated | None found | None found | Stated | | [eSentire](/services/esentire/) | Stated | Stated with limits | Stated with limits | Stated | None found | Stated with limits | Stated | | [Expel](/services/expel/) | Stated | Stated | Stated | Stated | None found | Stated | Stated | | [Huntress](/services/huntress/) | Stated | Stated with limits | Stated with limits | Stated with limits | None found | None found | Stated with limits | | [Kroll](/services/kroll/) | Stated | Stated | Stated | Stated with limits | None found | Stated with limits | Stated with limits | | [Mandiant](/services/mandiant/) | Stated | None found | Stated | Stated | None found | None found | Stated with limits | | [Microsoft](/services/microsoft/) | Stated | Stated | Stated with limits | Stated | Stated | None found | Stated with limits | | [Rapid7](/services/rapid7/) | Stated | Stated | Stated | Stated | Stated | None found | Stated with limits | | [Red Canary](/services/red-canary/) | Stated | Stated | Stated | Stated | Stated | Stated with limits | Stated | | [SentinelOne](/services/sentinelone/) | Stated | Stated | Stated | None found | None found | None found | Stated with limits | | [Sophos](/services/sophos/) | Stated | Stated | Stated | Stated | Stated | None found | Stated with limits | | [Sygnia](/services/sygnia/) | Stated | Stated | Stated | Stated | Stated | Stated | Stated | Alphabetical. Stated: a source says so plainly. Stated with limits: said with a condition or only as an aim. None found: no source on file on 10 November 2026, which does not mean the service cannot do it. Each cell's source is on the service page. ## Cite this MDR vs MSSP, "MDR Service Matrix", edition 10 November 2026, https://mdrvsmssp.com/matrix/ (CC BY 4.0). ## Related pages - [Download the matrix as CSV and JSON](/datasets/) - [How the matrix was read](/matrix/method/) - [The MDR Question Sheet](/questions/) - [How this site lists services](/method/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Arctic Wolf, "Technology integrations" page (the firm's own page): https://arcticwolf.com/partners/technology-integrations/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - Critical Start, "Why critical start" page (the firm's own page): https://www.criticalstart.com/why-critical-start (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - Deepwatch, "Leverage existing tools" page (the firm's own page): https://www.deepwatch.com/use-existing-tools/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - eSentire, home page (the firm's own page): https://www.esentire.com/ (read 10 November 2026) - Expel, "Managed detection response" page (the firm's own page): https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Kroll, "Kroll MDR services migrate to crowdstrike falcon complete next gen MDR" page (the firm's own page): https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Red Canary, "Introducing red canary active threat remediation" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/matrix/ --- # The matrix records what each provider's public service description says, on one date Matrix method, read 10 November 2026 **In short.** Every cell of the MDR Service Matrix was read from the provider's own service description, datasheet or terms, or a primary source, on 10 November 2026. Each cell cites the facts it rests on. None found records what was searched, not what the service can do. ## How was the MDR Service Matrix read? This matrix was read from public service descriptions, datasheets and product pages on 10 Nov 2026. Every value is what the provider says about its own service, labelled as the provider's, unless a note names IDC or a customer as the source. A blank cell reads 'None found on 10 Nov 2026'. That does not mean the provider cannot do it. It means no public page we read said so. Services are listed alphabetically by name. The matrix does not order them by merit. ## The grading rule One grading rule applies to every provider: Stated means a source (the provider's own page, or an analyst's text about the service) says plainly that the service does this; Stated with limits means it is said with a condition (approval each time, a tier or add-on, a scenario list, another company's product) or as an aim ("aims to"), or only on a page the provider has archived; None found means no source on file says it. Who said it is a separate label, shown in each cell's note and on the service page: a provider's own claim is marked as the provider's, and analyst text hosted on a provider's site is labelled as that provider's publication of it. ## Actions read - Isolate a host - Disable or reset an account - Block an IP, domain, hash or email - Kill a process or remove a file - Act in a cloud or SaaS console - Acts without asking first (pre-approved) ## Data sources read - Endpoint - Identity - Cloud - Network - Email - OT - Works on other vendors' tools ## Related pages - [The MDR Service Matrix](/matrix/) - [The MDR Question Sheet](/questions/) - [Datasets](/datasets/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/matrix/method/ --- # Fifteen questions to put to every MDR provider, with the answers already found MDR Question Sheet, edition 10 November 2026 **In short.** The 15 questions are the ones a buyer should put to every managed detection and response provider before signing. Each answer below is what the provider publishes, labelled as theirs, or None found on 10 Nov 2026. A blank answer is a question to ask, not a finding about the provider. Services appear alphabetically. ## What should you ask an MDR provider before signing? The fifteen questions are the ones a buyer should put to every managed detection and response provider before signing. A blank answer is a question to ask, not a finding about the provider. | # | Question | Why it matters | Answers found | | --- | --- | --- | --- | | 1 | [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) | The people on the night shift and the people called for a breach are often different teams with different contracts. | 16 of 16 | | 2 | [What may the provider do without asking first?](/questions/q02/) | Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. | 16 of 16 | | 3 | [Which data sources does the service monitor?](/questions/q03/) | Detection only works on the data the provider actually ingests. | 16 of 16 | | 4 | [Is the provider's own endpoint agent required?](/questions/q04/) | A required agent means replacing or running next to the tools already in place. | 16 of 16 | | 5 | [Is threat hunting included, and what output is published?](/questions/q05/) | Hunting that produces no written findings is hard to check. | 16 of 16 | | 6 | [Are incident response hours included, or is a retainer needed?](/questions/q06/) | IR billed separately changes the cost of the worst week of the year. | 16 of 16 | | 7 | [What response-time commitments are published?](/questions/q07/) | A stated number with a credit is something a contract can enforce. | 12 of 16 | | 8 | [Is the pricing model published?](/questions/q08/) | Knowing what is priced (endpoints, users, data volume) tells you how the bill grows. | 11 of 16 | | 9 | [Is OT covered?](/questions/q09/) | Plant and building systems often cannot run an agent and need different monitoring. | 8 of 16 | | 10 | [What cloud and identity coverage is stated?](/questions/q10/) | Many intrusions now move through accounts and cloud consoles, not hosts. | 16 of 16 | | 11 | [How long does onboarding take?](/questions/q11/) | Time to full coverage is time exposed during the change. | 1 of 16 | | 12 | [What reporting does the customer receive?](/questions/q12/) | Regular reports are how the security lead shows the board what was done. | 8 of 16 | | 13 | [Where is customer data kept, and for how long?](/questions/q13/) | Retention and location decide legal and audit questions. | 1 of 16 | | 14 | [Can the customer's analysts see what the provider sees?](/questions/q14/) | Shared access lets your team check the work and take over an investigation. | 5 of 16 | | 15 | [What are the exit and data-return terms?](/questions/q15/) | Leaving a provider is easier when data return is agreed before signing. | 0 of 16 | Answers found counts the providers whose public pages answer the question; the rest read "none found on 10 Nov 2026". Ask every provider every question in writing. ## Related pages - [The MDR Service Matrix](/matrix/) - [Download the question sheet](/datasets/) - [How this site lists services](/method/) - [Five buyer situations](/situations/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/ --- # Who watches the environment around the clock, and who handles a major incident: 16 of 16 providers publish an answer Question Sheet, question 1 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. The people on the night shift and the people called for a breach are often different teams with different contracts. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. ## Who watches the environment around the clock, and who handles a major incident? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. The people on the night shift and the people called for a breach are often different teams with different contracts. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its Concierge Security Team learns each customer's context; IR items sit within its delivery model. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says it runs 24x7 in-regional SOC monitoring and has forensic labs in EMEA and the Americas. | | [Critical Start](/services/critical-start/) | Critical Start says a human analyst investigates every alert not auto-resolved; its CIRT, available 24/7, already has environment context. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says experts own every outcome; IDC says each MDR analyst is an experienced incident response expert. | | [Deepwatch](/services/deepwatch/) | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | | [eSentire](/services/esentire/) | eSentire says a 24/7 SOC staffs response and DFIR responders share the eSentire Agent with MDR. | | [Expel](/services/expel/) | Expel says its Global Response Team leads critical incident investigations; SOC analysts, hunters and detection engineers form one 24x7 team. | | [Huntress](/services/huntress/) | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. | | [Kroll](/services/kroll/) | Kroll says the same DFIR team that conducts high-profile breach investigations extends remote DFIR to MDR customers. | | [Mandiant](/services/mandiant/) | Mandiant says frontline experts monitor the customer's technology and Mandiant Threat Defense prioritizes critical cases and leads rapid IR. | | [Microsoft](/services/microsoft/) | Microsoft says its experts run MDR; incident response for an active compromise is a separate Defender Experts service. | | [Rapid7](/services/rapid7/) | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. | | [Red Canary](/services/red-canary/) | Red Canary says in-house experts detect, respond and remediate; confirmed threats escalate to its Incident Handling Team. | | [SentinelOne](/services/sentinelone/) | SentinelOne says certified analysts investigate every alert and DFIR experts are available for critical incidents. | | [Sophos](/services/sophos/) | Sophos says its MDR is 24/7 with nine regional security operations teams; an Incident Response Advisor coordinates in MDR Plus. | | [Sygnia](/services/sygnia/) | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [What may the provider do without asking first?](/questions/q02/) ## Sources - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Deepwatch experts" page (the firm's own page): https://www.deepwatch.com/deepwatch-experts/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Meet the SOC experts" page (the firm's own page): https://expel.com/meet-the-soc-experts/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q01/ --- # What may the provider do without asking first: 16 of 16 providers publish an answer Question Sheet, question 2 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## What may the provider do without asking first? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Pre-approved actions decide whether a host is contained in minutes or after someone wakes up. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says threats are contained through Agentic SOC response with humans in the loop; its example used predefined customer instructions. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its endpoint service does automated blocking and threat containment; approval terms none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says response playbooks execute containment actions and analysts deliver full-cycle remediation on the customer's behalf. | | [Deepwatch](/services/deepwatch/) | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | | [eSentire](/services/esentire/) | eSentire says it performs host isolation, user suspension and TCP disruption on every incident, described as policy-bounded and reversible. | | [Expel](/services/expel/) | Expel says customers can let it press the respond button or choose what, how and when it acts. | | [Huntress](/services/huntress/) | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. | | [Kroll](/services/kroll/) | Kroll says on containment it will isolate endpoints, update WAFs and firewalls, and revoke access; pre-approval terms none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says experts can contain impacted hosts; with Technology Partner products, deeper actions include host containment and file acquisition. | | [Microsoft](/services/microsoft/) | Microsoft says experts act on the customer's behalf only if granted Security Operator access; otherwise actions stay pending. | | [Rapid7](/services/rapid7/) | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. | | [Red Canary](/services/red-canary/) | Red Canary says customers can keep human oversight on specific response actions or choose to automate. | | [SentinelOne](/services/sentinelone/) | SentinelOne says confirmed threats are contained per the configured response policy: processes killed, endpoints isolated, changes rolled back. | | [Sophos](/services/sophos/) | Sophos says the customer picks a Threat Response Mode: Authorize (pre-authorized, notified after) or Collaborate (written consent). | | [Sygnia](/services/sygnia/) | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Who watches the environment around the clock, and who handles a major incident?](/questions/q01/) - [Which data sources does the service monitor?](/questions/q03/) ## Sources - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Active response" page (the firm's own page): https://www.deepwatch.com/active-response/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Auto remediation" page (the firm's own page): https://expel.com/auto-remediation/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR managed response" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q02/ --- # Which data sources does the service monitor: 16 of 16 providers publish an answer Question Sheet, question 3 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Detection only works on the data the provider actually ingests. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## Which data sources does the service monitor? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Detection only works on the data the provider actually ingests. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says it covers all attack surfaces; IDC lists endpoint, network, cloud, identity and the human element. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR protects network, cloud, containers and endpoints; identity services appear in its Microsoft menu. | | [Critical Start](/services/critical-start/) | Critical Start says CORR supports 100+ integrations across seven security domains. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says analysts correlate endpoint, identity, AI agent, cloud, SaaS and third-party telemetry. | | [Deepwatch](/services/deepwatch/) | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | | [eSentire](/services/esentire/) | eSentire says Atlas ingests endpoint, network, log, cloud, identity, AI session and vulnerability signals. IDC places identity and cloud in a higher tier. | | [Expel](/services/expel/) | Expel says it unifies signals across ten attack surfaces including cloud, identity, SaaS, endpoints and networks. | | [Huntress](/services/huntress/) | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. | | [Kroll](/services/kroll/) | Kroll says clients get visibility across endpoint, identity, SIEM and cloud on its CrowdStrike foundation. | | [Mandiant](/services/mandiant/) | Mandiant says Threat Defense offers full-stack monitoring across endpoint, network and multicloud environments. | | [Microsoft](/services/microsoft/) | Microsoft says MDR protects endpoints, identities, email, cloud apps, cloud workloads and network infrastructure, Microsoft and third-party. | | [Rapid7](/services/rapid7/) | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. | | [Red Canary](/services/red-canary/) | Red Canary lists identity, endpoint, cloud, email and network, unifying AWS, GCP and Azure data. | | [SentinelOne](/services/sentinelone/) | SentinelOne says 24/7 monitoring runs across endpoints, cloud and identity, plus supported third-party integrations. | | [Sophos](/services/sophos/) | Sophos states endpoint, network, cloud, identity, email and business applications; OT is not mentioned. | | [Sygnia](/services/sygnia/) | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [What may the provider do without asking first?](/questions/q02/) - [Is the provider's own endpoint agent required?](/questions/q04/) ## Sources - Arctic Wolf, "Managed detection and response" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Deepwatch platform" page (the firm's own page): https://www.deepwatch.com/deepwatch-platform/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - Expel, "Detection coverage" page (the firm's own page): https://expel.com/detection-coverage/ (read 10 November 2026) - Huntress, "Platform" page (the firm's own page): https://www.huntress.com/platform (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Mandiant, "Mandiant incident response services" page (the firm's own page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) - Microsoft, "Microsoft defender experts MDR" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-mdr (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q03/ --- # Is the provider's own endpoint agent required: 16 of 16 providers publish an answer Question Sheet, question 4 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. A required agent means replacing or running next to the tools already in place. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## Is the provider's own endpoint agent required? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. A required agent means replacing or running next to the tools already in place. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its platform is compatible with other tools; its example used the Arctic Wolf Agent and whether it is required is not stated. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR is meant to strengthen existing tools; the Microsoft module is built around Microsoft Security technology. | | [Critical Start](/services/critical-start/) | Critical Start says it requires no proprietary agents and connects to existing stack by API. | | [CrowdStrike](/services/crowdstrike/) | IDC says Falcon Complete has endpoint at the core with practitioners controlling the Falcon agent; explicit requirement none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | | [eSentire](/services/esentire/) | eSentire says its MDR needs no stack replacement; its own eSentire Agent is offered as an option. | | [Expel](/services/expel/) | Expel says no agents need to be deployed and it plugs into the existing stack. | | [Huntress](/services/huntress/) | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR tools. | | [Kroll](/services/kroll/) | Kroll's 2025 and 2026 pages describe consolidating on CrowdStrike Falcon; an older page still says tech-agnostic. | | [Mandiant](/services/mandiant/) | Mandiant says it supports the customer's technology stack and lists supported EDR partners ingested via Google SecOps. | | [Microsoft](/services/microsoft/) | Plan 1 covers Microsoft Defender workloads; Plan 2 extends to listed third-party telemetry in Sentinel and requires Sentinel. | | [Rapid7](/services/rapid7/) | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. | | [Red Canary](/services/red-canary/) | Red Canary says it is available to organizations using Microsoft, CrowdStrike, Carbon Black, Palo Alto or SentinelOne as EDR. | | [SentinelOne](/services/sentinelone/) | SentinelOne says the service is built into the Singularity Platform; whether the agent is required none found on 10 Nov 2026. | | [Sophos](/services/sophos/) | Sophos says third-party endpoints can be covered agentless; MDR Complete needs the full Sophos XDR agent, per IDC. | | [Sygnia](/services/sygnia/) | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Which data sources does the service monitor?](/questions/q03/) - [Is threat hunting included, and what output is published?](/questions/q05/) ## Sources - Arctic Wolf, "Technology integrations" page (the firm's own page): https://arcticwolf.com/partners/technology-integrations/ (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "Why critical start" page (the firm's own page): https://www.criticalstart.com/why-critical-start (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Deepwatch, "Leverage existing tools" page (the firm's own page): https://www.deepwatch.com/use-existing-tools/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - Expel, "Managed detection response" page (the firm's own page): https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll MDR services migrate to crowdstrike falcon complete next gen MDR" page (the firm's own page): https://www.kroll.com/en/newsroom/kroll-mdr-services-migrate-to-crowdstrike-falcon-complete-next-gen-mdr (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Introducing red canary active threat remediation" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/introducing-red-canary-active-threat-remediation (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q04/ --- # Is threat hunting included, and what output is published: 16 of 16 providers publish an answer Question Sheet, question 5 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Hunting that produces no written findings is hard to check. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## Is threat hunting included, and what output is published? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Hunting that produces no written findings is hard to check. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf lists a Threat Hunting Agent in its Agentic SOC at no additional cost; no hunt reports published. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant's MDR for Endpoint page says proactive threat hunting is part of the service; no output published. | | [Critical Start](/services/critical-start/) | Critical Start says hunting engagements can be bought with service credits; it also describes continuous hunt-derived detections for all customers. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike publishes a 2026 Threat Hunting Report; its page does not state hunting is part of Falcon Complete. | | [Deepwatch](/services/deepwatch/) | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | | [eSentire](/services/esentire/) | eSentire says its MDR includes 24/7 Elite Threat Hunters; another page says 24/7 hunting is added at the Enhanced package. | | [Expel](/services/expel/) | Expel sells a Threat Hunting service with monthly hunts paired with MDR; findings and gaps are shared in a monthly report. | | [Huntress](/services/huntress/) | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat Report. | | [Kroll](/services/kroll/) | IDC says Kroll hunts weekly and publishes a monthly report showing hunting undertaken and output. | | [Mandiant](/services/mandiant/) | Mandiant says its hunters hunt continually and publishes Tales from the Trenches on attack and malware trends. | | [Microsoft](/services/microsoft/) | Microsoft says threat hunting is built in to both plans and customers receive interactive reports on each hunt. | | [Rapid7](/services/rapid7/) | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. | | [Red Canary](/services/red-canary/) | Red Canary says the service includes threat hunting and customers can view writeups of every hunt; it links a 2026 Threat Detection Report. | | [SentinelOne](/services/sentinelone/) | SentinelOne says Wayfinder TDR includes intelligence-led hunting; it publishes an Annual Threat Hunting Report 2024. | | [Sophos](/services/sophos/) | Sophos includes Threat Hunting in both tiers, limited to Sophos Fusion data; hunt report formats not described. | | [Sygnia](/services/sygnia/) | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Is the provider's own endpoint agent required?](/questions/q04/) - [Are incident response hours included, or is a retainer needed?](/questions/q06/) ## Sources - Arctic Wolf, "Aurora SOC" page (the firm's own page): https://arcticwolf.com/aurora-soc/ (read 10 November 2026) - BlueVoyant, "MDR for endpoint" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/detection-and-response/mdr-for-endpoint (read 10 November 2026) - Critical Start, "Service credits" page (the firm's own page): https://www.criticalstart.com/service-credits (read 10 November 2026) - CrowdStrike, "Threat hunting report" page (the firm's own page): https://www.crowdstrike.com/en-us/resources/reports/threat-hunting-report/ (read 10 November 2026) - Deepwatch, "Managed detection response service datasheet" page (the firm's own page): https://www.deepwatch.com/managed-detection-response-service-datasheet/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - Expel, "Threat hunting" page (the firm's own page): https://expel.com/services/threat-hunting/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Pricing" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/pricing/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Threat hunting" page (the firm's own page): https://www.sygnia.co/solutions/threat-hunting/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q05/ --- # Are incident response hours included, or is a retainer needed: 16 of 16 providers publish an answer Question Sheet, question 6 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. IR billed separately changes the cost of the worst week of the year. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## Are incident response hours included, or is a retainer needed? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. IR billed separately changes the cost of the worst week of the year. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf's retainer FAQ treats IR as separate from MDR; a warranty of up to 3 million dollars applies to a bundle. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR for Microsoft includes unlimited remote IR lifecycle support; its DFIR retainer is a separate page with pre-arranged SLAs. | | [Critical Start](/services/critical-start/) | Critical Start shows IR as an add-on to every MDR tier; unused retainer hours convert to credits at 3 hours per credit. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says Falcon Complete is backed by warranty coverage of up to $2 million; IR hours none found on 10 Nov 2026. | | [Deepwatch](/services/deepwatch/) | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | | [eSentire](/services/esentire/) | eSentire's Incident Response Retainer provides unlimited remote IR with a one-hour engage commitment; Elite MDR includes DFIR. | | [Expel](/services/expel/) | Expel lists a Global Response Team within MDR; no IR hours or retainer are stated. Packages cover incident escalations in the subscription. | | [Huntress](/services/huntress/) | Huntress says its price includes everything with no add-ons; included IR hours not stated. | | [Kroll](/services/kroll/) | Kroll says Responder MDR includes remote DFIR at no extra cost and a $1 million incident protection warranty. | | [Mandiant](/services/mandiant/) | Mandiant says attacks can be stopped without a formal IR engagement; included hours none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft presents incident response as a separate Defender Experts service under its own service terms. | | [Rapid7](/services/rapid7/) | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. | | [Red Canary](/services/red-canary/) | Red Canary states no included IR hours; an archived partner page says IR firms attach it to a 45-day engagement. | | [SentinelOne](/services/sentinelone/) | SentinelOne offers an IRR retainer of renewable expert hours, and a 40-hour on-demand DFIR block with no retainer required. | | [Sophos](/services/sophos/) | Sophos puts IR in MDR Plus with no caps; excludes disk forensics, on-site work and ransomware negotiation. | | [Sygnia](/services/sygnia/) | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are not stated. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Is threat hunting included, and what output is published?](/questions/q05/) - [What response-time commitments are published?](/questions/q07/) ## Sources - Arctic Wolf, "Incident response retainer" page (the firm's own page): https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) - BlueVoyant, "MDR for microsoft" page (the firm's own page): https://www.bluevoyant.com/cyber-defense-platform/managed-detection-and-response/mdr-for-microsoft (read 10 November 2026) - Critical Start, "Services" page (the firm's own page): https://www.criticalstart.com/services (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Ati" page (the firm's own page): https://www.deepwatch.com/ati/ (read 10 November 2026) - eSentire, "Incident response retainer" page (the firm's own page): https://www.esentire.com/what-we-do/digital-forensics-and-incident-response/incident-response-retainer (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - Red Canary, "Redcanary joining zscaler" page (the firm's own page): https://www.zscaler.com/blogs/product-insights/redcanary-joining-zscaler (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "Sygnia brings expert led managed 130000486" page (the firm's own page): https://finance.yahoo.com/technology/ai/articles/sygnia-brings-expert-led-managed-130000486.html (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q06/ --- # What response-time commitments are published: 12 of 16 providers publish an answer Question Sheet, question 7 of 15, read 10 November 2026 **In short.** 12 of sixteen MDR providers answer this in public pages read on 10 November 2026. A stated number with a credit is something a contract can enforce. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## What response-time commitments are published? 12 of sixteen MDR providers answer this in public pages read on 10 November 2026. A stated number with a credit is something a contract can enforce. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says its team contacts customers within minutes of a threat; it prints no minute-level SLA. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its DFIR retainer has pre-arranged response SLAs; MDR commitments none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | Critical Start publishes a 60-minute mean time to respond in all tiers, credits for misses, and a 15-minute emergency line callback. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike states a median time-to-contain of 1 minute, defined from detection to endpoint containment, results may vary. | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire publishes a mean time to engage a signal of 30 seconds and a one-hour engage under its IR retainer. | | [Expel](/services/expel/) | Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll cites a 10x reduction in mean time to respond; SLA minutes none found on 10 Nov 2026. | | [Mandiant](/services/mandiant/) | Mandiant says alerts are triaged and prioritized by an expert within minutes; no SLA printed. | | [Microsoft](/services/microsoft/) | Microsoft's overview prints no price or response-time commitment. | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | SentinelOne states a 4-hour SLA for initial expert response and 24 hours for preliminary findings (IR); MDR average detect 3.3 minutes. | | [Sophos](/services/sophos/) | Sophos commits MDR Plus to 60 minutes Time to Respond for 90 percent of priority investigations, with a service credit. | | [Sygnia](/services/sygnia/) | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Are incident response hours included, or is a retainer needed?](/questions/q06/) - [Is the pricing model published?](/questions/q08/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/company/faq/ (read 10 November 2026) - BlueVoyant, "Digital forensics incident response" page (the firm's own page): https://www.bluevoyant.com/solutions/digital-forensics-incident-response (read 10 November 2026) - Critical Start, "SLA commitment" page (the firm's own page): https://www.criticalstart.com/sla-commitment (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - eSentire, "Response and remediation" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) - Expel, "Security operations center SOC" page (the firm's own page): https://expel.com/security-operations-center-soc/ (read 10 November 2026) - Kroll, "Kroll responder" page (the firm's own page): https://www.kroll.com/en/services/cyber/kroll-responder (read 10 November 2026) - Mandiant, "Managed defense" page (the firm's own page): https://cloud.google.com/security/products/managed-defense (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - SentinelOne, "Incident readiness and response" page (the firm's own page): https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q07/ --- # Is the pricing model published: 11 of 16 providers publish an answer Question Sheet, question 8 of 15, read 10 November 2026 **In short.** 11 of sixteen MDR providers answer this in public pages read on 10 November 2026. Knowing what is priced (endpoints, users, data volume) tells you how the bill grows. Answers were found for Arctic Wolf, Critical Start, CrowdStrike, eSentire and others. The rest read none found, which means the question should go to the provider in writing. ## Is the pricing model published? 11 of sixteen MDR providers answer this in public pages read on 10 November 2026. Knowing what is priced (endpoints, users, data volume) tells you how the bill grows. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | Arctic Wolf says pricing is based on users, servers and network egress points, not event or log volume; no prices are printed. | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike's pricing page lists Falcon Complete as Contact sales; no model published. | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire says packages are priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. | | [Expel](/services/expel/) | Expel says pricing is by request, with Starter, Select and Premium packages. | | [Huntress](/services/huntress/) | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says the service is sold separately; Plan 2 requires a minimum of 1,500 seats; no price on the overview. | | [Rapid7](/services/rapid7/) | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | SentinelOne lists MDR as an add-on to Singularity plans with no price shown; three service levels are named. | | [Sophos](/services/sophos/) | Sophos says pricing is based on users and servers in two tiers (per IDC); no prices printed. | | [Sygnia](/services/sygnia/) | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [What response-time commitments are published?](/questions/q07/) - [Is OT covered?](/questions/q09/) ## Sources - Arctic Wolf, "FAQ" page (the firm's own page): https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Pricing" page (the firm's own page): https://www.crowdstrike.com/en-us/pricing/ (read 10 November 2026) - eSentire, "Pricing packaging" page (the firm's own page): https://www.esentire.com/pricing-packaging (read 10 November 2026) - Expel, "MDR packages" page (the firm's own page): https://expel.com/mdr-packages/ (read 10 November 2026) - Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - SentinelOne, "Pricing" page (the firm's own page): https://www.sentinelone.com/pricing/ (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Sygnia, "Prodview mjvsalxozaiuk" page (the firm's own page): https://aws.amazon.com/marketplace/pp/prodview-mjvsalxozaiuk (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q08/ --- # Is OT covered: 8 of 16 providers publish an answer Question Sheet, question 9 of 15, read 10 November 2026 **In short.** 8 of sixteen MDR providers answer this in public pages read on 10 November 2026. Plant and building systems often cannot run an agent and need different monitoring. Answers were found for Critical Start, eSentire, Expel, Kroll and others. The rest read none found, which means the question should go to the provider in writing. ## Is OT covered? 8 of sixteen MDR providers answer this in public pages read on 10 November 2026. Plant and building systems often cannot run an agent and need different monitoring. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | eSentire says its manufacturing MDR detects activity across IT and OT, with expertise in MES, ICS and SCADA. | | [Expel](/services/expel/) | Expel's site navigation lists OT among its coverage attack surfaces; service page detail none found on 10 Nov 2026. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll describes OT security monitoring as a separate service; IDC says it uses NDR for IoT or OT devices. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft's FAQ excludes IoT devices and does not mention OT. | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | An archived Red Canary manufacturing page states it protects OT and IT environments, framed from threat intelligence. | | [SentinelOne](/services/sentinelone/) | SentinelOne's navigation lists an OT industry page; the MDR page lists no OT coverage. | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 (Taegis MDR for Operational Technology is listed as a separate service). | | [Sygnia](/services/sygnia/) | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Is the pricing model published?](/questions/q08/) - [What cloud and identity coverage is stated?](/questions/q10/) ## Sources - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - eSentire, "Manufacturing cybersecurity" page (the firm's own page): https://www.esentire.com/how-we-do-it/industries/manufacturing-cybersecurity (read 10 November 2026) - Expel, home page (the firm's own page): https://expel.com/ (read 10 November 2026) - Kroll, "OT security" page (the firm's own page): https://www.kroll.com/en/services/cyber/cybersecurity-transformation/ot-security (read 10 November 2026) - Microsoft, "Defender experts MDR FAQ" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq (read 10 November 2026) - Red Canary, "Manufacturing services" page (the firm's own page): https://redcanary.com/solutions/industry/manufacturing-services/ (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "MDR description" page (the firm's own page): https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, "MDR datasheet 042026" page (the firm's own page): https://www.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q09/ --- # What cloud and identity coverage is stated: 16 of 16 providers publish an answer Question Sheet, question 10 of 15, read 10 November 2026 **In short.** 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Many intrusions now move through accounts and cloud consoles, not hosts. Answers were found for Arctic Wolf, BlueVoyant, Critical Start, CrowdStrike and others. The rest read none found, which means the question should go to the provider in writing. ## What cloud and identity coverage is stated? 16 of sixteen MDR providers answer this in public pages read on 10 November 2026. Many intrusions now move through accounts and cloud consoles, not hosts. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | IDC says Arctic Wolf aims for visibility across cloud and identity; Arctic Wolf says it covers all attack surfaces. | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its MDR protects cloud and containers, and lists Agentic Identity Services in its Microsoft menu. | | [Critical Start](/services/critical-start/) | Critical Start lists identity actions (reset password, disable account) and says cloud response is advisory and detection only. | | [CrowdStrike](/services/crowdstrike/) | CrowdStrike says it covers identities and cloud telemetry; IDC adds managed cloud workload and identity threat protection. | | [Deepwatch](/services/deepwatch/) | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | | [eSentire](/services/esentire/) | eSentire says Atlas ingests cloud and identity signals and supports correcting cloud misconfigurations. | | [Expel](/services/expel/) | Expel says coverage spans cloud workloads, control planes, identity and SaaS. | | [Huntress](/services/huntress/) | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. | | [Kroll](/services/kroll/) | Kroll says visibility spans identity and cloud; the Microsoft service lists revoking sessions. | | [Mandiant](/services/mandiant/) | Mandiant says monitoring spans multicloud environments; identity none found on 10 Nov 2026. | | [Microsoft](/services/microsoft/) | Microsoft says it covers identities and cloud apps; Defender for Cloud storage, containers and databases are not covered. | | [Rapid7](/services/rapid7/) | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. | | [Red Canary](/services/red-canary/) | Red Canary says it unifies AWS, GCP and Azure data and lists identity and cloud as key domains. | | [SentinelOne](/services/sentinelone/) | SentinelOne says its MDR page lists cloud and identity as core detection coverage. | | [Sophos](/services/sophos/) | Sophos states cloud and identity coverage, and Response Actions include disabling users and revoking sessions. | | [Sygnia](/services/sygnia/) | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Is OT covered?](/questions/q09/) - [How long does onboarding take?](/questions/q11/) ## Sources - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) - Critical Start, "MDR" page (the firm's own page): https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, "Falcon complete MDR" page (the firm's own page): https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Deepwatch, "Deepwatch platform" page (the firm's own page): https://www.deepwatch.com/deepwatch-platform/ (read 10 November 2026) - eSentire, "Esentire managed detection and response" page (the firm's own page): https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - Expel, "MDR packages" page (the firm's own page): https://expel.com/mdr-packages/ (read 10 November 2026) - Huntress, "Platform" page (the firm's own page): https://www.huntress.com/platform (read 10 November 2026) - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Mandiant, "Mandiant incident response services" page (the firm's own page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) - Microsoft, "Microsoft defender experts MDR" page (the firm's own page): https://www.microsoft.com/en-us/security/business/services/microsoft-defender-experts-mdr (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - SentinelOne, "Managed detection and response" page (the firm's own page): https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, "Managed detection and response" page (the firm's own page): https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q10/ --- # How long does onboarding take: 1 of 16 providers publish an answer Question Sheet, question 11 of 15, read 10 November 2026 **In short.** 1 of sixteen MDR providers answer this in public pages read on 10 November 2026. Time to full coverage is time exposed during the change. Answers were found for Kroll. The rest read none found, which means the question should go to the provider in writing. ## How long does onboarding take? 1 of sixteen MDR providers answer this in public pages read on 10 November 2026. Time to full coverage is time exposed during the change. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | None found on 10 Nov 2026 | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | Kroll says it migrated over 270 client environments in under eight months; per-client onboarding time none found. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | None found on 10 Nov 2026 | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [What cloud and identity coverage is stated?](/questions/q10/) - [What reporting does the customer receive?](/questions/q12/) ## Sources - Kroll, "Elevating global MDR with crowdstrike" page (the firm's own page): https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) - Sygnia, "Sygnia expands incident response and proactive security services to include managed extended detection and response service 301724165" page (the firm's own page): https://www.prnewswire.com/news-releases/sygnia-expands-incident-response-and-proactive-security-services-to-include-managed-extended-detection-and-response-service-301724165.html (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q11/ --- # What reporting does the customer receive: 8 of 16 providers publish an answer Question Sheet, question 12 of 15, read 10 November 2026 **In short.** 8 of sixteen MDR providers answer this in public pages read on 10 November 2026. Regular reports are how the security lead shows the board what was done. Answers were found for Critical Start, Deepwatch, Expel, Kroll and others. The rest read none found, which means the question should go to the provider in writing. ## What reporting does the customer receive? 8 of sixteen MDR providers answer this in public pages read on 10 November 2026. Regular reports are how the security lead shows the board what was done. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | Expel says customers see every alert, investigation and action in its Workbench platform. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | IDC says Kroll gives a monthly hunting report; Kroll lists weekly and out-of-band threat intelligence reports. | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [Rapid7](/services/rapid7/) | Rapid7 says every action in the SOC is logged, explainable and auditable. | | [Red Canary](/services/red-canary/) | Red Canary says reporting shows speed and accuracy of detection and response over time. | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [How long does onboarding take?](/questions/q11/) - [Where is customer data kept, and for how long?](/questions/q13/) ## Sources - Critical Start, "SLA commitment" page (the firm's own page): https://www.criticalstart.com/sla-commitment (read 10 November 2026) - Deepwatch, "Transparency and accountability" page (the firm's own page): https://www.deepwatch.com/transparency-and-accountability/ (read 10 November 2026) - Expel, "About" page (the firm's own page): https://expel.com/about/ (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Rapid7, "Managed detection and response MDR" page (the firm's own page): https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) - Red Canary, "Managed detection and response" page (the firm's own page): https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Sygnia, "Managed detection and response" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q12/ --- # Where is customer data kept, and for how long: 1 of 16 providers publish an answer Question Sheet, question 13 of 15, read 10 November 2026 **In short.** 1 of sixteen MDR providers answer this in public pages read on 10 November 2026. Retention and location decide legal and audit questions. Answers were found for BlueVoyant. The rest read none found, which means the question should go to the provider in writing. ## Where is customer data kept, and for how long? 1 of sixteen MDR providers answer this in public pages read on 10 November 2026. Retention and location decide legal and audit questions. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | BlueVoyant says its SOC monitoring is in-regional across Europe and the US; retention terms none found on 10 Nov 2026. | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | None found on 10 Nov 2026 | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | None found on 10 Nov 2026 | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [What reporting does the customer receive?](/questions/q12/) - [Can the customer's analysts see what the provider sees?](/questions/q14/) ## Sources - BlueVoyant, home page (the firm's own page): https://www.bluevoyant.com/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q13/ --- # Can the customer's analysts see what the provider sees: 5 of 16 providers publish an answer Question Sheet, question 14 of 15, read 10 November 2026 **In short.** 5 of sixteen MDR providers answer this in public pages read on 10 November 2026. Shared access lets your team check the work and take over an investigation. Answers were found for Deepwatch, Expel, Microsoft, Rapid7 and others. The rest read none found, which means the question should go to the provider in writing. ## Can the customer's analysts see what the provider sees? 5 of sixteen MDR providers answer this in public pages read on 10 November 2026. Shared access lets your team check the work and take over an investigation. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | Expel says customers see every alert, investigation and action in Workbench. | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | Microsoft says customers get live dashboards and reports of the work done on their behalf. | | [Rapid7](/services/rapid7/) | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. | | [Red Canary](/services/red-canary/) | IDC says Red Canary gives a per-threat portal page with a plain-language summary and timeline. | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Where is customer data kept, and for how long?](/questions/q13/) - [What are the exit and data-return terms?](/questions/q15/) ## Sources - Deepwatch, "Transparency and accountability" page (the firm's own page): https://www.deepwatch.com/transparency-and-accountability/ (read 10 November 2026) - Expel, "About" page (the firm's own page): https://expel.com/about/ (read 10 November 2026) - Microsoft, "Defender experts MDR overview" page (the firm's own page): https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - arcticwolf.com, "Idc marketscape worldwide managed detection and response 2024 vendor assessment": https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q14/ --- # What are the exit and data-return terms: 0 of 16 providers publish an answer Question Sheet, question 15 of 15, read 10 November 2026 **In short.** 0 of sixteen MDR providers answer this in public pages read on 10 November 2026. Leaving a provider is easier when data return is agreed before signing. The rest read none found, which means the question should go to the provider in writing. ## What are the exit and data-return terms? 0 of sixteen MDR providers answer this in public pages read on 10 November 2026. Leaving a provider is easier when data return is agreed before signing. | Service | Answer found | | --- | --- | | [Arctic Wolf](/services/arctic-wolf/) | None found on 10 Nov 2026 | | [BlueVoyant](/services/bluevoyant/) | None found on 10 Nov 2026 | | [Critical Start](/services/critical-start/) | None found on 10 Nov 2026 | | [CrowdStrike](/services/crowdstrike/) | None found on 10 Nov 2026 | | [Deepwatch](/services/deepwatch/) | None found on 10 Nov 2026 | | [eSentire](/services/esentire/) | None found on 10 Nov 2026 | | [Expel](/services/expel/) | None found on 10 Nov 2026 | | [Huntress](/services/huntress/) | None found on 10 Nov 2026 | | [Kroll](/services/kroll/) | None found on 10 Nov 2026 | | [Mandiant](/services/mandiant/) | None found on 10 Nov 2026 | | [Microsoft](/services/microsoft/) | None found on 10 Nov 2026 | | [Rapid7](/services/rapid7/) | None found on 10 Nov 2026 | | [Red Canary](/services/red-canary/) | None found on 10 Nov 2026 | | [SentinelOne](/services/sentinelone/) | None found on 10 Nov 2026 | | [Sophos](/services/sophos/) | None found on 10 Nov 2026 | | [Sygnia](/services/sygnia/) | None found on 10 Nov 2026 | Alphabetical. ## Related pages - [All fifteen questions](/questions/) - [The MDR Service Matrix](/matrix/) - [Five buyer situations](/situations/) - [Can the customer's analysts see what the provider sees?](/questions/q14/) ## Sources - MITRE ATT&CK Evaluations: https://evals.mitre.org/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/questions/q15/ --- # The matrix and the question sheet, as CSV and JSON Datasets, edition 10 November 2026 **In short.** Two datasets, edition 10 November 2026, under CC BY 4.0: the MDR Service Matrix (sixteen services, six actions and seven data sources each, with notes and fact references) and the MDR Question Sheet (fifteen questions, 240 answers found). Every row carries its source and read date. | Dataset | Rows | CSV | JSON | | --- | --- | --- | --- | | MDR Service Matrix | 16 | [mdr-service-matrix.csv](/datasets/mdr-service-matrix.csv) | [mdr-service-matrix.json](/datasets/mdr-service-matrix.json) | | MDR Question Sheet | 240 | [mdr-question-sheet.csv](/datasets/mdr-question-sheet.csv) | [mdr-question-sheet.json](/datasets/mdr-question-sheet.json) | ## Cite this MDR vs MSSP, "MDR Service Matrix and MDR Question Sheet", edition 10 November 2026, https://mdrvsmssp.com/datasets/ (CC BY 4.0). ## Related pages - [How the matrix was read](/matrix/method/) - [Guides](/guides/) - [Glossary](/glossary/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/datasets/ --- # 9 guides for running an MDR selection, and three explainers Guides, read 10 November 2026 **In short.** 9 guides for a team choosing a managed detection and response service: the six kinds of service, authority to act, the first 30 days, contract checks, pricing, the handoff to incident response, OT, measurement and reference calls. Three explainers set MDR beside MSSP, XDR and a SOC. - [Kinds of managed detection service](/guides/kinds-of-managed-detection/): Six kinds of service sell under similar names: managed EDR, MDR on the provider's own platform, MDR over your tools, co-managed SIEM, MSSP monitoring and MDR with incident response attached. - [Authority to act in an MDR service](/guides/authority-to-act/): Authority to act decides whether an MDR analyst can isolate a host or disable an account at 3 a.m. or must wait for your call. - [The first 30 days of an MDR service](/guides/first-30-days/): The first month decides whether the service works. - [What to check in an MDR contract](/guides/contract-checks/): Marketing pages promise speed and coverage. - [How MDR is priced](/guides/how-mdr-is-priced/): Published MDR pricing falls into four patterns: by endpoint, by user and server, by asset, and by quote. - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/): An MDR analyst can usually stop a threat on the endpoints it sees. - [MDR for OT and industrial networks](/guides/mdr-for-ot/): Industrial networks run controllers that cannot take agents and must not be interrupted. - [Measuring an MDR service after go-live](/guides/measuring-mdr/): After go-live, a monthly review of five measures keeps the service honest: coverage, time to first action, closed-alert quality, escalation quality and change handling. - [Questions to ask in an MDR reference call](/guides/reference-calls/): Providers publish customer statements, and a published statement is not a reference call. ## Explainers - [MDR vs MSSP: who takes the next step after an alert](/mdr-vs-mssp/) - [MDR vs XDR: a service against a platform](/mdr-vs-xdr/) - [MDR vs SOC: renting a team against building one](/mdr-vs-soc/) ## News - [12 dated news items](/news/) ## Related pages - [Home: MDR vs MSSP in short](/) - [The MDR Service Matrix](/matrix/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [How this site lists services](/method/) - [Glossary](/glossary/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/ --- # Managed detection comes in six kinds, and each kind hands a different job to your team Guide, read 10 November 2026 **The short answer.** Six kinds of service sell under similar names: managed EDR, MDR on the provider's own platform, MDR over your tools, co-managed SIEM, MSSP monitoring and MDR with incident response attached. They differ in who holds the tools, who acts and who pays for a breach. This guide describes each with published examples. ## What are the six kinds of MDR service? The label on the proposal rarely tells you what you are buying. Six patterns recur. They differ on three points: who owns the tooling and the data, who is allowed to act, and whether a breach is part of the price. Examples below are statements by the providers, read on 10 Nov 2026, and they are listed alphabetically within each kind. They illustrate a kind and do not compare providers. ## Managed EDR A provider watches the alerts from endpoint software and investigates them. The scope is the laptop and the server, and little else. Huntress, for instance, publishes $8.99 per endpoint per month for Managed EDR and says its human-led SOC investigates and acts on suspicious activity. This fits a team whose main exposure is endpoints and that wants a human behind the alert queue. Identity, cloud and email sit outside it unless you add products. ## MDR on the provider's own platform The provider ships its agent and console, and its analysts work inside them. Arctic Wolf describes an open XDR architecture with over 200 integrations on its platform, and its published ransomware example shows an endpoint contained through the Arctic Wolf Agent under predefined customer instructions. CrowdStrike states a median time to contain of 1 minute for Falcon Complete and defines that figure as the time from initial detection to successful containment on an endpoint, with results that may vary. You gain one throat to ask. You give up the ability to swap the tooling without swapping the service. ## MDR over your tools The provider's analysts work in products you already own. Expel says no agents are needed and that it plugs into an existing security stack. Microsoft's Defender Experts works on Microsoft Defender workloads, with response guidance for supported third-party products on Plan 2. Sophos says its service includes 500+ integrations. The strength is that your history stays in your tools. The cost is that detections depend on how well your tools are configured, and a gap in your logging becomes a gap in the service. ## Co-managed SIEM You own the SIEM, or a managed one, and the provider's analysts work its alerts with your team. Deepwatch says it connects to the customer's existing SIEM, EDR, cloud, identity and SaaS tools, and added Securonix support in a February 2026 release. Huntress describes a Managed SIEM that connects activity across endpoints, identities, networks and cloud services. The arrangement keeps the data under your control and the cost under the data volume, so agree the retention period first; the UK NCSC says to store your most important logs for at least 6 months. ## MSSP monitoring A provider watches logs and devices and forwards validated alerts. CrowdStrike describes this kind as broad monitoring plus technology management, upgrades, compliance and vulnerability management, and says MSSPs generally do not actively respond to threats, which leaves the customer to do that (vendor's description). It suits a team that wants to hand over device management and keep the investigation in-house. Confirm in writing who investigates. ## MDR with incident response attached Some services bundle forensics and breach response. Kroll says its Responder MDR includes remote digital forensics and incident response at no extra cost, plus a $1 million incident protection warranty for qualifying clients. Sophos says critical incident response is included with no caps or additional fees. Sygnia's August 2026 release says every Sygnia MDR engagement includes an incident response retainer. Arctic Wolf's retainer FAQ distinguishes MDR from incident response, which indicates it sells them separately. Ask what counts as critical, how many hours are included and who may start the clock. ## Choosing between kinds Write down which job you cannot staff: night triage, containment, forensics or device management. Then choose the kind that hands over that job and read its authority clause. A kind is a starting point, and the contract is what you buy. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [Authority to act in an MDR service](/guides/authority-to-act/) - [The first 30 days of an MDR service](/guides/first-30-days/) ## 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) - NCSC, 10 Steps: Logging and monitoring: https://www.ncsc.gov.uk/collection/10-steps/logging-and-monitoring (read 10 November 2026) - Huntress, pricing page: https://www.huntress.com/pricing (read 10 November 2026) - Huntress, Managed EDR page: https://www.huntress.com/platform/managed-edr (read 10 November 2026) - Arctic Wolf, MDR page: https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Arctic Wolf, ransomware containment timeline: https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) - CrowdStrike, Falcon Complete page: https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Expel, MDR service page: https://expel.com/services/managed-detection-response/ (read 10 November 2026) - Microsoft, Defender Experts MDR overview: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Deepwatch, home page: https://www.deepwatch.com/ (read 10 November 2026) - Deepwatch, press releases: https://www.deepwatch.com/press-release/ (read 10 November 2026) - Huntress, Managed SIEM page: https://www.huntress.com/platform/siem (read 10 November 2026) - Kroll, incident protection warranty: https://www.kroll.com/en/services/cyber/kroll-responder/incident-protection-warranty (read 10 November 2026) - Sygnia, August 2026 AWS Marketplace release: https://finance.yahoo.com/technology/ai/articles/sygnia-brings-expert-led-managed-130000486.html (read 10 November 2026) - Arctic Wolf, incident response retainer: https://arcticwolf.com/solutions/incident-response-retainer/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/kinds-of-managed-detection/ --- # Authority to act is the list of actions the provider may take without calling you, and you set it in writing Guide, read 10 November 2026 **The short answer.** Authority to act decides whether an MDR analyst can isolate a host or disable an account at 3 a.m. or must wait for your call. Published services range from automatic action to approval to monitor-only. This guide shows how to set it by asset class, test it and review it. ## What does authority to act mean in an MDR service? Authority to act is permission, given in advance, for named actions on named systems. Without it, an analyst who finds ransomware at 3 a.m. phones your on-call engineer and waits. With it, the analyst isolates the host and then phones. The phrase covers three parts: the action, the target and the condition. Providers publish their action lists. Critical Start lists endpoint actions as isolate host, block file hash and forensic capture, and identity actions as reset password, disable account and re-initiate MFA. Deepwatch lists session revocation, password reset and account control for identity, and process termination and host isolation for endpoints. Microsoft lists isolate device, quarantine file, restrict app execution, release from isolation, remove app restriction and disable user. These are the providers' own lists, read on 10 Nov 2026. ## The three modes providers describe Published pages describe three modes. In automatic mode the provider acts and tells you. In approval mode it asks first. In monitor-only mode it alerts and does not act. Deepwatch says its Active Response is opt-in and that actions run automatically, with analyst approval or in monitor-only mode, as set by the customer. Red Canary says customers can keep human oversight on specific response actions or choose to automate. Expel says customers can let it press the respond button or choose what, how and when it acts. Microsoft ties the mode to a permission setting. Its page says experts act on the customer's behalf only if granted Security Operator access; with the default Security Reader access, actions are left as pending for the customer. A service can therefore be bought as managed response and run, by default, as advice. ## How to set it Build a small matrix. Rows are asset classes: laptops, servers, domain controllers, executive accounts, production systems. Columns are actions: isolate host, kill process, disable account, block address, revoke sessions. Each cell holds one word: automatic, ask first or never. Start where the damage from waiting is high and the damage from acting is low. Isolating a laptop is reversible in minutes. Disabling a service account can stop an invoice run. Isolating a database server can stop a shop. eSentire describes its response as policy-bounded and reversible, which is the standard to ask of any provider: every automatic action needs an undo you can name. - Laptops: isolate and disable the user automatically; notify at once. - Servers: isolate automatically only outside business hours; otherwise ask first. - Domain controllers and identity systems: ask first, with a named approver and a back-up. - Production and OT systems: never automatic; advice and escalation only. - Executive accounts: disable the session, ask before password reset. ## Writing it into the contract Put the matrix in an appendix and refer to it from the service description. Name who may change it, by what route and how fast the provider must apply a change. Ask for a log of every action taken: time, target, analyst, reason. Critical Start says its analysts run the customer-approved playbook and that notice ahead of action is available if the customer prefers, which is an example of authority written as a playbook and not as a promise. Include a stop word. If your team calls a halt during an incident, the provider must stop automatic actions at once. ## Testing and review Test within the first two weeks. Create a harmless alert on a test laptop and watch what happens: who is called, which action is taken, how long it takes, and whether the undo works. Repeat the test whenever you change tools or staff. Review the matrix every quarter, and after any incident, against what the provider actually did. If the provider acted outside the matrix or waited when it should have acted, fix the paper first and the people second. Account actions deserve particular care because stolen credentials are a common route in. MITRE ATT&CK describes adversaries obtaining and abusing credentials of existing accounts for initial access, persistence, privilege escalation or defense evasion (technique T1078). Disabling an account is often the fastest way to stop that. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [Kinds of managed detection service](/guides/kinds-of-managed-detection/) - [The first 30 days of an MDR service](/guides/first-30-days/) - [What to check in an MDR contract](/guides/contract-checks/) ## Sources - MITRE ATT&CK, T1078 Valid Accounts: https://attack.mitre.org/techniques/T1078/ (read 10 November 2026) - Critical Start, MDR page: https://www.criticalstart.com/mdr (read 10 November 2026) - Deepwatch, Active Response: https://www.deepwatch.com/active-response/ (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) - Red Canary (Zscaler), MDR page: https://www.zscaler.com/products-and-solutions/managed-detection-and-response (read 10 November 2026) - Expel, auto remediation: https://expel.com/auto-remediation/ (read 10 November 2026) - eSentire, response and remediation: https://www.esentire.com/what-we-do/esentire-managed-detection-and-response/response-and-remediation (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/authority-to-act/ --- # The first 30 days should end with every in-scope source reporting, a signed authority matrix and one tested escalation Guide, read 10 November 2026 **The short answer.** The first month decides whether the service works. Week one covers contacts, access and the authority matrix. Week two covers data sources. Week three covers tuning. Week four covers a live test and review. This guide gives a day-by-day plan with published reference points on onboarding and log retention. ## Week one: people and permissions Name two contacts on your side for each shift, with phone numbers that ring. Give the provider a list of critical systems, a map of the network and a note of anything fragile. Agree the channel for urgent calls and the channel for routine tickets, and test both before the end of day three. Set the authority matrix now, not after the first alert. The guide on authority to act on this site covers it. If the service runs in Microsoft's Defender Experts, check which access level you granted, because the page read on 10 Nov 2026 says experts act only with Security Operator access. ## Week two: data sources The UK NCSC describes onboarding as adding systems to the scope of a SOC so that their logs are collected and monitored, and says onboarding is never complete because no IT estate stays the same. Treat it that way: keep a list of sources with three columns: connected, verified and owner. Verified means a test event was seen by the provider, not that a connector shows green. Check endpoint agents, identity logs, email, cloud audit logs and firewall logs in that order. Decide log retention at the same time. NCSC says it can be months before incidents are detected, and recommends storing your most important logs for at least 6 months. Ask where the provider holds your data and for how long. - Endpoint agents: percent of assets reporting, by group. - Identity: sign-in and admin-change logs. - Email and cloud audit logs. - Network and firewall logs, if in scope. - Anything excluded, written down with the reason. ## Week three: tuning Expect noise at the start. NIST's glossary defines a false positive as incorrectly classifying benign activity as malicious. Each week, review every alert the provider closed as benign and every one it escalated. Agree exclusions in writing, with an owner and a review date, so a quiet console does not hide a blind spot. Ask the provider whether it runs new detections against stored history on deployment. IDC says Kroll runs new detections against 30 to 90 days of historical client SIEM and EDR data on deployment. Whether another provider does the same is a fair question to put to each, not an assumption. ## Week four: a live test and a review Run a controlled test. Many providers publish targets you can measure. Sophos lists service level targets of 2 minutes to create a case and 30 minutes from case creation to first outreach, evidence collection or response action, and says these are targets. Time your own test against whatever your contract says, with the clock start written down. Hold a review at day 30 with the provider's lead analyst. Bring the source list, the closed-alert review, the test result and any action taken outside the matrix. Leave with a dated list of changes. ## What does done look like after 30 days of MDR? By day 30, every in-scope source reports and is verified. The authority matrix is signed. A test alert reached the right person within the contracted time, and the undo for an automatic action was tried. The exclusions list is short and owned. If any item is missing, ask for an extension in writing before the first invoice for the steady-state service. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [Kinds of managed detection service](/guides/kinds-of-managed-detection/) - [Authority to act in an MDR service](/guides/authority-to-act/) - [What to check in an MDR contract](/guides/contract-checks/) - [How MDR is priced](/guides/how-mdr-is-priced/) ## Sources - NCSC, Onboarding systems and log sources: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre/onboarding-systems-and-log-sources (read 10 November 2026) - NCSC, 10 Steps: Logging and monitoring: https://www.ncsc.gov.uk/collection/10-steps/logging-and-monitoring (read 10 November 2026) - NIST CSRC glossary, false positive: https://csrc.nist.gov/glossary/term/false_positive (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) - IDC MarketScape MDR 2024 (copy hosted by Arctic Wolf): https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Sophos, MDR service description: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/first-30-days/ --- # An MDR contract should name the actions, the clocks, the data and the exit, and anything vague costs you at 3 a.m. Guide, read 10 November 2026 **The short answer.** Marketing pages promise speed and coverage. The contract sets what you can enforce. This guide lists eight checks: scope, named actions, time commitments with start points, remedies, incident response hours, warranties, data and exit, and product change. It uses published service terms as reference points, listed alphabetically. ## What should an MDR service contract name as in scope? List the assets and sources in scope by name or by count, and list what is excluded. Microsoft's overview, for example, says Defender Experts MDR covers High and Medium severity incidents on Windows, Linux and macOS devices and excludes IoT, iOS and Android. A scope sentence like that is what you want to read before signing, not after an incident. Then list the actions the provider may take, using the matrix from the authority guide. Sophos says confirmed threats are fully contained and removed with no limits or extra fees; the page lists no individual actions such as isolate or disable account. If a page speaks in outcomes, ask for the actions in the contract. ## Time commitments and what starts the clock CrowdStrike's page defines its median time to contain as the time from initial detection to successful containment on an endpoint, and says results may vary. Sophos separates an SLA, a time to respond within 60 minutes for 90 percent of priority investigations for MDR Plus customers, from service level targets of 2 minutes to create a case and 30 minutes to first action. Critical Start publishes a 60-minute mean time to respond in all three tiers. Three different constructions, all legitimate. Your job is to know which one you hold: a commitment or a target, a mean or a percentile, and a clock that starts at detection, at case creation or at analyst assignment. - Is each figure a commitment with a remedy, or a target? - Mean, median or percentile, and over what period? - Where does the clock start and stop? - Does it apply to all severities or only to critical and high? ## Remedies, credits and caps A commitment without a remedy is a hope. Critical Start publishes service credits of 10 percent for a missed per-alert time, 10 percent for a missed monthly mean time to respond, and 50 percent for uptime below 98 percent. Sophos sets the credit for a missed SLA at the lesser of 5 percent of fees for the previous billing cycle or 5,000 US dollars. Compare the formula, the cap and the claim process, and ask whether repeated misses give you a right to leave. ## Incident response and warranties Ask whether response hours are included, capped or billed. Rapid7's pricing FAQ says its pricing is not tied to incident response hours. SentinelOne describes a retainer as a renewable pool of expert hours consumed across readiness, assessments and response. Some services also carry warranties. CrowdStrike states warranty coverage of up to $2 million for Falcon Complete. Kroll states a $1 million incident protection warranty for qualifying clients with endpoint protection. SentinelOne offers up to a $1 million breach response warranty. These are provider statements, read on 10 Nov 2026, listed alphabetically. For any warranty, ask for the document and read the conditions: who qualifies, what costs it covers, what is excluded, and who decides. ## Data, subprocessors and exit State where your telemetry is stored, for how long and who can read it. NCSC says to store your most important logs for at least 6 months, so a retention period shorter than that needs a copy under your control. List subprocessors and require notice of changes. Write the exit: export of cases and detections in a usable format, deletion on a date, and agent removal. Check what happens if the provider changes its product. Kroll's August 2026 case study says its previous MDR model required detection engineering across five EDR and three SIEM platforms and that it consolidated to CrowdStrike Falcon. SentinelOne's current pages name Wayfinder MDR, and the former Vigilance MDR address returns a 404 page. Platform changes and renames happen, so add a clause: material changes to the platform or ownership give you notice and a right to terminate. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [Authority to act in an MDR service](/guides/authority-to-act/) - [The first 30 days of an MDR service](/guides/first-30-days/) - [How MDR is priced](/guides/how-mdr-is-priced/) - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/) ## Sources - NCSC, 10 Steps: Logging and monitoring: https://www.ncsc.gov.uk/collection/10-steps/logging-and-monitoring (read 10 November 2026) - Microsoft, Defender Experts MDR FAQ: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - CrowdStrike, Falcon Complete page: https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - Sophos, MDR service description: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Critical Start, SLA page: https://www.criticalstart.com/sla-commitment (read 10 November 2026) - Rapid7, MDR FAQ: https://www.rapid7.com/services/managed-detection-and-response-mdr/#faq (read 10 November 2026) - SentinelOne, incident readiness and response: https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) - SentinelOne, MDR page: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Kroll, incident protection warranty: https://www.kroll.com/en/services/cyber/kroll-responder/incident-protection-warranty (read 10 November 2026) - Kroll, August 2026 case study: https://www.kroll.com/en/publications/cyber/case-studies/elevating-global-mdr-with-crowdstrike (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/contract-checks/ --- # MDR is priced by endpoints, users, assets or a negotiated package, and most providers publish no dollar figure Guide, read 10 November 2026 **The short answer.** Published MDR pricing falls into four patterns: by endpoint, by user and server, by asset, and by quote. Only a few providers print a figure. This guide lists what each provider has published as of 10 Nov 2026, alphabetically, with no comparison of cost, and shows what to put in a quote request. ## What have MDR providers published on price? This is a list of published facts, read on 10 Nov 2026, in alphabetical order. It is not a price comparison, and the units differ, so the figures cannot be set side by side. - Arctic Wolf: coverage is based on the number of users, servers and internet egress points, not event or log volume; no prices printed. - Critical Start: pricing is not published and varies by environment, integration scope and engagement level. - CrowdStrike: the pricing page lists Falcon Complete with Contact sales and no price. - eSentire: three packages (Professional, Enhanced, Elite) priced by endpoints, third-party technology, service engagement and add-ons; prices sit on an online shop. - Expel: pricing by request, with Starter, Select and Premium packages. - Huntress: $8.99 per endpoint per month for Managed EDR and $4.80 per licensed identity per month for Managed ITDR, with volume pricing on request. - Rapid7: asset-based, by endpoints, servers and networks protected, not by SIEM data volume or incident count; three named packages, no dollar prices on the page read. - ReliaQuest: GreyMatter prices by endpoint count with no AI usage meter; no dollar figures on the page read. - SentinelOne: Managed Detection and Response appears as an add-on row on its pricing page with no price shown. - Sophos: IDC says pricing is based on the number of users and servers; the MDR page prints no prices. - Sygnia: the AWS Marketplace listing shows one 12-month contract dimension at $1.00 per unit and does not define the unit; scope and quantity are agreed with the vendor. ## The four patterns Per endpoint is the simplest to model: count agents and multiply. Per user and server tracks headcount and is easy to budget but can climb with hiring. Per asset, as Rapid7 states, ties price to what is protected and not to log volume, which removes a data-growth surprise. By quote hides the unit until late in the process. Rapid7 and Arctic Wolf both state that price is not driven by log or event volume. That matters if you run a chatty SIEM, because volume-based pricing grows with your data. Ask each provider for the unit, the minimum and the rate at which you pay for a change. ## What drives the number Quotes move with five things. Count of assets or users. Breadth of sources, since eSentire says its packages are priced by endpoints, third-party technology, service engagement and add-ons. Response scope, such as active response and remote containment. Incident response hours, either included or billed. Contract term and payment terms. A marketplace listing can change the shape. Sygnia's AWS Marketplace listing says pricing is based on the duration and terms of the contract and that the buyer buys a specified quantity of use for the contract duration. Read the unit definition before you read the price. ## A quote request that gets comparable answers Send every provider the same sheet: endpoint count by operating system, server count, identity count, cloud accounts, log sources, locations and hours you cover yourselves. Ask for a price for the same scope at one-year and three-year terms, and a price for adding 10 percent more assets. Ask what is not in the price. Huntress says every product is fully managed by its 24/7 human SOC with no add-ons or service tiers. Others describe tiers. Whatever the model, get the list of exclusions and the price of each add-on in writing. Finally, ask for the renewal rule. A multi-year price with an uncapped renewal increase is not a price. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [The first 30 days of an MDR service](/guides/first-30-days/) - [What to check in an MDR contract](/guides/contract-checks/) - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/) - [MDR for OT and industrial networks](/guides/mdr-for-ot/) ## Sources - Arctic Wolf, MDR FAQ: https://arcticwolf.com/solutions/managed-detection-and-response/faq/ (read 10 November 2026) - Critical Start, MDR page: https://www.criticalstart.com/mdr (read 10 November 2026) - CrowdStrike, pricing page: https://www.crowdstrike.com/en-us/pricing/ (read 10 November 2026) - eSentire, pricing and packaging: https://www.esentire.com/pricing-packaging (read 10 November 2026) - eSentire, MDR page: https://www.esentire.com/what-we-do/esentire-managed-detection-and-response (read 10 November 2026) - Expel, MDR packages: https://expel.com/mdr-packages/ (read 10 November 2026) - Huntress, pricing page: https://www.huntress.com/pricing (read 10 November 2026) - Rapid7, MDR pricing: https://www.rapid7.com/services/managed-detection-and-response-mdr/pricing/ (read 10 November 2026) - ReliaQuest, GreyMatter pricing brief: https://reliaquest.com/solution-briefs/greymatter-ai-pricing/ (read 10 November 2026) - SentinelOne, pricing page: https://www.sentinelone.com/pricing/ (read 10 November 2026) - IDC MarketScape MDR 2024 (copy hosted by Arctic Wolf): https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - AWS Marketplace, Sygnia MDR listing: https://aws.amazon.com/marketplace/pp/prodview-mjvsalxozaiuk (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/how-mdr-is-priced/ --- # 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/ --- # Most MDR services watch IT first; OT coverage is a separate scope that you must find in the written terms Guide, read 10 November 2026 **The short answer.** Industrial networks run controllers that cannot take agents and must not be interrupted. Providers describe OT coverage in different ways: native, through partner sensors, as a separate service or not at all. This guide lists published statements, alphabetically, and the questions that expose where the scope stops. ## Why does OT differ for MDR services? Industrial control systems (ICS) and operational technology (OT) run physical processes. CISA's ICS page says they are the foundation of U.S. critical infrastructure, in sectors including energy, water, transportation and manufacturing. Controllers often cannot run an agent, patching waits for a shutdown window, and a wrong response action can stop production. MITRE publishes a separate ATT&CK matrix for ICS, which is a sign that adversary behavior against these systems differs from enterprise IT. CISA's page, read on 10 Nov 2026, also lists advisory AA26-231A, which warns that threat actors are targeting Siemens S7 Series programmable logic controllers. ## What providers publish Statements below are the providers', read on 10 Nov 2026, in alphabetical order. They describe scope and are not a comparison. - Critical Start: lists OT/ICS as escalation, advisory and read-only monitoring, with integrations including Microsoft Defender for IoT, Claroty xDome and Nozomi Networks. - eSentire: says its manufacturing MDR is built to detect malicious administrative activity before threats move from IT systems to OT controllers. - Kroll: its OT Security page describes 24/7 OT monitoring as a separate service; no statement that OT is part of Responder MDR was found on 10 Nov 2026. IDC says Kroll uses NDR, partnered with Darktrace, for IoT or OT devices where EDR agents cannot be deployed. - Microsoft: the Defender Experts FAQ says coverage includes High and Medium severity incidents on Windows, Linux and macOS and excludes IoT; no OT mention found on 10 Nov 2026. - ReliaQuest: says GreyMatter integrates OT technologies such as Armis, Dragos and Nozomi and correlates IT and OT sources including firewalls and PLC logs. - Sophos: no OT mention found on the MDR page on 10 Nov 2026, and its service description lists Taegis MDR for Operational Technology as a separate service. - Sygnia: says its platform ingests endpoint, cloud, network and application data for visibility across IT, OT and hybrid cloud, including legacy OT systems. ## Reading the scope The same word, OT, covers several arrangements. Monitoring only means sensors watch traffic and alert; nothing is blocked. Advisory means the analyst tells you what to do. Response means the provider acts. Critical Start's wording, escalation, advisory and read-only monitoring, is a clear example of the first two. When a page does not state a mode, ask for it. Also ask what the sensors are. Some services rely on a partner's OT monitoring product; others on network sensors they deploy. Find out who owns the sensor, who is on the hook if it fails and whether the data leaves the plant. ## Questions for an OT scope Bring the plant engineer to the call. IT analysts and plant engineers disagree on what is safe, and the provider should hear both. - Which protocols and device types are parsed, and which are not? - Is any response action allowed on OT assets, and who approves it? - What happens at the IT and OT boundary, and who owns the firewall rules? - Who is called at a plant at 2 a.m., and do they know the process? - How are legacy systems covered, and what is the evidence? - Which of the questions in CISA's third-party ICS integrator fact sheet apply to this provider? ## A staged approach Start with visibility: passive monitoring of the IT and OT boundary and of remote access paths. Add asset inventory. Then write response rules for each zone, with production systems set to advice only. CISA's ICS page lists role-specific guidance for asset owners and operators and a fact sheet from CISA and the FBI with questions and considerations for working with third-party ICS integrators. Use both in your provider conversations. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [How MDR is priced](/guides/how-mdr-is-priced/) - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/) - [Measuring an MDR service after go-live](/guides/measuring-mdr/) - [Questions to ask in an MDR reference call](/guides/reference-calls/) ## Sources - CISA, industrial control systems: https://www.cisa.gov/topics/industrial-control-systems (read 10 November 2026) - MITRE ATT&CK, ICS matrix: https://attack.mitre.org/matrices/ics/ (read 10 November 2026) - Critical Start, MDR page: https://www.criticalstart.com/mdr (read 10 November 2026) - eSentire, manufacturing cybersecurity: https://www.esentire.com/how-we-do-it/industries/manufacturing-cybersecurity (read 10 November 2026) - Kroll, OT security: https://www.kroll.com/en/services/cyber/cybersecurity-transformation/ot-security (read 10 November 2026) - IDC MarketScape MDR 2024 (copy hosted by Arctic Wolf): https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Microsoft, Defender Experts MDR FAQ: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-faq (read 10 November 2026) - ReliaQuest, securing operational technology: https://reliaquest.com/solutions/securing-operational-technology/ (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - Sophos, MDR service description: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) - Sygnia, MDR datasheet: https://cdn.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/mdr-for-ot/ --- # Measure an MDR service by what it did, how fast and what it missed, using definitions you fixed in advance Guide, read 10 November 2026 **The short answer.** After go-live, a monthly review of five measures keeps the service honest: coverage, time to first action, closed-alert quality, escalation quality and change handling. Providers publish figures with different definitions, so this guide shows how to build your own comparison from your own cases, with published examples. ## Why do published MDR figures not transfer? Providers publish speed figures, but each defines its figure its own way. Expel publishes 5 minutes mean time to detect, 13 minutes to respond on high severity and 14 minutes to remediate. SentinelOne says Wayfinder MDR mean time to detect averages 3.3 minutes across customer environments. Sophos cites an average of 89 seconds from alert to automated response where AI can act alone. CrowdStrike states a median time to contain of 1 minute, with a footnote defining it from detection to containment on an endpoint. ReliaQuest says GreyMatter contains threats in under 5 minutes. These are statements by the providers, read on 10 Nov 2026, and listed alphabetically. They differ in statistic (mean, median, average), in the start point and in the case mix. Do not set one beside another. Measure your own cases instead. ## Five measures that work Choose measures you can compute from the provider's case export and your own records. - Coverage: percent of assets and log sources reporting, checked weekly against your inventory. - Time to first action: from the alert time in your tool to the first analyst note or action on your case, by severity. - Closed-alert quality: sample ten alerts closed as benign each month and check them yourself. NIST's glossary defines a false positive as incorrectly classifying benign activity as malicious; the sample tells you whether closures were right. - Escalation quality: for each escalation, was the context enough to act, was the recommendation correct, and was anything repeated? - Change handling: days from your request to a detection change, exclusion or new source being live. ## Resolved without you is not the same as resolved well Sygnia states that it resolves 95% of alerts without involving the client's team. A figure like that tells you the share handled by the provider, not whether the handling was right. Pair any such number with the sampling check above. A low escalation count may mean a quiet month or a blind spot; the sample tells you which. Track the reverse as well: alerts you found yourself that the provider did not. Keep a log of every finding from your own tools, scanners and staff, and ask the provider each time why the service did not raise it. ## Mapping to ATT&CK MITRE's ATT&CK is a knowledge base of adversary tactics and techniques. Ask the provider to show which techniques its detections cover for your sources, and compare that with the techniques most relevant to your sector. Treat the map as a coverage question and not as a quality grade: a technique with a rule is not a technique that is always caught. MITRE's ATT&CK Evaluations has a Managed Services domain whose published rounds include OilRig (published 22 November 2022) and menuPass with ALPHV BlackCat (published 18 June 2024). If a provider cites a round, read the round's own publication for what was tested and for which service configuration. ## The monthly review Hold a monthly 45-minute review with the same agenda: the five measures, three sampled closures, every action taken, every exception to the authority matrix, open change requests and a decision list. Keep the minutes. At 6 and 12 months compare the trend with the contract commitments, including any credit you are owed. Record changes in your environment as well, since a new cloud account or a merger changes what you should expect. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [MDR and incident response: when an alert becomes a breach](/guides/when-an-alert-becomes-a-breach/) - [MDR for OT and industrial networks](/guides/mdr-for-ot/) - [Questions to ask in an MDR reference call](/guides/reference-calls/) ## Sources - NIST CSRC glossary, false positive: https://csrc.nist.gov/glossary/term/false_positive (read 10 November 2026) - MITRE ATT&CK, FAQ: https://attack.mitre.org/resources/faq/ (read 10 November 2026) - MITRE ATT&CK Evaluations, adversaries list (Managed Services domain): https://evals.mitre.org/api/adversaries/ (read 10 November 2026) - Expel, SOC page: https://expel.com/security-operations-center-soc/ (read 10 November 2026) - SentinelOne, MDR page: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) - Sophos, MDR page: https://www.sophos.com/en-us/products/managed-detection-and-response (read 10 November 2026) - CrowdStrike, Falcon Complete page: https://www.crowdstrike.com/en-us/services/falcon-complete-mdr/ (read 10 November 2026) - ReliaQuest, home page: https://reliaquest.com/ (read 10 November 2026) - Sygnia, MDR page: https://cdn.sygnia.co/solutions/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/measuring-mdr/ --- # A reference call is worth having only if you ask about incidents, changes and exits, not about satisfaction Guide, read 10 November 2026 **The short answer.** Providers publish customer statements, and a published statement is not a reference call. Ask for two customers of your size and one that has had an incident or left. This guide gives 20 questions in four groups, a way to take notes and a rule for how to read what you hear. ## What should you do before an MDR reference call? Ask the provider for three references: one of your size and sector, one with a real incident in the past year, and one that changed scope or left. A provider that cannot offer the third may have a reason. Write down what you need to learn, since a reference call lasts 30 minutes. Providers publish customer statements on their sites. Arctic Wolf's MDR page quotes the Head of IT at BetterHome Group on not needing to re-tool, and Huntress's Managed ITDR page quotes a customer on disable account remediations. These are customer statements as published by the providers, read on 10 Nov 2026. They show how the provider presents itself and are not a substitute for your own call. ## Questions on the first months These test onboarding and are the ones references answer most freely. - How long did onboarding take, and what slipped? - Which sources were hardest to connect, and are all of them reporting now? - How noisy was month one, and how many exclusions did you add? - Who was your day-to-day contact, and has that person changed? - What did you have to do that the sales team did not mention? ## Questions on authority and incidents These test the contract in practice. - What actions does the provider take without calling you? Has it ever acted outside that list? - Describe your last real incident. How long until the first call, and what did the analyst know? - Was the escalation useful, or did you have to redo the investigation? - Did the provider help with counsel, insurers or regulators, and was that included in the price? - How did the provider handle an alert that turned out to be a false positive? ## Questions on change and cost These test the relationship over time. - Has the price changed at renewal, and by how much? - Which add-ons did you end up buying? - Did the provider change its platform, team or ownership while you were a customer? - How long does a detection change take after you ask? - If you left, how would you export your cases and detections? ## Questions on scope and fit These test whether the provider understands your environment. - Which of your tools does the provider cover well, and which did it ask you to replace? - Does the provider know your sector's usual attack routes, and did it show that in a case? - How does it treat cloud and identity alerts compared with endpoint alerts? - Did the provider reduce your after-hours calls, and by how much? - What would you change in the contract if you signed again? ## How to read what you hear References are chosen by the provider, so expect good news. Listen for specifics: dates, hours, names of tools, numbers. A reference who says it works great has told you little. One who says the second night's alert came 40 minutes after the host went quiet has told you much. Keep notes in the same format for every call: question, answer, date, speaker's role. Share the notes with your team before you decide, and re-ask any answer that contradicts the contract. For scale, ENISA's Threat Landscape 2025 analyzes 4875 incidents between 1 July 2024 and 30 June 2025. Incident labels differ between reports and providers, so ask the reference what actually happened, in plain words, before accepting a category name. ## Related pages - [All guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [MDR glossary](/glossary/) - [The MDR Service Matrix](/matrix/) - [MDR for OT and industrial networks](/guides/mdr-for-ot/) - [Measuring an MDR service after go-live](/guides/measuring-mdr/) ## Sources - ENISA Threat Landscape 2025: https://www.enisa.europa.eu/publications/enisa-threat-landscape-2025 (read 10 November 2026) - Arctic Wolf, MDR page: https://arcticwolf.com/solutions/managed-detection-and-response/ (read 10 November 2026) - Huntress, Managed ITDR page: https://www.huntress.com/platform/managed-itdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/guides/reference-calls/ --- # 36 MDR terms, each with a sourced example Glossary, read 10 November 2026 **In short.** 36 terms a buyer meets in an MDR selection, from alert triage and authority to act to co-managed SIEM, ITDR and per-endpoint pricing. Each has a plain definition and an example from a standard, a regulator, MITRE or a provider's published description, labelled as the provider's. ## What do MDR terms mean in cybersecurity? Managed detection and response: a service in which an outside team monitors your environment around the clock, investigates alerts and takes or guides response actions. The provider supplies analysts and usually technology. - [Account disable](/glossary/account-disable/): Blocking a user or service account from signing in, often with revocation of active sessions, to stop use of s - [Alert triage](/glossary/alert-triage/): The first review of an alert to decide whether it is real, how serious it is and what happens next - [ATT&CK Evaluations Managed Services](/glossary/attack-evaluations-managed-services/): A part of MITRE's ATT&CK Evaluations program in which managed security services face an emulated adversary cam - [Bring your own tools](/glossary/bring-your-own-tools/): A service model in which the provider works inside security products you already license instead of supplying - [Cloud detection](/glossary/cloud-detection/): Finding attacks in cloud accounts, workloads and software-as-a-service tools from their audit logs and configu - [Co-managed](/glossary/co-managed/): A service model in which your staff and the provider share the work on the same tools and cases, for example y - [Containment](/glossary/containment/): Actions that stop a threat from spreading while the investigation continues, such as isolating a host, disabli - [Data source onboarding](/glossary/data-source-onboarding/): The work of connecting systems so their logs reach the provider and can be monitored, then checking that test - [Detection engineering](/glossary/detection-engineering/): The work of writing, testing and tuning the rules and analytics that raise alerts - [EDR](/glossary/edr/): Endpoint detection and response: software on laptops and servers that records activity, flags suspicious behav - [Escalation](/glossary/escalation/): Passing a case from the provider's analyst to your team, or from your team to a senior responder, with the con - [False positive](/glossary/false-positive/): An alert on activity that is actually harmless - [Forensic investigation](/glossary/forensic-investigation/): Collecting and analyzing evidence, such as disk images, memory and logs, to establish how an intrusion happene - [Host isolation](/glossary/host-isolation/): Cutting a device off from the network, except for the channel the security tool uses, so an attacker on it can - [Identity threat](/glossary/identity-threat/): An attack that uses accounts and credentials instead of malware, such as stolen passwords, abused sessions or - [Incident response retainer](/glossary/incident-response-retainer/): A contract that reserves incident response help in advance, usually as a pool of hours, a response time and ag - [ITDR](/glossary/itdr/): Identity threat detection and response: tooling and services that watch accounts, sign-ins and permissions for - [Log retention](/glossary/log-retention/): How long logs are kept and where - [Managed EDR](/glossary/managed-edr/): A service in which a provider's analysts watch the alerts from endpoint software and investigate them, usually - [MDR](/glossary/mdr/): Managed detection and response: a service in which an outside team monitors your environment around the clock, - [Mean time to respond](/glossary/mean-time-to-respond/): The average time from a defined start, such as alert creation or detection, to a defined response step, such a - [MITRE ATT&CK](/glossary/mitre-attack/): A public knowledge base of adversary tactics, techniques and procedures drawn from real observations - [MSSP](/glossary/mssp/): Managed security service provider: a firm that runs security tools or monitoring for a customer under contract - [NDR](/glossary/ndr/): Network detection and response: sensors and analytics that watch network traffic for signs of attack, useful w - [OT monitoring](/glossary/ot-monitoring/): Watching operational technology, the systems that run physical processes, for signs of attack - [Per-endpoint pricing](/glossary/per-endpoint-pricing/): A pricing model that charges a rate per protected device per month - [Response authority](/glossary/response-authority/): The actions a provider may take on your systems without calling you, written by action and by asset class - [Runbook](/glossary/runbook/): A written set of steps for a type of event, naming who does what, in which order and with what approval - [Service level agreement](/glossary/service-level-agreement/): A contract term that commits the provider to a measured level, such as a response time, with a remedy if misse - [SIEM](/glossary/siem/): Security information and event management: software that gathers logs from many systems into one place so they - [SOAR](/glossary/soar/): Security orchestration, automation and response: tooling that runs scripted steps across other security produc - [SOC](/glossary/soc/): Security operations center: the people, process and tools that watch an organization's systems for attacks and - [Telemetry](/glossary/telemetry/): The stream of data from endpoints, networks, cloud services and identity systems that detection depends on - [Threat hunting (as a service component)](/glossary/threat-hunting/): Analysts searching your data for attacker activity that no alert has flagged - [True positive](/glossary/true-positive/): An alert that correctly identifies real malicious activity - [XDR](/glossary/xdr/): Extended detection and response: a security platform that collects telemetry from several layers, such as endp ## Related pages - [Questions about MDR services, answered](/faq/) - [Guides](/guides/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/ --- # Account disable is locking a user account to stop attacker access Glossary term, read 10 November 2026 **The short answer.** Disabling an account can stop an intruder fast but can also lock out an executive, so decide in advance who the provider may disable. Critical Start lists identity response actions as reset password, disable account and re-initiate MFA (its MDR page, read 10 Nov 2026). ## What is account disable? Blocking a user or service account from signing in, often with revocation of active sessions, to stop use of stolen credentials. It is fast and effective but can interrupt work or automated jobs, so the authority to do it should be agreed in advance. ## A sourced example Critical Start lists identity response actions as reset password, disable account and re-initiate MFA (its MDR page, read 10 Nov 2026). ## Related terms - [Alert triage](/glossary/alert-triage/) - [ATT&CK Evaluations Managed Services](/glossary/attack-evaluations-managed-services/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - criticalstart.com: https://www.criticalstart.com/mdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/account-disable/ --- # Alert triage is the first review that decides which alerts matter Glossary term, read 10 November 2026 **The short answer.** Triage is the service you are really buying: it decides how many alerts reach your small team. Ask what share is reviewed by a person versus software. Huntress says a human reviews every alert before it reaches the customer, a claim worth testing against the contract wording (its Managed EDR page, read 10 Nov 2026). ## What is alert triage? The first review of an alert to decide whether it is real, how serious it is and what happens next. Good triage closes false positives quickly and passes real threats on with context. Ask who does it, how fast, and how closures are checked. ## A sourced example Huntress says a human reviews every alert before it reaches the customer (its Managed EDR page, read 10 Nov 2026). ## Related terms - [Account disable](/glossary/account-disable/) - [ATT&CK Evaluations Managed Services](/glossary/attack-evaluations-managed-services/) - [Bring your own tools](/glossary/bring-your-own-tools/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - huntress.com: https://www.huntress.com/platform/managed-edr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/alert-triage/ --- # ATT&CK Evaluations Managed Services are MITRE's published tests of managed detection services Glossary term, read 10 November 2026 **The short answer.** The ATT&CK Evaluations for managed services are test results for particular scenarios, not a verdict on your environment, so read what was tested. MITRE's evaluations data lists two Managed Services rounds: OilRig, published 22 November 2022, and menuPass with ALPHV BlackCat, published 18 June 2024 (read 10 Nov 2026). ## What is ATT&CK Evaluations Managed Services? A part of MITRE's ATT&CK Evaluations program in which managed security services face an emulated adversary campaign, with results published per round. Read the round's own publication for what was tested and in which configuration. ## A sourced example MITRE's evaluations data lists two Managed Services rounds: OilRig, published 22 November 2022, and menuPass with ALPHV BlackCat, published 18 June 2024 (read 10 Nov 2026). ## Related terms - [Account disable](/glossary/account-disable/) - [Alert triage](/glossary/alert-triage/) - [Bring your own tools](/glossary/bring-your-own-tools/) - [Cloud detection](/glossary/cloud-detection/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - evals.mitre.org: https://evals.mitre.org/api/adversaries/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/attack-evaluations-managed-services/ --- # Bring your own tools means the provider works with security products you already own Glossary term, read 10 November 2026 **The short answer.** Bringing your own tools can protect past purchases and avoid a new agent, but check the supported product list and who pays for licenses. Expel says no agents need deploying and that it plugs into the customer's existing and future security stack, a claim to verify against current integrations (its MDR service page, read 10 Nov 2026). ## What is bring your own tools? A service model in which the provider works inside security products you already license instead of supplying its own agent. It protects past spending and keeps your history, and its quality depends on how well your tools are configured and logged. ## A sourced example Expel says no agents need deploying and that it plugs into the customer's existing and future security stack (its MDR service page, read 10 Nov 2026). ## Related terms - [Alert triage](/glossary/alert-triage/) - [ATT&CK Evaluations Managed Services](/glossary/attack-evaluations-managed-services/) - [Cloud detection](/glossary/cloud-detection/) - [Co-managed](/glossary/co-managed/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - expel.com: https://expel.com/services/managed-detection-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/bring-your-own-tools/ --- # Cloud detection is monitoring of cloud accounts and workloads for attacks Glossary term, read 10 November 2026 **The short answer.** Cloud coverage is often a separate line item, so list the workloads you run and ask which are in scope. Microsoft's Defender Experts overview says neither plan covers Defender for Cloud workloads such as storage, containers and databases, a gap that illustrates why scope needs a check (read 10 Nov 2026). ## What is cloud detection? Finding attacks in cloud accounts, workloads and software-as-a-service tools from their audit logs and configuration data. Services differ on which clouds and which workload types are covered, so read the scope list line by line. ## A sourced example Microsoft's Defender Experts overview says neither plan covers Defender for Cloud workloads such as storage, containers and databases (read 10 Nov 2026). ## Related terms - [ATT&CK Evaluations Managed Services](/glossary/attack-evaluations-managed-services/) - [Bring your own tools](/glossary/bring-your-own-tools/) - [Co-managed](/glossary/co-managed/) - [Containment](/glossary/containment/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - learn.microsoft.com: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-overview (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/cloud-detection/ --- # Co-managed means your team and the provider share the work in your tools Glossary term, read 10 November 2026 **The short answer.** Co-managed models keep your tools and some control, but you must staff your share, so ask which tasks fall to you. Deepwatch says it connects to the customer's existing SIEM, EDR, cloud, identity and SaaS tools, an example of a provider working inside your stack (its home page, read 10 Nov 2026). ## What is co-managed? A service model in which your staff and the provider share the work on the same tools and cases, for example your team by day and theirs at night. It keeps data and context with you and demands a clear hand-off between shifts. ## A sourced example Deepwatch says it connects to the customer's existing SIEM, EDR, cloud, identity and SaaS tools (its home page, read 10 Nov 2026). ## Related terms - [Bring your own tools](/glossary/bring-your-own-tools/) - [Cloud detection](/glossary/cloud-detection/) - [Containment](/glossary/containment/) - [Data source onboarding](/glossary/data-source-onboarding/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - deepwatch.com: https://www.deepwatch.com/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/co-managed/ --- # Containment is the act of stopping a threat from spreading after detection Glossary term, read 10 November 2026 **The short answer.** Containment speed depends on whether the provider may act without calling you first, so settle that before signing. Arctic Wolf's published 2022 ransomware example records an endpoint contained 8 minutes after the attack began, using its agent under predefined customer instructions (its timeline page, read 10 Nov 2026). ## What is containment? Actions that stop a threat from spreading while the investigation continues, such as isolating a host, disabling an account or blocking an address. Containment limits damage; it does not remove the attacker or repair systems, which comes later. ## A sourced example Arctic Wolf's published 2022 ransomware example records an endpoint contained 8 minutes after the attack began, using its agent under predefined customer instructions (its timeline page, read 10 Nov 2026). ## Related terms - [Cloud detection](/glossary/cloud-detection/) - [Co-managed](/glossary/co-managed/) - [Data source onboarding](/glossary/data-source-onboarding/) - [Detection engineering](/glossary/detection-engineering/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - arcticwolf.com: https://arcticwolf.com/incident-response-timeline-ransomware-attack-containment/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/containment/ --- # Data source onboarding is adding your systems so the provider can monitor them Glossary term, read 10 November 2026 **The short answer.** Coverage is only as wide as what has been onboarded, so ask who does the work, how long it takes and what it costs. The UK NCSC describes onboarding as adding systems to a SOC's scope so logs are collected and monitored, and says no IT estate stays the same (read 10 Nov 2026). ## What is data source onboarding? The work of connecting systems so their logs reach the provider and can be monitored, then checking that test events arrive. Onboarding never finishes, since new systems appear. A connector showing green is not proof of coverage. ## A sourced example The UK NCSC describes onboarding as adding systems to the scope of a SOC so their logs are collected and monitored, and says no IT estate stays the same (read 10 Nov 2026). ## Related terms - [Co-managed](/glossary/co-managed/) - [Containment](/glossary/containment/) - [Detection engineering](/glossary/detection-engineering/) - [EDR](/glossary/edr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - ncsc.gov.uk: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre/onboarding-systems-and-log-sources (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/data-source-onboarding/ --- # Detection engineering is writing and tuning the rules that find attacks Glossary term, read 10 November 2026 **The short answer.** Detection engineering decides whether new attacker methods are caught across your environment, so ask how fast new rules reach you. IDC says Kroll's detection engineering team rolls new detection rules out to EDR and SIEM platforms for all Kroll Responder clients (analyst report copy hosted by Arctic Wolf, read 10 Nov 2026). ## What is detection engineering? The work of writing, testing and tuning the rules and analytics that raise alerts. In an MDR service it determines what is caught and how noisy the queue is. Ask who writes rules for your sources and who owns them. ## A sourced example IDC says Kroll's detection engineering team rolls new detection rules out to EDR and SIEM platforms for all Kroll Responder clients (analyst report copy hosted by Arctic Wolf, read 10 Nov 2026). ## Related terms - [Containment](/glossary/containment/) - [Data source onboarding](/glossary/data-source-onboarding/) - [EDR](/glossary/edr/) - [Escalation](/glossary/escalation/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - arcticwolf.com: https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/detection-engineering/ --- # EDR is endpoint software that records activity and lets responders act on devices Glossary term, read 10 November 2026 **The short answer.** Most MDR offers rest on EDR, so find out whether you must use the provider's agent or can keep yours. That choice shapes switching costs. NIST's glossary lists EDR with source documents NIST SP 1800-24C and SP 800-66r2, so the term appears in federal guidance (read 10 Nov 2026). ## What is EDR? Endpoint detection and response: software on laptops and servers that records activity, flags suspicious behavior and lets responders isolate a machine or stop a process. It is a tool. Managed EDR and MDR add people who watch what it reports. ## A sourced example NIST's glossary lists EDR with source documents NIST SP 1800-24C and SP 800-66r2, so the term appears in federal guidance (read 10 Nov 2026). ## Related terms - [Data source onboarding](/glossary/data-source-onboarding/) - [Detection engineering](/glossary/detection-engineering/) - [Escalation](/glossary/escalation/) - [False positive](/glossary/false-positive/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - csrc.nist.gov: https://csrc.nist.gov/glossary/term/endpoint_detection_and_response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/edr/ --- # Escalation is how and when the provider hands an incident to your team Glossary term, read 10 November 2026 **The short answer.** Escalation terms decide whether your phone rings in time. Ask for minutes in writing, and who is called. Sygnia's MDR datasheet says most escalations are initiated in under one hour after initial detection, and prints no SLA minutes or credits, so the figure is descriptive rather than a promise (read 10 Nov 2026). ## What is escalation? Passing a case from the provider's analyst to your team, or from your team to a senior responder, with the context needed to act. A good escalation says what happened, what was done, what is needed and by when. ## A sourced example Sygnia's MDR datasheet says most escalations are initiated in under one hour after initial detection and prints no SLA minutes or credits (read 10 Nov 2026). ## Related terms - [Detection engineering](/glossary/detection-engineering/) - [EDR](/glossary/edr/) - [False positive](/glossary/false-positive/) - [Forensic investigation](/glossary/forensic-investigation/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - sygnia.co: https://cdn.sygnia.co/wp-content/uploads/2026/07/MDR-datasheet-042026.pdf (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/escalation/ --- # A false positive is an alert that flags harmless activity as an attack Glossary term, read 10 November 2026 **The short answer.** False positives cost your team time, so ask how the provider filters them and whether you pay for noise. Request the rate for a comparable customer. NIST's glossary, citing SP 800-86, defines a false positive as incorrectly classifying benign activity as malicious (read 10 Nov 2026). ## What is false positive? An alert on activity that is actually harmless. Too many waste analyst time and bury real threats; closing too eagerly hides real ones. Check a sample of closed alerts each month to see whether closures were right. ## A sourced example NIST's glossary, citing SP 800-86, defines a false positive as incorrectly classifying benign activity as malicious (read 10 Nov 2026). ## Related terms - [EDR](/glossary/edr/) - [Escalation](/glossary/escalation/) - [Forensic investigation](/glossary/forensic-investigation/) - [Host isolation](/glossary/host-isolation/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - csrc.nist.gov: https://csrc.nist.gov/glossary/term/false_positive (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/false-positive/ --- # Forensic investigation is deep analysis of how an attack happened and what it touched Glossary term, read 10 November 2026 **The short answer.** Standard MDR usually covers detection and containment, and forensics may be a separate cost, so check where the line sits. SentinelOne says that for critical incidents, DFIR experts are available for rapid containment and forensic recovery, which you can compare with other services' wording (its MDR page, read 10 Nov 2026). ## What is forensic investigation? Collecting and analyzing evidence, such as disk images, memory and logs, to establish how an intrusion happened, what the attacker did and what data was touched. It is slower and deeper than MDR triage and often a separate engagement. ## A sourced example SentinelOne says that for critical incidents, DFIR experts are available for rapid containment and forensic recovery (its MDR page, read 10 Nov 2026). ## Related terms - [Escalation](/glossary/escalation/) - [False positive](/glossary/false-positive/) - [Host isolation](/glossary/host-isolation/) - [Identity threat](/glossary/identity-threat/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - sentinelone.com: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/forensic-investigation/ --- # Host isolation is cutting an infected device off from the network Glossary term, read 10 November 2026 **The short answer.** Isolation halts spread but also takes a machine offline, so decide which devices a provider may isolate on its own. Servers are the usual debate. Microsoft's Defender Experts managed response page lists isolate device and release from isolation among its one-click actions (read 10 Nov 2026). ## What is host isolation? Cutting a device off from the network, except for the channel the security tool uses, so an attacker on it cannot spread or send data out. It is reversible, which is why many buyers allow it automatically on laptops and ask first for servers. ## A sourced example Microsoft's Defender Experts managed response page lists isolate device and release from isolation among its one-click actions (read 10 Nov 2026). ## Related terms - [False positive](/glossary/false-positive/) - [Forensic investigation](/glossary/forensic-investigation/) - [Identity threat](/glossary/identity-threat/) - [Incident response retainer](/glossary/incident-response-retainer/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - learn.microsoft.com: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/host-isolation/ --- # Identity threat means attackers abusing real accounts instead of breaking in Glossary term, read 10 November 2026 **The short answer.** Identity attacks look like normal logins, so ask what signals the provider reads and whether it can act on accounts. MITRE ATT&CK technique T1078 says adversaries may obtain and abuse credentials of existing accounts for initial access, persistence, privilege escalation or defense evasion (read 10 Nov 2026). ## What is identity threat? An attack that uses accounts and credentials instead of malware, such as stolen passwords, abused sessions or added privileges. It can look like normal use, so detection depends on sign-in logs and identity context. ## A sourced example MITRE ATT&CK technique T1078 says adversaries may obtain and abuse credentials of existing accounts for initial access, persistence, privilege escalation or defense evasion (read 10 Nov 2026). ## Related terms - [Forensic investigation](/glossary/forensic-investigation/) - [Host isolation](/glossary/host-isolation/) - [Incident response retainer](/glossary/incident-response-retainer/) - [ITDR](/glossary/itdr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - attack.mitre.org: https://attack.mitre.org/techniques/T1078/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/identity-threat/ --- # An incident response retainer is prepaid expert time for serious incidents Glossary term, read 10 November 2026 **The short answer.** Some MDR services include or sell a retainer, so ask whether major incident work is covered or billed apart. SentinelOne says its Wayfinder IRR retainer gives a renewable pool of expert hours consumed across readiness, assessments and response, an example of hours shared across several uses (its IR page, read 10 Nov 2026). ## What is incident response retainer? A contract that reserves incident response help in advance, usually as a pool of hours, a response time and agreed terms. Some MDR services bundle one and others sell it separately, so check what counts against the hours. ## A sourced example SentinelOne says its Wayfinder IRR retainer gives a renewable pool of expert hours consumed across readiness, assessments and response (its IR page, read 10 Nov 2026). ## Related terms - [Host isolation](/glossary/host-isolation/) - [Identity threat](/glossary/identity-threat/) - [ITDR](/glossary/itdr/) - [Log retention](/glossary/log-retention/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - sentinelone.com: https://www.sentinelone.com/global-services/incident-readiness-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/incident-response-retainer/ --- # ITDR is detection and response focused on identities and the systems that manage them Glossary term, read 10 November 2026 **The short answer.** Stolen credentials are a common route in, so ask whether identity monitoring is in the base service or priced per user. Huntress publishes $4.80 per licensed identity per month for Managed ITDR, with volume pricing on request, which gives you a published price to compare against (its pricing page, read 10 Nov 2026). ## What is ITDR? Identity threat detection and response: tooling and services that watch accounts, sign-ins and permissions for misuse, such as stolen credentials or unexpected privilege changes. Providers sell it as a product, as a managed service or inside MDR, and priced per identity. ## A sourced example Huntress publishes $4.80 per licensed identity per month for Managed ITDR, with volume pricing on request (its pricing page, read 10 Nov 2026). ## Related terms - [Identity threat](/glossary/identity-threat/) - [Incident response retainer](/glossary/incident-response-retainer/) - [Log retention](/glossary/log-retention/) - [Managed EDR](/glossary/managed-edr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - huntress.com: https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/itdr/ --- # Log retention is how long collected logs stay available for investigation Glossary term, read 10 November 2026 **The short answer.** Short retention can leave you unable to investigate an old intrusion, so check the default and what longer storage costs. The UK NCSC says it can be months before incidents are detected, and recommends storing your most important logs for at least 6 months (read 10 Nov 2026). ## What is log retention? How long logs are kept and where. Short retention can hide an intrusion discovered late, while long retention costs storage. Ask what the provider keeps, where, for how long, and whether you can export a copy. ## A sourced example The UK NCSC says it can be months before incidents are detected, and recommends storing your most important logs for at least 6 months (read 10 Nov 2026). ## Related terms - [Incident response retainer](/glossary/incident-response-retainer/) - [ITDR](/glossary/itdr/) - [Managed EDR](/glossary/managed-edr/) - [MDR](/glossary/mdr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - ncsc.gov.uk: https://www.ncsc.gov.uk/collection/10-steps/logging-and-monitoring (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/log-retention/ --- # Managed EDR is an endpoint tool operated for you by the provider's analysts Glossary term, read 10 November 2026 **The short answer.** Managed EDR can cost less than full MDR but may cover only endpoints, so check what falls outside it. Ask who is on shift. Huntress says its Managed EDR is run by a 24/7 human-led SOC that investigates and acts on suspicious activity (its Managed EDR page, read 10 Nov 2026). ## What is managed edr? A service in which a provider's analysts watch the alerts from endpoint software and investigate them, usually with limited response on the endpoints themselves. Scope is endpoints. Identity, cloud and email need extra products or a broader MDR service. ## A sourced example Huntress says its Managed EDR is run by a 24/7 human-led SOC that investigates and acts on suspicious activity (its Managed EDR page, read 10 Nov 2026). ## Related terms - [ITDR](/glossary/itdr/) - [Log retention](/glossary/log-retention/) - [MDR](/glossary/mdr/) - [Mean time to respond](/glossary/mean-time-to-respond/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - huntress.com: https://www.huntress.com/platform/managed-edr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/managed-edr/ --- # MDR is an outside team that watches your environment and responds to threats Glossary term, read 10 November 2026 **The short answer.** MDR is meant for teams that cannot staff nights, so the contract must say who investigates and who acts. The label alone settles nothing. CrowdStrike, a vendor, defines MDR as a service combining technology with human expertise to identify and limit threats through threat hunting, monitoring and response (read 10 Nov 2026). ## What is MDR? Managed detection and response: a service in which an outside team monitors your environment around the clock, investigates alerts and takes or guides response actions. The provider supplies analysts and usually technology. Scope, tools and permitted actions differ by provider, so the contract defines the service. ## A sourced example CrowdStrike, a vendor, defines MDR as "a cybersecurity service that combines technology with human expertise to rapidly identify and limit the impact of threats by performing threat hunting, monitoring, and response" (read 10 Nov 2026). ## Related terms - [Log retention](/glossary/log-retention/) - [Managed EDR](/glossary/managed-edr/) - [Mean time to respond](/glossary/mean-time-to-respond/) - [MITRE ATT&CK](/glossary/mitre-attack/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - crowdstrike.com: https://www.crowdstrike.com/en-us/cybersecurity-101/managed-security/managed-detection-and-response-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/mdr/ --- # Mean time to respond is the average delay between an alert and a response Glossary term, read 10 November 2026 **The short answer.** An average can hide slow outliers, so ask what starts and stops the clock and whether a credit follows a miss. Critical Start's SLA page publishes a 60-minute mean time to respond in all three of its tiers, an example of a figure written into a service level page (read 10 Nov 2026). ## What is mean time to respond? The average time from a defined start, such as alert creation or detection, to a defined response step, such as first analyst action or containment. The start point, the stop point and the statistic decide what the number means, so compare definitions before numbers. ## A sourced example Critical Start's SLA page publishes a 60-minute mean time to respond in all three of its tiers (read 10 Nov 2026). ## Related terms - [Managed EDR](/glossary/managed-edr/) - [MDR](/glossary/mdr/) - [MITRE ATT&CK](/glossary/mitre-attack/) - [MSSP](/glossary/mssp/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - criticalstart.com: https://www.criticalstart.com/sla-commitment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/mean-time-to-respond/ --- # MITRE ATT&CK is a shared catalog of attacker tactics and techniques Glossary term, read 10 November 2026 **The short answer.** Providers cite ATT&CK to show detection coverage, so ask which techniques they cover in your tools. MITRE's FAQ says ATT&CK started in 2013 to document techniques that advanced persistent threats use against Windows enterprise networks, and defines tactics as the why and techniques as the how (read 10 Nov 2026). ## What is MITRE ATT&CK? A public knowledge base of adversary tactics, techniques and procedures drawn from real observations. Providers map their detections to it, which gives buyers a common vocabulary. A mapped technique shows coverage intent and not a guarantee of detection. ## A sourced example MITRE's FAQ says ATT&CK started in 2013 to document techniques that advanced persistent threats use against Windows enterprise networks, and defines tactics as the why and techniques as the how (read 10 Nov 2026). ## Related terms - [MDR](/glossary/mdr/) - [Mean time to respond](/glossary/mean-time-to-respond/) - [MSSP](/glossary/mssp/) - [NDR](/glossary/ndr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - attack.mitre.org: https://attack.mitre.org/resources/faq/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/mitre-attack/ --- # An MSSP is a provider that runs security tools or monitoring for you Glossary term, read 10 November 2026 **The short answer.** An MSSP agreement may stop at forwarding alerts, leaving your staff to investigate. Ask who acts at 3 a.m. and read the service description, not the label. CrowdStrike's MDR explainer, a vendor's description, says MSSPs typically provide broad monitoring and send validated alerts, and generally do not actively respond (read 10 Nov 2026). ## What is MSSP? Managed security service provider: a firm that runs security tools or monitoring for a customer under contract, often covering firewalls, log collection and alert forwarding. Whether it also investigates and responds depends on the agreement, so read the service description and not the label. ## A sourced example CrowdStrike's MDR explainer says MSSPs typically provide broad monitoring and send validated alerts, and generally do not actively respond to threats (a vendor's description, read 10 Nov 2026). ## Related terms - [Mean time to respond](/glossary/mean-time-to-respond/) - [MITRE ATT&CK](/glossary/mitre-attack/) - [NDR](/glossary/ndr/) - [OT monitoring](/glossary/ot-monitoring/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - crowdstrike.com: https://www.crowdstrike.com/en-us/cybersecurity-101/managed-security/managed-detection-and-response-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/mssp/ --- # NDR is detection that watches network traffic where agents cannot be installed Glossary term, read 10 November 2026 **The short answer.** NDR matters when devices cannot run an agent, such as IoT or industrial equipment, so ask whether network coverage is included or extra. IDC says Kroll uses NDR, partnered with Darktrace, to detect attacks against IoT or OT devices where EDR agents cannot be deployed (analyst report copy hosted by Arctic Wolf, read 10 Nov 2026). ## What is NDR? Network detection and response: sensors and analytics that watch network traffic for signs of attack, useful where devices cannot run an agent, such as many industrial and IoT devices. It sees traffic between systems and not what happens inside a host. ## A sourced example IDC says Kroll uses NDR, partnered with Darktrace, to detect attacks against IoT or OT devices where EDR agents cannot be deployed (analyst report copy hosted by Arctic Wolf, read 10 Nov 2026). ## Related terms - [MITRE ATT&CK](/glossary/mitre-attack/) - [MSSP](/glossary/mssp/) - [OT monitoring](/glossary/ot-monitoring/) - [Per-endpoint pricing](/glossary/per-endpoint-pricing/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - arcticwolf.com: https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/ndr/ --- # OT monitoring is watching industrial and operational systems for attacks Glossary term, read 10 November 2026 **The short answer.** Standard MDR is built for IT, so plants and utilities should ask for OT coverage by name. CISA's ICS page lists a fact sheet urging operators to reduce public internet exposure, strengthen access controls, apply updates and monitor their systems, which frames baseline duties you keep (read 10 Nov 2026). ## What is OT monitoring? Watching operational technology, the systems that run physical processes, for signs of attack. It often relies on passive network sensors because controllers cannot take agents. Coverage and permitted response differ greatly between services. ## A sourced example CISA's ICS page lists a fact sheet urging operators to reduce public internet exposure, strengthen access controls, apply updates and monitor their systems (read 10 Nov 2026). ## Related terms - [MSSP](/glossary/mssp/) - [NDR](/glossary/ndr/) - [Per-endpoint pricing](/glossary/per-endpoint-pricing/) - [Response authority](/glossary/response-authority/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - cisa.gov: https://www.cisa.gov/topics/industrial-control-systems (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/ot-monitoring/ --- # Per-endpoint pricing is a monthly fee for each protected device Glossary term, read 10 November 2026 **The short answer.** Per-endpoint pricing is easy to budget when headcount is stable, but check minimums, contract length and what counts as an endpoint. Huntress publishes $8.99 per endpoint per month for Managed EDR, a published figure that lets you compare quotes on a like-for-like basis (its pricing page, read 10 Nov 2026). ## What is per-endpoint pricing? A pricing model that charges a rate per protected device per month. It is easy to model and grows with device count. Ask what counts as an endpoint, whether servers cost the same and what the minimum is. ## A sourced example Huntress publishes $8.99 per endpoint per month for Managed EDR (its pricing page, read 10 Nov 2026). ## Related terms - [NDR](/glossary/ndr/) - [OT monitoring](/glossary/ot-monitoring/) - [Response authority](/glossary/response-authority/) - [Runbook](/glossary/runbook/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - huntress.com: https://www.huntress.com/pricing (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/per-endpoint-pricing/ --- # Response authority is the set of actions you allow the provider to take Glossary term, read 10 November 2026 **The short answer.** Response authority separates a provider that acts from one that only advises, so read it in the contract and in the tool permissions. Microsoft's page says Defender Experts act on the customer's behalf only if granted Security Operator access; with default Security Reader access, actions stay pending for the customer (read 10 Nov 2026). ## What is response authority? The actions a provider may take on your systems without calling you, written by action and by asset class. It decides whether an analyst at 3 a.m. acts or waits. Common modes are automatic, ask first and advice only. ## A sourced example Microsoft's page says Defender 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 (read 10 Nov 2026). ## Related terms - [OT monitoring](/glossary/ot-monitoring/) - [Per-endpoint pricing](/glossary/per-endpoint-pricing/) - [Runbook](/glossary/runbook/) - [Service level agreement](/glossary/service-level-agreement/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - learn.microsoft.com: https://learn.microsoft.com/en-us/defender-xdr/defender-experts/defender-experts-mdr-managed-response (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/response-authority/ --- # A runbook is the written set of steps a provider follows for a threat Glossary term, read 10 November 2026 **The short answer.** A runbook turns your approval into action, so ask who writes it and how you change it. Test it before an incident. Critical Start says that on a confirmed threat its analysts run the customer-approved playbook, which may include host isolation, process termination or account suspension (its MDR page, read 10 Nov 2026). ## What is runbook? A written set of steps for a type of event, naming who does what, in which order and with what approval. A shared runbook between you and the provider turns authority to act from a promise into a procedure that can be tested. ## A sourced example Critical Start says that on a confirmed threat its analysts run the customer-approved playbook, which may include host isolation, process termination or account suspension (its MDR page, read 10 Nov 2026). ## Related terms - [Per-endpoint pricing](/glossary/per-endpoint-pricing/) - [Response authority](/glossary/response-authority/) - [Service level agreement](/glossary/service-level-agreement/) - [SIEM](/glossary/siem/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - criticalstart.com: https://www.criticalstart.com/mdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/runbook/ --- # A service level agreement is the written promise of speed and remedies Glossary term, read 10 November 2026 **The short answer.** The SLA is where marketing turns into obligation, so read the clock start, the priority levels and the credit. Sophos commits, for MDR Plus customers, to a time to respond within 60 minutes for 90 percent of priority investigations, measured monthly, with a service credit (its service description, read 10 Nov 2026). ## What is service level agreement? A contract term that commits the provider to a measured level, such as a response time, with a remedy if missed. A target without a remedy is not an SLA. Check the clock start, the statistic, the exclusions and the credit. ## A sourced example Sophos commits, for MDR Plus customers, to a time to respond within 60 minutes for 90 percent of priority investigations, measured monthly, with a service credit (its service description, read 10 Nov 2026). ## Related terms - [Response authority](/glossary/response-authority/) - [Runbook](/glossary/runbook/) - [SIEM](/glossary/siem/) - [SOAR](/glossary/soar/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - sophos.com: https://www.sophos.com/en-us/legal/mdr-description (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/service-level-agreement/ --- # A SIEM is a system that collects and correlates logs from across your environment Glossary term, read 10 November 2026 **The short answer.** Many MDR services read from your SIEM or bring their own, which affects cost and data ownership. Ask who holds the logs when the contract ends. NIST's glossary cites SP 800-92, published September 2006, describing a SIEM as a program providing centralized logging capabilities for a variety of log types (read 10 Nov 2026). ## What is SIEM? Security information and event management: software that gathers logs from many systems into one place so they can be searched, correlated and alerted on. It is a tool and not a service, though some providers run it for you as a managed or co-managed offering. ## A sourced example NIST's glossary cites SP 800-92, published September 2006, which describes a SIEM as a program that provides centralized logging capabilities for a variety of log types (read 10 Nov 2026). ## Related terms - [Runbook](/glossary/runbook/) - [Service level agreement](/glossary/service-level-agreement/) - [SOAR](/glossary/soar/) - [SOC](/glossary/soc/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - csrc.nist.gov: https://csrc.nist.gov/glossary/term/security_information_and_event_management (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/siem/ --- # SOAR is software that automates alert handling and response steps Glossary term, read 10 November 2026 **The short answer.** SOAR automates steps your analysts or a provider would otherwise do by hand, so ask whether a provider's automation runs in your tools or theirs. IBM's XDR explainer lists SOAR next to SIEM, EDR, NDR, XDR and ITDR among categories of detection and response tooling, which helps when reading vendor feature lists (read 10 Nov 2026). ## What is SOAR? Security orchestration, automation and response: tooling that runs scripted steps across other security products, such as enriching an alert or opening a ticket. It automates work an analyst would otherwise repeat by hand. It is a term to know, and MDR providers may run it behind the service. ## A sourced example IBM's XDR explainer lists SOAR next to SIEM, EDR, NDR, XDR and ITDR among categories of detection and response tooling (read 10 Nov 2026). ## Related terms - [Service level agreement](/glossary/service-level-agreement/) - [SIEM](/glossary/siem/) - [SOC](/glossary/soc/) - [Telemetry](/glossary/telemetry/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - ibm.com: https://www.ibm.com/think/topics/xdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/soar/ --- # A SOC is the team and process that monitors for attacks and responds Glossary term, read 10 November 2026 **The short answer.** Your choice is often between building a SOC and renting one through MDR, and scope decides the cost. Define hours covered and actions allowed. The UK NCSC says a SOC's role is to limit damage by detecting and responding to attacks that get past preventive controls, and that SOC scope varies widely (read 10 Nov 2026). ## What is SOC? Security operations center: the people, process and tools that watch an organization's systems for attacks and respond to them. It can be built in-house, bought as a service or shared between both. Its scope varies, and some SOCs also handle vulnerability work and compliance. ## A sourced example The UK NCSC says a SOC's role is to limit damage by detecting and responding to attacks that get past preventive controls, and that SOC scope varies widely (read 10 Nov 2026). ## Related terms - [SIEM](/glossary/siem/) - [SOAR](/glossary/soar/) - [Telemetry](/glossary/telemetry/) - [Threat hunting (as a service component)](/glossary/threat-hunting/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - ncsc.gov.uk: https://www.ncsc.gov.uk/collection/building-a-security-operations-centre (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/soc/ --- # Telemetry is the stream of security data a provider collects from your systems Glossary term, read 10 November 2026 **The short answer.** A provider can only detect what it sees, so list the sources you need covered and ask which are included. Rapid7 says its MDR combines native multi-vector telemetry with third-party ingestion to cover endpoint, cloud, identity, email and network, a typical breadth to ask about (its MDR page, read 10 Nov 2026). ## What is telemetry? The stream of data from endpoints, networks, cloud services and identity systems that detection depends on. More sources widen what an analyst can see but add cost and onboarding work. A service can only detect what its telemetry shows. ## A sourced example Rapid7 says its MDR combines native multi-vector telemetry with third-party ingestion to cover endpoint, cloud, identity, email and network (its MDR page, read 10 Nov 2026). ## Related terms - [SOAR](/glossary/soar/) - [SOC](/glossary/soc/) - [Threat hunting (as a service component)](/glossary/threat-hunting/) - [True positive](/glossary/true-positive/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - rapid7.com: https://www.rapid7.com/services/managed-detection-and-response-mdr/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/telemetry/ --- # Threat hunting in an MDR service is analysts searching for threats alerts missed Glossary term, read 10 November 2026 **The short answer.** Hunting is often listed as a feature, so ask how often it happens, who does it and whether findings are reported to you. Expel lists threat hunters, SOC threat analysts, detection engineers and a global response team as parts of one 24x7 security operations team (its SOC experts page, read 10 Nov 2026). ## What is threat hunting (as a service component)? Analysts searching your data for attacker activity that no alert has flagged. As a component of MDR it may be continuous, periodic or sold separately. Term only; ask what is hunted, how often and how findings reach you. ## A sourced example Expel lists threat hunters, SOC threat analysts, detection engineers and a global response team as parts of one 24x7 security operations team (its SOC experts page, read 10 Nov 2026). ## Related terms - [SOC](/glossary/soc/) - [Telemetry](/glossary/telemetry/) - [True positive](/glossary/true-positive/) - [XDR](/glossary/xdr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - expel.com: https://expel.com/meet-the-soc-experts/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/threat-hunting/ --- # A true positive is an alert that correctly flags a real threat Glossary term, read 10 November 2026 **The short answer.** What happens after a true positive is the test of an MDR service: who acts, how fast, and under what rules. SentinelOne says confirmed threats are contained, with malicious processes killed, endpoints isolated and unauthorized changes rolled back, per the configured response policy (its MDR page, read 10 Nov 2026). ## What is true positive? An alert that correctly identifies real malicious activity. A service earns its keep on true positives, and a good one tells you what happened, what it did and what you must do. Contracts often use the phrase confirmed threat for the same idea. ## A sourced example SentinelOne says confirmed threats are contained: malicious processes are killed, endpoints isolated and unauthorized changes rolled back, per the configured response policy (its MDR page, read 10 Nov 2026). ## Related terms - [Telemetry](/glossary/telemetry/) - [Threat hunting (as a service component)](/glossary/threat-hunting/) - [XDR](/glossary/xdr/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - sentinelone.com: https://www.sentinelone.com/global-services/managed-detection-and-response/ (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/true-positive/ --- # XDR is detection technology spanning endpoint, identity, cloud and network data Glossary term, read 10 November 2026 **The short answer.** XDR is software, while MDR is a staffed service, so buying one does not give you the other. Ask whether a provider's service depends on a specific XDR platform. IBM's explainer says XDR is typically consumed as a cloud-based service and may be the core technology behind a provider's MDR offering (read 10 Nov 2026). ## What is XDR? Extended detection and response: a security platform that collects telemetry from several layers, such as endpoint, network, cloud and identity, correlates it and supports response. XDR is a product category; MDR is a service. A provider may run XDR to deliver its MDR. ## A sourced example IBM's explainer says XDR is typically consumed as a cloud-based service and may be the core technology behind a provider's MDR offering (read 10 Nov 2026). ## Related terms - [Threat hunting (as a service component)](/glossary/threat-hunting/) - [True positive](/glossary/true-positive/) ## Related pages - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Questions about MDR services, answered](/faq/) - [All MDR terms](/glossary/) ## Sources - ibm.com: https://www.ibm.com/think/topics/xdr (read 10 November 2026) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/glossary/xdr/ --- # 12 dated items an MDR buyer should know News, read 10 November 2026 **In short.** 12 dated items from the last ninety days, each from a primary source: providers' service and coverage announcements, acquisitions, MITRE evaluations and government advisories that change what a detection service should watch. Listed by date, newest first. Each item links to the source it was read from, with the read date. ## What is new with MDR services? 12 dated items from the last ninety days are listed, newest first, each from a primary source. The newest is "Huntress adds Brute Force Sentry to Managed SIEM", dated 6 November 2026. - [Huntress adds Brute Force Sentry to Managed SIEM](/news/huntress-brute-force-sentry-managed-siem/): 6 November 2026 - [Microsoft lists new Defender Experts MDR experiences in the Defender portal](/news/microsoft-defender-experts-new-portal-experiences/): 5 November 2026 - [CrowdStrike extends its Agentic SOC to cover AI agent insider threats](/news/crowdstrike-agentic-soc-agent-insider-threats/): 4 November 2026 - [Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier](/news/rapid7-cisa-bod-26-04-three-day-triage/): 4 November 2026 - [CrowdStrike announces intent to acquire Fiddler for AI agent observability](/news/crowdstrike-to-acquire-fiddler/): 3 November 2026 - [Rapid7 Q3 2026 threat update reports a three-day average to exploitation](/news/rapid7-q3-2026-threat-update/): 21 October 2026 - [Huntress introduces ITDR Lookback for new Microsoft 365 tenants](/news/huntress-managed-itdr-lookback/): 20 October 2026 - [Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools](/news/unit42-peerstitch-fortigate-implant-detection/): 14 October 2026 - [Huntress describes Athena, its agentic SOC system for alert investigation](/news/huntress-athena-agentic-soc-analyst/): 29 September 2026 - [Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation](/news/mandiant-citrix-netscaler-detection-guidance/): 29 September 2026 - [NCSC warns of disruption from internet-exposed systems and edge devices](/news/ncsc-edge-device-and-ot-exposure-guidance/): 27 August 2026 - [Red Canary publishes Intelligence Insights for July 2026 with four debuts](/news/red-canary-intelligence-insights-august-2026/): 20 August 2026 ## Related pages - [Guides](/guides/) - [Glossary](/glossary/) - [The MDR Service Matrix](/matrix/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/news/ --- # Huntress adds Brute Force Sentry to Managed SIEM News, 6 November 2026 **The short answer.** Huntress announced Brute Force Sentry for Managed SIEM on 6 November 2026. It is included for all Managed SIEM customers and watches RDP, RD Gateway and RDWeb on Windows and SSH on Linux for brute force, password spraying, credential stuffing and username enumeration. The Huntress SOC investigates when failures end in a success. The feature activates per organization once the needed authentication telemetry is flowing; if it is missing, the portal marks the feature unavailable and says why. Customers see attacked login surfaces, targeted accounts, attack sources and any compromises linked to an incident report, and can opt in to alerts on every attempt. Huntress cites a June 2026 case of about 1,700 attempts in 72 seconds before access was gained. In a review of 30 confirmed RDWeb and RD Gateway compromises during four weeks of testing, it says the signal would have reached the SOC up to an hour earlier in 20 of them. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Microsoft lists new Defender Experts MDR experiences in the Defender portal](/news/microsoft-defender-experts-new-portal-experiences/) - [CrowdStrike extends its Agentic SOC to cover AI agent insider threats](/news/crowdstrike-agentic-soc-agent-insider-threats/) ## Sources - huntress.com: https://www.huntress.com/blog/brute-force-sentry (read 10 November 2026) Last reviewed 6 November 2026. Canonical: https://mdrvsmssp.com/news/huntress-brute-force-sentry-managed-siem/ --- # Microsoft lists new Defender Experts MDR experiences in the Defender portal News, 5 November 2026 **The short answer.** Microsoft's November 2026 security roundup, published 5 November, lists new Microsoft Defender Experts MDR experiences in the Defender portal: a consolidated overview page, updated navigation, and visibility into active and completed hunts, Defender Experts findings and items needing follow-up. The post does not state availability. The same roundup lists a generally available Defender capability that discovers more than 50 supported local AI agents on Windows and macOS and correlates them with device, account and configured MCP server context. It also lists an updated agent for Defender for SQL Servers in the Azure Government cloud. The post carries no Sentinel or XDR announcement. Buyers who run Microsoft tooling can read the Defender Experts item as a change in what customers see about provider activity, and ask the provider how hunts and findings are reported outside the portal. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Huntress adds Brute Force Sentry to Managed SIEM](/news/huntress-brute-force-sentry-managed-siem/) - [CrowdStrike extends its Agentic SOC to cover AI agent insider threats](/news/crowdstrike-agentic-soc-agent-insider-threats/) - [Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier](/news/rapid7-cisa-bod-26-04-three-day-triage/) ## Sources - microsoft.com: https://www.microsoft.com/en-us/security/blog/2026/11/05/whats-new-in-microsoft-security-november-2026/ (read 10 November 2026) Last reviewed 5 November 2026. Canonical: https://mdrvsmssp.com/news/microsoft-defender-experts-new-portal-experiences/ --- # CrowdStrike extends its Agentic SOC to cover AI agent insider threats News, 4 November 2026 **The short answer.** CrowdStrike announced on 4 November 2026 additions to its Agentic SOC covering AI agents that act on an employee's behalf. Falcon Next-Gen SIEM is to learn normal behavior for each agent and flag deviations, with several items due in the fourth quarter of 2026 and others generally available now. Items listed as generally available include multi-agent triage and investigation, human-in-the-loop action requests, agent interruption, and a unified SOAR experience, plus new federated search connectors for Dynatrace, Databricks and Snowflake. Due in Q4 2026 are agent insider threat detection, agent risk figures on the existing 0 to 100 user and host scale, and policy-drift guardrails in beta. The post says it may discuss unreleased features that are subject to change. It also cites operational knowledge from tens of thousands of Falcon Complete customers as input to its agents. Buyers can use the availability labels to separate shipped features from planned ones. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Huntress adds Brute Force Sentry to Managed SIEM](/news/huntress-brute-force-sentry-managed-siem/) - [Microsoft lists new Defender Experts MDR experiences in the Defender portal](/news/microsoft-defender-experts-new-portal-experiences/) - [Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier](/news/rapid7-cisa-bod-26-04-three-day-triage/) - [CrowdStrike announces intent to acquire Fiddler for AI agent observability](/news/crowdstrike-to-acquire-fiddler/) ## Sources - crowdstrike.com: https://www.crowdstrike.com/en-us/blog/crowdstrike-detects-and-stops-agent-insider-threats/ (read 10 November 2026) Last reviewed 4 November 2026. Canonical: https://mdrvsmssp.com/news/crowdstrike-agentic-soc-agent-insider-threats/ --- # Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier News, 4 November 2026 **The short answer.** Rapid7 published an explainer on 4 November 2026 about CISA Binding Operational Directive 26-04, which it says was issued on 10 June 2026. For vulnerabilities that are exploited, publicly reachable and give full control, agencies get three calendar days to remediate and must run a forensic triage in parallel. Rapid7 describes five tiers, with deadlines of 3 days, 3 days without triage, 14 days, 60 days and the next system upgrade. It lists a 72-hour triage protocol in six phases, from scoping to an escalation decision, and says confirmed compromise must be reported to CISA. The directive applies to federal civilian agencies. Rapid7 says it replaces BOD 19-02 and BOD 22-01, and that cloud providers handling federal data are expected to follow the same triage standard. This is a vendor summary, not the directive text. Providers serving federal customers can be asked how their detection and escalation steps fit a 72-hour window. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Microsoft lists new Defender Experts MDR experiences in the Defender portal](/news/microsoft-defender-experts-new-portal-experiences/) - [CrowdStrike extends its Agentic SOC to cover AI agent insider threats](/news/crowdstrike-agentic-soc-agent-insider-threats/) - [CrowdStrike announces intent to acquire Fiddler for AI agent observability](/news/crowdstrike-to-acquire-fiddler/) - [Rapid7 Q3 2026 threat update reports a three-day average to exploitation](/news/rapid7-q3-2026-threat-update/) ## Sources - rapid7.com: https://www.rapid7.com/blog/post/it-racing-the-three-day-clock-cisa-bod-26-04 (read 10 November 2026) Last reviewed 4 November 2026. Canonical: https://mdrvsmssp.com/news/rapid7-cisa-bod-26-04-three-day-triage/ --- # CrowdStrike announces intent to acquire Fiddler for AI agent observability News, 3 November 2026 **The short answer.** CrowdStrike announced on 3 November 2026 its intent to acquire Fiddler, an AI observability company. Fiddler would become Falcon Observe, adding pre-deployment evaluation and ongoing monitoring of AI agent behavior to the Falcon platform. Price and closing date were not stated in the post. The post says Fiddler would also link agent decision data with Falcon security telemetry, extending CrowdStrike's AI security work from protecting AI systems to checking that agents operate safely. It states that the deal depends on closing conditions, and it gives no closing date for the transaction. Falcon Observe is described as generally available in the fourth quarter of CrowdStrike's fiscal 2027. The post gives no purchase price or deal structure. Teams that buy MDR from a platform vendor may want to ask how acquisitions like this change the scope of the service, since the post does not describe any change to managed detection and response coverage. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [CrowdStrike extends its Agentic SOC to cover AI agent insider threats](/news/crowdstrike-agentic-soc-agent-insider-threats/) - [Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier](/news/rapid7-cisa-bod-26-04-three-day-triage/) - [Rapid7 Q3 2026 threat update reports a three-day average to exploitation](/news/rapid7-q3-2026-threat-update/) - [Huntress introduces ITDR Lookback for new Microsoft 365 tenants](/news/huntress-managed-itdr-lookback/) ## Sources - crowdstrike.com: https://www.crowdstrike.com/en-us/blog/crowdstrike-to-acquire-fiddler/ (read 10 November 2026) Last reviewed 3 November 2026. Canonical: https://mdrvsmssp.com/news/crowdstrike-to-acquire-fiddler/ --- # Rapid7 Q3 2026 threat update reports a three-day average to exploitation News, 21 October 2026 **The short answer.** Rapid7 published its Q3 2026 threat update on 21 October 2026. It reports that high-severity vulnerabilities were exploited on average three days after public release, with 71 percent of Q3 exploitation inside seven days, 80 percent inside 14 days and 90 percent inside 30 days. Rapid7 tracked 43 newly exploited high and critical vulnerabilities, down 7 percent from Q2 and 19 percent above the same period last year. Of those, 34 needed neither authentication nor user interaction. It found 41 underground forum posts advertising RDP or network access, and says 8 percent of tracked threat reporting cited AI as an operational component. For detection teams, the timing figures bear on how fast a provider needs to apply new detections after a public advisory. Buyers can ask providers for the time between a flaw being added to a known exploited list and a matching detection reaching customers. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Rapid7 explains CISA BOD 26-04 and its three-day remediation and triage tier](/news/rapid7-cisa-bod-26-04-three-day-triage/) - [CrowdStrike announces intent to acquire Fiddler for AI agent observability](/news/crowdstrike-to-acquire-fiddler/) - [Huntress introduces ITDR Lookback for new Microsoft 365 tenants](/news/huntress-managed-itdr-lookback/) - [Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools](/news/unit42-peerstitch-fortigate-implant-detection/) ## Sources - rapid7.com: https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days (read 10 November 2026) Last reviewed 21 October 2026. Canonical: https://mdrvsmssp.com/news/rapid7-q3-2026-threat-update/ --- # Huntress introduces ITDR Lookback for new Microsoft 365 tenants News, 20 October 2026 **The short answer.** Huntress introduced ITDR Lookback on 20 October 2026. It reviews up to 180 days of Microsoft 365 login history from before a tenant was connected, runs once at onboarding, and applies the Unwanted Access detections to find earlier compromise. It is generally available for newly onboarded tenants, including trials. Active compromises produce a critical incident report that the Huntress SOC investigates, and the identity's active sessions are revoked. Compromises already remediated appear as historical context in the Identity Security Assessment and do not open a new incident. Huntress states the feature needs no configuration and runs automatically when onboarding finishes. Huntress reports reviewing more than 400 tenants in the first two weeks and describes three with active compromises, including a school district whose Global Admin account had been compromised 27 days before onboarding. For buyers, the item shows how providers treat pre-contract exposure, which is worth asking about in any selection. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [CrowdStrike announces intent to acquire Fiddler for AI agent observability](/news/crowdstrike-to-acquire-fiddler/) - [Rapid7 Q3 2026 threat update reports a three-day average to exploitation](/news/rapid7-q3-2026-threat-update/) - [Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools](/news/unit42-peerstitch-fortigate-implant-detection/) - [Huntress describes Athena, its agentic SOC system for alert investigation](/news/huntress-athena-agentic-soc-analyst/) ## Sources - huntress.com: https://www.huntress.com/blog/managed-itdr-lookback-feature (read 10 November 2026) Last reviewed 20 October 2026. Canonical: https://mdrvsmssp.com/news/huntress-managed-itdr-lookback/ --- # Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools News, 14 October 2026 **The short answer.** Unit 42 published a report on 14 October 2026 on PEERSTITCH, an in-memory implant for FortiOS tied to an intrusion in September 2024. It creates no files, listening ports or outbound connections of its own. One compromised FortiManager exposed configurations and keys for more than 500 FortiGate firewalls. Unit 42 calls the implant resistant to conventional endpoint and network detection. Checks it lists include 16,384-byte read-write-execute memory mappings in the logging and VPN daemons, integrity checks at three patched offsets, audit logs of cross-process memory writes, and Signal 11 crash entries. The actors also halted logging services, cleared crash logs and rolled back configuration objects, so log telemetry showed intermittent gaps. For buyers, the report is a reminder to ask providers which network devices they ingest logs from and what coverage exists when a device itself is the compromised component. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Rapid7 Q3 2026 threat update reports a three-day average to exploitation](/news/rapid7-q3-2026-threat-update/) - [Huntress introduces ITDR Lookback for new Microsoft 365 tenants](/news/huntress-managed-itdr-lookback/) - [Huntress describes Athena, its agentic SOC system for alert investigation](/news/huntress-athena-agentic-soc-analyst/) - [Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation](/news/mandiant-citrix-netscaler-detection-guidance/) ## Sources - unit42.paloaltonetworks.com: https://unit42.paloaltonetworks.com/fortimanager-cve-2024-47575-peerstitch-malware/ (read 10 November 2026) Last reviewed 14 October 2026. Canonical: https://mdrvsmssp.com/news/unit42-peerstitch-fortigate-implant-detection/ --- # Huntress describes Athena, its agentic SOC system for alert investigation News, 29 September 2026 **The short answer.** Huntress published a description of Athena on 29 September 2026. It says Athena is built from over 40 AI agents that work with human analysts on investigations. Ambiguous cases go to a person, and Huntress states that only vetted, high-confidence scenarios can be completed fully automatically. According to the post, Athena groups related signals, collects telemetry across endpoints, identities and logs, follows playbooks set by Huntress analysts, labels signals as malicious or benign, and drafts incident reports with indicators such as file hashes and affected accounts. Huntress reports a 90 percent drop in report generation time and more than 30 percent better report quality against a human-only baseline, and says its SOC defends over 250,000 organizations. The page gives no release date or tiers. Buyers can ask any provider which steps are automated and which stay with an analyst. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Huntress introduces ITDR Lookback for new Microsoft 365 tenants](/news/huntress-managed-itdr-lookback/) - [Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools](/news/unit42-peerstitch-fortigate-implant-detection/) - [Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation](/news/mandiant-citrix-netscaler-detection-guidance/) - [NCSC warns of disruption from internet-exposed systems and edge devices](/news/ncsc-edge-device-and-ot-exposure-guidance/) ## Sources - huntress.com: https://www.huntress.com/blog/athena-huntress-agentic-soc-analyst (read 10 November 2026) Last reviewed 29 September 2026. Canonical: https://mdrvsmssp.com/news/huntress-athena-agentic-soc-analyst/ --- # Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation News, 29 September 2026 **The short answer.** Mandiant and Google Threat Intelligence Group published detection guidance on 29 September 2026 for exploitation of Citrix NetScaler ADC and Gateway flaw CVE-2026-88772. Activity dates to at least early September. The post lists log patterns, file and configuration changes, and a warning that upstream devices cannot see HTTP paths after TLS ends on the appliance. Listed detection priorities include alerting on DTLSv1.0 handshake failures correlated with packet processing engine terminations, new core files, web shell files in VPN script paths, changes to the web server configuration, and the SUID bit set on the shell binary. The post advises forwarding appliance logs to the SIEM because network sensors in front of the appliance cannot read the traffic. Fixed builds are 14.1-73.37 and 13.1-64.23. Buyers can ask how a provider ingests logs from edge appliances and who writes the detections for them. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Unit 42 describes PEERSTITCH, a FortiGate implant that avoids endpoint and network tools](/news/unit42-peerstitch-fortigate-implant-detection/) - [Huntress describes Athena, its agentic SOC system for alert investigation](/news/huntress-athena-agentic-soc-analyst/) - [NCSC warns of disruption from internet-exposed systems and edge devices](/news/ncsc-edge-device-and-ot-exposure-guidance/) - [Red Canary publishes Intelligence Insights for July 2026 with four debuts](/news/red-canary-intelligence-insights-august-2026/) ## Sources - cloud.google.com: https://cloud.google.com/blog/topics/threat-intelligence/defending-against-active-exploitation-of-citrix-netscaler-adc-and-gateway-appliances/ (read 10 November 2026) Last reviewed 29 September 2026. Canonical: https://mdrvsmssp.com/news/mandiant-citrix-netscaler-detection-guidance/ --- # NCSC warns of disruption from internet-exposed systems and edge devices News, 27 August 2026 **The short answer.** The UK NCSC published guidance on 27 August 2026 saying it has seen increased targeting of operational technology across sectors, including in the UK, with limited real-world disruption. It tells organizations to verify rather than assume that OT is unreachable from the internet and to log and monitor all connectivity to and within OT networks. For organizations without OT, the NCSC advises in the same page that they keep an accurate inventory of internet-facing systems, apply vendor updates promptly, retire end-of-life equipment, disable insecure management protocols, and monitor for unexpected configuration changes or outbound connections from those systems. The guidance also points to the free NCSC Early Warning service and the Cyber Assessment Framework. For MDR buyers, the monitoring advice is a concrete list to compare against a provider's service description, including whether OT networks and edge equipment are in scope. It also recommends tested, ransomware-resistant backups and practiced restoration. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Huntress describes Athena, its agentic SOC system for alert investigation](/news/huntress-athena-agentic-soc-analyst/) - [Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation](/news/mandiant-citrix-netscaler-detection-guidance/) - [Red Canary publishes Intelligence Insights for July 2026 with four debuts](/news/red-canary-intelligence-insights-august-2026/) ## Sources - ncsc.gov.uk: https://www.ncsc.gov.uk/news/disruptive-cyber-activity-highlights-risk-from-internet-exposed-systems-and-edge-devices (read 10 November 2026) Last reviewed 27 August 2026. Canonical: https://mdrvsmssp.com/news/ncsc-edge-device-and-ot-exposure-guidance/ --- # Red Canary publishes Intelligence Insights for July 2026 with four debuts News, 20 August 2026 **The short answer.** Red Canary, now part of Zscaler, published Intelligence Insights on 20 August 2026 for July activity. ClearFake held first place on its prevalence list for the fourth month in a row. Four threats debuted: GraphSpy, Phexia, EtherRAT and CastleRAT. Atomic Stealer and NetSupport Manager fell off the list. The list counts the number of unique customer environments in which Red Canary observed each threat. Second was a ScreenConnect-themed traffic distribution system and third was Scarlet Goldfinch. GraphSpy is described as an open source tool used to steal and abuse Entra ID and Microsoft 365 tokens. The post notes the article was originally published by Red Canary, which is now part of Zscaler, and the original URL redirects to a Zscaler page. For MDR buyers, monthly prevalence reports show which techniques a provider sees across its customers, and who owns the provider now. ## Related pages - [All dated news items](/news/) - [Guides](/guides/) - [The MDR Service Matrix](/matrix/) - [Mandiant and GTIG publish detection guidance for Citrix NetScaler exploitation](/news/mandiant-citrix-netscaler-detection-guidance/) - [NCSC warns of disruption from internet-exposed systems and edge devices](/news/ncsc-edge-device-and-ot-exposure-guidance/) ## Sources - redcanary.com: https://redcanary.com/blog/threat-intelligence/intelligence-insights-august-2026/ (read 10 November 2026) Last reviewed 20 August 2026. Canonical: https://mdrvsmssp.com/news/red-canary-intelligence-insights-august-2026/ --- # 30 questions about MDR services, answered FAQ, read 10 November 2026 **In short.** 30 short answers on what MDR covers, what it costs to run, authority to act, onboarding, what happens when an alert becomes a breach, and how to leave a provider. Answers carry no verdict on any provider. Each answer draws on the guides, the glossary and the sourced facts elsewhere on the site. ## What are MDR services? MDR is a service in which an outside team watches your systems around the clock, investigates alerts and takes or advises on response. The provider supplies analysts and usually technology. **What is MDR in plain words?** MDR is a service in which an outside team watches your systems around the clock, investigates alerts and takes or advises on response. The provider supplies analysts and usually technology. CrowdStrike, a vendor, describes it as technology combined with human expertise for threat hunting, monitoring and response (read 10 Nov 2026). The contract defines what the team may do. **How does MDR differ from an MSSP?** An MSSP typically monitors, manages devices and forwards alerts, while an MDR provider investigates and acts or advises on response. CrowdStrike's explainer says MSSPs generally do not actively respond to threats (a vendor's view, read 10 Nov 2026). Many firms sell both, so read the service description for who takes the next step after an alert. **Is XDR the same as MDR?** No. XDR is software that collects and correlates telemetry from endpoint, network, cloud and identity. MDR is a service staffed by analysts. Palo Alto Networks says XDR can be used alone or combined with MDR (read 10 Nov 2026). A provider may run XDR to deliver MDR, or you may run XDR yourself with your own team. **Does an MDR service replace a SOC?** It can supply some or all of a SOC's function, but someone on your side still decides priorities, approves actions and runs recovery. The UK NCSC says SOC scope varies widely and can include vulnerability assessment and compliance work (read 10 Nov 2026). Map each SOC job to you, the provider or both. **What does authority to act mean?** It is the list of actions an MDR provider may take on your systems without calling you, written by action and asset class: isolate a host, disable an account, block an address. Microsoft's page says its experts act only if granted Security Operator access; the default leaves actions pending (read 10 Nov 2026). **Can an MDR provider isolate a laptop automatically?** Many publish that they can. Deepwatch says its Active Response runs actions automatically, with analyst approval or in monitor-only mode, as the customer sets. Critical Start lists isolate host among endpoint actions (both read 10 Nov 2026). Whether yours will depends on the authority you grant in the contract. **What happens if the provider disables a service account by mistake?** Jobs that use the account may fail until it is restored. That is why many buyers set service accounts and domain controllers to ask-first. eSentire describes its response as policy-bounded and reversible (read 10 Nov 2026). Ask for the undo steps, the restore time and a log of every action in writing. **How long should onboarding take?** No published standard was found on 10 Nov 2026, so ask each provider for a dated plan. A workable target is every in-scope source reporting and verified within 30 days. The UK NCSC describes onboarding as adding systems and their logs to a SOC's scope and says it never finishes (read 10 Nov 2026), so track it as ongoing. **How long should logs be kept?** The UK NCSC says it can be months before incidents are detected and recommends storing your most important logs for at least 6 months (read 10 Nov 2026). The right period for each source depends on cost, storage and use. Ask where the provider keeps your data, for how long, and whether you can export a copy. **Do MDR providers publish prices?** Some do, most do not. Huntress publishes $8.99 per endpoint per month for Managed EDR and $4.80 per licensed identity per month for Managed ITDR. Critical Start says its pricing is not published, and CrowdStrike lists Contact sales (all read 10 Nov 2026). Ask each provider for the unit before the number. **What are the usual pricing units?** Providers describe endpoints, users and servers, assets, and quoted packages. Arctic Wolf states users, servers and internet egress points; Rapid7 states assets protected, not SIEM data volume; ReliaQuest states endpoint count (all read 10 Nov 2026). Because units differ, build a single scope sheet and send it to every provider you ask. **Is incident response included in MDR?** Sometimes. Kroll says Responder MDR includes remote digital forensics and incident response at no extra cost. Sophos says critical incident response is included with no caps. Arctic Wolf's retainer FAQ distinguishes MDR from incident response (all read 10 Nov 2026). Ask what counts as critical, how many hours are included and who starts the clock. **What is an incident response retainer?** It is an advance contract that reserves incident response help, usually as a pool of hours with a response time. SentinelOne describes its retainer as a renewable pool of expert hours consumed across readiness, assessments and response (read 10 Nov 2026). Check what draws down the hours and whether MDR work counts against them. **What is a service level agreement in MDR?** It is a contract term that commits the provider to a measured level with a remedy if missed. Sophos, for example, commits for MDR Plus to a time to respond within 60 minutes for 90 percent of priority investigations, with a service credit (read 10 Nov 2026). A target with no remedy is not an SLA. **Why can I not compare published response times?** Providers define them differently. CrowdStrike publishes a median time to contain, Expel a time to respond on high severity, Sophos an average for automated response (all read 10 Nov 2026). The statistic, the start point and the case mix differ, so measure your own cases in your own review. **What should I ask about OT coverage?** Ask which protocols and devices are monitored, whether response on OT assets is allowed and who approves it. Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, and Sophos lists OT as a separate service (read 10 Nov 2026). Scope is often narrower than a home page suggests. **Does MDR cover cloud workloads?** It depends on the service. Microsoft's Defender Experts overview says neither plan covers Defender for Cloud workloads such as storage, containers and databases, while Rapid7 says its MDR covers endpoint, cloud, identity, email and network (both read 10 Nov 2026). Read the scope list line by line before you sign. **What is the difference between a true positive and a false positive?** A true positive is an alert that correctly flags real malicious activity. A false positive flags harmless activity; NIST's glossary defines it as incorrectly classifying benign activity as malicious (read 10 Nov 2026). Sample a few closed alerts each month to check that benign closures were right. **What is detection engineering?** It is the work of writing, testing and tuning the rules that raise alerts. IDC says Kroll's detection engineering team rolls new rules out to EDR and SIEM platforms for all Responder clients (read 10 Nov 2026). Ask who writes rules for your sources, who owns them, and whether you keep them when you leave. **Is threat hunting part of MDR?** Often, but the wording varies. Expel lists threat hunters among the members of one 24x7 operations team, and SentinelOne names Threat Hunting as a service level beside MDR Essentials and MDR Elite (read 10 Nov 2026). Ask what is hunted, how often and how findings reach you. **What is MITRE ATT&CK, and why do providers cite it?** ATT&CK is a public knowledge base of adversary tactics and techniques; MITRE says it began in 2013 (read 10 Nov 2026). Providers map detections to it for a common vocabulary. A mapped technique shows intended coverage and not a guarantee that every attempt is caught, so ask for evidence on your sources. **What are ATT&CK Evaluations Managed Services?** They are a part of MITRE's ATT&CK Evaluations in which managed security services face an emulated adversary campaign. MITRE's data lists OilRig, published 22 November 2022, and menuPass with ALPHV BlackCat, published 18 June 2024 (read 10 Nov 2026). Read a round's own publication for what was tested and how. **What should a contract say about warranties?** Ask for the document. CrowdStrike states warranty coverage of up to $2 million for Falcon Complete, Kroll a $1 million incident protection warranty for qualifying clients, and SentinelOne up to $1 million (all read 10 Nov 2026). Read who qualifies, what costs are covered, what is excluded and who decides. **What if the provider changes its platform or owner?** Add a clause for notice and a right to leave. Kroll's August 2026 case study says it consolidated its MDR from five EDR and three SIEM platforms to CrowdStrike Falcon, and SentinelOne's older Vigilance MDR address now returns a 404 page (both read 10 Nov 2026). Platform changes happen, so plan for them. **What should I measure after go-live?** Measure coverage of assets and sources, time to first action, the quality of closed alerts, the quality of escalations and the speed of changes. Use your own case export and a monthly sample of closures. Published provider figures use different definitions, so they will not transfer to your environment. **Who should be on a reference call?** Ask for three references: one of your size and sector, one that had a real incident in the past year and one that changed scope or left. Providers publish customer statements on their sites, and those are statements as published by the provider (read 10 Nov 2026), not a substitute for your own call. **What is co-managed MDR?** It is a model in which your staff and the provider share the same tools and cases, for example your analysts by day and theirs at night. Deepwatch says it connects to a customer's existing SIEM, EDR, cloud, identity and SaaS tools (read 10 Nov 2026). Agree the shift hand-off in the runbook and test it. **Can MDR work with the tools I already own?** Several providers say so. Expel says no agents need deploying and that it plugs into an existing stack, and Sophos says its service includes 500+ integrations (both read 10 Nov 2026). Your own configuration still limits detection, so ask which sources the provider needs and which it treats as out of scope. **What is a runbook, and who writes it?** A runbook is a written set of steps for a type of event, naming who does what and with what approval. The provider usually drafts it and you approve it. Critical Start says its analysts run a customer-approved playbook on a confirmed threat (read 10 Nov 2026). Test it with a harmless alert in the first month. **What do I do first if I suspect a breach now?** Call the number in your incident plan and your provider's emergency line, preserve evidence and avoid rebuilding systems yet. NIST SP 800-61 Rev. 3 (April 2025) places incident response inside CSF 2.0 risk management, and the UK NCSC lists plan, build, develop and maintain stages (read 10 Nov 2026). Involve counsel and your insurer early. ## Related pages - [Home: MDR vs MSSP in short](/) - [MDR vs MSSP, the full comparison](/mdr-vs-mssp/) - [Guides](/guides/) - [Glossary](/glossary/) - [The MDR Service Matrix](/matrix/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/faq/ --- # A reference on MDR services: who watches, and what they may do About, read 10 November 2026 **In short.** MDR vs MSSP is a publication that lists managed detection and response services and sets out, from public sources, what each will do on the customer's behalf and on which data. It is written for the security lead whose team cannot staff nights. It ranks nobody. Its own work is the MDR Service Matrix and the MDR Question Sheet, both downloadable under CC BY 4.0. The voice is that of a SOC manager who has run two MDR selections: specific about contracts, data and clocks. ## Related pages - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact the editors](/contact/) - [Privacy](/privacy/) - [Terms of use](/terms/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/about/ --- # How pages are written, sourced and corrected Editorial policy, read 10 November 2026 **In short.** Every fact on MDR vs MSSP carries a source address and the date it was read. What a provider says about itself is labelled as the provider's. Nothing found is written "none found on" a date. Services appear alphabetically, and no page gives a verdict on any provider. Sources, in order of preference: regulators, analyst reports, MITRE evaluations, customers' own published statements, and the providers' own service descriptions and terms. Facts older than 60 days are re-read before they are used again. ## Related pages - [About this reference](/about/) - [Corrections](/corrections/) - [Contact the editors](/contact/) - [Privacy](/privacy/) - [Terms of use](/terms/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/editorial-policy/ --- # Corrections are made on the page and listed here Corrections, read 10 November 2026 **In short.** Send a correction with the page address, the fact you dispute and a source that shows the right fact. Providers may correct their own facts under the same rule. Every correction is dated on this page. No corrections have been made to the edition of 10 November 2026. Corrections change facts only where a source supports the change. ## Related pages - [About this reference](/about/) - [Editorial policy](/editorial-policy/) - [Contact the editors](/contact/) - [Privacy](/privacy/) - [Terms of use](/terms/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/corrections/ --- # Write to the editors Contact, read 10 November 2026 **In short.** The editors read every message sent to editor@mdrvsmssp.com. For a correction, give the page address, the fact and a source. Providers who want a fact checked should send the page of their own site that states it. There is no phone line and no advertising desk. Address: editor@mdrvsmssp.com. ## Related pages - [About this reference](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Privacy](/privacy/) - [Terms of use](/terms/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/contact/ --- # The site sets no cookies and runs no analytics scripts Privacy, read 10 November 2026 **In short.** MDR vs MSSP sets no cookies and loads no analytics or advertising scripts. The host keeps standard request logs (address, time, page, user agent) for security and to count page views in aggregate. Logs stay in the site's own storage and are not shared or sold. Messages to the editors are used only to answer and to make corrections. ## Related pages - [About this reference](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact the editors](/contact/) - [Terms of use](/terms/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/privacy/ --- # Terms of use Terms, read 10 November 2026 **In short.** Text and datasets on MDR vs MSSP may be quoted and reused under CC BY 4.0 with a link to the page. Facts are as published by their sources on the dates shown and are not advice for any specific environment. Confirm every term with the provider in writing before signing. Provider names and marks belong to their owners and are used to identify the services. ## Related pages - [About this reference](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact the editors](/contact/) - [Privacy](/privacy/) - [How this site lists services](/method/) Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/terms/