ISO 27001:2022 Amendment 1 – Absolutely Everything You Need to Know

Home / ISO 27001 / ISO 27001:2022 Amendment 1 – Absolutely Everything You Need to Know

Last updated Dec 16, 2025

Author: Stuart Barker | ISO 27001 Lead Auditor

Introduction

In this article I lay bare the changes to the ISO 27001 standard that happened in 2024 in the ISO 27001:2022 Amendment 1 Climate Action Changes.

You will learn

  • What is ISO 27001:2022 Amendment 1
  • How to implement ISO 27001:2022 Amendment 1 Climate Action Changes 
  • What is new in ISO 27001:2022 Amendment 1 Climate Action Changes

What is ISO/IEC 27001:2022?

ISO 27001 is the international standard for information security. It is an Information Security Management Systems (ISMS) and the output is an ISO 27001 Certification. ISO/IEC 27001:2022 was the much anticipated 2022 update to the standard released in 2022.

Officially it is called: ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection — Information Security Management Systems Requirements

What is ISO/IEC 27001:2022 Amendment 1?

ISO 27001 Amendment 1 is a change to the ISO 27001 standard that introduces requirements on climate change to the information security management system. It officially known as ISO/IEC 27001:2022 Amendment 1 Climate Action Changes 

ISO/IEC 27001:2022 Amendment 1 Release Date

ISO/IEC 27001:2022 Amendment 1 Climate Change Actions was released in February 2024.

What has changed in the new ISO/IEC 27001:2022 Amendment?

The change is the addition of requirements on climate change to the ISO 27001 standard. The following is a summary of the ISO 27001:2022 changes:

Added the following sentence at the end of the sub-clause:

The organisation shall determine whether climate change is a relevant issue.

Added the following note at the end of the sub-clause:

NOTE 2 Relevant interested parties can have requirements related to climate change. 

Everything you need to know – 60 second video

Learn everything you need to know about ISO 27001:2022 Amendment 1 Climate Action Changes in this 60 second YouTube Short.

What do I need to know about the new version amendment to ISO 27001

You need to know that there is no need to panic and no significant work has been introduced, unless you want there to be. This is not an actual evolution of the information security management system (ISMS). The main focus is on introducing the climate change agenda to standards. Whether they are relevant to those standards or not.

How to implement ISO 27001 Amendment 1

To align with this ISO 27001 amendment 1, you should take proactive steps:

  • Conduct a risk assessment to consider climate-related threats to information security. Work with risk management teams to evaluate environmental and climate threats and the impact of your information security management system on them.
  • Engage with interested parties and stakeholders to understand their climate impact expectations. Regulatory bodies, industry groups, and business partners can help define climate requirements that could impact your information security implementation.
  • Review your business continuity and disaster recovery plans to account for climate risks. Your continuity plans should consider potential disruptions caused by extreme weather, which could affect key infrastructure.
  • Businesses can align security practices with environmental responsibility by incorporating sustainability considerations into their security policies. This can include exploring initiatives such as:
    • Using green data centres that rely on renewable energy and efficient cooling systems.
    • Opting for energy-efficient hardware to reduce power consumption.
    • Implementing digital waste reduction initiatives to minimise the environmental impact of data storage and disposal.
  • To maintain compliance with new industry standards, it’s essential to stay informed about evolving climate-related regulations. Taking a proactive approach to these changes will help your organisation adapt more smoothly.

If climate change is on your agenda then you are already covering this and there is nothing additional to do. If it is not then the following is the suggest approach.

You should update to the context of organisation document to include a line that sets out that climate change was reviewed and it was concluded that climate change is not a relevant risk to you or the information security management system. This is the easiest and quickest way to meet the requirement.

If it is a relevant risk to you then you should add it to the risk register and manage it via risk management.

In addition you should take note to ask interested parties if climate change is relevant to them and if so in what way so that you can include the requirement in your information security management system implementation. Be prepared when speaking to external ISO 27001 certification auditors to say that you asked them and it was not ( ideally ) or was relevant and what you did about it.

