ISO 27001:2022 is an international standard that sets out what an organization needs in order to manage information security in a systematic way. Its full name is ISO/IEC 27001:2022. It does not prescribe any product. It asks the organization to build an information security management system (ISMS): a set of policies, processes and responsible people used to manage information risk continuously. The full text of the standard is paywalled, so this article relies on ISO's public pages and other sources we could open.
What ISO/IEC 27001 is and who certifies
According to ISO's page, the standard sets requirements for an ISMS, a framework for managing information risk across people, policies and technology. Information in every form is in scope, including paper, cloud and digital data. The standard uses a risk management process scaled to each organization's size and needs. The current edition is the third, published in October 2022, and it replaced the 2013 edition, which has been withdrawn.
A certificate does not come with the standard automatically. ISO's page explains that certificates are issued by a certification body (an independent organization that audits and then issues the certificate), and that seeking one is optional for the organization. The same page recommends the full reference certified to ISO/IEC 27001:2022 rather than the shorter certified to ISO 27001.
How the 2022 edition is organized
From secondary summaries (we could not open the full text of the standard), there are two parts to know:
- Clauses 4 to 10: the requirements for the ISMS. An organization that claims conformity cannot leave any of them out.
- Annex A: an annex that lists controls (a control is something the organization does to reduce risk). The 2022 edition has 93, drawn from ISO/IEC 27002:2022.
ISO/IEC 27002:2022 and its 93 controls
ISO/IEC 27002:2022 is the companion standard. ISO 27001 says what an ISMS must contain, while 27002 gives guidance and detail on the controls used inside the ISMS. According to ISO's page, the 2022 edition restructured the controls, merging, removing and adding some compared with 2013, for a total of 93 controls in 4 groups (themes). The 2013 edition had 114 controls.
The four groups and what each covers are below. The counts and scope come from several secondary summaries, not from the full text of the standard:
- Organizational: policies, governance, supplier oversight, business continuity. 37 controls.
- People: hiring, training, remote working. 8 controls.
- Physical: secure areas, equipment protection. 14 controls.
- Technological: authentication, logging, configuration, software development. 34 controls.
How 2022 differs from 2013
An article from the Cloud Security Alliance (CSA) that we opened summarizes the main changes as follows. The article itself says this is not a complete list:
- Number of controls: Annex A in the 2013 edition had 114 controls, and the 2022 edition has 93.
- Clause 6.3 (planning of changes): a new clause that asks the organization to plan when it changes the ISMS.
- Clause 6.1.3 items c and d: wording made clearer, with the old references to control objectives removed.
There is also ISO/IEC 27001:2022/Amd 1:2024, titled Climate action changes, an amendment published in February 2024. ISO's page states that it is sold separately and is not included in the text of the 2022 standard. According to summaries from consultants and certification bodies (secondary sources), the change adds a short sentence to clauses 4.1 and 4.2 asking the organization to consider whether climate change is relevant to the ISMS. We could not open the text of the amendment itself.
2013 certificates and the transition deadline
The CSA article, citing the document IAF MD 26:2023, states that the transition from the 2013 edition to the 2022 edition lasts 36 months and ends on 31 October 2025. IAF (the International Accreditation Forum, a body that brings together the organizations that accredit certification bodies) issues this document, which applies to accredited certification bodies.
That date has already passed as of November 2026. According to secondary summaries, 2013 certificates are suspended or withdrawn when the period ends. We could not open the full IAF MD 26 document. An organization that still holds a 2013 certificate should ask its certification body directly what the status of the certificate is. An organization seeking a new certificate is audited against the 2022 edition.
The path to certification at a glance
The sequence below is an overview based on our own view, not text from the standard (which we could not read):
- Define the scope: state which units, systems and data the ISMS covers.
- Assess the risks: find where the information risk is. See A simple cyber risk assessment.
- Choose and apply controls: compare against the list of 93 controls and record which ones you chose or left out, and why.
- Check and review internally: run an internal audit, have management review the results, then fix what is found.
- Have a certification body audit: the certification body audits and issues the certificate if the organization passes.
If the organization is not ready to seek a certificate, other frameworks are a place to start. See NIST's guidance in Putting NIST CSF 2.0 into practice and the NIST AI RMF for the risk of AI systems. If a customer asks for SOC 2 instead, see ISO 27001 vs SOC 2: which to choose.
Common mistakes
- Writing certified to ISO 27001 without the edition: ISO recommends the full name with the year, for example ISO/IEC 27001:2022.
- Still using the 2013 Annex A (114 controls) as the checklist: the 2022 edition has 93 controls in 4 new groups.
- Setting a scope too wide for the team: covering the whole organization from the first round without enough people or time (our view).
- Treating the certificate as complete security: a certificate says the ISMS passed an audit against the requirements, not that the organization cannot be attacked (our view).
- Using ready-made documents without assessing your own risk: the controls you pick should come from your real risks (our view).
Mistake
- Writing ISO 27001 without the edition
- Using the 2013 Annex A (114 controls)
- A scope too wide for the team
Better practice
- Cite ISO/IEC 27001:2022 in full
- Use the 93 controls of the 2022 edition
- Start with a small, clear scope
Start today
- Ask management why they want ISO 27001: to answer customers, to improve internally, or both.
- Check the status of any existing certificate: if you ever held a 2013 certificate, ask the certification body where it stands now.
- Pick a small, clear first scope: for example one service or one business unit (our view).
- Run a first risk assessment: list the important data and systems, then rank the risks.
- Buy the full standard before real planning: the full text must be bought from ISO or a national standards body.
To see where your organization stands first, try the self-assessment.
Scope and accuracy
This article is general information, not advice on seeking certification and not legal advice. Facts about the 2022 edition of ISO/IEC 27001, its amendment and ISO/IEC 27002 come from the public ISO pages we could open. The detail of the requirements, the per-group control counts and the transition timeline come from secondary sources, because the full text of the standard and the IAF MD 26 document could not be opened. Before deciding, buy the full standard and ask the certification body you choose.
References and further reading
- ISO/IEC 27001:2022 (ISO committee page): overview, third edition, certification and the amendment
- ISO/IEC 27001:2022/Amd 1:2024: ISO page for the Climate action changes amendment
- ISO/IEC 27002:2022: ISO page for the information security controls standard
- ISO/IEC 27000 family: ISO page introducing the information security management family
- ISO/IEC 27000 (overview and vocabulary): ISO page for the overview and vocabulary standard
- ISO/IEC 27001:2013: ISO page for the previous edition, now withdrawn
- How to Prepare for ISO/IEC 27001:2022 (Cloud Security Alliance): secondary source summarizing the transition, control counts and timeline