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

## How do Critical Start and Sygnia differ?

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

## Actions on the customer's behalf

| Action | Critical Start | Sygnia |
| --- | --- | --- |
| Isolate a host | Stated Lists endpoint response actions including isolate host. | Stated with limits Client-approved automated isolation for defined scenarios; human experts approve environment-affecting actions. |
| Disable or reset an account | Stated Lists identity actions including disable account and reset password. | None found on 10 November 2026 |
| 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 | None found on 10 November 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 with limits Automated actions only for defined scenarios the client authorizes, under agreed policies. |

## Data watched

| Data | Critical Start | Sygnia |
| --- | --- | --- |
| Endpoint | Stated Lists endpoint response actions. | Stated Sygnia says Velocity ingests endpoint data. |
| Identity | Stated Lists identity response actions. | Stated Alternate MDR page lists identity among integrated data sources. |
| Cloud | Stated The provider says cloud is covered by detection; its cloud response is advisory. | Stated Velocity ingests cloud data across hybrid cloud, per Sygnia. |
| Network | Stated Lists network response actions such as block IP. | Stated Velocity ingests network data, per Sygnia. |
| Email | Stated Lists email actions such as quarantine message. | Stated Alternate MDR page lists email among data sources. |
| OT | Stated The provider says OT is read-only monitoring, with Claroty, Nozomi and Defender for IoT integrations. | Stated Sygnia states OT monitoring, including legacy OT systems. |
| Works on other vendors' tools | Stated Says 100+ integrations and no proprietary agents required. | Stated Sygnia describes its model as vendor agnostic with 250+ integrations. |

## The fifteen questions

| Question | Critical Start | Sygnia |
| --- | --- | --- |
| 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. | Sygnia says each client has a named team of 8 experts, and analysts work closely with its IR teams on the same platform. |
| What may the provider do without asking first? | Critical Start says analysts run the customer-approved playbook; the customer approves or rejects containment actions. | Sygnia says clients can authorize automated actions such as isolating an endpoint for defined scenarios; human experts approve actions affecting the environment. |
| Which data sources does the service monitor? | Critical Start says CORR supports 100+ integrations across seven security domains. | Sygnia says Velocity ingests endpoint, identity, network, cloud, application and email data, plus OT. |
| Is the provider's own endpoint agent required? | Critical Start says it requires no proprietary agents and connects to existing stack by API. | Sygnia describes its model as 100% vendor-agnostic; a January 2023 release also mentions a proprietary light-weight agent. |
| 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. | Sygnia lists Threat Hunting as a separate service with a report; the MDR pages read do not state hunting as included. |
| 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. | Sygnia's August 2026 AWS release says every MDR engagement includes an Incident Response Retainer; included hours are 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. | Sygnia says most escalations start in under one hour after detection; it prints no SLA minutes or credits. |
| Is the pricing model published? | Critical Start says MDR pricing is not published and varies by environment, integration scope and engagement level. | Sygnia's AWS Marketplace listing shows a 12-month contract at $1.00 per undefined unit; scope and quantity are agreed with Sygnia. |
| Is OT covered? | Critical Start lists OT/ICS as escalation, advisory and read-only monitoring, with Defender for IoT, Claroty xDome and Nozomi integrations. | Sygnia states monitoring of OT, including legacy OT systems, with visibility across IT, OT and hybrid cloud. |
| 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. | Sygnia says Velocity ingests cloud data and integrates identity sources, with cloud and hybrid cloud visibility. |
| How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 (a 2023 release mentions faster deployment with a light-weight agent, with no time stated). |
| What reporting does the customer receive? | Critical Start's SLA page publishes service credit remedies; report formats none found on 10 Nov 2026. | Sygnia states 24/7/365 protection and says it resolves 95% of alerts without involving the client's team; report formats none found. |
| 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 | Sygnia |
| --- | --- | --- |
| Does well | Critical Start lists named response actions across endpoint, identity, network and email, and publishes SLA credits. | Sygnia says it covers endpoint, identity, network, cloud, email and OT data and runs vendor-agnostic across 250+ integrations. |
| Limited | Critical Start lists cloud response as advisory and detection only, OT as read-only monitoring, and says MDR pricing is not published. | Sygnia's pages list isolation as an example action but none found on 10 Nov 2026 for account disable, IP block or process kill, and no SLA minutes are printed. |

## 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/)
- [Sygnia, all published facts](/services/sygnia/)
- [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)
- Sygnia, "Managed detection and response copy" page (the firm's own page): https://www.sygnia.co/solutions/managed-detection-and-response-copy/ (read 10 November 2026)

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