Skip to content
DekkoSecure
All articles

Industry Insights · Government file sharing · 8 min read

Secure File Sharing for Government: US and Australian Requirements

Secure file sharing for government: the US and Australian rules on markings, hosting, MFA, need-to-know and audit, from CUI and CJIS to the PSPF and IRAP.

Government agencies share files every day with other agencies, contractors, lawyers and partners. Each file carries rules about who may open it, where it may be stored and what record its handling must leave, and those rules differ between the United States and Australia.

This guide explains what secure file sharing for government involves, which frameworks set the rules in each country, and how they compare.

What is secure file sharing for government?

Secure file sharing for government is the exchange of official files, inside an agency and with other agencies, contractors and partners, under the controls government rules require: classification or CUI markings, approved hosting locations, strong sign-in, need-to-know access, a recorded audit trail and written agreements with outside parties.

In the United States, those controls come from the Controlled Unclassified Information (CUI) program, NIST SP 800-171, the FBI CJIS Security Policy and the FedRAMP program. In Australia, they come from the Protective Security Policy Framework (PSPF), the Information Security Manual (ISM) and IRAP assessments.

The frameworks behind government file sharing

United States

  • The CUI program: established by Executive Order 13556, it standardizes how the executive branch handles unclassified information that needs safeguarding or dissemination controls. Its rules are in 32 CFR Part 2002. Our CUI guide covers markings.
  • NIST SP 800-171: the requirements agencies must use to protect CUI on non-federal systems, such as a contractor's own network. Revision 3 (May 2024) has 17 requirement families, including audit and accountability.
  • The FBI CJIS Security Policy: the minimum security requirements for accessing FBI Criminal Justice Information Services systems and protecting criminal justice information (CJI). Version 6.1 is dated June 25, 2026. See our CJIS compliance guide.
  • The FedRAMP program: run by the General Services Administration (GSA), it assesses and authorizes cloud services used by federal agencies. Its Marketplace lists certified services, and each agency still issues its own authorization to operate (ATO).

Australia

  • The PSPF: the Australian Government's protective security policy, administered by the Department of Home Affairs. PSPF Release 2026 (1 July 2026) uses four security classifications: OFFICIAL: Sensitive, PROTECTED, SECRET and TOP SECRET. See What Is the PSPF? and our guide to OFFICIAL: Sensitive.
  • The ISM: the Australian Signals Directorate's (ASD) cyber security framework for information technology and operational technology systems, with the current release dated September 2026.
  • IRAP: independent assessments against the ISM by ASD-endorsed assessors. PSPF Requirement 0109 directs entities to use cloud service providers with an IRAP assessment against the latest ISM from the previous 24 months.

What government agencies need from file sharing

1. Classification and markings

A marking tells each recipient how to handle a file, so it has to stay with the file. Under 32 CFR 2002.16, authorized holders must label CUI according to the CUI Executive Agent's marking guidance before disseminating it. PSPF Requirement 0068 calls for the security classification to be applied as metadata on systems that store, process or communicate security classified information.

2. Hosting location and data sovereignty

Where a file is stored affects whose laws can reach it. The CJIS Security Policy (control SC-28) permits CJI to be stored only in cloud environments within the United States, US territories, Indian Tribes and Canada. In Australia, PSPF Requirement 0111 requires security classified information to be hosted with a cloud or data center service certified under the Hosting Certification Framework, and ISM control ISM-1572 calls for contracts to document the regions where data is processed, stored and communicated.

3. Identity assurance

A stolen password should not be enough to open a government file. NIST SP 800-63B-4 says federal agencies shall require their staff, contractors and partners to use phishing-resistant authentication to access federal information systems. It gives PIV and CAC smart cards and WebAuthn (FIDO2) authenticators as phishing-resistant examples, and does not count one-time codes typed in by hand. The CJIS Security Policy requires multi-factor authentication for privileged and non-privileged accounts. In Australia, ISM-1872 calls for the multi-factor authentication used for online services to be phishing-resistant.

4. Need-to-know access

A clearance or a senior role does not, on its own, entitle anyone to a file. The PSPF's need-to-know principle limits access to people who need the information for their official duties; personnel aren't entitled to it because it would be convenient, or because of their status, position or rank. Requirement 0075 applies the same test, plus a security clearance where required, to people outside the entity. For CUI, access must further a lawful government purpose: an activity within the legal authorities of the US Government or of non-executive branch entities, such as state and local law enforcement (32 CFR 2002.4).

5. Audit trails

