Macquarie Government vs Thales (S21sec)
Macquarie Government and Thales (S21sec) are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Thales (S21sec) serves Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 2 for Thales (S21sec) (Network, OT/ICS).
Buyer brief
Macquarie Government and Thales (S21sec) are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Thales (S21sec) serves Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 2 for Thales (S21sec) (Network, OT/ICS).
Macquarie Government offers broader coverage (3 surfaces vs. 2). Thales (S21sec) may suit teams that need depth over breadth.
At a glance
| FIELD | ||
|---|---|---|
| Best fit | Australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR | Critical infrastructure and public-sector buyers that need Thales/S21sec regional cyber detection and response |
| Price | Custom quote | Custom quote |
| Response authority | 3/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
- Australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR
- Price
- Custom quote
- Response authority
- 3/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 | Macquarie GovernmentTECH-AGNOSTIC | Thales (S21sec)TECH-AGNOSTIC |
|---|---|---|
| Fit | ||
| Target size | Enterprise | Enterprise |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | Workstation logs Customer endpoint security tools | Customer endpoint security tools |
| SIEM integrations | Macquarie Government SIEMaaSSplunk Enterprise Customer SIEM platforms | Thales SOC tooling Customer SIEM platforms |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Not covered | EPEndpoint: LimitedCloudCloud: LimitedIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Covered |
| Response | ||
| Response type | Active Remediation | Active Remediation |
| Approval policy | Configurable | Configurable |
| Response actions | IsolateContainCustom 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 | ✓ Included | ~ Limited |
| Identity | ~ Limited | ~ Limited |
| SaaS apps | ~ Limited | ~ Limited |
| Network | ✓ Included | ✓ Included |
| OT/ICS | Not offered | ✓ Included |
| Threat hunting | ✓ Included | ✓ Included |
| Response SLA | Not disclosed | Not disclosed |
| 24/7 coverage | ✓ | ✓ |
| Pricing model | Custom government subscription and procurement model. SOCaaS, SIEMaaS and SASE pricing is not published. | Custom quote for Thales Cyber Detection and Response, Managed Security Services, SOC and MDR. Public prices are not published. |
| Hidden cost warnings | The service is explicitly built for Australian Commonwealth and state government agencies, so private-sector and non-Australian buyers may not be eligible or may not fit the operating model.. Public pages do not publish prices, minimum terms, MTTD/MTTR, service credits or formal MDR SLAs.. SOCaaS is closely tied to Macquarie Government SIEMaaS, Splunk, sovereign hosting, SASE and gateway services; model migration work if replacing the service later.. Buyers should document which automated response actions are allowed by default and which require agency approval.. Log retention, ingestion, secure cloud, SASE and CTI options can materially change the total contract scope. | 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 | SOCaaS subscription, SIEMaaS subscription, SASE for Government, Custom government procurement | 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 | APAC | EuropeMEAAPAC |
| Onboarding | Not published. Macquarie Government describes customized playbooks aligned with agency security processes and integration with existing security systems. | Not published. Thales describes customer-centric service roadmaps and selecting/deploying detection and response technologies, but no standard MDR onboarding timeline. |
| Industry focus | GovernmentDefensePublic SectorCritical Infrastructure | Critical InfrastructureGovernmentDefenseEnergyManufacturingAviationSpaceFinancial ServicesTelecommunicationsHealthcareTransportationAutomotiveUtilitiesMaritime |
| MTTD | Not published | Not published |
| MTTR | Not published | Not published |
| Community view | Macquarie Government has strong vendor-controlled evidence for Australian government sovereignty, 24x7 SOC operations, SIEMaaS, threat intelligence and SASE integration, but little independent MDR-specific buyer-review signal in public communities. Government buyers should use procurement references to validate analyst quality, response authority, onboarding effort and Splunk/log-volume cost exposure. | 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 | Essential 8ISMIRAPASDACSCDISP | DORATIBER-EUPCI DSSEASA Part-ISEASAICAOUNECE |
| Certifications | NV1-cleared specialistsIndustry Security Program memberAustralian Government Strategic certified data centresPROTECTED-level secure web gateway assessmentIRAP-aligned virtual services gateway language | 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 | – | – |
| Data retention | SIEMaaS pages describe sovereign local hosting and storage of up to seven years of security and event information. Public pages do not publish default retention for SOCaaS contracts or export terms. | 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 Macquarie Government and Thales (S21sec)?
Macquarie Government 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). Macquarie Government covers 3 attack surfaces in base pricing vs. 2 for Thales (S21sec).
How do Macquarie Government and Thales (S21sec) differ in response capabilities?
Macquarie Government supports 3 autonomous actions (custom playbooks, endpoint isolation, network containment) and approval is configurable. Thales (S21sec) supports 2 autonomous actions (custom playbooks, network containment) and approval is configurable. Incident response is not included with Macquarie Government and included with Thales (S21sec).
How does Macquarie Government pricing compare to Thales (S21sec)?
Macquarie Government pricing: Not published. Thales (S21sec) pricing: Not published. Watch for with Macquarie Government: The service is explicitly built for Australian Commonwealth and state government agencies, so private-sector and non-Australian buyers may not be eligible or may not fit the operating model.; Public pages do not publish prices, minimum terms, MTTD/MTTR, service credits or formal MDR SLAs.. 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 Macquarie Government or Thales (S21sec)?
Choose Macquarie Government if: australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR. Choose Thales (S21sec) if: critical infrastructure and public-sector buyers that need Thales/S21sec regional cyber detection and response. Macquarie Government is not ideal for private-sector or non-Australian buyers that do not need a government-specific sovereign provider. 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.