Skip to content
The number one comparison site for certification in the Netherlands

ISO 27001 requirements per clause and the controls from Annex A

ISO 27001 has two kinds of requirements. Clauses 4 to 10 describe your information security management system. Those requirements always apply. Annex A gives 93 controls in four themes. There are 37 organisational, 8 for people, 14 physical and 34 technological. Which controls you apply follows from your risk assessment. You may exclude a control if you justify it in your Statement of Applicability. You may never exclude a requirement from clauses 4 to 10. The applicable edition is ISO/IEC 27001:2022 with the 2024 climate amendment.

Compare certification bodies for ISO 27001
On this page
  1. Structure of the ISO 27001 requirements
  2. Annex A of ISO 27001: 93 controls in four themes
  3. Excluding a control from Annex A of ISO 27001
  4. Climate amendment of ISO 27001
  5. Applicable edition of ISO 27001
  6. ISO 27001 requirements and the choice of your certification body

Anyone who opens ISO 27001 mainly sees a long list of 93 controls and quickly assumes they are all mandatory. But which requirements always apply, and which controls may you leave aside? After reading this article you will know what each clause of ISO/IEC 27001:2022 requires, how Annex A is structured, when you may exclude a control, what the climate requirement means and which edition applies.

Structure of the ISO 27001 requirements

The requirements for your company are in clauses 4 to 10 and in Annex A. Clauses 1 to 3 only say what the standard is about. For the terms they refer to ISO/IEC 27000. Together the requirements describe an information security management system. That is called ISMS for short. It is a fixed way to safeguard the confidentiality, integrity and availability of your information. You use risk management to do so.

The two parts work differently:

  • Clauses 4 to 10. These are the requirements for the system itself. According to clause 1 of the standard you may not leave anything out of these. Otherwise you cannot claim that you conform to ISO 27001.
  • Annex A. This is a reference list of 93 controls. You determine with your risk assessment which ones you need. You record that.

The clauses follow the fixed structure that ISO uses for all management system standards. That is called the harmonized structure. The headings are the same, and the text is partly the same as ISO 9001. Do you already have an ISO 9001 certificate? Then you will recognise clauses 4, 5, 7, 9 and 10. The standard itself adds that the order of the requirements says nothing about their importance. The order also says nothing about the order in which you implement them.

Clause 4 of ISO 27001: context of your organisation

Clause 4 requires you to know the environment in which you work. It also asks what falls under your ISMS. You determine which issues inside and outside your company affect your information security. You also consider whether climate change plays a role for you. You determine who has an interest, such as customers, suppliers and regulators. You record what they require of you. You determine which of those requirements you address with your ISMS. Then you record the scope. Those are the departments, locations, systems and services that are covered. You also record where you depend on others.

The auditor wants to see that your scope matches what can be seen in your company. A software company that hosts its customer data with a hosting provider must name that dependency. Even if the server is not on its own premises.

Clause 5 of ISO 27001: leadership

Clause 5 places responsibility with top management. Management sets an information security policy. That policy fits the purpose of the company. Management also provides the resources. And it assigns who is responsible for what. You communicate the policy within the company. Where appropriate, you also communicate it to interested parties.

The auditor wants to hear from the managing director personally how security is weighed in decisions. Does everything rest with the IT administrator? And does management not know which risks have been accepted? Then that is a weak spot.

Clause 6 of ISO 27001: planning and risk assessment

Clause 6 is the heart of ISO 27001. Here you assess and treat your information security risks. First record how you assess risks. Also record when you accept a risk. That way a repeat or a different assessor arrives at comparable results. Then for each risk you work out what can go wrong. That can concern confidentiality, integrity or availability. You determine who the owner is. You determine how large the likelihood and the consequences are. And you determine which risks get attention first.

For each risk you choose what you do. You also choose which controls are needed for that. You compare those with Annex A. That way you do not miss a necessary control. You record the result in two documents. The first is the Statement of Applicability. The second is the risk treatment plan. The risk owners approve that plan. They also approve the risks that remain. In addition, you set measurable information security objectives. And you plan changes to the ISMS before you make them.

Clause 7 of ISO 27001: support

Clause 7 is about what you need to make the ISMS work. You need people and resources. The people must be competent for their task. They must also know what the policy means for their work. You make arrangements about what you communicate to whom and when. And you control the documents you record.

Here the auditor often asks an employee what they do with a suspicious email. If the employee knows, that says more than a signed statement. That statement says the training has been completed.

Clause 8 of ISO 27001: operation

Clause 8 requires you to do what you planned in clause 6. You control your processes. That also applies to processes you have placed with a supplier. You repeat the risk assessment at fixed moments. You also do so as soon as something significant changes. Think of a new cloud service or a new site. You carry out the risk treatment plan. You keep the results of both.

Clause 9 of ISO 27001: performance evaluation

Clause 9 requires you to check for yourself whether the ISMS works. You determine what you measure. Think of the number of incidents or how quickly you install security updates. You also determine who evaluates the figures. You hold an internal audit. You also hold a management review. In it, management looks at whether the system does what it should do.

In stage 1 of the certification audit the auditor checks whether both are planned and under way. In stage 2 the auditor tests them again.

Clause 10 of ISO 27001: improvement

