The PSPF binds Commonwealth entities directly, not contractors. But its requirements reach contractors and suppliers through contract, deed, panel agreement or direction whenever they handle Commonwealth information or assets. If a provider processes, stores, transmits or can influence the protection of Commonwealth information, it will be required to apply the relevant PSPF controls.
The plain answer to “does the PSPF apply to my business” is that the framework does not bind the business, but its contract does, and the contract carries the framework. That distinction decides how a provider should respond to a government tender that asks about protective security.
Does the PSPF apply to contractors and suppliers?
Not directly, but effectively yes through contract. The PSPF is Australian Government policy, and compliance is mandatory for non-corporate Commonwealth entities, which is most departments and agencies. Contractors and suppliers are not entities, so the framework does not apply to them of its own force.
The reach comes through the work. Any service provider, whether a cloud host, a software vendor, a consultancy, a facilities manager or a recruitment firm, must implement the relevant PSPF controls where a contract, deed, panel head agreement or direction requires it. The trigger is handling Commonwealth information or assets. If a provider processes, stores, transmits or can influence the protection of Commonwealth information, it will be asked to map its controls to the PSPF and keep them current. So the framework applies to the entity, and the entity passes the relevant parts to the supplier as a condition of the engagement. Whether a provider feels it depends entirely on whether it touches government data. For the framework itself, see what is the PSPF.
How does the PSPF flow down to a supplier?
Through the contract, because the PSPF requires the engaging entity to manage it that way. The governance domain includes a requirement covering security for contracted goods and service providers, which obliges the entity to build the relevant protective security requirements into its arrangements with the supplier. So the entity, not the framework, is what reaches the supplier.
The common vehicles are specific. Hosting is often channelled through the Digital Transformation Agency’s Hosting Certification Framework. Cloud is often channelled through IRAP assessed terms. Panels and requests for tender increasingly carry minimum security clauses that require the relevant PSPF controls, or the Information Security Manual as a minimum standard, to be applied. The result is that the obligation is written into the agreement in concrete terms: a certification the supplier must hold, an assessment it must pass, controls it must maintain. In the tenders we see, reading the security schedule of the contract shows exactly what applies, which is more reliable than reasoning from the framework in the abstract.
Do we need an IRAP assessment to meet PSPF obligations as a supplier?
For the technology parts, usually yes. If a provider hosts or processes Commonwealth data, the engaging entity typically requires the system to be assessed against the Information Security Manual at the classification of the data it holds. An IRAP assessment is what produces that evidence, measuring the system control by control and recording how each is implemented.
The assessment is how a provider evidences that its system meets the technology requirements the PSPF places on the entity. The entity cannot accept that system into its own protective security posture on trust; it needs the assessment report to rely on. This is also why gateways and Security Service Edges used by entities must have been assessed against the current ISM within the last 24 months, so a lapsed assessment stops satisfying the requirement. Whether one is actually needed, and at what level, depends on the data classification and the contract, which is worked through in do we need an IRAP assessment. The PSPF and the ISM explains why the assessment is run against the ISM rather than the PSPF directly.
Does the PSPF apply to our business if we only handle OFFICIAL data?
The framework still reaches the provider, but the obligation is lighter. Controls scale with classification, so a system holding only OFFICIAL or OFFICIAL: Sensitive data carries a much smaller control set than one holding PROTECTED. A provider is not exempt because the data is low classification; it is simply held to a proportionate standard.
The determining step is confirming the classification with the engaging entity, because that single fact sets which ISM controls apply and what level of assessment, if any, is required. In the work we see, suppliers get this wrong in both directions. Some assume any government data means a full PROTECTED build and overspend. Others assume OFFICIAL data means no obligation and get caught short at contract. The classification, confirmed in writing by the owner, is what resolves it, which is why understanding business impact levels and classification is worth the time before responding to a tender.
What happens if a supplier does not meet its PSPF obligations?
It becomes a contract problem before anything else. Because the obligation reaches the supplier through the agreement, failing it can mean losing the work, failing to win it, or being removed from a panel. It also creates a security gap that the engaging entity may have to account for in its own reporting, which makes them reluctant to keep the supplier.
There is a second exposure worth naming. The PSPF 2025 release requires entities to report potential or identified foreign ownership, control or influence risks found during procurement to the Department of Home Affairs as soon as possible. So ownership structure and foreign control are now a live eligibility question, not a background formality, and they can affect whether a supplier is engaged at all. The practical takeaway is to treat the security schedule as a real deliverable with cost and lead time, not a box to tick after award.
To work out which PSPF obligations reach a provider’s systems and evidence them with an IRAP assessment at the right classification, we provide IRAP assessment and readiness.
Frequently asked questions
Does the PSPF apply to contractors and suppliers?
The PSPF binds non-corporate Commonwealth entities directly, not contractors. But its requirements reach contractors and suppliers through contract, deed, panel agreement or direction whenever they handle Commonwealth information or assets. If a provider processes, stores, transmits or can influence the protection of Commonwealth information, it will be required to apply the relevant PSPF controls as a term of doing that work.
How does the PSPF flow down to a supplier?
It flows down through the contract. The engaging entity is required under the PSPF governance domain to manage security for contracted goods and services, so it writes the relevant PSPF and Information Security Manual requirements into the contract, deed or panel head agreement. Common vehicles include the Hosting Certification Framework for hosting and IRAP assessed terms for cloud, so the supplier’s obligation comes from the agreement rather than the framework applying to it directly.
Do we need an IRAP assessment to meet PSPF obligations as a supplier?
Often yes, for the technology parts. If a provider hosts or processes Commonwealth data, the engaging entity usually requires the system to be assessed against the Information Security Manual at the data’s classification, which is what an IRAP assessment provides. The assessment is how a provider evidences that its system meets the technology requirements the PSPF places on the entity it serves.
Does the PSPF apply to our company if we only handle OFFICIAL data?
The controls scale with the classification, so handling only OFFICIAL or OFFICIAL Sensitive data means a lighter obligation than handling PROTECTED. But the framework still reaches a provider through the contract if it handles Commonwealth information of any classification. The right move is to confirm the classification of the data with the engaging entity, because that decides which controls and what level of assessment apply.
What happens if a supplier does not meet its PSPF obligations?
Because the obligation is contractual, failing to meet it is a contract issue first. It can mean losing the work, failing to win it, or being removed from a panel, and it can expose the engaging entity to a security gap it has to report. Foreign ownership, control or influence risks now also have to be reported to Home Affairs during procurement, so ownership and control can affect eligibility as well.
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
- The Protective Security Policy Framework has been updated: what’s new?, King and Wood Mallesons, 2025
- PSPF Annual Release 2025, Department of Home Affairs, 24 July 2025
- Information Security Manual, Australian Signals Directorate, 2026
Last updated: 5 September, 2026
