DOT Security vs Sapphire
DOT Security and Sapphire are both Services firms that work with your existing tools. DOT Security targets SMB and Mid-market organizations, while Sapphire serves SMB, Mid-market, and Enterprise. DOT Security includes 1 attack surfaces in base pricing (Endpoint), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Buyer brief
DOT Security and Sapphire are both Services firms that work with your existing tools. DOT Security targets SMB and Mid-market organizations, while Sapphire serves SMB, Mid-market, and Enterprise. DOT Security includes 1 attack surfaces in base pricing (Endpoint), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Sapphire 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 | UK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC |
| 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 | Dashboards |
| 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
- 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 | DOT SecurityTECH-AGNOSTIC | SapphireTECH-AGNOSTIC |
|---|---|---|
| ›› Fit | ||
| Target size | SMB, Mid-market | SMB, Mid-market, Enterprise |
| Sentiment | Mixed | Mixed |
| ›› Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | None listed | EDR toolsMicrosoft technologies |
| SIEM integrations | None listed | ExabeamSIEM tools |
| Coverage | EPEndpoint: CoveredCloudCloud: LimitedIDIdentity: Optional add-onSaaSSaaS: LimitedNetNetwork: Optional add-onOTOT/IoT: Not covered | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: CoveredNetNetwork: 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 | ✓ Included |
| ›› 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 | ~ Limited |
| SaaS apps | ~ Limited | ✓ Included |
| 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. Sapphire 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 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 | Limited | Partial |
| Contract terms | Custom | Custom |
| Channels | EmailPhone | PortalEmailPhone |
| Data access | Reports only | Dashboards |
| 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. | Sapphire references onboarding and implementation that can be shorter than expected, but no standard public MDR onboarding timeline was found. |
| Industry focus | HospitalityHealthcareManufacturingGovernmentConstructionFinancial Services | Public SectorDefenceFinancial ServicesProfessional ServicesIndustrialsManufacturingOperational TechnologyHealthcare |
| 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. | 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 | HIPAACMMCNISTCCPAGDPR | ISO 27001NISTHIPAADORACyber Essentials PlusCRESTGDPRPCI DSS |
| Certifications | – | CREST SOCCREST Penetration TestingCyber Essentials PlusISO 27001 |
| Founded | 2020 | 1996 |
| 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 Sapphire?
DOT Security 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). DOT Security covers 1 attack surfaces in base pricing vs. 4 for Sapphire.
How do DOT Security and Sapphire differ in response capabilities?
DOT Security supports 0 autonomous actions (none) and approval is configurable. Sapphire supports 1 autonomous actions (custom playbooks) and approval is configurable. Incident response is not included with DOT Security and included with Sapphire.
How does DOT Security pricing compare to Sapphire?
DOT Security pricing: Custom quote. No public price bands found.. Sapphire 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 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 DOT Security or Sapphire?
Choose DOT Security if: sMB and mid-market buyers that want endpoint MDR plus broader managed security guidance. Choose Sapphire if: uK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC. DOT Security is not ideal for buyers requiring public pricing, named EDR support or published detection metrics. 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.