Red Canary / Zscaler MDR
The 2025 report names Red Canary. Zscaler acquired it August 1, 2025; current docs call the service Zscaler MDR. Documentation distinguishes MDR from MDR + Active Remediation; do not assume active remediation in every package.
Documented focus
Correlates security telemetry with detection engineering and human investigations across customer environments.
Trade-offs and boundaries to verify
The 2025 report names Red Canary. Zscaler acquired it August 1, 2025; current docs call the service Zscaler MDR. Documentation distinguishes MDR from MDR + Active Remediation; do not assume active remediation in every package.
Public product documentation is not proof of entry-package entitlement. Confirm paid modules and unclear entitlements in the quote.
Confirm the named offering against your required workflow. A documented feature is evidence of product functionality, not a guarantee of your subscription entitlement or a measured result in your environment.
Product evidence at a glance
Verified consolidates established base inclusion and documented product capability. Package evidence is reported separately. Module / integration / activation, Outside assessed base, and Not established preserve the boundaries. Missing evidence is not a finding that a product lacks the capability.
| Research area | Evidence | Source |
|---|---|---|
| Managed monitoring | Not established | Official source ↗ |
| Analyst investigation | Not established | Official source ↗ |
| Managed response | Not established | Official source ↗ |
| Threat hunting | Verified | Official source ↗ |
| Existing-stack support | Verified | Official source ↗ |
| Cloud & identity | Verified | Official source ↗ |
| Service visibility | Verified | Official source ↗ |
| Guidance & improvement | Not established | Official source ↗ |
What to ask in a demonstration
- Which capabilities and integrations are included in the exact package being quoted?
- Demonstrate the workflow using representative data from our own environment.
- Who owns implementation, day-to-day operation, and each action during the pilot?
Package and implementation boundaries
Public product documentation is not proof of entry-package entitlement. Confirm paid modules and unclear entitlements in the quote.
Research date and scope
The underlying source record was checked October 28, 2026. This summary was published October 30, 2026. Source-check dates above identify retained research and any new checks separately. The publication date is not a new verification of every vendor claim. This is documentation-based buying research, not a hands-on review.
Read our research approach · Understand product and package evidence