Agencies need a record of who opened, downloaded or shared each file. The CJIS Security Policy (control AU-11) requires audit records to be kept for at least one year, or longer while they are still needed. The ISM's security monitoring controls call for event logs to be protected from unauthorized modification and deletion (ISM-1815) and kept searchable for at least 12 months (ISM-1988).

6. Sharing across agencies and with contractors

Under 32 CFR 2002.16, agencies should enter into formal agreements, whenever feasible, with non-executive branch entities they share CUI with, and those agreements must require compliance with the CUI rules. A system a contractor operates on an agency's behalf counts as a federal information system; a contractor's own system is held to NIST SP 800-171.

In Australia, PSPF Requirement 0077 requires an agreement or arrangement, such as a contract or deed, before security classified information is shared with a person or organization outside government, with limited exceptions. Requirement 0076 applies the Memorandum of Understanding between the Commonwealth, states and territories when sharing with state and territory agencies.

US vs Australian requirements for government file sharing

United StatesAustralia
Main rulesCUI program (32 CFR Part 2002); FBI CJIS Security Policy for criminal justice informationPSPF Release 2026 and the ISM
Labels on filesCUI markings listed in the CUI RegistrySecurity classifications: OFFICIAL: Sensitive, PROTECTED, SECRET and TOP SECRET
Assurance for providersNIST SP 800-171 for contractor systems that hold CUI; FedRAMP authorization for cloud services used by federal agenciesIRAP assessment against the latest ISM within the previous 24 months
Hosting locationCJI stored in the cloud only within the United States, its territories, Indian Tribes or CanadaSecurity classified information hosted with services certified under the Hosting Certification Framework; data regions documented in contracts
Sign-inPhishing-resistant authentication for staff, contractors and partners on federal systems; MFA for privileged and non-privileged CJIS accountsPhishing-resistant MFA for online services (ISM-1872)
Who can accessAuthorized holders acting for a lawful government purposePeople with a need-to-know and, where required, a security clearance
Audit recordsKept for at least one year on CJIS systemsEvent logs kept searchable for at least 12 months
Sharing outside governmentFormal agreements with non-executive branch entities whenever feasibleA contract, deed or other agreement before security classified information is shared

Where DekkoCORE fits

DekkoCORE is IRAP assessed to PROTECTED, and the assessment documentation is shared with security teams on request. Each customer chooses Australia, the United States or Canada at setup; data is replicated within that country and never moves to another region unless the customer authorizes it or the law requires it. Files and Hubs can be marked OFFICIAL, OFFICIAL: Sensitive or PROTECTED, markings can be required on uploads, and region protection can limit which countries, judged by IP location, can open a Hub.

External Members see only the folders shared with them, not other external parties, and can be required to use TOTP two-factor authentication or passkeys, including hardware security keys. Every view, download, signature, approval and version is logged, and the audit log exports as CSV or streams to an Azure Log Analytics workspace. Files are encrypted on the user's device with AES-256 keys before upload, so not even DekkoSecure can read them. Read more about secure file sharing.

Common questions

Frequently Asked Questions

What is CUI file sharing?

CUI file sharing is sharing Controlled Unclassified Information with people who need it for a lawful government purpose, under the rules in 32 CFR Part 2002. Files keep their CUI markings, agencies set terms in written agreements whenever feasible, and contractor systems that hold the CUI are held to NIST SP 800-171.

Can government agencies use cloud file sharing?

Government agencies can use cloud file sharing within the limits each framework sets. Non-corporate Commonwealth entities must use cloud providers with an IRAP assessment from the previous 24 months and host security classified information with services certified under the Hosting Certification Framework. In the US, CJI can be stored only in clouds within the United States, its territories, Indian Tribes or Canada.

Do government contractors need phishing-resistant MFA?

Contractors that access US federal information systems should expect to need phishing-resistant MFA. NIST SP 800-63B-4 says federal agencies shall require their staff, contractors and partners to use phishing-resistant authentication for federal information systems, and one-time codes typed in by hand do not count.

Can PROTECTED information be shared with a contractor?

PROTECTED information can be shared with a contractor once an agreement or arrangement, such as a contract or deed, sets out handling requirements and protections. PSPF Release 2026 also limits access to people with a need-to-know and, where required, an appropriate security clearance.

How long should government file sharing logs be kept?

The CJIS Security Policy requires audit records to be kept for at least one year, or longer while they are still needed. The ISM calls for event logs to be kept searchable for at least 12 months, and for longer where National Archives of Australia retention rules require it.

Like to learn more?

Talk to our team about protecting your most sensitive files and evidence.