The short answer
ISO/IEC 27001 is a voluntary international standard. No general Australian law says a business must hold the certificate. What makes it mandatory for many businesses is the people they sell to: government buyers, enterprises and regulated organisations that write it into tenders and contracts.
Australian law tends to set security outcomes, such as “reasonable steps” or security “proportionate to the threats”, and leaves the method to you. A regulated organisation then needs evidence that it met the outcome, both for itself and for its suppliers. A certificate from an independent, accredited auditor is the most widely recognised form of that evidence, which is why the requirement keeps arriving through the supply chain rather than from Parliament.
Where it is actually required
| Situation | Is ISO 27001 required? |
|---|---|
| A government or enterprise tender lists it as a condition | Yes, for that tender. Some score it rather than require it, or accept equivalents |
| A customer contract requires certification | Yes, under that contract, often by a set date |
| Employment services under DEWR’s Right Fit For Risk | Yes for larger (Category 1) providers, with extra Australian Government security controls on top |
| Supplying an APRA-regulated bank, insurer or super fund | Not by name, but they must assess your security, and a certificate or SOC 2 report is the usual evidence |
| Owning or operating critical infrastructure | One of five frameworks you can comply with; certification isn’t required |
| Handling personal information under the Privacy Act | No, but it helps show “reasonable steps” under APP 11 |
| Supplying federal agencies | Not by law; the agency’s PSPF obligations reach you through contract terms |
| Joining DISP as a defence supplier | No; DISP requires the Essential Eight at Maturity Level 2 instead |
| Seeking CDR accreditation | No, but an ISO 27001 certificate can count as partial evidence |
| None of the above | No. It’s a business decision |
Tenders and contracts
This is where most Australian businesses meet ISO 27001. Government and enterprise tenders handle it in three ways: as a mandatory condition, as a scored criterion that improves your ranking, or as one of several acceptable forms of evidence, sometimes alongside the Essential Eight. The wording matters, so read the requirement closely before committing to a timeline. Our guide to ISO 27001 for government tenders covers how to read it and what to do if you aren’t certified yet.
Private contracts are often stricter in practice. An enterprise customer may require certification within a set period after signing, or before renewal, and may ask for your certificate and Statement of Applicability each year.
Once it is in a contract, it is a legal obligation like any other term. Letting the certificate lapse, or shrinking its scope so it no longer covers the service, can put you in breach. Treat the three-year cycle of surveillance and recertification audits as part of the contract. See the ISO 27001 audit cycle.
Government: the PSPF and state policies
The Protective Security Policy Framework is mandatory for non-corporate Commonwealth entities, not for businesses. The current release, PSPF Release 2026, was released on 1 July 2026. It requires agencies to include proportionate security terms in their contracts and to monitor suppliers against them. That is how the obligation reaches you. PSPF Release 2026 also requires agencies to implement all eight Essential Eight strategies at Maturity Level Two, which is why federal buyers so often ask suppliers about the Essential Eight as well as ISO 27001.
States run their own policies. Queensland’s IS18 requires its departments to operate an ISMS based on the current version of ISO 27001, which is as close as Australian government policy comes to mandating the standard, but it binds the departments, not their suppliers. Victoria’s VPDSS and the NSW Cyber Security Policy reach suppliers through contracts in the same way as the PSPF. Our guide for government suppliers explains what those contract terms look like.
Government schemes that require certification
A few schemes go further than tenders. The clearest example is the Department of Employment and Workplace Relations’ Right Fit For Risk framework for employment services providers. Larger providers must be certified to ISO 27001 by a JAS-ANZ-accredited certification body, with selected controls from the Australian Government’s Information Security Manual added to the scope. Smaller providers can follow a lighter path.
Under Right Fit For Risk, Category 1 providers need independent certification, either to ISO 27001 or to DEWR’s own ISMS scheme. Category 2A providers self-assess against ISO/IEC 27001:2022, and Category 2B providers give an annual management attestation. DEWR has said it is updating its accreditation requirements and will move providers across over a transition period, so check the current position with DEWR before you plan.
Regulators: strong security, no named standard
APRA CPS 234
Banks, insurers and superannuation funds must maintain information security proportionate to their threats under CPS 234. It doesn’t require ISO 27001. But where a third party manages their information assets, they must assess that party’s information security capability. That obligation flows down to their suppliers as security questionnaires, audit rights and, very often, a request for ISO 27001 or SOC 2. See CPS 234 vs ISO 27001 for how the two map. CPS 230 adds obligations for managing material service providers; suppliers to banks should read ISO 27001 for fintechs and suppliers to banks.
Critical infrastructure
Under the Security of Critical Infrastructure Act, responsible entities for covered assets must run a risk management program that includes complying with a recognised cyber security framework. AS ISO/IEC 27001 is one of the listed options, alongside the Essential Eight, NIST CSF 2.0, the C2M2 and the Australian Energy Sector Cyber Security Framework. The rules require compliance with a framework, not a certificate, though many entities choose certification as independent proof.
The enhanced rules commenced on 10 June 2026 for higher-risk asset classes, including electricity, gas, water, liquid fuel and freight. They lift the Essential Eight option to Maturity Level Two and the C2M2 to Maturity Indicator Level Two, add specific cyber requirements such as phishing-resistant MFA for certain systems, and give 12 or 24 months to comply depending on the obligation. If you supply a critical infrastructure entity, expect its supply chain hazard management to reach you through questionnaires and contract terms.
The Privacy Act
Australian Privacy Principle 11 requires reasonable steps to protect personal information from misuse, interference, loss and unauthorised access. The OAIC’s guidance describes what reasonable steps can include, such as governance, risk assessment, access control and incident response, without requiring any particular standard. An ISO 27001 management system covers all of those, which makes it strong evidence if your practices are ever questioned. See Australia’s new cyber and privacy laws.
The 2024 amendments made the point explicit: reasonable steps include technical and organisational measures. That is close to how ISO 27001 itself is built, with Annex A split into organisational, people, physical and technological controls. Separately, the Notifiable Data Breaches scheme requires you to assess suspected eligible data breaches and notify the OAIC and affected individuals. An ISMS with tested incident procedures makes both easier to evidence.
Licensees and directors
If you hold an Australian financial services or credit licence, your general obligations include adequate risk management systems. In ASIC’s case against RI Advice in 2022, the Federal Court found a licensee breached those obligations by failing to have adequate cyber security risk management. The case didn’t name a standard, but it shows that “no law requires ISO 27001” is not the same as “no law requires security”.
The Cyber Security Act 2024
The Act requires businesses above a turnover threshold to report ransomware or cyber extortion payments to ASD within 72 hours, and it sets security standards for smart devices. It doesn’t mention ISO 27001.
Sector rules at a glance
| Sector | What sits alongside ISO 27001 | Read more |
|---|---|---|
| Victorian public sector suppliers | The 12 VPDSS standards, reaching you through contracts | VPDSS |
| Defence suppliers | DISP membership and the Essential Eight at Maturity Level 2 | DISP |
| Health tech | Sensitive information under the Privacy Act; My Health Record conformance | Health tech |
| Fintech and bank suppliers | CPS 234 and CPS 230 due diligence, CDR, PCI DSS | Fintech |
| Managed service providers | Privileged access to many clients, so regulated clients’ obligations flow to you | MSPs |
Certified, compliant or aligned?
These words get used loosely, and buyers notice the difference:
- Certified means an accredited certification body has audited your ISMS and issued a certificate. It’s the only claim most tenders accept. In Australia, check the body is accredited by JAS-ANZ or another member of the international recognition arrangement now run by Global ACI, which replaced the International Accreditation Forum on 1 January 2026. See ISO 27001 certification bodies in Australia.
- Compliant or aligned means you believe you follow the standard, without independent verification. It carries much less weight, and some buyers treat it as a warning sign.
Where a law or framework asks you to “comply with” a framework, as the critical infrastructure rules do, being aligned can be enough legally. Where a buyer asks for “certified”, it isn’t.
If it isn’t mandatory, should you do it anyway?
Three signals say yes: the same security questionnaires keep arriving, you are losing or failing to reach shortlists, or a large customer has asked when, not whether. Two say not yet: nobody has asked, and your basic controls (MFA, patching, backups, admin rights) aren’t in place. In that case fix the basics first. When certification does make sense, scope it to the service customers buy and time it to the contract that needs it. Effort depends mostly on scope; see what drives the cost.
What to do next
- Find the requirement. Look at the exact wording in the tender, contract or questionnaire. Does it say certified, and by when?
- Check for alternatives. Some buyers accept SOC 2, the Essential Eight or an equivalent. See ISO 27001 vs SOC 2 and Essential Eight vs ISO 27001.
- Work back from the date. A small or medium business can often be audit-ready in about eight weeks; see how long ISO 27001 takes.
- Scope to the requirement. Certify what the customer needs, not the whole business by default. Our guide to what drives the cost explains why scope matters most.
Not sure whether a requirement applies to you? Book a free 30-minute consultation and we’ll read it with you, or see how our ISO 27001 service works.
