Kroll vs Sapphire
Kroll and Sapphire are both Services firms that work with your existing tools. Kroll targets SMB, Mid-market, and Enterprise organizations, while Sapphire serves SMB, Mid-market, and Enterprise. Kroll includes 5 attack surfaces in base pricing (Endpoint, Cloud, SaaS, Identity, Network), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Buyer brief
Kroll and Sapphire are both Services firms that work with your existing tools. Kroll targets SMB, Mid-market, and Enterprise organizations, while Sapphire serves SMB, Mid-market, and Enterprise. Kroll includes 5 attack surfaces in base pricing (Endpoint, Cloud, SaaS, Identity, Network), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Kroll offers broader coverage (5 surfaces vs. 4). Sapphire may suit teams that need depth over breadth.
At a glance
| FIELD | ||
|---|---|---|
| Best fit | Organizations wanting IR expertise built into MDR with 3,000+ annual cases feeding detection | UK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC |
| Price | Unverified MDR field estimate: $30K-$200K+/yr | Custom quote |
| Response authority | 6/6 actions · Configurable | 1/6 actions · Configurable |
| Stack | Works with existing stack | Works with existing stack |
| Data access | Dashboards | Dashboards |
| Warranty | $1,000,000 | None listed |
- Best fit
- Organizations wanting IR expertise built into MDR with 3,000+ annual cases feeding detection
- Price
- Unverified MDR field estimate: $30K-$200K+/yr
- Response authority
- 6/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Dashboards
- Warranty
- $1,000,000
- Best fit
- UK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC
- Price
- Custom quote
- Response authority
- 1/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Dashboards
- Warranty
- None listed
›› Detailed comparison
| FIELD | KrollTECH-AGNOSTIC | SapphireTECH-AGNOSTIC |
|---|---|---|
| ›› Fit | ||
| Target size | SMB, Mid-market, Enterprise | SMB, Mid-market, Enterprise |
| Sentiment | Positive | Mixed |
| ›› Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | CrowdStrike FalconMicrosoft DefenderSentinelOne | EDR toolsMicrosoft technologies |
| SIEM integrations | Microsoft Sentinel | ExabeamSIEM tools |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: CoveredSaaSSaaS: CoveredNetNetwork: CoveredOTOT/IoT: Optional add-on | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: CoveredNetNetwork: CoveredOTOT/IoT: Optional add-on |
| ›› Response | ||
| Response type | Active Remediation | Active Remediation |
| Approval policy | Configurable | Configurable |
| Response actions | IsolateKill processContainDisable accountsQuarantineCustom playbooks | Custom playbooks |
| IR included | ✓ Included | ✓ Included |
| ›› Cost | ||
| Price range | Not publicly disclosed. Unverified field estimates suggest $30K-$200K+/year depending on scope. | Not published |
| Minimum seats | None | None |
| Breach warranty | $1,000,000 | – |
| ›› More details | ||
| Requires own agent | No | No |
| Endpoints | ✓ Included | ✓ Included |
| Cloud workloads | ✓ Included | ✓ Included |
| Identity | ✓ Included | ~ Limited |
| SaaS apps | ✓ Included | ✓ Included |
| Network | ✓ Included | ✓ Included |
| OT/ICS | + Optional | + Optional |
| Threat hunting | ✓ Included | ✓ Included |
| Response SLA | Not disclosed | Not disclosed |
| 24/7 coverage | ✓ | ✓ |
| Pricing model | Custom quote-based pricing, not publicly disclosed | Custom quote. Sapphire does not publish MDR package pricing. |
| Hidden cost warnings | CrowdStrike Falcon Complete migration (Dec 2025) increases platform dependency, customers wanting vendor-agnostic EDR lose that flexibility. Named TAM support (vs. Shared TAM) likely incurs additional cost, cost delta not disclosed. No published minimum seat requirements or pricing, likely enterprise-focused | Public pages do not publish response SLAs or exact response-authority rules.. MDR, MXDR and OT SOC scope can differ materially, so buyers should define monitored surfaces in the order form.. The page publishes vendor-reported comparative metrics without independent methodology.. IR hours are included as standard, but buyers should confirm number of hours, coverage triggers and overage rates. |
| Data portability | Partial | Partial |
| Contract terms | Annual, Multi-year | Custom |
| Channels | EmailPortalPhone | PortalEmailPhone |
| Data access | Dashboards | Dashboards |
| Dedicated analyst | ✓ | – |
| SOC regions | North AmericaEuropeAsia-Pacific | Europe |
| Onboarding | Varies by environment complexity | Sapphire references onboarding and implementation that can be shorter than expected, but no standard public MDR onboarding timeline was found. |
| Industry focus | Financial ServicesHealthcareGovernmentRetailTechnologyEducation | Public SectorDefenceFinancial ServicesProfessional ServicesIndustrialsManufacturingOperational TechnologyHealthcare |
| MTTD | Not published | Not published |
| MTTR | Not published | Not published |
| Community view | Trusted for deep IR pedigree and Complete Response methodology. Gartner Peer Insights 4.6/5 (26 reviews). KuppingerCole MDR Leader 2023. Lower market visibility than pure-play MDR brands (~0.4% PeerSpot mindshare). December 2025 CrowdStrike migration generates mixed reactions around vendor lock-in. | Sapphire has limited MDR-specific community review volume. The public buyer case is strongest for UK ownership, UK-based SOC delivery, CREST SOC accreditation and IT/OT services depth. Buyers should validate response authority, price, metrics and the exact split between MDR, MXDR, OT SOC and incident-response work. |
| Compliance | SOC 2 Type IIISO 27001PCI DSS | ISO 27001NISTHIPAADORACyber Essentials PlusCRESTGDPRPCI DSS |
| Certifications | SOC 2 Type IIISO 27001CREST | CREST SOCCREST Penetration TestingCyber Essentials PlusISO 27001 |
| Founded | 1972 | 1996 |
| Data retention | Not publicly disclosed. | Not published as a standard MDR retention period. |
| API available | ✓ | – |
| Website | Visit → | Visit → |
›› FAQ
What is the main difference between Kroll and Sapphire?
Kroll is a Services firm that is technology-agnostic (works with your existing tools). Sapphire is a Services firm that is technology-agnostic (works with your existing tools). Kroll covers 5 attack surfaces in base pricing vs. 4 for Sapphire.
How do Kroll and Sapphire differ in response capabilities?
Kroll supports 6 autonomous actions (account disable, custom playbooks, endpoint isolation, file quarantine, network containment, process termination) and approval is configurable. Sapphire supports 1 autonomous actions (custom playbooks) and approval is configurable.
How does Kroll pricing compare to Sapphire?
Kroll pricing: Not publicly disclosed. Unverified field estimates suggest $30K-$200K+/year depending on scope.. Sapphire pricing: Not published. Watch for with Kroll: CrowdStrike Falcon Complete migration (Dec 2025) increases platform dependency, customers wanting vendor-agnostic EDR lose that flexibility; Named TAM support (vs. Shared TAM) likely incurs additional cost, cost delta not disclosed. Watch for with Sapphire: Public pages do not publish response SLAs or exact response-authority rules.; MDR, MXDR and OT SOC scope can differ materially, so buyers should define monitored surfaces in the order form..
Should I choose Kroll or Sapphire?
Choose Kroll if: organizations wanting IR expertise built into MDR with 3,000+ annual cases feeding detection. Choose Sapphire if: uK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC. Kroll is not ideal for organizations that need vendor-agnostic EDR choice (CrowdStrike migration reduces flexibility). Sapphire is not ideal for buyers that need public MDR pricing or contractual response SLAs before sales engagement.
Daylight Security
AI-native MDR for buyers comparing active remediation across endpoint, cloud, identity, and SaaS. Daylight works with existing EDR/SIEM stacks and uses ChatOps-native collaboration, so it can be a useful third reference point in this comparison.