ISO 27001 Clauses

ISO 27001 Clause 4.1 – Understanding The Organisation And Its Context

ISO 27001 Clause 4.2 – Understanding The Needs And Expectations of Interested Parties

ISO 27001 Clause 4.3 – Determining The Scope Of The Information Security Management System

ISO 27001 Clause 4.4 – Information Security Management System

ISO 27001 Clause 5.1 – Leadership and Commitment

ISO 27001 Clause 5.3 – Organisational Roles, Responsibilities and Authorities

ISO 27001 Clause 6.1.1 – Planning General

ISO 27001 Clause 6.1.2 – Information Security Risk Assessment

ISO 27001 Clause 6.1.3 – Information Security Risk Treatment

ISO 27001 Clause 6.2 – Information Security Objectives and Planning to Achieve Them

ISO 27001 Clause 6.3 – Planning Of Changes

ISO 27001 Clause 7.1 – Resources

ISO 27001 Clause 7.2 – Competence

ISO 27001 Clause 7.3 – Awareness

ISO 27001 Clause 7.4 – Communication

ISO 27001 Clause 7.5.1 – Documented Information

ISO 27001 Clause 7.5.2 – Creating and Updating Documented Information

ISO 27001 Clause 8.3 – Information Security Risk Treatment

ISO 27001 Clause 9.1 – Monitoring, Measurement, Analysis, Evaluation

ISO 27001 Clause 9.2 – Internal Audit

ISO 27001 Clause 9.3 – Management Review

ISO 27001 Clause 10.1 – Continual Improvement

ISO 27001 Clause 10.2 – Nonconformity and Corrective Action

ISO 27001 Organisation Controls

ISO 27001 Annex A 5.1: Policies for information security

ISO 27001 Annex A 5.2: Information Security Roles and Responsibilities

ISO 27001 Annex A 5.3: Segregation of duties

ISO 27001 Annex A 5.4: Management responsibilities

ISO 27001 Annex A 5.5: Contact with authorities

ISO 27001 Annex A 5.6: Contact with special interest groups

ISO 27001 Annex A 5.7: Threat intelligence

ISO 27001 Annex A 5.8: Information security in project management

ISO 27001 Annex A 5.9: Inventory of information and other associated assets

ISO 27001 Annex A 5.10: Acceptable use of information and other associated assets

ISO 27001 Annex A 5.11: Return of assets

ISO 27001 Annex A 5.12: Classification of information

ISO 27001 Annex A 5.13: Labelling of information

ISO 27001 Annex A 5.14: Information transfer

ISO 27001 Annex A 5.15: Access control

ISO 27001 Annex A 5.16: Identity management

ISO 27001 Annex A 5.17: Authentication information

ISO 27001 Annex A 5.18: Access rights

ISO 27001 Annex A 5.19: Information security in supplier relationships

ISO 27001 Annex A 5.20: Addressing information security within supplier agreements

ISO 27001 Annex A 5.21: Managing information security in the ICT supply chain

ISO 27001 Annex A 5.22: Monitoring, review and change management of supplier services

ISO 27001 Annex A 5.23: Information security for use of cloud services

ISO 27001 Annex A 5.24: Information security incident management planning and preparation

ISO 27001 Annex A 5.25: Assessment and decision on information security events

ISO 27001 Annex A 5.26: Response to information security incidents

ISO 27001 Annex A 5.27: Learning from information security incidents

ISO 27001 Annex A 5.28: Collection of evidence

ISO 27001 Annex A 5.29: Information security during disruption

ISO 27001 Annex A 5.30: ICT readiness for business continuity

ISO 27001 Annex A 5.31: Identification of legal, statutory, regulatory and contractual requirements

ISO 27001 Annex A 5.32: Intellectual property rights

ISO 27001 Annex A 5.33: Protection of records

ISO 27001 Annex A 5.34: Privacy and protection of PII

ISO 27001 Annex A 5.35: Independent review of information security

ISO 27001 Annex A 5.36: Compliance with policies and standards for information security

ISO 27001 Annex A 5.37: Documented operating procedures

Home / ISO 27001 Tutorials / ISO 27001 Risk Treatment – Tutorial

ISO 27001 Risk Treatment – Tutorial

Last updated Mar 30, 2025

Author: Stuart Barker | ISO 27001 Expert and Thought Leader

Introduction

In this tutorial we will cover ISO 27001 Risk Treatment.

You will learn what ISO 27001 Risk Treatment is and how to implement it.

ISO 27001 Risk Treatment