ISO 27001 Toolkit Business Edition

How to implement ISO 27001 Amendment 1 – 60 second video

Learn how to implement ISO 27001:2022 Amendment 1 Climate Action Changes in this 60 second YouTube Short.

The top 3 Mistakes People make with the new ISO 27001:2022 Amendment 1

1. Overthinking it

You can do as much or as little as you need to do and should not overthink it. Stating that it is not a relevant risk and that you asked interested parties and they were not interested is enough. If climate change is on your agenda then you are already handling and implementing this through other standards and initiatives.

2. Paying consultants to work out the impact

Paying consultants to tell you that nothing has fundamentally changed is a big mistake. It is literally a couple of lines long and I have told you what it says.

3. Thinking climate change relates to an information security management system.

Parking any politics or agenda I leave it for you to work out if climate change has impact in risk terms to an information security management system (ISMS).

ISO 27001:2022 Amendment 1 – Climate Action Changes Explained Simply | The Lead Auditor Podcast

In this episode: Lead Auditor Stuart Barker and team do a deep dive into the ISO 27001:2022 Amendment 1 – Climate Action Changes. Technically referenced as ISO/IEC 27001:2022 Amendment 1 Climate Change Actions. The podcast explores what it is, why it is important and two paths to compliance. The most tactical taking less than 1 hour to implement.

ISO 27001:2022 Amendment 1 – Strategic Implementation Briefing [Auditor Explained]

In this strategic implementation briefing, Lead Auditor Stuart Barker and team do a deep dive into the introduction of ISO 27001:2022 Amendment 1 Climate Change Actions.

ISO 27001:2022 requirements

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

ISO 27001 Technical Controls

ISO 27001 Annex A 8.1: User Endpoint Devices

ISO 27001 Annex A 8.2: Privileged Access Rights

ISO 27001 Annex A 8.3: Information Access Restriction

ISO 27001 Annex A 8.4: Access To Source Code

ISO 27001 Annex A 8.5: Secure Authentication

ISO 27001 Annex A 8.6: Capacity Management

ISO 27001 Annex A 8.7: Protection Against Malware

ISO 27001 Annex A 8.8: Management of Technical Vulnerabilities

ISO 27001 Annex A 8.9: Configuration Management 

ISO 27001 Annex A 8.10: Information Deletion

ISO 27001 Annex A 8.11: Data Masking

ISO 27001 Annex A 8.12: Data Leakage Prevention

ISO 27001 Annex A 8.13: Information Backup

ISO 27001 Annex A 8.14: Redundancy of Information Processing Facilities

ISO 27001 Annex A 8.15: Logging

ISO 27001 Annex A 8.16: Monitoring Activities

ISO 27001 Annex A 8.17: Clock Synchronisation

ISO 27001 Annex A 8.18: Use of Privileged Utility Programs

ISO 27001 Annex A 8.19: Installation of Software on Operational Systems

ISO 27001 Annex A 8.20: Network Security

ISO 27001 Annex A 8.21: Security of Network Services

ISO 27001 Annex A 8.22: Segregation of Networks

ISO 27001 Annex A 8.23: Web Filtering

ISO 27001 Annex A 8.24: Use of Cryptography

ISO 27001 Annex A 8.25: Secure Development Life Cycle

ISO 27001 Annex A 8.26: Application Security Requirements

ISO 27001 Annex A 8.27: Secure Systems Architecture and Engineering Principles

ISO 27001 Annex A 8.28: Secure Coding

ISO 27001 Annex A 8.29: Security Testing in Development and Acceptance

ISO 27001 Annex A 8.30: Outsourced Development

ISO 27001 Annex A 8.31: Separation of Development, Test and Production Environments

ISO 27001 Annex A 8.32: Change Management

ISO 27001 Annex A 8.33: Test Information

ISO 27001 Annex A 8.34: Protection of information systems during audit testing