Macquarie Government vs Sapphire
Macquarie Government and Sapphire are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Sapphire serves SMB, Mid-market, and Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Buyer brief
Macquarie Government and Sapphire are both Services firms that work with your existing tools. Macquarie Government targets Enterprise organizations, while Sapphire serves SMB, Mid-market, and Enterprise. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 4 for Sapphire (Endpoint, Cloud, SaaS, Network).
Sapphire 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 | UK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC |
| 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 | Dashboards |
| 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
- 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 | Macquarie GovernmentTECH-AGNOSTIC | SapphireTECH-AGNOSTIC |
|---|---|---|
| Fit | ||
| Target size | Enterprise | SMB, Mid-market, Enterprise |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Works with your tools |
| EDR integrations | Customer endpoint security toolsWorkstation logs | EDR toolsMicrosoft technologies |
| SIEM integrations | Macquarie Government SIEMaaSSplunk EnterpriseCustomer SIEM platforms | ExabeamSIEM tools |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/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 | IsolateContainCustom playbooks | Custom 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 | ✓ Included |
| Cloud workloads | ✓ Included | ✓ Included |
| Identity | ~ Limited | ~ Limited |
| SaaS apps | ~ Limited | ✓ Included |
| 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. Sapphire 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 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 | Partial | Partial |
| Contract terms | SOCaaS subscription, SIEMaaS subscription, SASE for Government, Custom government procurement | Custom |
| Channels | PortalEmailPhone | PortalEmailPhone |
| Data access | Dashboards | Dashboards |
| 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. | Sapphire references onboarding and implementation that can be shorter than expected, but no standard public MDR onboarding timeline was found. |
| Industry focus | GovernmentDefensePublic SectorCritical Infrastructure | Public SectorDefenceFinancial ServicesProfessional ServicesIndustrialsManufacturingOperational TechnologyHealthcare |
| 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. | 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 | Essential 8ISMIRAPASDACSCDISP | ISO 27001NISTHIPAADORACyber Essentials PlusCRESTGDPRPCI DSS |
| Certifications | NV1-cleared specialistsIndustry Security Program memberAustralian Government Strategic certified data centresPROTECTED-level secure web gateway assessmentIRAP-aligned virtual services gateway language | CREST SOCCREST Penetration TestingCyber Essentials PlusISO 27001 |
| Founded | – | 1996 |
| 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 Sapphire?
Macquarie Government 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). Macquarie Government covers 3 attack surfaces in base pricing vs. 4 for Sapphire.
How do Macquarie Government and Sapphire differ in response capabilities?
Macquarie Government supports 3 autonomous actions (custom playbooks, endpoint isolation, network containment) and approval is configurable. Sapphire supports 1 autonomous actions (custom playbooks) and approval is configurable. Incident response is not included with Macquarie Government and included with Sapphire.
How does Macquarie Government pricing compare to Sapphire?
Macquarie Government pricing: Not published. Sapphire 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 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 Macquarie Government or Sapphire?
Choose Macquarie Government if: australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR. Choose Sapphire if: uK organisations that want MDR from a UK-owned provider with a UK-based CREST-accredited SOC. Macquarie Government is not ideal for private-sector or non-Australian buyers that do not need a government-specific sovereign provider. 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.