Building on the foundation of risk management explored in previous blogs, videos, and guides, we’ll now focus specifically on risk treatment within the context of ISO 27001. This standard mandates a defined and implemented risk treatment process encompassing several key steps:

  • Selecting appropriate information security risk treatment options: This involves choosing the most effective strategies to address identified risks.
  • Determining necessary controls: Based on the chosen treatment options, you’ll need to identify the specific controls required for implementation.
  • Mapping controls to ISO 27001 Annex A: This step involves comparing your chosen controls to the extensive list provided in the standard’s Annex A, ensuring alignment.
  • Developing a Statement of Applicability: This document will outline the controls chosen to mitigate your specific organisational risks.
  • Formulating a risk treatment plan: This plan will detail the actions necessary to implement the chosen controls and mitigate risks.
  • Obtaining approval: Secure necessary approvals for the selected risk treatment options.
  • Documenting the process: Maintaining documented information on the entire risk treatment process is crucial for ongoing monitoring and improvement.

Information Security Risk Management Procedure

The first step is to implement a risk management procedure.

The risk management procedure will cover

  • how you identify risk
  • how you assess risk
  • how you treat risk
  • how you manage risk
  • the risk register

ISO 27001 Templates

ISO 27001 Risk Management Procedure Template
ISO 27001 Toolkit

Risk Treatment Options

Risk assessment generates a risk score and based on that score we have a risk treatment option.

You can select the risk treatment options that work for you but the industry standard risk treatment options are:

  • risk avoidance
  • risk reduction
  • risk acceptance
  • risk transfer

Risk avoidance

Risk avoidance is where the failure cost is too great and therefore, the risk is not taken and we don’t accept the risk.

Risk reduction

Risk reduction is where the gross risk is high thereby reducing the probability or impact of the risk through controls.

Risk acceptance

Risk acceptance is where the gross risk is accepted as it stands.

Risk Transfer

Risk transfer is that we transfer part of a risk to a third party, for example, via insurance or outsourcing.

Risk Treatment Defaults

The process includes default risk treatment options based on the risk score. These can be overridden and are guidance.

ISO 27001-Risk-Classification-and-Mitigation-Table

Risk Treatment Plan

The risk treatment plan is the record and management of risk treatment.

To risk treatment plan and management of risk is via the risk register. This risk register tool is a fundamental tool when it comes to the management of risk, including risk treatment.

ISO 27001 Risk Register Example 2

Risk Treatment Process

The steps in managing risk treatment are:

allocate a treatment owner

  • select the risk treatment option
  • set a treatment date
  • record whether or not it’s open or closed
  • managing the risk treatment to completion
  • regularly review progress of risk treatment plans

On completion of the risk treatment the risk is rescored and this gives what is called ‘residual risk’. Residual risk is the amount of risk that still remains after a risk treatment has occurred. This is the acceptable level of risk as nothing can be risk free.

In the risk treatment plan there will now be the risk score when the risk was first identified and the residual risk score. The score should have decreased as the risk has been managed. It is not sensible to do a risk treatment that doesn’t mitigate, reduce, address, or treat a risk. The risk score should never go up.

Determining Controls To Mitigate Risks

Having identified what the risk treatments options are you are going to determine the controls that are necessary to mitigate risks.

The steps are:

  • identify what the risks are to your information security management system
  • identify what the risks are to your information security posture
  • choose the controls from ISO 27001 Annex A that help to mitigate those risks

ISO 27001 Statement of Applicability

The ISO 27001 Statement of Applicability is a list of the ISO 27001 Annex A controls where you record if that control applies to you or not and if not why not.

The way that the statement of applicability is set out to take the annex a controls and list what those annex A controls are with their control objective and to state why it is needed. The need for the control can be

  • a business need – the business has determined it needs the control
  • a risk need – there is a risk that the control mitigates
  • a legal need – the law requires the control to be in place
  • a contractual need – a contract or client requires the control

If a control is not required for any of those reasons then a control is recorded as being not applicable and a short summary of why is provided.

Risk Treatment – Training Video

About the author

Stuart Barker is an information security practitioner of over 30 years. He holds an MSc in Software and Systems Security and an undergraduate degree in Software Engineering. He is an ISO 27001 expert and thought leader holding both ISO 27001 Lead Implementer and ISO 27001 Lead Auditor qualifications. In 2010 he started his first cyber security consulting business that he sold in 2018. He worked for over a decade for GE, leading a data governance team across Europe and since then has gone on to deliver hundreds of client engagements and audits.

He regularly mentors and trains professionals on information security and runs a successful ISO 27001 YouTube channel where he shows people how they can implement ISO 27001 themselves. He is passionate that knowledge should not be hoarded and brought to market the first of its kind online ISO 27001 store for all the tools and templates people need when they want to do it themselves.

In his personal life he is an active and a hobbyist kickboxer.

His specialisms are ISO 27001 and SOC 2 and his niche is start up and early stage business.