Last updated: 23 October 2026. This page replaces our older article on the “114 controls in 14 categories” of ISO/IEC 27001:2013. That edition has been withdrawn, and certificates against it ended on 31 October 2025.

Annex A of ISO/IEC 27001:2022 lists 93 information security controls grouped into four themes. It replaced the 114 controls in 14 domains (A.5 to A.18) of the 2013 edition. Nothing important was dropped: 11 controls are new, many were merged, and the rest were renamed or updated. This guide lists every 2022 control, shows where each one came from in 2013, and explains what you need to do if your ISMS is still built around the old structure.

ISO 27001:2022 at a glance

ISO/IEC 27001:2013ISO/IEC 27001:2022
Annex A controls11493
Structure14 domains (A.5–A.18)4 themes (5–8)
New controls–11
Control guidanceISO/IEC 27002:2013ISO/IEC 27002:2022 (adds attributes such as control type and cybersecurity concepts)
Certification statusWithdrawn; certificates ended 31 Oct 2025Current (with Amendment 1:2024)

The management system requirements (clauses 4 to 10) changed only slightly in 2022, for example a new clause 6.3 “Planning of changes”. Amendment 1:2024 added climate action wording to clauses 4.1 and 4.2: organisations must consider whether climate change is a relevant issue and whether interested parties have climate-related requirements.

The four themes

ThemeControlsCovers
5. Organizational controls37policies, roles, assets, access, suppliers, incidents, continuity and compliance
6. People controls8screening, employment terms, awareness, discipline, NDAs, remote working and event reporting
7. Physical controls14perimeters, entry, secure areas, equipment and media
8. Technological controls34endpoints, access, malware, vulnerabilities, backup, logging, networks, cryptography and secure development

The 11 new controls

ControlNameWhat it expects
5.7Threat intelligenceCollect and analyse information about threats to make better security decisions.
5.23Information security for use of cloud servicesDefine how cloud services are acquired, used, managed and exited securely.
5.30ICT readiness for business continuityPlan, test and maintain ICT readiness so systems can recover within business continuity objectives.
7.4Physical security monitoringMonitor premises continuously for unauthorised physical access (for example CCTV, alarms).
8.9Configuration managementDefine, document and monitor secure configurations for hardware, software, services and networks.
8.10Information deletionDelete information when it is no longer required, including on systems and devices.
8.11Data maskingMask data (for example pseudonymisation) in line with access control and legal requirements.
8.12Data leakage preventionApply data leakage prevention to systems, networks and devices that handle sensitive information.
8.16Monitoring activitiesMonitor networks, systems and applications for anomalous behaviour and act on it.
8.23Web filteringManage access to external websites to reduce exposure to malicious content.
8.28Secure codingApply secure coding principles to software development.

All 93 controls with their 2013 equivalents

Use this table to map an existing 2013-based Statement of Applicability (SoA), risk register or policy set to the 2022 numbering.

5. Organizational controls (37 controls)

2022 controlName2013 control(s)
5.1Policies for information securityA.5.1.1, A.5.1.2
5.2Information security roles and responsibilitiesA.6.1.1
5.3Segregation of dutiesA.6.1.2
5.4Management responsibilitiesA.7.2.1
5.5Contact with authoritiesA.6.1.3
5.6Contact with special interest groupsA.6.1.4
5.7Threat intelligenceNew
5.8Information security in project managementA.6.1.5, A.14.1.1
5.9Inventory of information and other associated assetsA.8.1.1, A.8.1.2
5.10Acceptable use of information and other associated assetsA.8.1.3, A.8.2.3
5.11Return of assetsA.8.1.4
5.12Classification of informationA.8.2.1
5.13Labelling of informationA.8.2.2
5.14Information transferA.13.2.1, A.13.2.2, A.13.2.3
5.15Access controlA.9.1.1, A.9.1.2
5.16Identity managementA.9.2.1
5.17Authentication informationA.9.2.4, A.9.3.1, A.9.4.3
5.18Access rightsA.9.2.2, A.9.2.5, A.9.2.6
5.19Information security in supplier relationshipsA.15.1.1
5.20Addressing information security within supplier agreementsA.15.1.2
5.21Managing information security in the ICT supply chainA.15.1.3
5.22Monitoring, review and change management of supplier servicesA.15.2.1, A.15.2.2
5.23Information security for use of cloud servicesNew
5.24Information security incident management planning and preparationA.16.1.1
5.25Assessment and decision on information security eventsA.16.1.4
5.26Response to information security incidentsA.16.1.5
5.27Learning from information security incidentsA.16.1.6
5.28Collection of evidenceA.16.1.7
5.29Information security during disruptionA.17.1.1, A.17.1.2, A.17.1.3
5.30ICT readiness for business continuityNew
5.31Legal, statutory, regulatory and contractual requirementsA.18.1.1, A.18.1.5
5.32Intellectual property rightsA.18.1.2
5.33Protection of recordsA.18.1.3
5.34Privacy and protection of PIIA.18.1.4
5.35Independent review of information securityA.18.2.1
5.36Compliance with policies, rules and standards for information securityA.18.2.2, A.18.2.3
5.37Documented operating proceduresA.12.1.1

