ISO/IEC 27001:2022 Annex A lists 93 information security controls in four themes: 37 organisational (A.5), 8 people (A.6), 14 physical (A.7) and 34 technological (A.8). The 2022 edition merged, renumbered and regrouped the earlier set and added 11 new controls. None of the 93 is mandatory on its own: you select the controls your risk assessment calls for and justify every inclusion and exclusion in the Statement of Applicability, which the auditor reads first. This guide lists the control titles; the purpose and implementation guidance for each sit in ISO/IEC 27002:2022.
ISO/IEC 27001:2022 Annex A contains 93 controls organized into four themes — organizational, people, physical and technological — that form the reference set for an information security management system. Annex A is not a checklist to implement in full: organizations consider each control, apply the ones their risk treatment calls for, and justify the rest in the Statement of Applicability.
This guide lists every Annex A control by theme, explains what changed from the 2013 edition, and gives practical advice for selecting and implementing the right controls for your organization's risk profile.
Understanding ISO 27001 Annex A
What is Annex A?
Annex A is a reference control set that provides a comprehensive list of information security controls that organizations can implement as part of their ISMS. It's not mandatory to implement all controls, but organizations must consider each control and implement those that are relevant to their risk assessment and treatment plan.
Control Selection Process
The selection of controls from Annex A should be based on:
- Results of the risk assessment
- Risk treatment plan
- Legal and regulatory requirements
- Business requirements
- Cost-benefit analysis
The four Annex A themes
ISO/IEC 27001:2022 groups its 93 Annex A controls into four themes, numbered A.5 to A.8. ISO/IEC 27002:2022 gives the purpose and guidance behind each control, and tags every one with attributes — control type, information security properties, cybersecurity concepts, operational capabilities and security domains — so the same set can be viewed in other ways than by theme.
A.5 Organizational controls (37)
Purpose: Policies, roles, asset and information handling, access management, supplier relationships, incident management, continuity and compliance — the controls that are mostly decided and documented rather than configured.
- A.5.1: Policies for information security
- A.5.2: Information security roles and responsibilities
- A.5.3: Segregation of duties
- A.5.4: Management responsibilities
- A.5.5: Contact with authorities
- A.5.6: Contact with special interest groups
- A.5.7: Threat intelligence
- A.5.8: Information security in project management
- A.5.9: Inventory of information and other associated assets
- A.5.10: Acceptable use of information and other associated assets
- A.5.11: Return of assets
- A.5.12: Classification of information
- A.5.13: Labelling of information
- A.5.14: Information transfer
- A.5.15: Access control
- A.5.16: Identity management
- A.5.17: Authentication information
- A.5.18: Access rights
- A.5.19: Information security in supplier relationships
- A.5.20: Addressing information security within supplier agreements
- A.5.21: Managing information security in the ICT supply chain
- A.5.22: Monitoring, review and change management of supplier services
- A.5.23: Information security for use of cloud services
- A.5.24: Information security incident management planning and preparation
- A.5.25: Assessment and decision on information security events
- A.5.26: Response to information security incidents
- A.5.27: Learning from information security incidents
- A.5.28: Collection of evidence
- A.5.29: Information security during disruption
- A.5.30: ICT readiness for business continuity
- A.5.31: Legal, statutory, regulatory and contractual requirements
- A.5.32: Intellectual property rights
- A.5.33: Protection of records
- A.5.34: Privacy and protection of PII
- A.5.35: Independent review of information security
- A.5.36: Compliance with policies, rules and standards for information security
- A.5.37: Documented operating procedures
Implementation guidance: start with the policy set and the asset inventory, because most other organizational controls refer back to them. Access control (A.5.15 to A.5.18) and the supplier controls (A.5.19 to A.5.23) are where auditors most often ask for evidence of operation rather than a policy — access reviews that actually ran, supplier assessments that were actually done.
A.6 People controls (8)
Purpose: Security before, during and after employment: who you hire, what they agree to, what they know, and what happens when they leave or work remotely.
- A.6.1: Screening
- A.6.2: Terms and conditions of employment
- A.6.3: Information security awareness, education and training
- A.6.4: Disciplinary process
- A.6.5: Responsibilities after termination or change of employment
- A.6.6: Confidentiality or non-disclosure agreements
- A.6.7: Remote working
- A.6.8: Information security event reporting
Implementation guidance: people controls are evidenced person by person, so run them from the HR system of record — every joiner screened and trained, every leaver's access removed and assets returned.
A.7 Physical controls (14)
Purpose: Protecting premises, equipment and media from unauthorized physical access, damage and interference.
- A.7.1: Physical security perimeters
- A.7.2: Physical entry
- A.7.3: Securing offices, rooms and facilities
- A.7.4: Physical security monitoring
- A.7.5: Protecting against physical and environmental threats
- A.7.6: Working in secure areas
- A.7.7: Clear desk and clear screen
- A.7.8: Equipment siting and protection
- A.7.9: Security of assets off-premises
- A.7.10: Storage media
- A.7.11: Supporting utilities
- A.7.12: Cabling security
- A.7.13: Equipment maintenance
- A.7.14: Secure disposal or re-use of equipment
Implementation guidance: for cloud-hosted services most data-centre controls are inherited from the provider and evidenced through its own certification. Your offices, laptops used off-premises (A.7.9) and storage media (A.7.10) usually remain yours.
A.8 Technological controls (34)
Purpose: Endpoints, identity and privileged access, malware and vulnerability management, configuration, data protection, logging and monitoring, networks, cryptography and secure development.
- A.8.1: User endpoint devices
- A.8.2: Privileged access rights
- A.8.3: Information access restriction
- A.8.4: Access to source code
- A.8.5: Secure authentication
- A.8.6: Capacity management
- A.8.7: Protection against malware
- A.8.8: Management of technical vulnerabilities
- A.8.9: Configuration management
- A.8.10: Information deletion
- A.8.11: Data masking
- A.8.12: Data leakage prevention
- A.8.13: Information backup
- A.8.14: Redundancy of information processing facilities
- A.8.15: Logging
- A.8.16: Monitoring activities
- A.8.17: Clock synchronization
- A.8.18: Use of privileged utility programs
- A.8.19: Installation of software on operational systems
- A.8.20: Networks security
- A.8.21: Security of network services
- A.8.22: Segregation of networks
- A.8.23: Web filtering
- A.8.24: Use of cryptography
- A.8.25: Secure development life cycle
- A.8.26: Application security requirements
- A.8.27: Secure system architecture and engineering principles
- A.8.28: Secure coding
- A.8.29: Security testing in development and acceptance
- A.8.30: Outsourced development
- A.8.31: Separation of development, test and production environments
- A.8.32: Change management
- A.8.33: Test information
- A.8.34: Protection of information systems during audit testing
Implementation guidance: these are the controls most readily evidenced from connected systems — endpoint management, identity provider settings, vulnerability scans, cloud configuration, logs and backups — and the secure development controls A.8.25 to A.8.34 map directly onto your engineering workflow.
What changed from the 2013 edition
The 2022 revision merged and regrouped the previous edition's controls into four themes, renumbered all of them, and added eleven new ones. Certificates issued against the 2013 edition had to move to the 2022 version by 31 October 2025, so a current certificate is a 2022 certificate. The new controls are:
- A.5.7 Threat intelligence
- A.5.23 Information security for use of cloud services
- A.5.30 ICT readiness for business continuity
- A.7.4 Physical security monitoring
- A.8.9 Configuration management
- A.8.10 Information deletion
- A.8.11 Data masking
- A.8.12 Data leakage prevention
- A.8.16 Monitoring activities
- A.8.23 Web filtering
- A.8.28 Secure coding
Control Selection and Implementation Strategy
Step 1: Risk Assessment
Conduct a comprehensive risk assessment to identify threats, vulnerabilities, and risks to your information assets. This will help determine which controls are most relevant to your organization.
Step 2: Control Selection
Based on your risk assessment, select the appropriate controls from Annex A. Consider:
- Risk level and business impact
- Legal and regulatory requirements
- Cost-benefit analysis
- Organizational capabilities
Step 3: Implementation Planning
Develop a detailed implementation plan that includes:
- Implementation timeline
- Resource requirements
- Responsibility assignments
- Success criteria
Step 4: Implementation
Implement the selected controls according to your plan, ensuring proper documentation and evidence collection.
Step 5: Monitoring and Review
Establish ongoing monitoring and review processes to ensure controls remain effective and relevant.
Common Implementation Challenges
Challenge 1: Control Overlap
Solution: Map controls to identify overlaps and ensure efficient implementation without duplication.
Challenge 2: Resource Constraints
Solution: Prioritize controls based on risk level and implement incrementally.
Challenge 3: Technical Complexity
Solution: Engage technical experts and consider phased implementation approaches.
Challenge 4: Documentation Requirements
Solution: Use templates and establish systematic documentation processes.
Best Practices for Control Implementation
- Start with high-risk areas: Focus on controls that address your highest risks first
- Use a phased approach: Implement controls incrementally to manage complexity
- Engage stakeholders: Involve all relevant parties in control implementation
- Document everything: Maintain comprehensive documentation of all control implementations
- Regular testing: Test controls regularly to ensure they remain effective
- Continuous improvement: Regularly review and improve control implementations
Conclusion
ISO 27001 Annex A provides a comprehensive framework for implementing information security controls. Success depends on careful control selection based on risk assessment, systematic implementation, and ongoing monitoring and improvement. By following the guidance in this article and addressing implementation challenges proactively, organizations can effectively implement the controls needed to protect their information assets and achieve ISO 27001 compliance.
Remember that control implementation is not a one-time activity but an ongoing process that requires continuous attention and improvement. Organizations that invest in proper control implementation will not only achieve ISO 27001 compliance but also build a robust information security program that protects their assets and supports business objectives.
How Noru Automates ISO 27001 Control Implementation
Implementing ISO 27001 Annex A controls doesn't have to be a manual, time-consuming process. Noru integrates with your existing systems — cloud platforms, security tools, HR systems, and more — to gather evidence continuously and map it to the Annex A controls it satisfies, so each control carries a current status and a dated evidence history. Controls no system can observe, such as most physical controls, are evidenced with uploaded documents instead.
Cortex, Noru's AI layer, drafts the policies ISO 27001 expects, grounded in the evidence already in your program, and people review and approve them. Vulnerability and pen-test findings are tracked to resolution and linked to risk, so when the certification audit arrives the evidence for each applicable control is already dated and in place.