Defendable vs Thales (S21sec)
Defendable and Thales (S21sec) are both Services firms that work with your existing tools. Defendable targets Mid-market and Enterprise organizations, while Thales (S21sec) serves Enterprise. Defendable includes 1 attack surfaces in base pricing (Endpoint), compared to 2 for Thales (S21sec) (Network, OT/ICS).
Buyer brief
Defendable and Thales (S21sec) are both Services firms that work with your existing tools. Defendable targets Mid-market and Enterprise organizations, while Thales (S21sec) serves Enterprise. Defendable includes 1 attack surfaces in base pricing (Endpoint), compared to 2 for Thales (S21sec) (Network, OT/ICS).
Thales (S21sec) offers broader coverage (2 surfaces vs. 1). Defendable may suit teams that need depth over breadth.
At a glance
| FIELD |  |  |
|---|---|---|
| Best fit | Norwegian and Nordic buyers that want MDR operated from Oslo and Gjovik | Critical infrastructure and public-sector buyers that need Thales/S21sec regional cyber detection and response |
| Price | Custom quote | Custom quote |
| Response authority | 1/6 actions · Configurable | 2/6 actions · Configurable |
| Stack | Works with existing stack | Works with existing stack |
| Data access | Dashboards | Reports only |
| Warranty | None listed | None listed |
- Best fit
- Norwegian and Nordic buyers that want MDR operated from Oslo and Gjovik
- Price
- Custom quote
- Response authority
- 1/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Dashboards
- Warranty
- None listed
- Best fit
- Critical infrastructure and public-sector buyers that need Thales/S21sec regional cyber detection and response
- Price
- Custom quote
- Response authority
- 2/6 actions · Configurable
- Stack
- Works with existing stack
- Data access
- Reports only
- Warranty
- None listed
Detailed comparison
| FIELD | DefendableTECH-AGNOSTIC | Thales (S21sec)TECH-AGNOSTIC |
|---|---|---|
| Fit | ||
| Target size | Mid-market, Enterprise | Enterprise |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | Microsoft Defender | Customer endpoint security tools |
| SIEM integrations | Microsoft Sentinel | Customer SIEM platformsThales SOC tooling |
| Coverage | EPEndpoint: CoveredCloudCloud: LimitedIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: LimitedOTOT/IoT: Not covered | EPEndpoint: LimitedCloudCloud: LimitedIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Covered |
| Response | ||
| Response type | Active Remediation | Active Remediation |
| Approval policy | Configurable | Configurable |
| Response actions | Custom playbooks | ContainCustom playbooks |
| IR included | Separate | ✓ Included |
| Cost | ||
| Price range | Not published | Not published |
| Minimum seats | None | None |
| Breach warranty | – | – |
| More details | ||
| Requires own agent | No | No |
| Endpoints | ✓ Included | ~ Limited |
| Cloud workloads | ~ Limited | ~ Limited |
| Identity | ~ Limited | ~ Limited |
| SaaS apps | ~ Limited | ~ Limited |
| Network | ~ Limited | ✓ Included |
| OT/ICS | Not offered | ✓ Included |
| Threat hunting | ✓ Included | ✓ Included |
| Response SLA | Not disclosed | Not disclosed |
| 24/7 coverage | ✓ | ✓ |
| Pricing model | Custom quote. Defendable does not publish MDR package pricing. | Custom quote for Thales Cyber Detection and Response, Managed Security Services, SOC and MDR. Public prices are not published. |
| Hidden cost warnings | Public pages do not publish MDR pricing, contract minimums or service-credit language.. Response authority should be defined in writing because named autonomous endpoint and identity actions are not published.. Log storage can sit in the customer's Microsoft Log Analytics tenant or Defendable's platform, so retention and storage costs should be modeled early.. Incident-response retainer SLA is separate language and should not be assumed to be the MDR SLA.. Threat hunting is public, but hunt cadence and staffing are not published. | The current S21sec domain routes to Thales-branded services, so buyers wanting legacy S21sec-specific delivery should confirm contracting entity, SOC location and delivery team.. Public pages do not publish prices, minimum terms, service credits, MTTD/MTTR or formal MDR SLAs.. Thales offers a broad cybersecurity services portfolio; buyers should separate base MDR scope from CTI, DRPS, DFIR, CERT, ICS monitoring and advisory services.. Named endpoint, identity and cloud containment actions are not public and should be confirmed tool by tool.. Data retention, raw log access, offboarding and detection-content export rights are not described publicly. |
| Data portability | Partial | Partial |
| Contract terms | Custom, Incident Response Retainer | Custom cyber detection and response engagement, Managed Security Services, SOC and MDR, Critical-infrastructure cybersecurity services |
| Channels | PortalEmailPhone | EmailPhonePortal |
| Data access | Dashboards | Reports only |
| Dedicated analyst | – | – |
| SOC regions | Europe | EuropeMEAAPAC |
| Onboarding | Defendable publishes an MDR onboarding flow covering identification, planning, platform establishment and execution. It does not publish a standard onboarding duration. | Not published. Thales describes customer-centric service roadmaps and selecting/deploying detection and response technologies, but no standard MDR onboarding timeline. |
| Industry focus | Not published | Critical InfrastructureGovernmentDefenseEnergyManufacturingAviationSpaceFinancial ServicesTelecommunicationsHealthcareTransportationAutomotiveUtilitiesMaritime |
| MTTD | Not published | Not published |
| MTTR | Not published | Not published |
| Community view | Defendable has limited MDR-specific public review volume in major English-language review communities. The public buyer case rests on Norwegian SOC delivery, a direct MDR page, Microsoft Sentinel support, proactive threat hunting, a customer portal and incident-response depth. Buyers should validate pricing, response authority, retention cost and contractual SLA terms directly. | The current public evidence is strong for Thales-branded global SOC, MDR, CTI, DFIR and critical-infrastructure detection and response, but weak for S21sec as a standalone public MDR brand. Buyers should validate current delivery model, SOC location, response authority, pricing and whether the contract is with Thales/S21sec in the relevant country. |
| Compliance | ISO 27001Norwegian National Security Authority Quality Scheme for Incident Response | DORATIBER-EUPCI DSSEASA Part-ISEASAICAOUNECE |
| Certifications | ISO 27001:2023Norwegian National Security Authority Quality Scheme for Incident ResponseEco-lighthouse certified | 8 threat intelligence and AI-driven SOCs around the worldSOCs in France, Morocco, the Netherlands, Belgium and Luxembourg, Portugal and Spain, and New Zealand and Australia |
| Founded | 2020 | – |
| Data retention | Defendable says customers can store additional log data in their own Microsoft Log Analytics tenant or in Defendable's log management platform. It does not publish standard MDR retention periods. | Not published. Public pages do not describe default log retention, raw log access, storage tiers or export terms for Thales SOC and MDR. |
| API available | – | – |
| Website | Visit → | Visit → |
FAQ
What is the main difference between Defendable and Thales (S21sec)?
Defendable is a Services firm that is technology-agnostic (works with your existing tools). Thales (S21sec) is a Services firm that is technology-agnostic (works with your existing tools). Defendable covers 1 attack surfaces in base pricing vs. 2 for Thales (S21sec).
How do Defendable and Thales (S21sec) differ in response capabilities?
Defendable supports 1 autonomous actions (custom playbooks) and approval is configurable. Thales (S21sec) supports 2 autonomous actions (custom playbooks, network containment) and approval is configurable. Incident response is not included with Defendable and included with Thales (S21sec).
How does Defendable pricing compare to Thales (S21sec)?
Defendable pricing: Not published. Thales (S21sec) pricing: Not published. Watch for with Defendable: Public pages do not publish MDR pricing, contract minimums or service-credit language.; Response authority should be defined in writing because named autonomous endpoint and identity actions are not published.. Watch for with Thales (S21sec): The current S21sec domain routes to Thales-branded services, so buyers wanting legacy S21sec-specific delivery should confirm contracting entity, SOC location and delivery team.; Public pages do not publish prices, minimum terms, service credits, MTTD/MTTR or formal MDR SLAs..
Should I choose Defendable or Thales (S21sec)?
Choose Defendable if: norwegian and Nordic buyers that want MDR operated from Oslo and Gjovik. Choose Thales (S21sec) if: critical infrastructure and public-sector buyers that need Thales/S21sec regional cyber detection and response. Defendable is not ideal for buyers that need public MDR pricing or contractual SLA terms before sales. Thales (S21sec) is not ideal for buyers that need a standalone legacy S21sec-branded MDR package.
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.