ISO 27001 Controls: A Guide to Annex A
ISO 27001 controls are the specific security measures your organisation selects, implements, and evidences to protect information assets. They are not optional extras.
Trusted by 100+ organisations across Europe
What you need to know about iso 27001 controls
- ISO 27001:2022 contains 93 controls in Annex A, organised across four themes: Organisational, People, Physical, and Technological.
- Control selection must be driven by your risk assessment and documented in the Statement of Applicability, with justified exclusions.
- Eleven new controls were introduced in 2022, covering cloud services, threat intelligence, data leakage prevention, and secure coding, among others.
- Every implemented control must be evidenced with records of operation, not just policies stating intent.
- Controls that overlap with NIS2 Article 21 and DORA Article 28 obligations should be prioritised, as a single control can satisfy multiple regulatory requirements.
Sources: ISO/IEC 27001. Last updated May 2026.
How ISO 27001 Controls Are Structured in the 2022 Version
ISO 27001 controls are the specific security measures your organisation selects, implements, and evidences to protect information assets. They are not optional extras. They are the operational core of your Information Security Management System (ISMS). Get them wrong and certification fails. Get them right and you have an audit-ready security programme that satisfies regulators and reassures customers. The 2022 revision of the standard restructured the control set entirely. Annex A now contains 93 controls organised into four themes, down from 114 controls across 14 domains in the 2013 version. The consolidation is not cosmetic. It reflects how modern security teams actually work: across people, technology, physical environments, and organisational processes simultaneously. StartComply maps every Annex A control to your evidence requirements automatically, so your team spends time on security rather than spreadsheet maintenance. This guide explains what the controls are, how they are structured, which ones matter most, and how to select and evidence them correctly. For broader context on the standard itself, see our iso 27001 guide.
The iso 27001 2022 revision reorganised all controls into four themes. This replaced the previous fourteen-domain structure with something more coherent and easier to map to real operational responsibilities. The four themes are: Organisational controls (37 controls), People controls (8 controls), Physical controls (14 controls), and Technological controls (34 controls).
For the complete standard, see our ISO 27001 guide.
ISO 27001 maps directly to the regulations European teams already face. See how it connects to cybersecurity risk assessment.
The Most Critical ISO 27001 Controls for European Organisations
Organisational Controls Worth Prioritising
A.5.1 (Policies for information security) is the foundational control. Without a documented, approved, communicated information security policy, nothing else holds together.
Technological Controls That Auditors Test Directly
Technological controls are the category most likely to be tested with technical evidence rather than documentation alone. Auditors will ask for configuration records, access logs, and scan results, not just policy statements.
People Controls: The Most Commonly Underestimated Category
People controls cover only eight controls, but they address one of the most common root causes of security incidents: human behaviour. A.6.3 (Information security awareness, education and training) requires that all personnel receive regular, role-appropriate security training.
ISO 27001 Controls and the Certification Audit
The Stage 2 certification audit is where your control implementation is tested. Auditors will sample controls, interview personnel, review evidence, and test technical configurations. Controls that exist on paper but are not operational will result in nonconformities. Minor nonconformities can be remediated and closed without failing certification, but major nonconformities will delay or block your certificate.
See also our guide to ISO 27001 vs NIST.
Common Control Failures in Certification Audits. Access control reviews are the most frequently cited control failure in ISO 27001 audits. Organisations implement access provisioning processes but neglect the review cycle.
Maintaining ISO 27001 Controls After Certification
Certification is not the endpoint. See also our guide to threat and vulnerability management.
Certification is not the endpoint
Certification is not the endpoint.
ISO 27001 requires continuous operation
ISO 27001 requires continuous operation of your ISMS, including the controls you have selected.
Annual surveillance audits and a
Annual surveillance audits and a three-year recertification cycle mean your controls must remain operational and evidenced throughout.
Control effectiveness must be measured
Control effectiveness must be measured.
Frequently Asked Questions About ISO 27001 Controls
How many controls are in ISO 27001 Annex A?
ISO 27001:2022 Annex A contains 93 controls, organised into four themes: 37 Organisational controls, 8 People controls, 14 Physical controls, and 34 Technological controls. This is a reduction from the 114 controls across 14 domains in the 2013 version. Eleven controls are entirely new in the 2022 version, covering areas such as cloud security, threat intelligence, and data leakage prevention. Organisations still certified to the 2013 standard must transition to the 2022 version by October 2025.
Do I need to implement all 93 ISO 27001 controls?
No. ISO 27001 requires you to select controls based on your risk assessment results, not implement all 93 by default. Controls that are not applicable to your organisation can be excluded, but every exclusion must be justified and documented in your Statement of Applicability. For example, a fully remote company with no physical office may legitimately exclude certain physical security controls. Auditors will scrutinise your exclusions closely, so justifications must be specific and risk-based, not generic.
What is the Statement of Applicability in ISO 27001?
The Statement of Applicability (SoA) is a mandatory document that records which Annex A controls you have selected, which you have excluded, the justification for each decision, and the current implementation status of each control. It is one of the first documents a certification auditor will request. The SoA must be kept current throughout your ISMS lifecycle. Any change to your risk profile, technology environment, or regulatory obligations may require the SoA to be updated and re-approved by management.
What is the difference between ISO 27001 and ISO 27002?
ISO 27001 is the auditable requirements standard. It specifies what your ISMS must do and lists the controls in Annex A that you select from. ISO 27002 is the implementation guidance standard. For each control in Annex A, ISO 27002 provides the control statement, its purpose, and detailed implementation guidance. You are certified against ISO 27001, not ISO 27002. However, ISO 27002 is an essential reference for understanding how to operationalise each control correctly. Our guide to iso 27002 covers the relationship in detail.
How do ISO 27001 controls relate to NIS2 requirements?
Many ISO 27001 Annex A controls directly address obligations under NIS2 Article 21, which mandates specific security measures for essential and important entities. Controls covering incident management (A.5.24 to A.5.28), supplier security (A.5.19 to A.5.22), business continuity (A.5.29 to A.5.30), and access control (A.8.2 to A.8.5) all map to NIS2 requirements. Implementing ISO 27001 controls does not automatically mean NIS2 compliance, but it substantially closes the gap and provides the audit-ready evidence regulators require.
How often do ISO 27001 controls need to be reviewed?
ISO 27001 requires that your ISMS, including its controls, is reviewed continuously and formally assessed at least annually as part of management review. Individual controls should be monitored for effectiveness on an ongoing basis. Surveillance audits occur annually after initial certification, and a full recertification audit takes place every three years. Controls that have lapsed, lost evidence, or become ineffective due to changes in technology or organisational context must be remediated before the next audit cycle. Waiting until an audit is scheduled to review control posture is a common and costly mistake.
Client Testimonials
“We evaluated enterprise platforms costing 10x more. StartComply does what we need at a price that makes sense.”Elena Kowalski
“Finally, a compliance tool that understands European regulations. StartComply got us audit-ready in weeks, not months.”Maria Papadopoulou
“The AI policy engine alone saved us hundreds of hours. And the third-party risk management is exactly what DORA requires.”Thomas Müller