Macquarie Government vs VikingCloud
Macquarie Government is a Services firm that works with your existing tools. VikingCloud is a Platform vendor that requires its own security platform. Macquarie Government targets Enterprise organizations; VikingCloud serves SMB and Mid-market. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 2 for VikingCloud (Endpoint, Network).
Buyer brief
Macquarie Government is a Services firm that works with your existing tools. VikingCloud is a Platform vendor that requires its own security platform. Macquarie Government targets Enterprise organizations; VikingCloud serves SMB and Mid-market. Macquarie Government includes 3 attack surfaces in base pricing (Endpoint, Cloud, Network), compared to 2 for VikingCloud (Endpoint, Network).
VikingCloud is the choice if you want a single-vendor stack with deep integration. Macquarie Government is better if you have existing tools and want flexibility.
At a glance
| FIELD |  |  |
|---|---|---|
| Best fit | Australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR | Retail, hospitality, and financial services organizations where PCI DSS compliance is the primary driver for buying MDR |
| Price | Custom quote | Not published |
| Response authority | 3/6 actions · Configurable | 1/6 actions · Configurable |
| Stack | Works with existing stack | Requires own platform |
| 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
- Retail, hospitality, and financial services organizations where PCI DSS compliance is the primary driver for buying MDR
- Price
- Not published
- Response authority
- 1/6 actions · Configurable
- Stack
- Requires own platform
- Data access
- Dashboards
- Warranty
- None listed
Detailed comparison
| FIELD | Macquarie GovernmentTECH-AGNOSTIC | VikingCloudPLATFORM |
|---|---|---|
| Fit | ||
| Target size | Enterprise | SMB, Mid-market |
| Sentiment | Mixed | Mixed |
| Your stack | ||
| Approach | Works with your tools | Requires their platform |
| EDR integrations | Customer endpoint security toolsWorkstation logs | VikingCloud Endpoint Security |
| SIEM integrations | Macquarie Government SIEMaaSSplunk EnterpriseCustomer SIEM platforms | VikingCloud Managed SIEM |
| Coverage | EPEndpoint: CoveredCloudCloud: CoveredIDIdentity: LimitedSaaSSaaS: LimitedNetNetwork: CoveredOTOT/IoT: Not covered | EPEndpoint: CoveredCloudCloud: Not coveredIDIdentity: LimitedSaaSSaaS: Not coveredNetNetwork: CoveredOTOT/IoT: Not covered |
| Response | ||
| Response type | Active Remediation | Guided Response |
| Approval policy | Configurable | Configurable |
| Response actions | IsolateContainCustom playbooks | Quarantine |
| IR included | Separate | Separate |
| Cost | ||
| Price range | Not published | Not published |
| Minimum seats | None | None |
| Breach warranty | – | – |
| More details | ||
| Requires own agent | No | Yes |
| Endpoints | ✓ Included | ✓ Included |
| Cloud workloads | ✓ Included | Not offered |
| Identity | ~ Limited | ~ Limited |
| SaaS apps | ~ Limited | Not offered |
| Network | ✓ Included | ✓ Included |
| OT/ICS | Not offered | Not offered |
| 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 pricing, not publicly disclosed. VikingCloud uses quote-based pricing requiring direct sales consultation. |
| 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. | Pricing is completely opaque: no public ranges, no published minimums, quote-only. Requires VikingCloud's proprietary endpoint agent (Bitdefender-based), replacing your existing EDR. DFIR incident response is a separate retainer, not included in base MDR. The 4M customer base is mostly compliance clients. Ask how many are active MDR customers to gauge service maturity. |
| Data portability | Partial | Limited |
| Contract terms | SOCaaS subscription, SIEMaaS subscription, SASE for Government, Custom government procurement | Annual |
| Channels | PortalEmailPhone | EmailPhonePortal |
| Data access | Dashboards | Dashboards |
| Dedicated analyst | – | – |
| SOC regions | APAC | North AmericaEuropeAsia-Pacific |
| Onboarding | Not published. Macquarie Government describes customized playbooks aligned with agency security processes and integration with existing security systems. | Not published. Agent installation is described as one-click download. |
| Industry focus | GovernmentDefensePublic SectorCritical Infrastructure | RetailQuick Service RestaurantsFinancial ServicesHospitalityHealthcareTravel and Tourism |
| MTTD | Not published | Not published |
| MTTR | Not published | Less than 30 minutes (vendor blog claim, not independently validated) |
| 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. | Very limited public reviews for VikingCloud's MDR service specifically. The company is established in PCI compliance consulting (100+ QSAs, 35-year heritage) but has near-zero visibility in practitioner communities discussing MDR. No Reddit discussions found. Four customer testimonials on Featured Customers are positive but compliance-focused, not about detection and response quality. |
| Compliance | Essential 8ISMIRAPASDACSCDISP | PCI DSSISO 27001SOC 2 |
| Certifications | NV1-cleared specialistsIndustry Security Program memberAustralian Government Strategic certified data centresPROTECTED-level secure web gateway assessmentIRAP-aligned virtual services gateway language | PCI QSA (Qualified Security Assessor Company)PCI ASV (Approved Scanning Vendor)PCI PFI (Payment Card Industry Forensic Investigator) |
| Founded | – | 1989 |
| 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 |
| API available | – | – |
| Website | Visit → | Visit → |
FAQ
What is the main difference between Macquarie Government and VikingCloud?
Macquarie Government is a Services firm that is technology-agnostic (works with your existing tools). VikingCloud is a Platform vendor that is platform-native (requires their own security stack). Macquarie Government covers 3 attack surfaces in base pricing vs. 2 for VikingCloud.
How do Macquarie Government and VikingCloud differ in response capabilities?
Macquarie Government supports 3 autonomous actions (custom playbooks, endpoint isolation, network containment) and approval is configurable. VikingCloud supports 1 autonomous actions (file quarantine) and approval is configurable.
How does Macquarie Government pricing compare to VikingCloud?
Macquarie Government pricing: Not published. VikingCloud pricing: Custom-quoted pricing. 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 VikingCloud: Pricing is completely opaque: no public ranges, no published minimums, quote-only; Requires VikingCloud's proprietary endpoint agent (Bitdefender-based), replacing your existing EDR.
Should I choose Macquarie Government or VikingCloud?
Choose Macquarie Government if: australian Commonwealth and state agencies that require sovereign onshore SOCaaS and MDR. Choose VikingCloud if: retail, hospitality, and financial services organizations where PCI DSS compliance is the primary driver for buying MDR. Macquarie Government is not ideal for private-sector or non-Australian buyers that do not need a government-specific sovereign provider. VikingCloud is not ideal for organizations with existing EDR investments wanting vendor-agnostic MDR (VikingCloud requires their own endpoint agent).
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.