Skip to main content

Guide

ISO 27001 Annex A: Controls by category in 2026

Use Annex A’s four themes practically: allocate ownership, connect measures and assess evidence meaningfully.

ISO 27001 Annex A: Controls by category in 2026
Julian Köhn
|Read time: 3 minutes

Annex A is a reference for security controls, not a list of 93 independent projects. For implementation, organise the themes and ask which measures treat your specific risks.

This ISO/IEC 27001:2022 overview helps allocate responsibilities. The offboarding example tests which measure supports several controls and where additional evidence is missing.

Four themes rather than isolated task lists

The 2022 control collection distinguishes organisational, people, physical and technological controls. The ISO overview of 27002 describes complementary implementation guidance; management system requirements are in ISO/IEC 27001. All 93 controls with mappings to NIS2, TISAX and GDPR are in our ISO 27001 overview.

ThemeTypical practical questionRoles often involved
OrganisationalWho governs responsibility and collaboration?Management, information security, procurement and business teams
PeopleWhat must employees know and do?Managers, HR and employees
PhysicalHow are rooms, devices and physical access protected?Site owners and operations
TechnologicalHow are systems and data protected technically?IT, engineering and operations

These examples are a working aid, not verbatim standard text. One measure can address several themes.

One workflow connects several categories

Fictional example: Someone leaves the organisation. The process needs an organisational notification, controlled handling of devices, technical access revocation and information for participants. Four separate checklists can request the same handover repeatedly while still leaving a gap.

First describe the complete workflow, then map relevant requirements. The actual owner of the result remains visible.

From category to reasoned selection

Derive necessary controls from scope, risks and requirements. Use Annex A as a reference to avoid overlooking a necessary control.

A technical focus does not automatically justify ignoring organisational questions. Conversely, an approved policy does not demonstrate effective technical implementation. Our ISO 27001 checklist helps with preparation.

Assign measures and evidence

Map an offboarding workflow to the requirements it supports. A recorded revocation of user access and confirmed return of equipment answer different questions.

Our evidence reuse guide explains why the same attachment does not automatically answer every assessment question. Period, scope and result must fit.

The Statement of Applicability remains a separate task

A theme assignment explains where a control belongs conceptually. The Statement of Applicability justifies which controls your scope needs and how you handle them. A clear display is not a completed selection decision.

Keep reasoning close to your risks and requirements. Excluding a control merely because you do not currently use a suitable software function would not be a substantive justification. An imported standards catalogue does not replace assessment of your own operation.

One measure can support several controls without proving everything

An offboarding process may address several protection aspects. Evidence of revoked user access does not automatically demonstrate return of a physical device. Check the meaning of each item individually.

In Kopexa, evidence belongs to the measure. Mapping the measure to controls preserves requirement relationships. This reduces duplicate maintenance while retaining the substantive question: which implementation is actually evidenced for this requirement?

If the answer remains unresolved, you need additional evidence or a more precise measure. Another green mapping entry does not close the gap.

Start with a sample

Choose a completed case and trace it from trigger to result. Missing device return or remaining access reveals a specific improvement. Green control counts alone tell you little. Add effectiveness metrics that make these outcomes visible.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Are the four themes four separate projects?

No. Many operational workflows touch several themes. Organise implementation around traceable processes, then map the requirements.

Sources

  1. ISO/IEC 27002:2022 — ISO [Accessed ]
  2. ISO/IEC 27001 — ISO [Accessed ]