| Current version | ISO/IEC 27001:2022 |
| Annex A structure | 4 themes — 93 controls |
| New controls | 11 compared with the previous version |
| Reference standard for controls | ISO/IEC 27002:2022 |
What was reorganized
The previous version of Annex A grouped controls into fourteen domains. The 2022 version reorganizes them into four themes and reduces the total to 93 controls, mainly by merging overlapping controls:
- Organizational controls — policies, roles, supplier management, continuity, compliance.
- People controls — screening, terms of employment, awareness, remote working, disciplinary process.
- Physical controls — perimeters, secure areas, equipment, clear desk, storage media.
- Technological controls — access, cryptography, secure development, logging and monitoring, vulnerability management.
In addition, each control is tagged with five attributes —control type, information security properties, cybersecurity concepts, operational capabilities and security domains— which make it possible to filter and present the set according to the audience. It is a very useful communication tool with top management, and it is underused.
The eleven new controls
They are the ones that generate the most findings, because they did not exist in systems designed under the previous version:
- Threat intelligence
- Information security for 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
What to review in your statement of applicability
The statement of applicability is the most audited document and usually the one in the worst shape. Three concrete checks:
- That the numbering corresponds to the 2022 version. If the controls are still numbered by the fourteen previous domains, the document does not reflect the current standard, even if the implemented controls are correct.
- That exclusions are justified in writing and sustainable. Excluding “cloud security” in an organization that uses cloud email and storage does not withstand a single question.
- That every control declared as implemented has evidence that can be located. The auditor does not ask whether the control exists: they ask to see how it operated last quarter.
The system and technical testing
A recurring finding: the statement of applicability claims that the technical controls operate, but no one has tested them. Vulnerability management, access control, secure coding and web filtering are technically verifiable controls, and that verification is first-class evidence.
That is why it makes sense to link the implementation of the system with real tests —vulnerability assessments and penetration tests— rather than contracting them separately and unconnected to the ISMS. The technical test stops being a report that gets filed and becomes the evidence that backs the statement of applicability.
ISO/IEC 27001 and personal data protection in Colombia
They are different frameworks that are worth coordinating. Law 1581 of 2012 and its regulations impose specific obligations —processing policy, data subject authorization, handling of inquiries and claims, database registration with the Superintendence of Industry and Commerce— that an ISMS does not cover automatically. ISO/IEC 27701 extends the ISMS toward privacy management and is the natural bridge between the two frameworks.
Frequently asked questions
How many controls does Annex A of ISO/IEC 27001:2022 have?
93 controls, organized into four themes: organizational, people, physical and technological. The previous version had 114 controls in fourteen domains; the reduction is mainly due to merging overlapping controls.
Which new controls did ISO/IEC 27001:2022 introduce?
Eleven: threat intelligence, information security for cloud services, ICT readiness for business continuity, physical security monitoring, configuration management, information deletion, data masking, data leakage prevention, monitoring activities, web filtering and secure coding.
Does ISO/IEC 27001 cover personal data protection in Colombia?
Not automatically. Law 1581 of 2012 imposes its own obligations, such as the processing policy, data subject authorization and database registration with the SIC. ISO/IEC 27701 extends the system toward privacy management and serves as a bridge between the two frameworks.
Primary sources
Need support on this topic? We offer an initial scope assessment at no cost.
Let’s talk about your case →About the author
ONAC Lead Evaluator since 2012 and ISO Management Systems Lead Auditor since 2005 at accredited certification bodies. Industrial Engineer, Master in Organizational Management and Specialist in Occupational Health and Safety. Graduate professor in specialization and master’s programs at Colombian universities. More than 25 years of experience in manufacturing and services, in the public and private sectors.
View professional profile on LinkedIn →