Sovereign data centres in Australia: what to check beyond the address
Your provider has confirmed that the data will stay in Australia. That’s a useful answer, but it doesn’t tell you who can administer the environment, where support is delivered from or which entities control the service. Those details matter when you’re deciding whether a hosting arrangement meets your sovereignty requirements.
A practical review separates data location, operational access and corporate control. We’ll work through the evidence behind each, including backups, key custody and subcontractors, so you can turn a broad sovereignty promise into questions a provider can answer. Use the findings with your legal and security advisers to assess the obligations that apply to your workload.
What is a Sovereign data centre?
A sovereign data centre is a facility that provides organisations with greater control over where their data is stored, who can access it and which legal jurisdictions govern its management. In Australia, data centre sovereignty goes beyond keeping data within national borders.
Give each sovereignty question its own answer
A facility address is easy to confirm. The less visible details often take more work: whether an overseas team can administer supporting systems, who holds encryption keys, or how a change in ownership would affect the service. Keep those questions in the review even when the proposed facility is local.
For due diligence, it helps to organise these issues as data location, operational sovereignty and corporate sovereignty. These are practical assessment lenses, not a universal certification test. Record the evidence and any gap separately; a strong answer on one does not resolve the others. Our data sovereignty guide provides further context for this review.
Data location: follow every copy
Start with primary storage, then follow the copies. Include backups, replicas, disaster recovery targets and any monitoring or support data collected about the environment. Confirm which parts you manage and which the provider manages. A sovereign colocation service may supply the physical environment while your team controls replication, applications and keys.
Ask where encryption keys are generated, stored and escrowed, and who can use them. Record the same information for relevant provider management systems. Key location and custody can change the access risk even when the underlying data stays in Australia, so make those arrangements explicit in the architecture and contract.
Operational data centre sovereignty: who can reach the systems
Work from the equipment outwards. Who can enter the hall, unlock a cabinet, perform remote hands work or administer the supporting systems? Confirm the access required for each role and the relevant vetting or clearance. Where government clearances are required, ask for an appropriate assurance process and issuing-authority details rather than seeking unrestricted access to personnel records.
Extend the review to monitoring, service desks and engineering subcontractors. Establish where each function is delivered and what access it has. For example, remote hands support involves someone physically working on your equipment, so it needs a clear authorisation and logging process. Offshore involvement should be assessed against the actual access and service scope, not inferred from a staffing label alone.
Corporate sovereignty: who ultimately controls the provider
Trace the ownership chain to the ultimate parent and identify the jurisdictions relevant to the operating entity. Ask about board control and any investment or financing arrangements that confer control. Your legal advisers can then assess the implications for lawful access. Australian ownership is relevant to that assessment, but it does not replace scrutiny of contracts, access and applicable law.
Ask how the provider handles lawful access requests and when it can notify customers, recognising that disclosure may be legally restricted. Check the change-of-control clause too. If the business is acquired or a support arrangement changes, you need a way to reassess the service rather than discover the change at renewal.
Use assurance frameworks to support the review
Certification and assessment evidence can answer parts of the sovereignty question. It still needs to match the service you intend to use. Start with the certifications relevant to the deployment, then check the entity, facility and control boundaries behind each claim.
For government workloads, check the Hosting Certification Framework and its certified-service register. Certified Strategic is the framework’s highest level, but confirm the exact service scope. The HCF website currently records a pause from 3 November 2025 on new registrations and supplementary assessments during reform; existing certifications are not impacted. If your procurement depends on a future certification or extension, verify that pathway before relying on it.
If the SOCI regime applies to your organisation or asset, confirm the relevant obligations and the evidence you need from the provider. Risk-management requirements vary by asset class. For government physical security, have your security adviser identify the applicable PSPF zone, certification and accreditation requirements for the proposed space. A portfolio-level security statement cannot establish the scope of a particular room or hall.
For Defence work, confirm the applicable DISP membership domains and levels. At the systems layer, request the scope and findings of any relevant IRAP assessment; it is an assessment, not system certification. MDC’s government colocation information is a starting point for discussing the facilities, personnel and evidence available for a proposed service.
The evidence request table
Use this table to make the evidence request specific. Where a document cannot be shared in full, ask what scoped, redacted or independently verified evidence is available. Record what remains unverified and the impact on your decision.
| Sovereignty dimension | What to establish | Document or artefact to request |
| Data location | Where every copy resides, including backups, replicas and disaster recovery | Data flow and residency statement covering all environments and copies |
| Telemetry and tooling | Where provider monitoring and support data about your environment is held | Description of management plane architecture and its hosting locations |
| Key custody | Where keys are generated, stored and escrowed, and who can access them | Key management policy and the list of roles with key access |
| Physical access | Which roles can enter your halls and cages, and under what authorisation | Access control procedure, plus a sample access log for the facility |
| Personnel vetting | Clearance levels held by on-site staff and the issuing authority | Vetting and clearance policy, issuing-authority details and agreed verification process |
| Support chain | Whether any support, monitoring or engineering is offshore or subcontracted | Service delivery model and the subcontractor register with vetting standards |
| Corporate control | Ownership chain, parent jurisdiction, foreign debt or investment, board composition | Corporate structure diagram and the change of control clause in the contract |
| Certification status | Which certifications apply to the specific site, and whether they are current | Certificates with scope and expiry, verified against the relevant public register |
Reading the response critically
Check that the response answers the question you asked. Does a certificate cover the proposed site, or another part of the business? Is the evidence current, and does it describe the service you’ll receive? An assertion without supporting material leaves a question open; follow it up before treating it as an established control.
Then reconcile the commitments with the contract. Review the service description, access and location obligations, notification requirements and remedies. Where marketing material and contract wording differ, ask the provider and your legal team to resolve the gap before signature.
Data centre sovereignty due diligence checklist
Document the answer, supporting evidence and any unresolved condition for each item. This record should be usable by the people who will manage the supplier after procurement.
• Physical location of primary data, backups, replicas and disaster recovery copies
• Location of monitoring, telemetry and support tooling data about your environment
• Where encryption keys are generated, stored and escrowed, and who can access them
• Named list of roles with physical access to your halls and cages
• Clearance or vetting requirements for relevant staff, issuing-authority details and an appropriate verification process
• Whether any support, monitoring or engineering function is performed offshore
• Use of subcontractors for on-site work, and how they are vetted
• Full corporate ownership chain and the jurisdiction of the ultimate parent
• Foreign debt or foreign investment conferring control, and board composition
• Policy on responding to foreign lawful access requests, and customer notification
• Change of control provisions in the contract and their effect on your data
• Hosting Certification Framework status, verified against the framework register
• Certificates naming the specific facility, with scope statements and expiry dates
• Applicable physical security zone, certification and accreditation evidence for the proposed space
• IRAP assessment scope and date, described accurately as assessed rather than certified
• The contracted service level, its outage definition, exclusions and remedy
The useful outcome is a clear account of where your information goes, who can reach it and how control can change. Keep that account with the contract and supplier review record. It gives your team something concrete to revisit as the service and your requirements evolve.
Looking for a data centre partner that can support your infrastructure today and as your requirements evolve? Macquarie Data Centres provides secure, resilient and scalable data centre solutions for hyperscale, enterprise, government and cloud environments.
Contact us to discuss your requirements, learn more about our team, or request a tour to see our facilities firsthand.
Frequently asked questions
What is a sovereign data centre?
A sovereign data centre offering needs to be assessed against your requirements for data location, operational access and corporate control. An Australian location alone does not establish those arrangements. There is no single marketing label that replaces a review of the service, ownership, access paths and relevant legal obligations.
Is data stored in Australia automatically sovereign?
No. Location does not answer who can access the environment, where keys are controlled or which jurisdictions apply to the organisations delivering it. Review those details together, including any offshore support, then assess the arrangement against the requirements for your workload.
What is Certified Strategic under the Hosting Certification Framework?
Certified Strategic is the highest level under the Australian Government’s Hosting Certification Framework. Check the register for the certified entity and service scope. The framework is undergoing reform, so confirm current requirements and any effect on new or supplementary assessments when you procure.
Can a provider be IRAP certified?
IRAP provides independent security assessments, not certification of a provider or system. Ask for the assessment scope, date, findings and relevant system boundaries. An assessment does not by itself establish that every control is met or that the system is authorised for your use.
What evidence should I request to verify sovereignty?
Request the corporate ownership chain and the ultimate parent’s jurisdiction, the physical location of all data copies including backups and telemetry, key custody arrangements, a list of roles with physical access and their clearance levels, whether any support is performed offshore, certification documents naming the specific site, and the change of control provisions in the contract.
How often should sovereignty be reassessed?
Set a review cycle based on risk and contract obligations, with additional checks when ownership, support locations, subcontractors or certification status change. Agree notification triggers so your organisation can respond when the arrangements behind the original assessment change.