Noru

ISO 27001 Controls: Complete Guide to Annex A Implementation

Every ISO 27001:2022 Annex A control across the four themes, what changed from the 2013 edition, and how to select and implement the controls your risks call for.

Bip Thelin7 min readUpdated

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.

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.

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.

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.

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.

Primary sources

Framework overviews

Related reading

FAQ

ISO 27001 questions answered

Talk to us

How many controls are in ISO 27001:2022 Annex A?

93, grouped into four themes: 37 organisational controls (A.5), 8 people controls (A.6), 14 physical controls (A.7) and 34 technological controls (A.8).

Which Annex A controls are new in the 2022 edition?

Eleven: threat intelligence (A.5.7), information security for use of cloud services (A.5.23), ICT readiness for business continuity (A.5.30), physical security monitoring (A.7.4), configuration management (A.8.9), information deletion (A.8.10), data masking (A.8.11), data leakage prevention (A.8.12), monitoring activities (A.8.16), web filtering (A.8.23) and secure coding (A.8.28).

Can we exclude an Annex A control?

Yes, if your risk assessment gives no reason to apply it and you record the justification in the Statement of Applicability. A cloud-only company with no premises, for example, commonly excludes several physical controls. The auditor checks that each exclusion is justified, not that the list is complete.

Is Annex A the same as ISO 27002?

They list the same 93 controls with the same numbering. Annex A gives each control's title and one-line statement; ISO/IEC 27002:2022 adds the purpose, implementation guidance and attributes for each. Certification is against ISO 27001, which includes Annex A.

Does Noru map Annex A controls to other frameworks?

Yes. Each Annex A control maps onto Noru's shared control library, so the control that answers A.5.18 also answers the SOC 2 criteria, NIS2 measures and other framework requirements that ask the same thing, with one set of evidence.