Security Insights · Sovereign cloud · 8 min read
Secure File Sharing in Australia: A Sovereign Cloud Checklist
Secure file sharing in Australia: what to check before choosing, from sovereign cloud hosting and the CLOUD Act to APP 8, APP 11, IRAP and who holds the keys.
A file sharing provider that says your files are hosted in Australia has answered one question. It hasn't said where backups and logs are kept, which foreign laws reach the company, or whether its own staff can open your files.
This guide covers what an Australian organization should check before choosing a file sharing service, with a checklist to send to providers.
What should you check before choosing secure file sharing in Australia?
Before choosing secure file sharing in Australia, check five things: where files and every copy of them are stored, which countries' laws can compel the provider, how the service supports your Privacy Act obligations, whether it meets government requirements such as IRAP and the Hosting Certification Framework, and who holds the keys that open your files.
What is a sovereign cloud in Australia?
A sovereign cloud is a cloud service that keeps data in Australia and limits who can reach it, including foreign governments, through the way the provider is owned, operated and supported. "Sovereign cloud" is an industry term, not a certification, and hosting in Australia is only part of it: our guide to data sovereignty explains why. For Australian Government work, the official test of these qualities is the Hosting Certification Framework, covered below.
1. Where your files are stored and replicated
For Australian cloud storage, "hosted in Australia" should cover every copy: the primary files, replicas, backups, disaster recovery sites, logs and metadata. For government buyers, control ISM-1572 in the Australian Signals Directorate's Information Security Manual (ISM) calls for contracts to document the regions or availability zones where data is processed, stored and communicated, with a minimum notification period for configuration changes.
2. Which countries' laws can compel access
Location is only part of the answer. The US CLOUD Act, enacted in March 2018, requires providers of electronic communication or remote computing services to comply with US legal process to preserve or disclose data in their "possession, custody, or control", whether the data is stored inside or outside the United States (18 U.S.C. 2713).
The ISM warns Australian buyers that offshore services may be subject to lawful and covert data collection without customers' knowledge, and that foreign-owned suppliers operating in Australia may be subject to a foreign government's lawful access to their customers' data.
3. What the Privacy Act expects
Three parts of the Privacy Act 1988 apply directly to file sharing.
- APP 8, cross-border disclosure: before disclosing personal information to an overseas recipient, an entity must take reasonable steps to ensure the recipient does not breach the Australian Privacy Principles, and under section 16C it is generally accountable for the recipient's breaches. The OAIC's APP 8 guidelines say that giving personal information to an overseas cloud provider only to store it may be a use rather than a disclosure, if a binding contract keeps the entity in effective control.
- APP 11, security: an entity must take reasonable steps to protect the personal information it holds from misuse, interference and loss, and from unauthorized access, modification or disclosure. APP 11.3, added in 2024, says those steps include technical and organizational measures. The OAIC's APP 11 guidelines include third-party providers, such as cloud computing, in those steps.
- The Notifiable Data Breaches (NDB) scheme: organizations and agencies covered by the Privacy Act must notify affected individuals and the OAIC when a data breach is likely to result in serious harm. Section 26WG of the Privacy Act lists what to weigh, including whether the information was protected by security measures, how likely it is that those measures could be overcome, and whether the people who obtained it could get the information needed to circumvent them. A note to the section gives an encryption key as an example.
4. Government work: IRAP, the PSPF and the Hosting Certification Framework
Non-corporate Commonwealth entities must apply the Protective Security Policy Framework (PSPF). Two requirements in PSPF Release 2026 shape the choice of a file sharing service:
- IRAP: Requirement 0109 directs entities to use cloud service providers that have completed an IRAP assessment against the latest ISM within the previous 24 months. Our IRAP assessment guide explains what the assessment covers.
- Hosting certification: Requirement 0111 requires security classified information to be hosted using a cloud or data center service certified under the Hosting Certification Framework (HCF) or its successor, HCF 2.
The Hosting Certification Framework certifies data center and cloud service providers against requirements for data sovereignty, ownership, control and supply chain. The Department of Home Affairs runs it, having taken it over from the Digital Transformation Agency on 1 May 2023. Under the framework, sensitive government data, whole-of-government systems and systems rated PROTECTED must be hosted using certified services. The HCF is being reformed: registrations from new providers were paused from 3 November 2025, and PSPF Release 2026 expects certification under HCF 2 to open in late 2026 or early 2027.
5. Who can read your files
Encryption only protects files from people without the keys. If a provider generates and holds the keys, it can decrypt your files, and so can anyone who compels or compromises the provider. With zero-knowledge, end-to-end encryption, files are encrypted on the sender's device and decrypted on the recipient's, and the provider stores only ciphertext it cannot open.
That bears on both legal risks above. The US Department of Justice says CLOUD Act agreements are "encryption-neutral" and will not resolve the challenges end-to-end encryption poses for law enforcement, where decryption capability is limited to the end user. A provider can still be ordered to hand over what it holds, but with zero knowledge that is ciphertext. And under section 26WG, whether someone could obtain the key is part of judging a breach.
Checklist: questions to ask a file sharing provider
| Question | Why it matters | What a good answer looks like |
|---|---|---|
| Where are our files, backups, logs and metadata stored? | Copies held overseas can bring other laws into play | Named Australian regions for every copy, written into the contract, with notice before any change |
| Which countries' laws apply to the provider, its parent company and its support staff? | Laws such as the US CLOUD Act follow the provider, wherever the data is stored | A clear list of jurisdictions, including owners and support locations |
| Who holds the encryption keys? | A provider that holds the keys can decrypt files if it is compelled or breached | Keys handled on users' devices; the provider stores only ciphertext |
| Can support staff see our files? | Making personal information accessible to someone overseas can be a disclosure under APP 8 | No standing access; support sees only a file you choose to share, for a limited time, and it is logged |
| Does the service have a current IRAP assessment? | PSPF Requirement 0109 sets a 24-month window for cloud providers | Assessed against the latest ISM in the past 24 months, at the classification you need |
| Is the hosting certified under the HCF? | PSPF Requirement 0111 applies to security classified government information | A stated HCF certification for the cloud or data center services that host your data |
| What is logged, and can we export it? | Records of who accessed what help you assess a suspected breach | Every view, download and share recorded, with export to your own tools |
Where DekkoCORE fits
DekkoCORE is hosted in Australia for customers who choose Australia at setup. Data is replicated within the country and never moves to another region unless the customer authorizes it or the law requires it. Files are encrypted on the user's device with AES-256 keys before they're uploaded; DekkoCORE stores only ciphertext and never has the keys, so not even DekkoSecure can read them. Support sees a file only if a user chooses to share that one file, and that access is time-limited and logged.
DekkoCORE is IRAP assessed to PROTECTED, and the assessment documentation is shared with security teams on request. Every view, download, signature, approval and version is logged. Read more about secure file sharing.
Common questions
Frequently Asked Questions
What is a sovereign cloud?
A sovereign cloud is a cloud service that keeps data in one country and limits who can reach it, including foreign governments, through how the service is owned, operated and supported. For Australian Government hosting, the Hosting Certification Framework tests these qualities.
Can a foreign government access files stored in Australia?
A foreign government can sometimes reach files stored in Australia through the company that holds them. The US CLOUD Act requires providers subject to US jurisdiction to disclose data in their possession, custody or control wherever it is stored. If the files are end-to-end encrypted and the provider has no keys, what it holds is ciphertext.
Is using an overseas cloud provider a disclosure under APP 8?
Using an overseas cloud provider is not always a disclosure under APP 8. The OAIC says that giving personal information to an overseas provider only to store it may be a use, if a binding contract limits the provider to that purpose and keeps the entity in effective control. Otherwise APP 8 applies.
Do you have to report a data breach involving encrypted files?
Whether a breach of encrypted files must be reported depends on the likely risk of serious harm. Section 26WG of the Privacy Act asks whether the information was protected by security measures and whether the people who obtained it could get what they need to circumvent them, such as an encryption key.
What does zero knowledge mean in file sharing?
Zero knowledge means the provider cannot read the files it stores, because files are encrypted on users' devices and the provider never has the keys. If the provider is ordered to hand over data, what it holds is ciphertext.