After the tender: what changes
Our guide to ISO 27001 for government tenders covers the bid: reading the requirement and getting certified in time. This guide covers what comes after. Once you are a supplier, the security requirements stop being an evaluation criterion and become contract obligations, with reporting duties, audit rights and consequences if you fall short.
None of this makes ISO 27001 a legal requirement. See is ISO 27001 mandatory in Australia? What it does is put you inside the agency’s own compliance obligations, which are mandatory for the agency.
How the PSPF flows down to contractors
The Protective Security Policy Framework (PSPF) is the Australian Government’s protective security policy, administered by the Department of Home Affairs. The current release, PSPF Release 2026, was published in July 2026. The PSPF is mandatory for non-corporate Commonwealth entities; corporate Commonwealth entities are expected to apply it as better practice. It doesn’t bind businesses directly; its third-party risk management requirements reach you instead. Agencies must:
- stay accountable for security risks from procuring goods and services, and not let contract decisions expose the entity or the government to unacceptable risk
- include proportionate security terms in procurements, contracts and outsourcing, so that service providers, contractors and subcontractors comply with the PSPF requirements the agency specifies
- require service providers to report actual or suspected security incidents, and to follow reasonable directions arising from incident investigations
- monitor and review the contract’s security terms to confirm the controls are implemented, operated and maintained by you and your subcontractors for the whole contract
- include security arrangements for completion or termination of the contract
- consider the risks of foreign ownership, control or influence before engaging a provider, and if it changes during the contract
In practice that means questionnaires before signing, specific security schedules in the contract, evidence requests each year and a right to direct you after an incident. Your ISO 27001 certificate and Statement of Applicability answer the first of these. The rest depends on your ISMS actually running.
The frameworks that sit alongside ISO 27001
| Framework | What it is | When it reaches you |
|---|---|---|
| PSPF | Federal protective security policy, with mandatory requirements for agencies | Through contract security terms set by the agency |
| Essential Eight | ASD’s eight mitigation strategies, assessed against maturity levels | When the agency asks you to meet a maturity level for systems that handle its information |
| ISM | ASD’s Information Security Manual, a catalogue of security controls | When you build or run systems for government, especially cloud services |
| IRAP | Independent assessment of a system against the ISM by an ASD-endorsed assessor | When you provide a cloud service, gateway or system the agency must have assessed |
| Hosting Certification Framework | Certification of data centre and cloud service providers for sovereignty and supply chain controls | When your service hosts sensitive or classified government data |
| State policies | Victoria’s VPDSF, the NSW Cyber Security Policy, Queensland’s IS18 | When you supply a state agency |
Defence suppliers have a separate path through the Defence Industry Security Program; see DISP and ISO 27001.
Essential Eight expectations
PSPF Release 2026 requires agencies to implement all eight Essential Eight mitigation strategies to Maturity Level Two. Agencies under that obligation are cautious about suppliers whose systems hold their information or connect to their networks, so expect contracts and questionnaires to ask which maturity level you have reached, how it was assessed and when.
In October 2026 the ASD published ASD Essentials, which evolves the Essential Eight into principles, actions and domains. Home Affairs has not changed the PSPF requirement, so Maturity Level Two is still what agencies are measured against and what they ask suppliers for. See Essential Eight to ASD Essentials for what to do now.
There is no Essential Eight certificate. ASD publishes an assessment process guide, and the evidence is a maturity assessment against each strategy. ISO 27001 covers the same areas (patching, admin privileges, MFA, application control, backups) but lets you choose the method based on risk; the Essential Eight prescribes the settings. The efficient approach is to treat the target maturity level as a measurable objective inside your ISMS. See Essential Eight vs ISO 27001 and our Essential Eight assessments.
The ISM and IRAP: when they apply instead of ISO 27001
The Information Security Manual (ISM) is ASD’s cyber security framework for protecting IT and operational technology systems. It is a detailed control catalogue, updated regularly; the current release at the time of writing is September 2026. Where ISO 27001 asks you to choose controls through risk assessment, the ISM tells you which controls apply to a system at a given classification.
The Infosec Registered Assessors Program (IRAP) is how those controls get checked. ASD endorses individual assessors from the private and public sectors, who assess a specific system or service against the ISM and report on its strengths, weaknesses and risks. Two points are often misunderstood:
- IRAP assesses a system, not an organisation. Your ISO 27001 certificate covers your ISMS; an IRAP report covers, say, your SaaS platform at a stated classification.
- IRAP is not a pass mark. ASD is explicit that assessors don’t accredit or register systems, that assessments generally don’t cover every ISM control, and that completing one doesn’t mean the system complies. The agency reads the report and decides.
The PSPF requires agencies to use cloud service providers that have completed an IRAP assessment against the latest ISM within the previous 24 months, and to consider the assessment’s findings. If you sell a cloud service to federal agencies, expect to need both: ISO 27001 for the organisation and IRAP for the service. If you supply professional services, software development or support without hosting government data, ISO 27001 plus the contract’s security schedule is the usual position.
The Hosting Certification Framework
The Hosting Certification Framework (HCF), now administered by Home Affairs, certifies data centre providers and cloud service providers against privacy, sovereignty, ownership and supply chain requirements. Under the framework, sensitive government data, whole-of-government systems and systems classified PROTECTED must be hosted using certified services. The PSPF reinforces this for security classified information and systems of government significance. It has applied to new contracts and extensions since 30 June 2022.
There are three certification levels, with Certified Strategic the highest, available only to providers that let the government set ownership and control conditions. The framework is being reformed, and new registrations have been paused since 3 November 2025; existing certified providers aren’t affected.
Most suppliers aren’t hosting providers themselves. The question for you is whether your product runs on a certified service in the right region, and whether your ISMS records that dependency. The major cloud platforms’ Australian regions appear on the certified list. Record the hosting choice and its rationale under your cloud services control (5.23).
BuyICT and DTA panels
Most federal ICT buying runs through BuyICT, the Digital Transformation Agency’s procurement platform, and panels such as the Digital Marketplace Panel. In March 2025 the DTA, with the Australian Government Solicitor, published cyber risk model clauses that buyers can use in panel contracts and other ICT agreements. They include obligations to comply with the PSPF, the Essential Eight and the ISM as they apply to what you supply, to undergo an IRAP assessment and act on its findings, to allow supply chain due diligence, to prepare a Commonwealth Data Protection Plan, to provide evidence of compliance, to allow audit and to hold cyber insurance where the buyer requires it.
Buyers select and tailor these clauses to the risk of each procurement, so read the clauses in each contract rather than assuming a panel-wide standard.
State government policies
Each state runs its own framework. At a high level:
- Victoria. The Victorian Protective Data Security Framework and Standards, overseen by OVIC, apply to Victorian public sector organisations. Contracted service providers have no direct obligations, but Standard 8 requires organisations to make sure third parties handle public sector information securely, and the agency head must ensure a contracted provider doesn’t contravene the standards. See VPDSS and ISO 27001.
- New South Wales. The NSW Cyber Security Policy 2026–2027 (July 2026) requires agencies to keep an inventory of third-party providers, have a contractual process for providers to notify suspected or actual incidents and data breaches, monitor providers using assurance reports, audits and test results, and include security requirements and break clauses in contracts. It embeds Essential Eight Maturity Level One controls.
- Queensland. The Information and cyber security policy (IS18), current version effective June 2026, requires departments to operate an ISMS based on the current version of ISO 27001, implement the Essential Eight with maturity targets and run cyber incident simulations at least annually. Your ISO 27001 certificate speaks their language directly.
Local councils, universities and state-owned corporations are often outside these policies or follow their own variants, so check the specific buyer.
The security clauses to expect
Across federal and state contracts, security schedules cover much the same ground:
- notification of actual or suspected incidents within a set number of hours, and cooperation with investigations
- compliance with named frameworks (PSPF requirements, ISM controls, an Essential Eight maturity level) for the systems you use to deliver
- data location, sovereignty and restrictions on offshore access
- personnel security, including background checks and, for classified work, clearances through the Australian Government Security Vetting Agency
- flow-down of the same terms to your subcontractors
- audit and inspection rights, and annual evidence of compliance
- return or destruction of government information at the end of the contract
- disclosure of changes in ownership or control
A Commonwealth contract also brings privacy obligations: contractors handling personal information for an agency are covered by the Privacy Act for that work, even if they would otherwise be exempt as a small business.
ISO 27001 already expects you to identify your legal, regulatory and contractual requirements (clause 4.2 and control 5.31). For a government supplier, that means a maintained register of each contract’s security obligations, mapped to the controls and the people who meet them. Auditors look for it, and it saves you when an agency wants evidence at short notice.
Incident reporting: who you tell, and when
A single incident can trigger several reporting duties at once:
| Obligation | Who you report to | Timing |
|---|---|---|
| Contract security terms | The agency | As the contract specifies, often within hours; includes suspected incidents |
| Notifiable Data Breaches scheme | OAIC and affected individuals | Assess a suspected eligible data breach within 30 days; notify as soon as practicable once you know |
| Ransomware payment reporting | ASD | Within 72 hours of the payment, if you are covered |
| Critical infrastructure reporting | ASD | 12 hours for significant impact, 72 hours for relevant impact, if you are a responsible entity |
See Australia’s new cyber and privacy laws for the ransomware and privacy rules. ISO 27001’s incident controls (5.24 to 5.28) expect a planned, tested process; for a government supplier, the plan must name each agency contact, the contractual deadline and who decides what counts as reportable. Test it with an exercise that includes the agency notification step.
Making one ISMS carry it all
Suppliers who find this manageable run every requirement through one ISMS, not separate projects:
- Scope covers the people, systems and locations that deliver the government service, and the certificate wording says so.
- Interested parties (clause 4.2) list each agency and the frameworks its contract invokes.
- Classification (5.12 and 5.13) maps to the Australian Government’s markings, such as OFFICIAL: Sensitive and PROTECTED, where you handle them.
- Objectives include the Essential Eight maturity target and any IRAP findings you have agreed to fix.
- Internal audit and management review test contract compliance, not only the standard.
Common mistakes: treating the certificate as the end of the obligation, scoping out the team that delivers the contract, signing unread security schedules and incident plans with no agency deadlines. Mapping contract schedules and agency frameworks into one set of controls and evidence is the part we take on for clients. Effort depends mainly on scope and how many frameworks your contracts invoke; see what drives the cost and the ISO 27001 audit cycle.
Next step
If you run the ISMS yourselves, build contract compliance into your internal audit. ISO 27001 requires internal audits to be objective and impartial; your own staff can do it if they aren’t auditing their own work, which is why many small teams bring in an independent internal auditor. To see how we get government suppliers certified and keep them there, read how our ISO 27001 service works, or book a free 30-minute consultation and bring your contract’s security schedule.
