PSPF
What Is the Protective Security Policy Framework (PSPF)?
3 July 2026 · Updated 3 July 2026
The Protective Security Policy Framework (PSPF) is Australian Government policy administered by the Department of Home Affairs. It sets what entities must do to protect their people, information and assets across six security domains, governance, risk, information, technology, personnel and physical. It is mandatory for non-corporate Commonwealth entities and flows to their suppliers by contract.
The PSPF is not a cyber security standard. It is the whole of government protective security policy that governs the technical detail, and the cyber controls people usually think of live in a separate document the PSPF points to. Getting that distinction right is the first step to knowing what actually applies to an organisation.
What is the Protective Security Policy Framework (PSPF)?
The Protective Security Policy Framework (PSPF) is Australian Government policy that prescribes what entities must do to protect their people, information and assets, both in Australia and overseas. It is administered by the Department of Home Affairs, which publishes an annual release, issues directions and runs the reporting process.
The PSPF is organised into six security domains: governance, risk, information, technology, personnel and physical. Each domain holds numbered PSPF Requirements that entities must meet. It is deliberately broad. It covers who is accountable for security, how information is classified, how staff are vetted, how buildings are secured and how technology is protected. The cyber security controls are set out in the Information Security Manual, which the technology domain references. So the PSPF answers what must be protected and to what standard, while the ISM answers how, in technical terms, for the systems that hold the information.
Who administers the Protective Security Policy Framework (PSPF)?
The Department of Home Affairs administers the PSPF. The Secretary of Home Affairs issues Protective Security Directions that non-corporate Commonwealth entities must comply with, and Home Affairs runs the annual reporting portal through which entities self-assess and report their security maturity each financial year.
This is a change worth knowing. The PSPF was previously administered by the Attorney-General’s Department, and older guidance and templates still carry that attribution. The Australian Signals Directorate owns the Information Security Manual, so responsibility is split: Home Affairs owns the policy framework, ASD owns the technical control set the framework relies on. A Protective Security Direction, for example the 2025 direction restricting a named product on government systems, comes from Home Affairs under the PSPF, while a control identifier and a maturity level come from ASD under the ISM.
What are the six domains of the Protective Security Policy Framework (PSPF)?
The six PSPF domains carve protective security into governance, risk, information, technology, personnel and physical. Each groups a set of numbered requirements.
| Domain | What it covers |
|---|---|
| Governance | Accountable authority, Chief Security Officer and Chief Information Security Officer roles, security planning, annual reporting |
| Risk | Security risk tolerance, third party and supplier risk, foreign ownership control or influence, insider threat |
| Information | Classification of information, handling requirements, need to know, protective markings |
| Technology | Cyber security strategy, the Information Security Manual, the Essential Eight, gateways, system authorisation |
| Personnel | Pre employment screening, security clearances, ongoing assessment, separation |
| Physical | Facility security, certified security zones, storage of classified material |
The technology domain took the most change in the most recent release. Governance and risk are where accountability and supplier obligations are set, which is why they matter most to a company that does business with government rather than one that only runs internal systems.
Who must comply with the Protective Security Policy Framework (PSPF)?
Compliance is mandatory for non-corporate Commonwealth entities, which is most Australian Government departments and agencies. Corporate Commonwealth entities and wholly owned Commonwealth companies are expected to treat the PSPF as better practice rather than a hard obligation.
The reach does not stop at the boundary of government. State and territory agencies apply the PSPF when they hold or access Commonwealth classified material, under arrangements agreed with the Commonwealth. Suppliers pick up PSPF obligations through contract, deed or panel agreement whenever they handle Commonwealth information or assets. For a cloud host, a managed service provider or a consultancy holding government data, the relevant PSPF controls flow through the contract, and the technology parts are usually evidenced through an IRAP assessment of the system. Whether that applies to a given business is worked through in does the PSPF apply to my business.
How does the PSPF relate to the ISM, IRAP and the Essential Eight?
The PSPF is the policy, and the ISM, IRAP and the Essential Eight are how the technology parts of it get done. The PSPF technology domain sets the obligation to protect systems and points to the Information Security Manual for the detailed controls. The Essential Eight is a prioritised subset of ISM mitigations that the PSPF requires as a baseline.
IRAP is the mechanism that measures a system against the ISM. A supplier holding government data typically evidences the technology domain by having the system IRAP assessed at the right classification (set by the PSPF Business Impact Level), which is why the relationship between the PSPF and the ISM matters so much in practice. The framework hierarchy runs top down: policy in the PSPF, controls in the ISM, a prioritised baseline in the Essential Eight, and an assessment method in IRAP.
What changed in the most recent release of the PSPF?
The 2025 release, published on 24 July 2025, moved cyber security to the centre of the framework. It embedded Zero Trust into the technology domain, added new policy content on artificial intelligence and post-quantum cryptography, and required entities to take a stocktake of their internet-facing systems. The full detail is covered in the PSPF 2025 changes.
The framework now runs on an annual release model. Each year Home Affairs publishes an updated release, entities self-assess against it, and they report their maturity. That cadence is why anyone relying on the PSPF needs to check the current year’s release rather than an older copy, because requirement numbers and content move between releases.
For a supplier working out which PSPF obligations apply to its systems and how to evidence them, Cybernion provides IRAP assessment and readiness.
Frequently asked questions
What is the Protective Security Policy Framework (PSPF)?
The Protective Security Policy Framework (PSPF) is Australian Government policy that sets what entities must do to protect their people, information and assets. It is administered by the Department of Home Affairs and organised into six security domains, governance, risk, information, technology, personnel and physical. It carries mandatory requirements for non-corporate Commonwealth entities and is treated as better practice by corporate Commonwealth entities.
Who administers the Protective Security Policy Framework (PSPF)?
The Department of Home Affairs administers the PSPF. It publishes an annual release each year, issues Protective Security Directions that entities must comply with, and runs the reporting portal through which entities self-assess and report their security maturity. The Australian Signals Directorate owns the Information Security Manual, which the PSPF technology domain points to for cyber security controls.
Who must comply with the Protective Security Policy Framework (PSPF)?
Compliance is mandatory for non-corporate Commonwealth entities, which is most Australian Government departments and agencies. Corporate Commonwealth entities and wholly owned Commonwealth companies are expected to treat the PSPF as better practice. State and territory agencies apply the PSPF when they hold or access Commonwealth classified material, and suppliers pick up the relevant requirements through contracts.
What are the six domains of the Protective Security Policy Framework (PSPF)?
The six PSPF security domains are governance, risk, information, technology, personnel and physical. Governance sets accountability and reporting. Risk covers security risk management, foreign interference and insider threat. Information covers classification and handling. Technology covers cyber security and the Information Security Manual. Personnel covers vetting and clearances. Physical covers facilities and security zones.
How does the Protective Security Policy Framework (PSPF) relate to the ISM and the Essential Eight?
The PSPF technology domain points to the Information Security Manual (ISM) for the detailed cyber security controls and requires the Essential Eight as a baseline. The PSPF sets the policy obligation, the ISM carries the technical controls, and the Essential Eight is a prioritised subset of ISM mitigations. An IRAP assessment measures a system against the ISM, which is how a supplier evidences the technology parts of the PSPF.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Protective Security Policy Framework, Department of Home Affairs, July 2026
- Structure of the Protective Security Policy Framework, Department of Home Affairs, July 2026
- PSPF Annual Release 2025, Department of Home Affairs, 24 July 2025
- The Protective Security Policy Framework has been updated: what’s new?, King and Wood Mallesons, 2025
- Information Security Manual, Australian Signals Directorate, 2026
Last updated: 3 July, 2026
