ISO 27001 Requirements: Clauses 4 to 10 Explained
ISO/IEC 27001 consists of two parts: clauses 4 to 10 with the requirements for the management system, and Annex A with the controls. Clauses 4 to 10 are mandatory. None of them may be excluded, otherwise conformity, and therefore certification, is not possible. Annex A controls, on the other hand, may be excluded with justification if they are not necessary for your risks. Clauses 0 to 3 contain the introduction, scope, normative references and terms and definitions, and do not themselves place any requirements on your ISMS.
This article explains what the individual clauses require. The path to an ISMS in eight steps is described in the article Implementing an ISMS, and the controls in the article ISO 27001 Annex A.
Structure of the standard
| Part | Content | Binding nature |
|---|---|---|
| Clauses 0 to 3 | Introduction, scope, normative references, terms and definitions | no requirements of their own for the ISMS |
| Clauses 4 to 10 | Requirements for the management system | mandatory, no exclusion possible |
| Annex A | Controls in four themes: organisational, people, physical, technological | selection based on risk, exclusion with justification in the Statement of Applicability |
Clauses 4 to 10 follow the harmonised structure that ISO uses for all management system standards, for example also for ISO 9001 or ISO 22301. If you already operate another management system, you will recognise the structure and can share processes such as document control, internal audits or management review.
The clauses build on one another: without a defined scope from clause 4, no reliable risk assessment under clause 6 is possible, and without the controls from clause 6 there is nothing to implement in clause 8 and nothing to measure in clause 9.
- 7 mandatory clauses, from clause 4 to clause 10
- 4 phases of the PDCA cycle that the clauses follow
Why clauses 4 to 10 are mandatory
The standard makes clear in its scope: anyone who wants to claim conformity with ISO 27001 may not exclude any of the requirements in clauses 4 to 10. A certification body therefore audits each of these clauses. If, for example, the management review or the internal audit is missing, a certificate is not possible.
Annex A is different: it is a reference catalogue against which you compare the controls derived from your risk assessment. Controls you do not need are excluded with justification in the Statement of Applicability.
An ISMS is not a task for the IT department. Clauses 4 to 10 are aimed at the organisation as a whole: clause 5 expressly holds top management responsible, and the scope, risks, competence and audits concern all departments. IT takes on a supporting part.
Clauses 4 to 10 in detail
Clause 4: Context of the organization
- Determine the internal and external issues that are relevant to your information security. Since Amd 1:2024, this expressly includes the question of whether climate change is a relevant issue.
- Identify interested parties and their requirements, for example customers, authorities, insurers or laws such as the BSIG (the German BSI Act).
- Define and document the scope, including interfaces and dependencies with activities performed by other organisations.
- Establish, implement, maintain and continually improve the ISMS.
In practice: defining the scope carefully is the most important first step. It determines the effort, the audit time and the type of certification, i.e. single, matrix or multi-site, or group certification. More on this in the article ISO 27001 certification.
Clause 5: Leadership
- Top management demonstrates leadership and commitment: it provides resources, integrates the ISMS into the business processes and promotes continual improvement.
- Establish an information security policy with information security objectives or the framework for setting them, and a commitment to satisfy requirements and to improve the ISMS.
- Assign and communicate roles, responsibilities and authorities.
In practice: the standard requires the role, not the title. Without an information security officer, however, this management is not possible, so for us the role is a must. The head of IT, management and the data protection officer should not take on the role. More on this on the page external information security officer.
Clause 6: Planning
- Determine the risks and opportunities that affect the ISMS.
- Carry out a risk assessment with defined criteria that produces consistent and comparable results.
- Plan the risk treatment, determine the necessary controls, compare them with Annex A and record them in the Statement of Applicability. The risk owners approve the treatment plan and the residual risks.
- Establish information security objectives and plan how to achieve them.
- Carry out changes to the ISMS in a planned manner.
In practice: clause 6 is the core. All controls are derived from the risk assessment, explained step by step in the article Implementing an ISMS. For each risk you choose a treatment option, in practice usually to mitigate, avoid, transfer or consciously accept it. If your company falls under NIS2, note that according to the BSI, blanket risk acceptance and risk transfer are ruled out under the BSIG. Information security objectives should be measurable and have a deadline, for example full participation in the annual awareness training by the end of the year.
Clause 7: Support
- Provide the necessary resources.
- Ensure and document the competence of those involved.
- Create awareness: all employees know the policy, their contribution and the consequences of non-compliance.
- Determine internal and external communication on information security.
- Create, update and control documented information.
In practice: training and evidence of competence are regularly checked in the audit. Proper document control prevents outdated versions from circulating.
Clause 8: Operation
- Plan, control and implement processes, including those provided by external suppliers.
- Repeat the risk assessment at planned intervals and when significant changes occur.
- Implement the risk treatment plan and document the results.
In practice: this is where the plan becomes day-to-day reality. The controls from the Statement of Applicability must actually be lived, not just described.
Clause 9: Performance evaluation
- Determine what is monitored and measured, using which method, when and by whom, and evaluate the results.
- Carry out internal audits at planned intervals based on an audit programme. Auditors must be objective and impartial.
- Have top management carry out the management review at planned intervals and decide on improvements and changes.
In practice: typical metrics include the training rate, the status of open risks and actions, patch levels or the response time to security incidents. Whether technical controls work is shown by a penetration test. Nobody audits their own work. If SDG is your external information security officer, an SDG ISMS consultant who is not your information security officer therefore carries out the internal audit once a year.
Clause 10: Improvement
- Continually improve the ISMS.
- React to nonconformities: correct them, determine their causes, check whether similar nonconformities exist, implement corrective actions and review their effectiveness.
- Document nonconformities, actions and results.
In practice: findings from the internal audit that are not closed by the certification audit must be recorded in the ISMS as a corrective action, with cause, action, responsible persons and deadline. Common weaknesses are a missing root cause analysis, no check of whether the corrective action has worked, and missing evidence of continual improvement.
Which documented information the individual clauses require is shown in the overview of mandatory documents in the article Implementing an ISMS.
Typical evidence per clause
In the audit, you show for each clause that the requirements are not only described but lived. Typical evidence includes:
| Clause | Typical evidence |
|---|---|
| 4 Context | analysis of internal and external issues, interested parties and their requirements, documented scope |
| 5 Leadership | approved information security policy, described roles and responsibilities, evidence that they have been communicated |
| 6 Planning | risk assessment method and results, risk treatment plan, Statement of Applicability, information security objectives |
| 7 Support | training and competence records, communication rules, controlled and up-to-date documents |
| 8 Operation | evidence of implementation, updated risk assessments, control of outsourced processes |
| 9 Performance evaluation | metrics and evaluations, audit programme and audit reports, minutes of the management review |
| 10 Improvement | list of nonconformities with causes, corrective actions and effectiveness review |
Which documented information the standard expressly requires is shown in the overview of mandatory documents in the article Implementing an ISMS.
What changed in 2022
With the ISO/IEC 27001:2022 edition, clauses 4 to 10 mainly changed in wording and structure; the basic logic has remained the same:
- New clause 6.3: changes to the ISMS must be carried out in a planned manner.
- Finer structure: the internal audit (9.2) and the management review (9.3) are divided into subclauses.
- Annex A: the controls were reorganised and consolidated from 114 to 93, see ISO 27001 Annex A.
- Amd 1:2024: since then, clause 4 expressly requires you to determine whether climate change is a relevant issue.
- Transition: the transition period for certificates under the 2013 edition ended on 31 October 2025.
Clauses 4 to 10 and NIS2
For NIS2, clauses 4 to 10 in particular provide the structure: clause 4 captures the BSIG as a requirement of an interested party, clause 5 involves management, clauses 6 and 8 support risk management under Section 30 BSIG, clause 7.5 the documentation and clause 9 the evaluation of effectiveness. ISO 27001 certification is not mandatory for NIS2. We recommend a mapping, which in our experience usually covers 90 to 95 % of the NIS2 requirements. More in the article NIS2 and ISO 27001.
How SDG supports you
- Gap analysis of your ISMS against clauses 4 to 10 and Annex A, with a prioritised action plan
- Building the ISMS as an all-inclusive package or classic consulting, with a properly defined scope from the start
- Internal audit by an SDG ISMS consultant and preparation of the management review
- External information security officer who manages the ISMS on an ongoing basis: external information security officer
- Support through to certification up to the audit: ISO 27001 certification
Frequently asked questions about the requirements of ISO 27001
Which clauses of ISO 27001 are mandatory?
Clauses 4 to 10. They contain the requirements for the management system: context of the organization, leadership, planning, support, operation, performance evaluation and improvement. None of them may be excluded.
May I exclude requirements from clauses 4 to 10?
No. Anyone who wants to claim conformity with ISO 27001 or be certified must meet all the requirements of clauses 4 to 10. Only Annex A controls can be excluded, and only with justification.
What is the difference between clauses 4 to 10 and Annex A?
Clauses 4 to 10 describe how the management system must work. Annex A is a catalogue of controls against which you compare the controls derived from your risk assessment. Controls you do not need are excluded with justification in the Statement of Applicability.
What did Amendment 1:2024 change?
Since then, clause 4.1 expressly requires the organisation to determine whether climate change is a relevant issue. For clause 4.2, a note adds that interested parties can have requirements related to climate change.
Are clauses 0 to 3 also requirements?
No. They contain the introduction, scope, normative references and terms and definitions. The requirements for the ISMS begin with clause 4.
Is the ISMS a task for the IT department?
No. Clause 5 holds top management responsible, and the other clauses concern all departments. IT takes on a supporting part, above all for technical controls.
Do I need to be certified for clauses 4 to 10?
No. You can also build and operate an ISMS in line with clauses 4 to 10 without certification. Whether a certificate is needed depends on customers, insurers or tenders and should be checked in each individual case.
What changed in clauses 4 to 10 in 2022?
Mainly the wording and structure. Clause 6.3 on planned changes to the ISMS is new, and the internal audit and management review are structured in more detail. Since Amd 1:2024, climate change must be considered in clause 4. The transition period for certificates under the 2013 edition ended on 31 October 2025.
Sources: ISO/IEC 27001:2022, ISO/IEC 27001:2022/Amd 1:2024
Note: this article is for general information only and reflects the requirements of the standard in substance. The text of the standard is authoritative.