Clause 10 requires you to tackle errors at the root cause. It also requires you to keep improving the ISMS. Does something go wrong? Think of a data breach or a missed commitment from your policy. Then you fix it. Then you find out why it happened. You take a measure that prevents recurrence. Finally you check whether that measure worked.

Annex A of ISO 27001: 93 controls in four themes

Annex A has 93 controls, divided over four themes. The list comes from ISO/IEC 27002. That is a separate standard. For each control it explains how to implement it. You cannot be certified against ISO 27002.

ThemeNumberNumbersWhat it covers
Organisational 37 5.1 to 5.37 policy, roles, assets, access, suppliers and cloud services, incidents, continuity, laws and regulations
People 8 6.1 to 6.8 screening, agreements in contracts, awareness and training, confidentiality, remote working, reporting incidents
Physical 14 7.1 to 7.14 secure areas, access to buildings, a clear desk, equipment, storage media
Technological 34 8.1 to 8.34 laptops and phones, access rights, malware, backups, logging, networks, encryption, secure development

Annex A is a reference list. It is not a complete list. Do you have a risk that none of the 93 controls covers? Then you include a control of your own. How far you go with a control is determined by your risk. A company of ten people with a cloud environment sets up access management differently. A hospital with its own servers does it differently again.

Excluding a control from Annex A of ISO 27001

You may exclude a control from Annex A. That is allowed if your risk assessment shows that you do not need it. You write that reason down in your Statement of Applicability. You may never exclude a requirement from clauses 4 to 10. That is stated in clause 1 of the standard itself.

For each control from Annex A the Statement of Applicability states three things:

  • whether it is needed, and why;
  • whether you have already implemented it;
  • why you exclude it, if you do.

An exclusion that the auditor usually accepts has a factual reason. A company that does not develop software itself and has nothing developed can exclude the controls for secure development.

In two situations an exclusion often runs aground:

  • Outsourced work. A control does not lapse because someone else does the work. Do you have software built? Then the control for outsourced development (8.30) applies. Is your data with a cloud service? Then the controls for suppliers and cloud services (5.19 to 5.23) apply.
  • An external requirement. Does a customer, a contract or the law ask for a control? Then it is needed. That also applies if your own risk seems low. The Statement of Applicability then names that requirement as the reason.

How the auditor further uses the Statement and the risk treatment plan is explained in the mandatory documents for ISO 27001. That article also lists which other documents are mandatory.

Climate amendment of ISO 27001

Since February 2024 ISO 27001 requires you to determine whether climate change is a relevant issue for your ISMS. That is in an amendment to the standard, ISO/IEC 27001:2022/Amd 1:2024. ISO offers that amendment free of charge. The amendment adds that requirement in clause 4.1. In 4.2 there is a note. It says that interested parties can have requirements related to climate change. In the Netherlands this is called NEN-EN-ISO/IEC 27001:2023/A1:2024.

IAF and ISO call it a clarification. You already had to determine all issues that affect your ISMS. That is why there was no transition period. The answer may also be no, if you can explain it. For information security it is mainly about availability. Think of a data centre in an area at risk of flooding. Or of a server room that gets too hot in a heatwave.

Applicable edition of ISO 27001

The edition that currently applies is ISO/IEC 27001:2022, the third edition. It includes the 2024 climate amendment. In the Netherlands you buy the European version NEN-EN-ISO/IEC 27001:2023 from NEN. Apart from the European foreword it is the same as the 2022 version. The Dutch text is the same too. A certificate on the 2013 version has no longer been valid since the end of October 2025.

ISO 27001 requirements and the choice of your certification body

Your scope and your Statement of Applicability determine what the certification body has to assess. They therefore also determine how many audit days are charged. For ISO 27001 that is done according to ISO/IEC 27006-1:2024. That starts with the number of people within your scope. The days and amounts are in the costs of ISO 27001. Sector codes play no role for ISO 27001. Every certification body with ISO 27001 in its accreditation may certify you. On 24 September 2026 CertificeerWijzer counted 23 with an office in the Netherlands.

In your quote request, state what falls under your ISMS. Say how many people work there and how many sites you have. Then certification bodies calculate with the same data. That way you can compare their quotes fairly. Through CertificeerWijzer you send that data once to several certification bodies that may cover ISO 27001. Do you work in healthcare? Then also look at NEN 7510. That standard builds on ISO 27001.

Sources

  1. ISO, ISO/IEC 27001:2022, Information security management systems, Requirements (edition 3) iso.org
  2. ISO, ISO/IEC 27001:2022/Amd 1:2024, Climate action changes iso.org
  3. NEN, NEN-EN-ISO/IEC 27001:2023 nl, preview copy (contents, introduction, clauses 1 to 3) nen.nl
  4. NEN, NEN-EN-ISO/IEC 27001:2023/A1:2024 nl, preview copy nen.nl
  5. NEN, Frequently asked questions about ISO/IEC 27001 nen.nl
  6. NEN, NEN 7510 and the new ISO 27002 (presentation with the four themes) wpn.nen.nl
  7. ISO, ISO/IEC 27002:2022, Information security controls iso.org
  8. ISO/TMBG, ISO/IEC Harmonized structure for MSS with guidance for use, 2026-07-01 iso.org
  9. IAF and ISO, Joint Communiqué and IAF Final Decision on climate change in management system standards, February 2024 iaf.nu
  10. RvA, Transition ISO/IEC 27001:2022 rva.nl