IMScollect
ISO 27001

ISO 27001, Annex A: Annex A: the controls at a glance

Title in the standard: “Annex A”

What is in Annex A, how does it relate to your risk treatment, and how does an auditor check 93 controls in a few audit days? Annex A of ISO/IEC 27001 from the audit’s point of view.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

Annex A of ISO/IEC 27001 is a catalogue of information security controls. It is not a compulsory programme to be implemented in full but a reference: during risk treatment, the organisation compares the controls it has selected against it, and the result is recorded in the Statement of Applicability.

The 2022 edition arranges 93 controls in four themes. The 37 organisational controls govern how information security is managed: policies, responsibilities, the handling of information and assets, suppliers and cloud services, incidents, continuity and legal obligations. The 8 people controls concern people before, during and after their employment, for example screening, confidentiality, training and remote working. The 14 physical controls protect buildings, rooms and equipment, from entry through to secure disposal. The 34 technological controls cover the technology: access and privileges, protection against malware, backup, logging, networks, cryptography and secure development.

What each control means and how it can be implemented is described in ISO/IEC 27002. It is guidance, not a requirement, and it also assigns attributes to each control, such as whether it is preventive, detective or corrective. For a business with twenty employees, implementing the same control looks quite different from a large group; what matters is that it fits your own risks.

The starting point of almost every implementation is the inventory of information and of the assets that carry it (A.5.9): hardware, software, data, sites and people with special knowledge, each with an owner. Anyone who does not know what they are protecting can hardly justify how well they are protecting it.

What the auditor checks

  • “Show me how this control is implemented here.”

    The sample. Nobody checks all 93 controls in equal depth in one audit. The auditor selects controls from the Statement of Applicability that relate to the most important risks, that are new or that stood out in the last audit, and spreads the selection over the certification cycle. Then the implementation is traced from the policy into operations.

  • “May I see the server room and the reception area?”

    The auditor almost always includes physical security in the sample, because it can be checked directly on the site tour: who gets into the building and how, are sensitive rooms locked, are documents lying around, how are old storage media disposed of? What stands out here often says a lot about how seriously the whole system is taken.

  • “Who has access to this application, and when were the access rights last reviewed?”

    Technological controls are checked on the system: a user list, a configuration, a log. What is looked for is agreement between the rule, the authorisation concept and the actual state, for example whether former employees still have accounts.

  • “What happened during the last security incident?”

    Whether reporting, assessing, handling and learning worked, with dates and the people involved. An organisation in which no incident has ever been reported tends to raise the question of whether anything gets reported at all.

  • “How do you check the security of your service providers?”

    Suppliers and cloud services: requirements in the contract, a check before engagement, monitoring afterwards. Especially with outsourced operations, a large share of the controls lies outside your own organisation.

  • “What do you do if an email looks suspicious to you?”

    Asked of an employee at their workstation. People controls only work if people know them. Someone who can describe how they report a suspicious attachment demonstrates training and awareness better than any attendance list.

Which evidence convinces

  • The Statement of Applicability with a reference to the implementation of each control

    It is the map for the sample. The more directly a row points to a policy, process or record, the faster and calmer the audit runs.

  • An up-to-date inventory of assets with owners

    It is the basis for protection needs, access rights and risk assessment, and it is often one of the first documents requested in the audit.

  • Technical evidence from operations

    Extracts from user management, logs of backup and restore, reports from malware protection, results of vulnerability scans. They show the state on the day of the audit, not the intended one.

  • Records about people

    Confidentiality undertakings, training records, checklists for joiners and leavers. They show that the people controls are not just in the policy.

  • Traces of physical security

    Access rules, visitor log, maintenance records for building services, evidence of the destruction of storage media. They can be compared directly on the site tour with what the auditor sees.

Typical nonconformities

  1. Implementation on paper only

    The policy requires access rights to be reviewed every six months, the last review was two years ago. If evidence is missing for a control that counts as implemented, it is usually a minor nonconformity. If a whole area is not effective, such as backup, it is a major nonconformity.

  2. Open doors and cluttered desks

    The server room is unlocked, visitors walk around unaccompanied, confidential printouts lie on the printer, old hard drives end up in the normal rubbish. Physical security findings are immediately visible on the site tour.

  3. Leavers who still have access

    Accounts of former employees or service providers are still active, because the leaving process does not reach IT, or reaches it too late.

  4. The inventory is incomplete

    Cloud services, private devices used for work or data held by service providers are missing, or assets have no owner. It then remains unclear who decides on their protection.

  5. New controls of the 2022 edition overlooked

    During the transition from 2013, only the numbers were carried over. Controls added in 2022, for example on threat information, configuration, the deletion of data, monitoring or secure coding, have not been considered in their own right.

  6. Restore never tested

    Backups run every night, but nobody has ever tried whether a system can be restored from them within an acceptable time.

Differences by standard

ISO 27001ISO/IEC 27001

Annex A belongs only to ISO/IEC 27001 and is normative there: it must be used during risk treatment, but not every control has to be implemented. The 2022 edition has 93 controls in four themes instead of 114 in 14 sections as in 2013; eleven controls are new, many have been merged. The transition period for certificates under the old edition ended in October 2025. The detailed description of each control is in ISO/IEC 27002:2022. The annexes of ISO 9001 and ISO 14001, by contrast, are explanatory and contain no catalogue of controls.

How IMScollect covers it

In IMScollect you manage the Annex A controls in the Statement of Applicability: for each control, applicability, justification, implementation status, owner, tasks, linked risks and evidence. That way, every row an auditor takes into the sample is connected to its evidence.

The asset inventory records hardware, software, data, people and sites with owner, protection needs and life cycle. Assets can be linked to risks, processes and emergency plans, and the relationships view shows how a failure carries on through dependencies. Rooms and buildings are assets in their own right, where other assets have their location; this helps with physical security in particular. You bring in existing lists via Excel import.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

Do all 93 Annex A controls have to be implemented?▾

No. You implement the controls that are necessary according to your risk assessment, your obligations and your decisions. But you have to consider all of them: every control appears in the Statement of Applicability, either included or excluded with a justification.

What is the difference between ISO 27001 Annex A and ISO 27002?▾

Annex A of ISO 27001 lists the controls briefly and is part of the certifiable standard. ISO 27002 explains each control in detail with its purpose, implementation guidance and attributes. Certification is to ISO 27001; ISO 27002 helps with implementation.

How many controls does an auditor check in a certification audit?▾

There is no fixed number. The auditor takes a sample that fits the risks, the scope and the audit duration and spreads it over the certification cycle. Frequently included are access and privileges, backup, incidents, suppliers and physical security.

What changed with the 2022 edition?▾

The 114 controls in 14 sections became 93 in four themes. Many were merged and eleven are new, among them controls on threat information, the use of cloud services, the configuration of systems, the deletion and masking of data and secure coding.

Further reading and viewing

Template for this clause

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.