When starting a gap analysis, the first place to look is the SoA’s header: are control numbers written like A.9.2.3 or like 5.18? The former is the 2013 structure and on its own shows the project is built on an old foundation. ISO/IEC 27001 has gone through two changes in recent years: the 2022 version renewed the structure and Annex A controls, and Amd 1, published in 2024, added climate change to the context analysis. Below are the points organizations starting a compliance project or updating their existing ISMS should check.
Current version: ISO/IEC 27001:2022 + Amd 1:2024
The standard in force is ISO/IEC 27001:2022, applied together with Amd 1 of 2024, titled “Climate action changes”. The three-year transition period set by IAF for certificates based on the 2013 version ended in 2025; new certification and surveillance audits are carried out against the 2022 version. For the transition timeline and your organization’s specific situation, go by your certification body’s announcements.
When buying the standard or keeping it in your internal library, keep two documents together: the 2022 main text and Amd 1:2024. A situation you may come across is a team working only from the main text and first hearing about the climate clause in the audit. One PDF isn’t enough.
Main changes in the 2022 version
| Field | Change | Impact on the compliance project |
|---|---|---|
| Management system clauses | Alignment with the common management system structure; additions such as planning processes and their interactions, and planning of changes | Process interactions and change management in scope and planning documents |
| Annex A structure | Controls regrouped into four themes (organizational, people, physical, technological) | Moving the SoA to the new structure |
| New controls | Threat intelligence, use of cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering, secure coding | Assessing the new controls in the risk assessment, new procedures if needed |
| Merged controls | Many controls from the 2013 version were merged | Updating procedure references |
The number of controls in Annex A fell from 114 to 93; 11 of these are new controls, and the rest is merging and renaming. A lower number doesn’t mean less work. Merged controls are mostly broader in scope, and one-line justifications in the old SoA may not cover the whole of the new control.
A practical method for moving the SoA
The annex to ISO/IEC 27002:2022 contains a mapping table between the 2013 and 2022 controls. Do the move with this table: link the old SoA line by line to the new numbers, then make a separate applicability decision for each new control. This is the step most often skipped: the mapping is done, the 11 new controls are marked “applicable”, but there’s no process or record behind them.
On the technical side, some of the new controls directly touch IT operations. Configuration management (8.9) requires an approved baseline configuration and drift checks on servers and network devices. For information deletion (8.10), disk destruction and data deletion records are looked for; for web filtering (8.23), a proxy or firewall policy and logs. Trying to meet these controls with a policy sentence alone produces findings at the first technical sample.
What does Amd 1:2024 bring?
Amd 1 is part of the climate action change ISO made simultaneously to many of its management system standards. A note was added to the context analysis clause that the organization shall determine whether climate change is a relevant issue, and to the interested parties clause that interested parties can have requirements related to climate change.
This change doesn’t add new controls to the information security management system; however, it requires the assessment to have been done in the context analysis and its result recorded. For example, whether the data center is exposed to flooding or extreme heat, suppliers’ resilience to power outages, or customers’ expectations under sustainability reporting can be the subject of the assessment. A decision of “not relevant” can also be recorded, with its justification.
From an information security perspective, the climate assessment doesn’t have to stay abstract. A server room in the basement, no redundancy in air conditioning, or UPS and generator capacity that isn’t enough for a long outage are direct availability risks. If these risks are already in the risk inventory, referring to them in the context analysis becomes concrete evidence of the assessment. There’s no need to write a separate climate report.
Checklist for your existing ISMS
- Is the climate change assessment and its result recorded in the context analysis?
- Have climate-related expectations been assessed in the interested parties list?
- Is the SoA in the 2022 Annex A structure, and have the new controls been assessed?
- Are control references in procedures and policies up to date?
- Are the internal audit program and checklists based on the new structure?
- Does the risk assessment include the risks the new controls address (cloud, data leakage, configuration)?
The fourth item is the most time-consuming. Old references such as “in accordance with A.12.3.1” are scattered throughout procedures. Searching the document library for references starting with “A.” and listing them shows in a few minutes how many documents you need to touch. When updating references, increase the document version too; the auditor sees the change trail in the version history.
The internal audit checklist must be updated in the same way. An internal audit report done with the old numbers doesn’t show the system has really moved to the new structure.
Common mistakes
- Moving the SoA to the new numbers without updating the applicability justifications.
- Marking new controls directly as “applicable” without linking them to the risk assessment.
- Keeping no records for clause 6.3 (planning of changes).
- Dismissing the climate assessment in the context document with a single sentence and no justification.
- Old control references remaining in supplier contracts and training materials.
For organizations just starting out
An organization starting from scratch works directly with the 2022 + Amd 1 structure; there’s no extra transition work. What matters is not using old (2013-based) templates downloaded from the internet. For the setup path, see the how to set up an ISMS guide.
A quick test is enough when choosing a template: are the Annex A controls listed under four themes, and are there 93 of them? If not, the template is old. Don’t use it.
Frequently asked questions
Is a separate document needed for the climate change assessment?
No separate document is needed; it should be clear from the context analysis and interested parties documents that the assessment was done and its result recorded.
Is recertification needed for Amd 1?
The amendment is assessed within the current certification cycle, during planned audits. We recommend confirming your certification body’s approach.
Can we keep using the old 2013 templates?
Not recommended. As the Annex A structure and control references have changed, old templates create inconsistencies in SoA and procedure references.
To measure how well your existing system fits the current version, our ISO 27001 gap analysis service reports version differences and gaps in a prioritized list.