Defendable vs Macquarie Government
Defendable and Macquarie Government are both Services firms that work with your existing tools. Defendable targets Mid-market and Enterprise organizations, while Macquarie Government serves Enterprise. Defendable includes 1 attack surfaces in base pricing (Endpoint), compared to 3 for Macquarie Government (Endpoint, Cloud, Network).
Buyer brief
Defendable and Macquarie Government are both Services firms that work with your existing tools. Defendable targets Mid-market and Enterprise organizations, while Macquarie Government serves Enterprise. Defendable includes 1 attack surfaces in base pricing (Endpoint), compared to 3 for Macquarie Government (Endpoint, Cloud, Network).
Macquarie Government offers broader coverage (3 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 | Australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR |
| Price | Custom quote | Custom quote |
| Response authority | 1/6 actions · Configurable | 3/6 actions · Configurable |
| Stack | Works with existing stack | Works with existing stack |
| Data access | Dashboards | Dashboards |
| 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
- 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
Detailed comparison
| FIELD | DefendableTECH-AGNOSTIC | Macquarie GovernmentTECH-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 toolsWorkstation logs |
| SIEM integrations | Microsoft Sentinel | Macquarie Government SIEMaaSSplunk EnterpriseCustomer SIEM platforms |
| Coverage | EPEndpoint: CoveredCloudCloud: LimitedIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: LimitedOTOT/IoT: Not covered | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Not covered |
| Response | ||
| Response type | Active Remediation | Active Remediation |
| Approval policy | Configurable | Configurable |
| Response actions | Custom playbooks | IsolateContainCustom 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 | ~ Limited | ✓ Included |
| Identity | ~ Limited | ~ Limited |
| SaaS apps | ~ Limited | ~ Limited |
| Network | ~ Limited | ✓ Included |
| OT/ICS | Not offered | Not offered |
| 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 government subscription and procurement model. SOCaaS, SIEMaaS and SASE pricing is 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 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. |
| Data portability | Partial | Partial |
| Contract terms | Custom, Incident Response Retainer | SOCaaS subscription, SIEMaaS subscription, SASE for Government, Custom government procurement |
| Channels | PortalEmailPhone | PortalEmailPhone |
| Data access | Dashboards | Dashboards |
| Dedicated analyst | – | – |
| SOC regions | Europe | APAC |
| Onboarding | Defendable publishes an MDR onboarding flow covering identification, planning, platform establishment and execution. It does not publish a standard onboarding duration. | Not published. Macquarie Government describes customized playbooks aligned with agency security processes and integration with existing security systems. |
| Industry focus | Not published | GovernmentDefensePublic SectorCritical Infrastructure |
| 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. | 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. |
| Compliance | ISO 27001Norwegian National Security Authority Quality Scheme for Incident Response | Essential 8ISMIRAPASDACSCDISP |
| Certifications | ISO 27001:2023Norwegian National Security Authority Quality Scheme for Incident ResponseEco-lighthouse certified | NV1-cleared specialistsIndustry Security Program memberAustralian Government Strategic certified data centresPROTECTED-level secure web gateway assessmentIRAP-aligned virtual services gateway language |
| 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. | 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. |
| API available | – | – |
| Website | Visit → | Visit → |
FAQ
What is the main difference between Defendable and Macquarie Government?
Defendable is a Services firm that is technology-agnostic (works with your existing tools). Macquarie Government is a Services firm that is technology-agnostic (works with your existing tools). Defendable covers 1 attack surfaces in base pricing vs. 3 for Macquarie Government.
How do Defendable and Macquarie Government differ in response capabilities?
Defendable supports 1 autonomous actions (custom playbooks) and approval is configurable. Macquarie Government supports 3 autonomous actions (custom playbooks, endpoint isolation, network containment) and approval is configurable.
How does Defendable pricing compare to Macquarie Government?
Defendable pricing: Not published. Macquarie Government 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 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..
Should I choose Defendable or Macquarie Government?
Choose Defendable if: norwegian and Nordic buyers that want MDR operated from Oslo and Gjovik. Choose Macquarie Government if: australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR. Defendable is not ideal for buyers that need public MDR pricing or contractual SLA terms before sales. Macquarie Government is not ideal for private-sector or non-Australian buyers that do not need a government-specific sovereign provider.
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.