# 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/
