Annex A is the list of security controls that accompanies ISO 27001. The main body of the standard sets out how to run an information security management system, while Annex A provides a catalog of concrete controls from which a company selects the ones that reduce its risks. The 2022 revision cut the number of controls and reorganized them into four themes. This post explains how Annex A is structured and how the controls are chosen.
This is part of our security program overview. We guide the selection and rollout of controls through governance, risk, and compliance.
Annex A is a list of reference controls, while the detailed description of each one lives in the companion standard ISO/IEC 27002.2 The split matters in practice: Annex A names the control and states its objective in a single line, and ISO 27002 explains how to implement it, what it is for, and what to watch out for. When you design controls you work from both, but the certificate is issued against ISO 27001 and its Annex A.
The most important thing to understand is that Annex A is not a list of obligations you must all satisfy. It is a catalog from which a company selects the controls relevant to its own risks. The selection and the reasoning behind it are recorded in the Statement of Applicability. A control may be left out, as long as the company can explain why it does not apply. That is what keeps an ISMS proportionate instead of forcing every organization to implement every control regardless of context.
The 2022 revision reorganized the controls into four clear themes.1
The four themes replace the older structure but do not change the goal: to cover the full surface of information security, not only the technical part. Most companies instinctively reach for the technological controls first, yet many real incidents start with a person, a supplier, or an unguarded door. Grouping the controls this way is a reminder that the organizational and people themes carry as much weight as the technology.
The choice of controls follows directly from the risk assessment. For each identified risk, the company considers which Annex A controls reduce it and which it will put in place. If a control does not apply, that is allowed, but it has to be justified. This is how Annex A connects risks to concrete measures, rather than leaving security at the level of good intentions.
The direction matters. Controls follow risk, not the other way around. A company that starts by copying the full Annex A list and then tries to invent risks to justify each control has the process backwards, and an auditor will see it. Sound risk management gives every control a reason to exist, and gives every exclusion a defensible explanation.
Supplier risk is a common place where this mapping gets thin. Several organizational controls in Annex A deal with the security of the relationships you depend on, so vendor risk management is not a separate exercise bolted on later; it is part of selecting and justifying the right controls from the start.
The previous version had more controls spread across 14 domains. The 2022 revision merged and modernized them, bringing the total down to 93 across four themes, and added new controls for topics such as cloud security and threat monitoring. The aim was a clearer, more current framework that maps closer to the risks organizations actually face today.
If you certified under the older structure, the change is not a reason to panic. The underlying expectations are largely the same, and the main work is re-mapping your existing controls and Statement of Applicability to the new themes and numbering. We cover the wider path to certification in our ISO 27001 certification guide.
We help connect your risks to the right Annex A controls and prepare the documentation for the audit, through governance, risk, and compliance. Book a scoping call.