Side by side, read 10 Nov 2026
Deepwatch and Rapid7, side by side: what each says it will do, and on which data
How do Deepwatch and Rapid7 differ?
On the six actions read, Deepwatch has 4 stated, 0 with limits, 2 none found, and Rapid7 has 2 stated, 0 with limits, 4 none found. On the seven data sources read, Deepwatch has 5 stated, 0 with limits, 2 none found, and Rapid7 has 5 stated, 1 with limits, 1 none found.
Actions on the customer's behalf
| Action | Deepwatch | Rapid7 |
|---|---|---|
| Isolate a host | Stated Active Response lists host isolation for endpoints. | Stated The provider says the team contains affected assets remotely, aligned to the customer's approved policies. |
| Disable or reset an account | Stated Active Response lists password reset and account control actions. | None found on 10 Nov 2026 |
| Block an IP, domain, hash or email | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| Kill a process or remove a file | Stated Active Response lists process termination for endpoints. | None found on 10 Nov 2026 |
| 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 Active Response is opt-in; actions run automatically, with analyst approval, or monitor-only, as the customer sets. | Stated The provider says response actions follow the customer's approved policies. |
Data watched
| Data | Deepwatch | Rapid7 |
|---|---|---|
| Endpoint | Stated Platform page shows endpoint in the environment it works with. | Stated MDR page lists endpoint. |
| Identity | Stated Platform page shows identity. | Stated MDR page lists identity. |
| Cloud | Stated Platform page shows cloud. | Stated MDR page lists cloud. |
| Network | Stated Platform page shows network. | Stated MDR page lists network. |
| None found on 10 Nov 2026 | Stated MDR page lists email. | |
| OT | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| Works on other vendors' tools | Stated Calls itself agnostic with a Bring Your Own Tech approach. | Stated with limits Provides SOC support for supported third-party tools with 190+ integrations; its own agent is also offered. |
The fifteen questions
| Question | Deepwatch | Rapid7 |
|---|---|---|
| Who watches the environment around the clock, and who handles a major incident? | Deepwatch names security analysts for triage, investigation and response; its ATI group includes DFIR professionals and an emergency operations center. | Rapid7 says its SOC and Incident Response team both act when a threat is detected, performing forensic analysis. |
| What may the provider do without asking first? | Deepwatch says Active Response is opt-in and nothing happens without the customer's say-so; actions can be automatic, approved or monitor-only. | Rapid7 says the team contains affected assets remotely and takes response actions aligned to the customer's approved policies. |
| Which data sources does the service monitor? | Deepwatch shows SIEM, endpoint, cloud, identity and network, and says it supports 800+ telemetry sources. | Rapid7 says native telemetry plus third-party ingestion covers endpoint, cloud, identity, email and network. |
| Is the provider's own endpoint agent required? | Deepwatch says it is agnostic with a Bring Your Own Tech approach connecting to existing SIEM, EDR, cloud, identity and SaaS tools. | Rapid7 offers its own agent; IDC says it can also integrate with any third-party EPP in the customer's stack. |
| Is threat hunting included, and what output is published? | Deepwatch says its MDR includes proactive threat hunting and it publishes Deepwatch Labs reports weekly with hunts. | Rapid7 lists proactive threat hunting in its packages and a Quarterly Threat Landscape Report (Q3 2026); hunt findings none found. |
| Are incident response hours included, or is a retainer needed? | Deepwatch lists 24/7/365 response; whether IR hours or a retainer come with MDR none found on 10 Nov 2026. | Rapid7 says IR is unlimited and not tied to hours; a breach protection warranty is a separate row. |
| What response-time commitments are published? | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| Is the pricing model published? | None found on 10 Nov 2026 | Rapid7 states asset-based pricing (endpoints, servers, networks), not SIEM data volume or incident count; three packages, no dollar prices. |
| Is OT covered? | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| What cloud and identity coverage is stated? | Deepwatch shows cloud and identity in the environment; Active Response covers identities and endpoints. | Rapid7 says its MDR covers cloud and identity; its Microsoft page operationalizes Defender across identity and cloud. |
| How long does onboarding take? | None found on 10 Nov 2026 | None found on 10 Nov 2026 |
| What reporting does the customer receive? | Deepwatch says its Security Center gives a consolidated view of alert volume, incidents and actions. | Rapid7 says every action in the SOC is logged, explainable and auditable. |
| 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? | Deepwatch says customers see what it sees, with no black box of anonymous alerts or events. | IDC says Rapid7 customers can see what the Rapid7 team sees and build dashboards alongside experts. |
| 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 | Deepwatch | Rapid7 |
|---|---|---|
| Does well | Deepwatch lets the customer define eligible detections and actions through a Response Intent Matrix, with named endpoint and identity actions. | Rapid7 says IR is unlimited with no cap on hours, and states an asset-based pricing model not tied to incident count. |
| Limited | 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. | Rapid7 prints no dollar prices, lists no OT coverage, and says SOC-managed monitoring applies to supported tools. |
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
- Deepwatch, all published facts
- Rapid7, all published facts
- The MDR Service Matrix
- All side-by-side pages
Sources
- Deepwatch, "Active response" page (the firm's own page), read 10 Nov 2026
- Rapid7, "Managed detection and response MDR" page (the firm's own page), read 10 Nov 2026
Last reviewed 10 Nov 2026.