# Critical Start and Huntress, 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 Huntress, 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; Huntress 1 stated, 2 with limits, 3 none found. The page gives no verdict.

## How do Critical Start and Huntress differ?

On the six actions read, Critical Start has 3 stated, 2 with limits, 1 none found, and Huntress has 1 stated, 2 with limits, 3 none found. On the seven data sources read, Critical Start has 7 stated, 0 with limits, 0 none found, and Huntress has 1 stated, 4 with limits, 2 none found.

## Actions on the customer's behalf

| Action | Critical Start | Huntress |
| --- | --- | --- |
| Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated The provider says its SOC contains threats and evicts them from endpoints. |
| Disable or reset an account | Stated Lists identity actions including disable account and reset password. | Stated with limits A customer quoted by Huntress cites disable account remediations for BEC (customer statement). |
| Block an IP, domain, hash or email | Stated Lists block file hash, block IP and block sender. | None found on 10 November 2026 |
| Kill a process or remove a file | Stated with limits The provider says its customer-approved playbook may include process termination. | None found on 10 November 2026 |
| Act in a cloud or SaaS console | None found on 10 November 2026 | Stated with limits Managed ITDR covers Microsoft 365 and Google Workspace identity threats with automated remediation. |
| Acts without asking first (pre-approved) | Stated with limits Analysts run the customer-approved playbook; customer approves or rejects containment, notice ahead available. | None found on 10 November 2026 |

## Data watched

| Data | Critical Start | Huntress |
| --- | --- | --- |
| Endpoint | Stated Lists endpoint response actions. | Stated Native agents cover Windows, macOS and Linux. |
| Identity | Stated Lists identity response actions. | Stated with limits The provider says Managed ITDR covers Microsoft 365 and Google Workspace identity; it is priced separately. |
| Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated with limits Managed SIEM page says it connects cloud services activity. |
| Network | Stated Lists network response actions such as block IP. | Stated with limits Managed SIEM page says it connects network activity. |
| 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. | None found on 10 November 2026 |
| Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated with limits Managed EDR includes Huntress's own agent; Managed SIEM connects other sources. |

## The fifteen questions

| Question | Critical Start | Huntress |
| --- | --- | --- |
| 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. | Huntress says a 24/7 human-led SOC investigates and acts, and a human reviews every alert; a separate IR team none found. |
| What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Huntress says the SOC contains threats and removes the attacker's foothold; on ransomware indicators it takes action fast. |
| Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Huntress says its platform covers endpoints, identities and logs; Managed SIEM connects endpoints, identities, networks and cloud services. |
| Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Huntress says Managed EDR pairs its own lightweight agent with its SOC and does not rely on other vendors' EDR 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. | Huntress says its SOC and threat hunters work together; its Threat Library links a 2026 Cyber Threat 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. | Huntress says its price includes everything with no add-ons; included IR hours not stated. |
| 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. | Huntress publishes $8.99 per endpoint per month (Managed EDR) and $4.80 per licensed identity per month (Managed ITDR). |
| 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. | Huntress says Managed ITDR covers identity threats in Microsoft 365 and Google Workspace; Managed SIEM connects cloud services. |
| 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 | Huntress |
| --- | --- | --- |
| Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Huntress publishes prices ($8.99 per endpoint, $4.80 per identity per month) and says a human reviews every alert before it reaches the customer. |
| Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Huntress Managed EDR uses its own agent, identity and SIEM coverage are separate products, and none found on 10 Nov 2026 for a separate IR team, included IR hours 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

- [Critical Start, all published facts](/services/critical-start/)
- [Huntress, all published facts](/services/huntress/)
- [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)
- Huntress, "Managed EDR" page (the firm's own page): https://www.huntress.com/platform/managed-edr (read 10 November 2026)
- Huntress, "Managed ITDR" page (the firm's own page): https://www.huntress.com/platform/managed-itdr (read 10 November 2026)
- Huntress, "Pricing" page (the firm's own page): https://www.huntress.com/pricing (read 10 November 2026)

Last reviewed 10 November 2026. Canonical: https://mdrvsmssp.com/side-by-side/critical-start-and-huntress/
