Macquarie Government vs Tesorion
Macquarie Government and Tesorion are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Tesorion serves Mid-market and Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Buyer brief
Macquarie Government and Tesorion are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Tesorion serves Mid-market and Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 4 for Tesorion (Endpoint, Cloud, Identity, Network).
Tesorion offers broader coverage (4 surfaces vs. 3). Macquarie Government 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 | Dutch organisations that want MDR from a Netherlands-based cybersecurity services firm |
| Price | Custom quote | Custom quote |
| Response authority | 3/6 actions · Configurable | 1/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
- 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 | Macquarie GovernmentTECH-AGNOSTIC | TesorionTECH-AGNOSTIC |
|---|---|---|
| Fit | ||
| Target size | Enterprise | Mid-market, Enterprise |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | Customer endpoint security toolsWorkstation logs | SentinelOneCustomer endpoint telemetry |
| SIEM integrations | Macquarie Government SIEMaaSSplunk EnterpriseCustomer SIEM platforms | None listed |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/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 | IsolateContainCustom playbooks | Custom playbooks |
| IR included | Separate | Separate |
| Cost | ||
| Price range | Not published | Not published |
| Minimum seats | None | None |
| Breach warranty | – | – |
| More details | ||
| Requires own agent | No | No |
| Endpoints | ✓ Included | ✓ Included |
| Cloud workloads | ✓ Included | ✓ Included |
| Identity | ~ Limited | ✓ Included |
| SaaS apps | ~ Limited | ~ Limited |
| Network | ✓ Included | ✓ Included |
| OT/ICS | Not offered | + Optional |
| 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. Tesorion does not publish MDR package pricing. |
| 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. | 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 | SOCaaS subscription, SIEMaaS subscription, SASE for Government, Custom government procurement | Custom |
| Channels | PortalEmailPhone | EmailPhone |
| Data access | Dashboards | Reports only |
| Dedicated analyst | – | – |
| SOC regions | APAC | Europe |
| Onboarding | Not published. Macquarie Government describes customized playbooks aligned with agency security processes and integration with existing security systems. | Tesorion says MDR use cases are tailored per organisation and linked to mitigating measures. No standard public onboarding duration was found. |
| Industry focus | GovernmentDefensePublic SectorCritical Infrastructure | Financial ServicesHealthcarePublic SectorManufacturingCritical InfrastructureTechnologyProfessional Services |
| 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. | 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 | Essential 8ISMIRAPASDACSCDISP | ISO 27001NEN 7510NIS2DORABIO |
| Certifications | NV1-cleared specialistsIndustry Security Program memberAustralian Government Strategic certified data centresPROTECTED-level secure web gateway assessmentIRAP-aligned virtual services gateway language | ISO 27001NEN 7510 |
| Founded | – | 2018 |
| 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 as a standard MDR retention period. |
| API available | – | – |
| Website | Visit → | Visit → |
FAQ
What is the main difference between Macquarie Government and Tesorion?
Macquarie Government 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). Macquarie Government covers 3 attack surfaces in base pricing vs. 4 for Tesorion.
How do Macquarie Government and Tesorion differ in response capabilities?
Macquarie Government supports 3 autonomous actions (custom playbooks, endpoint isolation, network containment) and approval is configurable. Tesorion supports 1 autonomous actions (custom playbooks) and approval is configurable.
How does Macquarie Government pricing compare to Tesorion?
Macquarie Government pricing: Not published. Tesorion 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 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 Macquarie Government or Tesorion?
Choose Macquarie Government if: australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR. Choose Tesorion if: dutch organisations that want MDR from a Netherlands-based cybersecurity services firm. Macquarie Government is not ideal for private-sector or non-Australian buyers that do not need a government-specific sovereign provider. 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.