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