Side by side, read 10 Nov 2026
Critical Start and Deepwatch, side by side: what each says it will do, and on which data
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 Nov 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 Nov 2026 | None 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 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. |
| Stated Lists email actions such as quarantine message. | None found on 10 Nov 2026 | |
| OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | None found on 10 Nov 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
- Deepwatch, all published facts
- The MDR Service Matrix
- All side-by-side pages
Sources
- Critical Start, "MDR" page (the firm's own page), read 10 Nov 2026
- Deepwatch, "Active response" page (the firm's own page), read 10 Nov 2026
Last reviewed 10 Nov 2026.