DOT Security vs Tesorion
DOT Security and Tesorion are both Services firms that work with your existing tools. DOT Security targets SMB and Mid-market organizations, while Tesorion serves Mid-market and Enterprise. DOT Security includes 1 attack surfaces in base pricing (Endpoint), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Buyer brief
DOT Security and Tesorion are both Services firms that work with your existing tools. DOT Security targets SMB and Mid-market organizations, while Tesorion serves Mid-market and Enterprise. DOT Security includes 1 attack surfaces in base pricing (Endpoint), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Tesorion offers broader coverage (4 surfaces vs. 1). DOT Security may suit teams that need depth over breadth.
At a glance
| FIELD |  |  |
|---|---|---|
| Best fit | SMB and mid-market buyers that want endpoint MDR plus broader managed security guidance | Dutch organisations that want MDR from a Netherlands-based cybersecurity services firm |
| Price | Custom quote | Custom quote |
| Response authority | 0/6 actions · Configurable | 1/6 actions · Configurable |
| Stack | Works with existing stack | Works with existing stack |
| Data access | Reports only | Reports only |
| Warranty | None listed | None listed |
- Best fit
- SMB and mid-market buyers that want endpoint MDR plus broader managed security guidance
- Price
- Custom quote
- Response authority
- 0/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Reports only
- Warranty
- None listed
- 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 | DOT SecurityTECH-AGNOSTIC | TesorionTECH-AGNOSTIC |
|---|---|---|
| ›› Fit | ||
| Target size | SMB, Mid-market | Mid-market, Enterprise |
| Sentiment | Mixed | Mixed |
| ›› Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | None listed | SentinelOneCustomer endpoint telemetry |
| SIEM integrations | None listed | None listed |
| Coverage | EPEndpoint: CoveredCloudCloud: LimitedIDIdentity: Optional add-onSaaSSaaS: LimitedNetNetwork: Optional add-onOTOT/IoT: Not covered | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: CoveredSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Optional add-on |
| ›› Response | ||
| Response type | Active Remediation | Active Remediation |
| Approval policy | Configurable | Configurable |
| Response actions | Alert and notify only | Custom playbooks |
| IR included | Separate | Separate |
| ›› Cost | ||
| Price range | Custom quote. No public price bands found. | Not published |
| Minimum seats | None | None |
| Breach warranty | – | – |
| ›› More details | ||
| Requires own agent | No | No |
| Endpoints | ✓ Included | ✓ Included |
| Cloud workloads | ~ Limited | ✓ Included |
| Identity | + Optional | ✓ Included |
| SaaS apps | ~ Limited | ~ Limited |
| Network | + Optional | ✓ Included |
| OT/ICS | Not offered | + Optional |
| Threat hunting | Extra cost | ✓ Included |
| Response SLA | Not disclosed | Not disclosed |
| 24/7 coverage | ✓ | ✓ |
| Pricing model | Custom pricing. DOT does not publish endpoint, user, device or package pricing for MDR. | Custom quote. Tesorion does not publish MDR package pricing. |
| Hidden cost warnings | DOT positions its offering as a managed cybersecurity program, so buyers should separate endpoint MDR cost from compliance, vCISO, network monitoring and backup scope.. No public response SLA or detection metric was found.. Public materials emphasize customized stack design, which can make quotes harder to compare against per-endpoint MDR products.. Specific response actions and approval rules are not published. | 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 | Limited | Partial |
| Contract terms | Custom | Custom |
| Channels | EmailPhone | EmailPhone |
| Data access | Reports only | Reports only |
| Dedicated analyst | – | – |
| SOC regions | North America | Europe |
| Onboarding | DOT says every relationship begins with a cybersecurity risk audit or gap analysis, followed by stack design, deployment and ongoing management. No standard MDR onboarding timeline was found. | Tesorion says MDR use cases are tailored per organisation and linked to mitigating measures. No standard public onboarding duration was found. |
| Industry focus | HospitalityHealthcareManufacturingGovernmentConstructionFinancial Services | Financial ServicesHealthcarePublic SectorManufacturingCritical InfrastructureTechnologyProfessional Services |
| MTTD | Not published | Not published |
| MTTR | Not published | Not published |
| Community view | DOT Security has a current vendor-controlled MDR signal through its endpoint security page and a clear U.S.-based SOC story. Independent MDR review volume was not found in this pass, so buyer diligence should rely on references, a proof of value and careful quote scoping. | 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 | HIPAACMMCNISTCCPAGDPR | ISO 27001NEN 7510NIS2DORABIO |
| Certifications | – | ISO 27001NEN 7510 |
| Founded | 2020 | 2018 |
| Data retention | Not published | Not published as a standard MDR retention period. |
| API available | – | – |
| Website | Visit → | Visit → |
›› FAQ
What is the main difference between DOT Security and Tesorion?
DOT Security 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). DOT Security covers 1 attack surfaces in base pricing vs. 4 for Tesorion.
How do DOT Security and Tesorion differ in response capabilities?
DOT Security supports 0 autonomous actions (none) and approval is configurable. Tesorion supports 1 autonomous actions (custom playbooks) and approval is configurable.
How does DOT Security pricing compare to Tesorion?
DOT Security pricing: Custom quote. No public price bands found.. Tesorion pricing: Not published. Watch for with DOT Security: DOT positions its offering as a managed cybersecurity program, so buyers should separate endpoint MDR cost from compliance, vCISO, network monitoring and backup scope.; No public response SLA or detection metric was found.. 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 DOT Security or Tesorion?
Choose DOT Security if: sMB and mid-market buyers that want endpoint MDR plus broader managed security guidance. Choose Tesorion if: dutch organisations that want MDR from a Netherlands-based cybersecurity services firm. DOT Security is not ideal for buyers requiring public pricing, named EDR support or published detection metrics. 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.