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