ISO/IEC 27001:2022 is the international standard for an information security management system. An accredited body certifies the management system, not a product or a one off scan. It covers management clauses 4 to 10 and 93 Annex A controls, runs on a three year cycle, and in Australia is driven by customers and tenders, not regulation.
Teams buy the certificate, but the auditor tests the system behind it. ISO 27001 is a management system, not a list of technical fixes, and that gap is where most readiness projects lose months.
What is ISO 27001:2022?
ISO/IEC 27001 is the international standard for an information security management system (ISMS), published jointly by ISO and IEC. An ISMS is the set of policies, processes, roles and decisions an organisation uses to manage information security risk, so it runs security as a continuing system rather than a one time project. The 2022 version is the current edition, and the transition from the 2013 edition closed on 31 October 2025, so every current certificate is against the 2022 standard.
An accredited certification body audits the ISMS and issues a certificate. This is real third party certification, unlike the Essential Eight, which has no certificate and no pass mark, and unlike an IRAP assessment, which produces a report rather than a certificate. The certificate has limits, though. It does not say an organisation is secure. It says the organisation runs a system for managing information security, that the system meets a defined standard, and that an independent auditor has checked it. Buyers often read the badge as a guarantee, when it is a statement about governance.
What does ISO 27001 actually certify?
ISO 27001 certifies the management system, not any single product or control. The standard defines that system in clauses 4 to 10: context, leadership, planning, support, operation, performance evaluation and improvement. Certification confirms the system exists, runs and is improved over time, so a control switched on once is not a management system. The standard asks whether an organisation governs security, not whether it bought a tool.
The clauses also set the documented information an auditor expects to see. That includes the ISMS scope (clause 4.3), the information security policy (5.2), the risk assessment and risk treatment processes (6.1.2 and 6.1.3), the Statement of Applicability, information security objectives (6.2), evidence of competence (7.2), the results of risk assessment and treatment (8.2 and 8.3), monitoring and measurement results (9.1), the internal audit programme and results (9.2), management review results (9.3), and nonconformities with their corrective actions (10.2). Since the 2024 amendment, clauses 4.1 and 4.2 also require the organisation to decide whether climate change is a relevant issue and whether interested parties have climate related requirements. Our ISO 27001 readiness checklist walks those documents in order.
What is the difference between ISO 27001 and ISO 27002?
ISO 27001 holds the requirements an organisation is certified against, while ISO 27002 is the guidance that explains how to implement each Annex A control. Certification is to 27001, and 27002 is read to build and operate the controls. ISO 27002:2022 also tags every control with five attributes, including control type and the cybersecurity concepts of identify, protect, detect, respond and recover, which helps when mapping to other frameworks.
The two are often treated as one, which leads teams to chase control detail before they have a management system to hang it on. In our experience the more reliable order is to get the system right first, then use 27002 to deepen each control, because only 27001 is auditable for certification.
What does ISO 27001 Annex A require?
Annex A lists 93 controls grouped into four themes, down from 114 in the 2013 version, and it is a reference set rather than a mandatory checklist. Controls are selected from the risk assessment, and clause 6.1.3 requires each inclusion and exclusion to be recorded, with justification, in the Statement of Applicability. That is the document an auditor opens first, so vague risk decisions surface quickly.
| Theme | Controls | Examples |
|---|---|---|
| Organisational (A.5) | 37 | Security policies, supplier relationships, threat intelligence (new in 2022) |
| People (A.6) | 8 | Screening, security awareness, remote working |
| Physical (A.7) | 14 | Secure areas, equipment security, physical security monitoring (new in 2022) |
| Technological (A.8) | 34 | Access control, cryptography, logging, secure coding (new in 2022) |
The 2022 revision restructured the old fourteen domains into these four themes and added 11 new controls, covering areas such as threat intelligence, information security for use of cloud services, configuration management, data leakage prevention and secure coding. Annex A controls explained goes through each theme in detail.
Is ISO 27001 mandatory in Australia?
No. Australian government ties its mandates to the Information Security Manual, IRAP and the Essential Eight, not to ISO 27001. For an organisation selling cloud or software to government, an IRAP assessment is the relevant bar rather than an ISO certificate.
ISO 27001 demand in Australia is commercial. Customers, partners and tenders ask for it, especially from software and services companies that hold other organisations’ data, and it is the most widely recognised security credential in private sector procurement. In practice it is required by a buyer far more often than by a law, which is why the decision usually starts in a sales conversation rather than a compliance one. For the detail, see is ISO 27001 mandatory in Australia.
How does the ISO 27001 audit work, Stage 1 and Stage 2?
An accredited certification body runs the audit, so this is not a self declaration or a vendor badge. The two stage initial audit is set by ISO/IEC 17021-1, the standard for bodies that certify management systems, rather than by ISO 27001 itself. Stage 1 reviews the documentation and whether the ISMS is ready: the scope, the policy, the risk assessment and treatment, the Statement of Applicability and evidence that the system has started running. Stage 2 then tests whether the ISMS operates in practice, by sampling evidence, records and interviews.
The standard sets no fixed minimum operating period, but because Stage 2 tests operation, at least one internal audit, one management review and a run of operating records are needed before it. Once both stages are passed, the certificate runs for three years, with annual surveillance audits in between and a full recertification at the end of the cycle. The surveillance audits mean the system has to keep working rather than simply look right on audit day. We cover the detail in Stage 1 versus Stage 2 audits.
How long does ISO 27001 certification take, and what does it cost?
It depends on size, scope and how much of the management system already exists. As an indicative guide from our own engagements, gap analysis and ISMS design commonly take 4 to 8 weeks, and full implementation through to certification more often takes 6 to 12 months once the controls, the evidence and the internal audit are done. These are indicative ranges, not a quote.
Cost follows scope, the number of in scope sites and the certification body’s day rate, not a single list price, because a ten person SaaS and a national insurer are not the same job. The slow part is rarely the audit itself. It is building the habits the audit checks. See how long ISO 27001 certification takes and what ISO 27001 certification costs.
ISO 27001 or SOC 2: which do we need?
They answer different buyers. ISO 27001 certifies a management system against an international standard on a three year cycle and suits customers and tenders worldwide. SOC 2 is a US origin American Institute of Certified Public Accountants (AICPA) attestation report against the Trust Services Criteria, typically renewed each year and asked for wherever a customer’s own risk or procurement process expects it. Neither substitutes for the other, although the AICPA publishes a mapping between the two that confirms a substantial control overlap. Many technology firms end up doing both, because the control work overlaps while the reports do not. ISO 27001 vs SOC 2 compares them side by side.
How does ISO 27001 fit with IRAP and the Essential Eight?
ISO 27001 is the broad management system, while IRAP and the Essential Eight are narrower Australian government instruments. IRAP assesses a specific system against the ISM for government use, and the Essential Eight is eight ASD technical mitigation strategies. The Essential Eight maps onto part of the ISO 27001 technological theme only, such as patching, multi factor authentication, privileged access, application control, hardening and backups. The organisational, people and physical controls, and the clause 4 to 10 management system, have no Essential Eight equivalent. So an ISO 27001 certificate is useful evidence for a government buyer, but it does not replace an IRAP assessment or an Essential Eight maturity assessment. Essential Eight vs ISO 27001 sets out the mapping.
How do we start ISO 27001 for a SaaS company?
For a SaaS provider the ISMS scope is usually the platform, its build pipeline and the people who run it, which keeps the certificate meaningful and the audit focused. The controls customers look at most closely are information security for use of cloud services, the secure development life cycle, secure coding, security testing in development and configuration management. The hyperscaler’s own certificate covers its infrastructure layer only, so the provider’s configuration, application and data handling still need their own ISMS.
We start with a gap analysis against clauses 4 to 10 and Annex A, set the scope, then build the risk assessment and the Statement of Applicability before Stage 1. ISO 27001 for SaaS and the implementation checklist cover the steps, and Cybernion’s ISO 27001 readiness service runs from that gap analysis through to support across both external audit stages.
Frequently asked questions
What is ISO 27001 in simple terms?
ISO 27001 is the international standard for an information security management system. It sets out how an organisation governs, runs and improves information security, and an accredited certification body can independently certify that the system meets the standard.
Is ISO 27001 mandatory in Australia?
No. Australian government mandates are tied to the ISM, IRAP and the Essential Eight, not ISO 27001. Demand in Australia is commercial, driven by customers, partners and tenders.
How many controls are in ISO 27001:2022?
Annex A lists 93 controls across four themes: 37 organisational, 8 people, 14 physical and 34 technological. Eleven are new in the 2022 version.
Do we have to implement all 93 ISO 27001 controls?
No. Controls are selected from the risk assessment, and every included and excluded control is recorded, with reasons, in the Statement of Applicability.
What is the difference between ISO 27001 and ISO 27002?
ISO 27001 holds the requirements an organisation is certified against. ISO 27002 is the guidance that explains how to implement the Annex A controls. Certification is only ever to ISO 27001.
How long is an ISO 27001 certificate valid?
Three years, with annual surveillance audits during the cycle and a full recertification audit before it expires.
Is ISO 27001 the same as SOC 2?
No. ISO 27001 certifies a management system against an international standard. SOC 2 is a US origin AICPA attestation report against the Trust Services Criteria, used by customers worldwide. Companies whose buyers ask for both often hold both.
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.
Talk to us. We aren’t always chasing a transaction.
Sources:
- ISO/IEC 27001:2022, Information security management systems, Requirements, 2022, including Amendment 1, 2024
- ISO/IEC 27002:2022, Information security controls, 2022
- ISO/IEC 17021-1:2015, Requirements for bodies providing audit and certification of management systems, 2015
- Mapping of the 2017 Trust Services Criteria to ISO/IEC 27001, AICPA, accessed June 2026
- ASD Essential Eight explained, current June 2026
Last updated: 7 November, 2026