6. People controls (8 controls)

2022 controlName2013 control(s)
6.1ScreeningA.7.1.1
6.2Terms and conditions of employmentA.7.1.2
6.3Information security awareness, education and trainingA.7.2.2
6.4Disciplinary processA.7.2.3
6.5Responsibilities after termination or change of employmentA.7.3.1
6.6Confidentiality or non-disclosure agreementsA.13.2.4
6.7Remote workingA.6.2.2
6.8Information security event reportingA.16.1.2, A.16.1.3

7. Physical controls (14 controls)

2022 controlName2013 control(s)
7.1Physical security perimetersA.11.1.1
7.2Physical entryA.11.1.2, A.11.1.6
7.3Securing offices, rooms and facilitiesA.11.1.3
7.4Physical security monitoringNew
7.5Protecting against physical and environmental threatsA.11.1.4
7.6Working in secure areasA.11.1.5
7.7Clear desk and clear screenA.11.2.9
7.8Equipment siting and protectionA.11.2.1
7.9Security of assets off-premisesA.11.2.6
7.10Storage mediaA.8.3.1, A.8.3.2, A.8.3.3, A.11.2.5
7.11Supporting utilitiesA.11.2.2
7.12Cabling securityA.11.2.3
7.13Equipment maintenanceA.11.2.4
7.14Secure disposal or re-use of equipmentA.11.2.7

8. Technological controls (34 controls)

2022 controlName2013 control(s)
8.1User endpoint devicesA.6.2.1, A.11.2.8
8.2Privileged access rightsA.9.2.3
8.3Information access restrictionA.9.4.1
8.4Access to source codeA.9.4.5
8.5Secure authenticationA.9.4.2
8.6Capacity managementA.12.1.3
8.7Protection against malwareA.12.2.1
8.8Management of technical vulnerabilitiesA.12.6.1, A.18.2.3
8.9Configuration managementNew
8.10Information deletionNew
8.11Data maskingNew
8.12Data leakage preventionNew
8.13Information backupA.12.3.1
8.14Redundancy of information processing facilitiesA.17.2.1
8.15LoggingA.12.4.1, A.12.4.2, A.12.4.3
8.16Monitoring activitiesNew
8.17Clock synchronizationA.12.4.4
8.18Use of privileged utility programsA.9.4.4
8.19Installation of software on operational systemsA.12.5.1, A.12.6.2
8.20Networks securityA.13.1.1
8.21Security of network servicesA.13.1.2
8.22Segregation of networksA.13.1.3
8.23Web filteringNew
8.24Use of cryptographyA.10.1.1, A.10.1.2
8.25Secure development life cycleA.14.2.1
8.26Application security requirementsA.14.1.2, A.14.1.3
8.27Secure system architecture and engineering principlesA.14.2.5
8.28Secure codingNew
8.29Security testing in development and acceptanceA.14.2.8, A.14.2.9
8.30Outsourced developmentA.14.2.7
8.31Separation of development, test and production environmentsA.12.1.4, A.14.2.6
8.32Change managementA.12.1.2, A.14.2.2, A.14.2.3, A.14.2.4
8.33Test informationA.14.3.1
8.34Protection of information systems during audit testingA.12.7.1

Moving an ISMS from 2013 to 2022

  1. Update the Statement of Applicability to the 93 controls, with a justification for each inclusion or exclusion.
  2. Re-run risk treatment against the new controls, especially the 11 new ones (threat intelligence, cloud services, configuration management, monitoring and data leakage prevention are often gaps).
  3. Update policies and procedures so they reference the new control numbers and cover the new topics.
  4. Address the clause changes, including planning of changes (6.3) and the climate-change considerations from Amendment 1:2024.
  5. Train internal auditors on the new structure and run an internal audit and management review before your certification audit.

Our free ISO 27001 readiness checklist is a quick way to find gaps. For a full gap assessment against the 2022 controls, see our ISO 27001 readiness assessment.

Our ISO 27001 series

Each article below explains one of the 2013 domains in depth and includes a table showing where its controls now sit in the 2022 edition.

Frequently asked questions

Can I still be certified to ISO 27001:2013?

No. Certification bodies stopped certifying to the 2013 edition, and all remaining 2013 certificates expired or were withdrawn after 31 October 2025.

Do I have to implement all 93 controls?

No. You must consider all 93, but you include only those needed to treat your risks (or required by law or contracts), and justify every exclusion in the Statement of Applicability.

Where is the detailed guidance for each control?

In ISO/IEC 27002:2022, which gives purpose and implementation guidance for each control. ISO 27001 Annex A only gives a one-line control statement.

Sources

Post author avatar

Bhaskar Soni

Bhaskar Soni is a Security Engineer and the founder of Youngster Company, based in Ahmedabad, Gujarat. He works hands-on with Linux server hardening, vulnerability assessment and penetration testing (VAPT), ISO 27001 compliance and OSINT investigations. He writes practical, tested guides for IT professionals and Indian businesses, and every article on this site is written or reviewed by him.

Leave a Reply