Kroll vs Tesorion
Kroll and Tesorion are both Services firms that work with your existing tools. Kroll targets SMB, Mid-market, and Enterprise organizations, while Tesorion serves Mid-market and Enterprise. Kroll includes 5 attack surfaces in base pricing (Endpoint, Cloud, SaaS, Identity, Network), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Buyer brief
Kroll and Tesorion are both Services firms that work with your existing tools. Kroll targets SMB, Mid-market, and Enterprise organizations, while Tesorion serves Mid-market and Enterprise. Kroll includes 5 attack surfaces in base pricing (Endpoint, Cloud, SaaS, Identity, Network), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Kroll offers broader coverage (5 surfaces vs. 4). Tesorion 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 | Dutch organisations that want MDR from a Netherlands-based cybersecurity services firm |
| 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 | Reports only |
| 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
- Dutch organisations that want MDR from a Netherlands-based cybersecurity services firm
- Price
- Custom quote
- Response authority
- 1/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Reports only
- Warranty
- None listed
›› Detailed comparison
| FIELD | KrollTECH-AGNOSTIC | TesorionTECH-AGNOSTIC |
|---|---|---|
| ›› Fit | ||
| Target size | SMB, Mid-market, Enterprise | Mid-market, Enterprise |
| Sentiment | Positive | Mixed |
| ›› Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | CrowdStrike FalconMicrosoft Defender SentinelOne | Customer endpoint telemetry SentinelOne |
| SIEM integrations | Microsoft Sentinel | None listed |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: CoveredSaaSSaaS: CoveredNetNetwork: CoveredOTOT/IoT: Optional add-on | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: CoveredSaaSSaaS: LimitedNetNetwork: 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 | Separate |
| ›› 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 | ✓ Included |
| SaaS apps | ✓ Included | ~ Limited |
| 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. Tesorion 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 named default response actions.. The public MDR page says mitigation is immediate where possible, but does not specify what Tesorion can do without customer approval.. T-CERT incident response is prominent, but buyers should confirm whether IR hours are included in MDR or sold separately.. Tesorion lists broad coverage across domains, so buyers should confirm which monitored sources are included in base MDR. |
| Data portability | Partial | Partial |
| Contract terms | Annual, Multi-year | Custom |
| Channels | EmailPortalPhone | EmailPhone |
| Data access | Dashboards | Reports only |
| Dedicated analyst | ✓ | – |
| SOC regions | North AmericaEuropeAsia-Pacific | Europe |
| Onboarding | Varies by environment complexity | Tesorion says MDR use cases are tailored per organisation and linked to mitigating measures. No standard public onboarding duration was found. |
| Industry focus | Financial ServicesHealthcareGovernmentRetailTechnologyEducation | Financial ServicesHealthcarePublic SectorManufacturingCritical InfrastructureTechnologyProfessional Services |
| 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. | Tesorion has limited MDR-specific public review volume. The public buyer case rests on Dutch delivery, T-SOC operations, XDR and SOAR correlation, threat intelligence and nearby T-CERT incident response. Buyers should validate pricing, response authority, included source scope and whether T-CERT support is included before signing. |
| Compliance | SOC 2 Type IIISO 27001PCI DSS | ISO 27001NEN 7510NIS2DORABIO |
| Certifications | SOC 2 Type IIISO 27001CREST | ISO 27001NEN 7510 |
| Founded | 1972 | 2018 |
| 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 Tesorion?
Kroll is a Services firm that is technology-agnostic (works with your existing tools). Tesorion is a Services firm that is technology-agnostic (works with your existing tools). Kroll covers 5 attack surfaces in base pricing vs. 4 for Tesorion.
How do Kroll and Tesorion 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. Tesorion supports 1 autonomous actions (custom playbooks) and approval is configurable. Incident response is included with Kroll and not included with Tesorion.
How does Kroll pricing compare to Tesorion?
Kroll pricing: Not publicly disclosed. Unverified field estimates suggest $30K-$200K+/year depending on scope.. Tesorion 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 Tesorion: Public pages do not publish response SLAs or named default response actions.; The public MDR page says mitigation is immediate where possible, but does not specify what Tesorion can do without customer approval..
Should I choose Kroll or Tesorion?
Choose Kroll if: organizations wanting IR expertise built into MDR with 3,000+ annual cases feeding detection. Choose Tesorion if: dutch organisations that want MDR from a Netherlands-based cybersecurity services firm. Kroll is not ideal for organizations that need vendor-agnostic EDR choice (CrowdStrike migration reduces flexibility). Tesorion 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.