Skip to content

Side by side, read 10 Nov 2026

Critical Start and Expel, side by side: what each says it will do, and on which data

Set any two services side by side

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

ActionCritical StartExpel
Isolate a hostStated Lists endpoint response actions including isolate host.None found on 10 Nov 2026
Disable or reset an accountStated Lists identity actions including disable account and reset password.None found on 10 Nov 2026
Block an IP, domain, hash or emailStated Lists block file hash, block IP and block sender.None found on 10 Nov 2026
Kill a process or remove a fileStated with limits The provider says its customer-approved playbook may include process termination.None found on 10 Nov 2026
Act in a cloud or SaaS consoleNone found on 10 Nov 2026None found on 10 Nov 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

DataCritical StartExpel
EndpointStated Lists endpoint response actions.Stated Packages page lists endpoints.
IdentityStated Lists identity response actions.Stated Packages page lists identity.
CloudStated The provider says cloud is covered by detection; its cloud response is advisory.Stated Packages page lists cloud workloads and control planes.
NetworkStated Lists network response actions such as block IP.Stated Packages page lists networks.
EmailStated Lists email actions such as quarantine message.None found on 10 Nov 2026
OTStated 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' toolsStated Says 100+ integrations and no proprietary agents required.Stated Says no agents need to be deployed; pulls telemetry from 160+ tools.

The fifteen questions

QuestionCritical StartExpel
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 2026None 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 2026None found on 10 Nov 2026
Can the customer's analysts see what the provider sees?None found on 10 Nov 2026Expel says customers see every alert, investigation and action in Workbench.
What are the exit and data-return terms?None found on 10 Nov 2026None found on 10 Nov 2026

What each does well, and where each is limited

FieldCritical StartExpel
Does wellCritical 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.
LimitedCritical 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.

Sources

  1. Critical Start, "MDR" page (the firm's own page), read 10 Nov 2026
  2. Expel, "Auto remediation" page (the firm's own page), read 10 Nov 2026

Last reviewed 10 Nov 2026.