ISO 27001 Clause 4.1 Understanding the Context of the Organisation Explained

Home / ISO 27001 Clauses / ISO 27001 Clause 4.1 Understanding the Context of the Organisation Explained

Last updated Dec 18, 2025

Author: Stuart Barker | ISO 27001 Lead Auditor

ISO 27001 Clause 4.1 Understanding The Organisation and Its Context is the requirement to identify and manage the internal and external issues that can affect the information security management system (ISMS) and prevent it from achieving its intended outcomes.

In ISO 27001 this is known as ISO27001:2022 Clause 4.1 Understanding The Organisation And Its Context. It is one of the mandatory ISO 27001 clauses.

Internal issues and external issues are just another way of saying risks.

Internal and external issues are risks to the information security management system and they should be identified and managed.

So the clause is asking you to consider and record what internal and external risks there are to your information security management system (ISMS). What could stop your information security management system from being able to achieve its outcomes?

Key Takeaways

  • Internal and external issues are risks to the information security management system.
  • You identify them by doing a brainstorming session
  • You manage them via risk management

What is ISO 27001 Clause 4.1?

ISO 27001 Clause 4.1 Understanding The Organisation And Its Context is an ISO 27001 clause that requires us to understand the internal and external issues that could impact your information security management system (ISMS).

Reference: What is ISO 27001 Clause 4.1?

ISO 27001 Clause 4.1 Purpose

ISO 27001 Clause 4.1 is an Information Security Management System (ISMS) control to ensure you identify, manage and mitigate risks to the management system achieving its intended outcomes.

ISO 27001 Clause 4.1 Definition

The ISO 27001 standard defines ISO 27001 Clause 4.1 as:

The organisation shall determine external issues and internal issues that are relevant to its purpose and that affect its ability to achieve the intended outcome(s) of its information security management system.
The organisation shall determine whether climate change is a relevant issue.

ISO27001:2022 Clause 4.1 Understanding The Organisation And Its Context

What is ISO 27001 Amendment 1: Climate action changes?

The standard amended the definition in February 2024. This amendment, referred to as Amendment 1: Climate action changes added climate change to ISO 27001 Clause 4.1. The standard also added the following sentence:

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

ISO27001:2022 Amendment 1

For more information on the changes in ISO 27001:2022 Amendment 1, I recommend reading the article ISO27001:2022 Amendment 1: – Absolutely Everything You Need to Know.

What are ISO 27001 internal issues?

ISO 27001 Internal Issues are threats that could hinder the effective functioning of your information security management system (ISMS). In other words, consider them as risks that could prevent the ISMS from achieving its desired outcomes.

ISO 27001 Internal Issues are inherent risks originating within an organisation that can hinder the effective functioning of its Information Security Management System (ISMS). These issues originate within your organisation and, to a large extent, are within your control. These internal risks can impede the ISMS from achieving its objectives, particularly in safeguarding the confidentiality, integrity, and availability of information assets.

Internal issues is defined as – organisational risks to the Information Security Management System (ISMS) achieving its interned outcomes.

ISO 27001 Internal Issues examples

The following are 10 real world examples of ISO 27001 Internal Issues:

  1. Lack of management commitment: This can hinder the successful implementation and maintenance of the ISMS, as employees may not perceive information security as a critical organisational objective.
  2. Inadequate resource allocation: This can lead to gaps in security coverage, delayed responses to incidents, and an inability to implement necessary security measures.  
  3. Lack of employee awareness and training: This can increase the risk of data breaches, system disruptions, and reputational damage.
  4. Poor communication and coordination: This can create silos within the organisation, hindering the collective effort to maintain information security.
  5. Resistance to change: This can lead to non-compliance with security measures, hindering the effectiveness of the ISMS6.
  6. Lack of Regular Reviews and Updates: This can lead to outdated security controls, increased vulnerability to new threats, and non-compliance with evolving standards and regulations.
  7. Inadequate access control management: This can lead to data breaches, system disruptions, and loss of confidentiality, integrity, and availability of information assets.
  8. Insufficient incident response planning: This can exacerbate the impact of security incidents, increasing the risk of data loss, system downtime, and reputational damage.
  9. Inadequate physical and environmental security: This can lead to data breaches, system disruptions, and loss of critical infrastructure.
  10. Lack of Business Continuity and Disaster Recovery Planning: This can lead to significant financial losses, reputational damage, and disruption to business operations.

By identifying and addressing these internal issues, organisations can significantly improve the effectiveness of their ISMS and enhance their overall information security posture.

What are ISO 27001 external issues?

External Issues are inherent risks originating outside an organisation that can hinder the effective functioning of its Information Security Management System (ISMS). These external risks, primarily outside the organisation’s control, can impede the ISMS from achieving its objectives, particularly in safeguarding the confidentiality, integrity, and availability of information assets.

External issues is defined as – external risks to the Information Security Management System (ISMS) achieving its interned outcomes.

ISO 27001 External Issues examples

The following are 10 real world examples of ISO 27001 External Issues:

  1. Legal and Regulatory Requirements: Changes in data privacy laws (e.g., GDPR, CCPA), industry-specific regulations (e.g., HIPAA, PCI DSS), and cybersecurity frameworks (e.g., NIST Cybersecurity Framework). Non-compliance can lead to severe financial penalties, reputational damage, and loss of customer trust.
  2. Competitive Landscape: Actions of competitors, such as new product offerings, market share shifts, and cyberattacks targeting rivals. This can indirectly affect an organisation’s information security posture by increasing pressure to innovate and adapt, potentially leading to security vulnerabilities.
  3. Technological Advancements: Rapid changes in technology, such as the rise of cloud computing, artificial intelligence, and the Internet of Things. This creates new security challenges and opportunities, requiring organisations to constantly update their security controls and adapt to evolving threats.
  4. Economic Conditions: Economic downturns or recessions can impact an organisation’s budget, potentially leading to reduced spending on information security measures. This can weaken the organisation’s security posture, making it more vulnerable to cyberattacks.
  5. Social and Cultural Factors: Changing societal norms and expectations regarding data privacy and security, as well as cultural differences between countries. This can influence an organisation’s approach to information security and its reputation among stakeholders.
  6. Political Stability: Political instability, such as wars, conflicts, or changes in government. This can disrupt business operations and increase the risk of cyberattacks, particularly those targeting critical infrastructure.
  7. Natural Disasters: Natural disasters, such as earthquakes, floods, and hurricanes can damage physical infrastructure and disrupt business operations, potentially impacting the availability and integrity of information assets.
  8. Geopolitical Events: Global events, such as pandemics, trade wars, and geopolitical tensions can create uncertainty and disrupt supply chains, potentially affecting an organisation’s ability to maintain its information security controls.
  9. Cybersecurity Threats: The evolving threat landscape, including new malware, ransomware attacks, and social engineering techniques. This requires organisations to constantly adapt their security measures to stay ahead of cybercriminals.
  10. Stakeholder Expectations: The expectations of customers, suppliers, and other stakeholders regarding data privacy and security can influence an organisation’s information security policies and practices, as well as its reputation and brand image.

ISO 27001 Clause 4.1 Explained: Video Tutorial

In the video ISO 27001 Clause 4.1 Understanding The Organisation And Its Context Explained I show you how to implement it and how to pass the audit.

How to implement ISO 27001 Clause 4.1

To implement ISO 27001 Clause 4.1, follow the ISO 27001 Lead Auditor guide How to implement ISO 27001 Clause 4.1

How to implement ISO 27001 Clause 4.1
How to implement ISO 27001 Clause 4.1

ISO 27001 Clause 4.1 Implementation Checklist

The ISO 27001 Clause 4.1 Implementation Checklist supports the guide on how to implement ISO 27001 Clause 4.1

ISO 27001 clause 4.1 implementation checklist
ISO 27001 clause 4.1 implementation checklist

How to audit ISO 27001 Clause 4.1

To audit ISO 27001 Clause 4.1, follow the ISO 27001 Lead Auditor guide How to audit ISO 27001 Clause 4.1

How to audit ISO 27001 Clause 4.1
How to audit ISO 27001 Clause 4.1

ISO 27001 Clause 4.1 Audit Checklist

The ISO 27001 Clause 4.1 Audit Checklist supports the guide on how to audit ISO 27001 Clause 4.1

ISO 27001 clause 4.1 audit checklist
ISO 27001 clause 4.1 audit checklist

How to pass the ISO 27001 Clause 4.1 audit

To successfully pass an audit of ISO 27001 Clause 4.1 Understanding The Organisation And Its Context you must

  • Identify ISO 27001 internal Issues
  • Identify ISO 27001 external issues
  • Document internal and external issues in a Context of Organisation Document

Watch this short video on what you need to implement and what will be audited for Clause 4.1.

What an auditor looks for

The auditor is going to check a number of areas for compliance with ISO 2001 Clause 4.1 Understanding The Organisation And Its Context.

Let’s take a look at the top 4 in more details.

1. That you have documented your internal and external issues

The simplest way to do this is with the fully populated ISO 27001 Context of Organisation Template. In this short vide I explain why you document your internal and external issues when implementing ISO 27001 clause 4.1.

2. That you are risk managing internal and external issues

If you identify internal issues or external issues that can impact the information security management system and you are not addressing them directly then you need to manage it via risk management.

This means as a minimum putting it on the ISO 27001 risk register and following your ISO 27001 risk management process.

Be sure to link the issue to the risk by cross referencing.

3. That you have approved the included common issues

Auditors often raise common internal issues and external issues that they have seen elsewhere. Therefore, it is good practice to list out all potential internal issues and external issues that could impact your information security management system, regardless of whether they apply to you or not.

If they do not apply to you, record them and explain why. By doing this, you can demonstrate that you have conducted a thorough review and avoid awkward questions or the auditor raising points that you have considered but placed out of scope.

Since you have recorded these issues and determined that they do not apply, you can provide evidence to support your conclusion.

Legal and regulatory compliance is the biggest driver of internal and external issues and as such assess if has been considered.

  • Review the legal register
  • Examine meeting minutes

Top 3 ISO 27001 Clause 4.1 Mistakes and How to Fix Them

Based on experience, the top 3 mistakes people make for ISO 27001 clause 4.1 are

1. You have no evidence that anything actually happened

You need to keep records and minutes and documented evidence.

As a result, recording internal issues and external issues that apply and those that do not shows a thorough understand of the requirement and will avoid awkward questions.

Where internal issues or external issues are identified but you cannot satisfy it you should have this on the risk register and managed via risk management.

This is a point often overlooked.

It must be remember that if you identify an issue and do nothing about, or cannot evidence that you have done something about it, it will be raised as a non conformity.

3. Your document and version control is wrong

Best practice for documentation includes:

  • Keeping your document version control up to date
  • Making sure that version numbers match where used
  • Having a review evidenced in the last 12 months
  • Having documents that have no comments

How can the ISO 27001 Toolkit help with ISO 27001 Clause 4.1?

The ISO 27001 toolkit can significantly assist with ISO 27001 Clause 4.1 by providing pre-written templates and structured guidance. 

The toolkit provides pre written templates for context of the organisation that includes internal issues and external issues as well as a structured methodology on how to identify them and meet their needs.

ISO 27001 Toolkit Business Edition

ISO 27001 Context of Organisation Template

The ISO 27001 Context Of Organisation template fully meets the requirements of ISO 27001 Clause 4.1 and includes pre-written examples of common internal issues and external issues. The template can be purchase as an individual download or as part of the internationally acclaimed and award-winning ISO 27001 Toolkit.

ISO 27001 Context of Organisation Template

ISO 27001 Clause 4.1 FAQ

What is ISO 27001 Clause 4.1?

ISO 27001 clause 4.1 is the requirement of defining what the internal and external issues are to the organisation that directly impact the information security system and addressing or accepting them. 
In February 2024 it was updated to include the need to document if climate change is a relevant issue.

What is the purpose of ISO 27001 Clause 4.1?

The purpose of ISO27001 Clause 4.1 Understanding The Organisation And Its Context is to ensure you identify, manage and mitigate risks to the management system achieving its intended outcomes.

What are the ISO27001:2022 Changes to Clause 4.1?

There are no changes to ISO27001:2022 Clause 4.1 in the 2022 update.

What is ISO 27001 Amendment 1?

The ISO 27001 standard amended the definition of clause 4.1 in February 2024. This amendment, referred to as ISO 27001 Amendment 1: Climate action changes added climate change to ISO 27001 Clause 4.1.

Do I need to document ISO 27001 internal and external issues?

Yes. It’s not sufficient to simply know them; you must also document them to demonstrate that you considered them. A best practice is to share these issues with the Management Review Team and document the fact that they were shared, signed off, and accepted.

Why is ISO 27001 Clause 4.1 important?

ISO 27001 Clause 4.1 is important because it allows you to understand what can impact your information security management system so you can address it. By understanding the internal and external issues that could impact the information security management system allows to you to plan for them, mitigate and manage them and as a result increase in the effectiveness of the information security management system in meeting the business objectives and needs.
Understanding The Organisation And Its Context is important because you need to understand whether or not your management system is going to be effective. To do that you are going to spend time to identify any risks that could impact it.
There is a process of continual Improvement built into ISO 27001 that’s going to continually improve this management system but you need to make sure that you’ve documented and understood the issues and given your fledgling information security management system a fighting chance before it gets off the ground.

What are the benefits of ISO 27001 Clause 4.1?

The following are benefits of implementing ISO 27001 Clause A 4.1:
Improved security: You will have an effective information security management system that address known internal and external issues that could impact it
Reduced risk: You will reduce the risk to your information security management system by identifying those risks and addressing them
Improved compliance: Standards and regulations require context of organisation to be in place
Reputation Protection: In the event of a breach having effectively managed risks to the management system will reduce the potential for fines and reduce the PR impact of an event

Who is responsible for ISO 27001 Clause 4.1?

Responsibility for Understanding The Organisation And Its Context lies with Senior Management and the doing will be delegated to the information security manager.

What are ISO 27001 internal issues?

Internal issues are factors within an organisation that can negatively impact the effectiveness of its Information Security Management System (ISMS). They are inherent risks originating within the organisation that can hinder the ISMS from achieving its objectives, particularly in safeguarding the confidentiality, integrity, and availability of information assets.

How do internal issues differ from external issues?

Internal issues originate within the organisation itself, such as lack of management commitment, inadequate resource allocation, or resistance to change.
External issues stem from factors outside the organisation’s direct control, such as economic downturns, regulatory changes, or competitive pressures.

Why is it important to identify internal issues?

Identifying internal issues is crucial for several reasons:
Risk mitigation: It allows organisations to proactively address potential threats and vulnerabilities.
Improved security posture: It helps strengthen security controls and reduce the likelihood of security incidents.
Enhanced compliance: It demonstrates a commitment to compliance with ISO 27001 and other relevant regulations.
Increased efficiency: It can streamline operations and improve overall productivity.
Enhanced reputation: It builds trust with customers, partners, and stakeholders.

How can I identify internal issues?

Brainstorming sessions: Involve key stakeholders in brainstorming sessions to identify potential internal issues.
PESTLE analysis: Adapt the PESTLE framework to identify internal factors such as political, economic, social, technological, legal, and environmental issues.
Risk assessments: Conduct regular risk assessments to identify and evaluate potential threats, including those arising from internal factors.
Internal audits: Utilise internal audits to uncover potential internal issues and areas for improvement.

When should internal issues be reviewed and updated?

Regularly review and update internal issues at least annually.
Trigger events such as security incidents, internal audits, management reviews, and changes to risk assessments also warrant immediate review.

What are some common examples of internal issues?

Lack of management commitment
Inadequate resource allocation
Lack of employee awareness and training
Poor communication and coordination
Resistance to change
Lack of regular reviews and updates
Inadequate access control management
Insufficient incident response planning

How can organisations address internal issues?

Implement corrective and preventive actions to address identified issues.
Improve communication and collaboration within the organisation.
Enhance employee awareness and training programs.
Allocate adequate resources to information security initiatives.
Obtain management commitment and support for information security.

Who is responsible for identifying and addressing internal issues?

Information security management team
Department heads
Employees at all levels
Internal auditors
Management representatives

What is the relationship between internal issues and risk management?

Internal issues are essentially internal risks. Identifying and addressing these issues is a fundamental part of the risk management process within an ISO 27001 framework.

What are ISO 27001 external issues?

External issues are factors outside an organisation that can negatively impact the effectiveness of its Information Security Management System (ISMS). They are inherent risks originating outside the organisation that can hinder the ISMS from achieving its objectives, particularly in safeguarding the confidentiality, integrity, and availability of information assets.

How do external issues differ from internal issues?

External issues stem from factors outside the organisation’s direct control, such as economic downturns, regulatory changes, or competitive pressures.
Internal issues originate within the organisation itself, such as lack of management commitment, inadequate resource allocation, or resistance to change.

Why is it important to identify external issues?

Identifying external issues is crucial for several reasons:
Risk mitigation: It allows organisations to proactively address potential threats and vulnerabilities.
Improved security posture: It helps strengthen security controls and reduce the likelihood of security incidents.
Enhanced compliance: It demonstrates a commitment to compliance with ISO 27001 and other relevant regulations.
Increased efficiency: It can streamline operations and improve overall productivity.
Enhanced reputation: It builds trust with customers, partners, and stakeholders.

How can organisations address external issues?

Implement corrective and preventive actions to address identified issues.
Improve communication and collaboration within and outside the organisation.
Enhance employee awareness and training programs.
Join industry specific special interest groups.
Maintain contact with authorities.

Who is responsible for identifying and addressing external issues?

Information security management team
Department heads
Employees at all levels
External auditors
Management representatives

What is the relationship between external issues and risk management?

External issues are essentially external risks. Identifying and addressing these issues is a fundamental part of the risk management process within an ISO 27001 framework.

How should internal and external issues be documented?

Document internal and external issues within the Context of the Organisation section of the ISO 27001 documentation.
Use a table format with two columns: Issue Name and The Issue with a detailed description.

Further Reading

What is ISO 27001 Clause 4.1?

How to implement ISO 27001 Clause 4.1

ISO 27001 Clause 4.1 Implementation Checklist

How to audit ISO 27001 Clause 4.1

ISO 27001 Clause 4.1 Audit Checklist

ISO 27001 Clause 4.1 Understanding the Organisation and Its Context Explained

About the author

Stuart Barker is a veteran practitioner with over 30 years of experience in systems security and risk management.

Holding an MSc in Software and Systems Security, Stuart combines academic rigor with extensive operational experience. His background includes over a decade leading Data Governance for General Electric (GE) across Europe, as well as founding and exiting a successful cyber security consultancy.

As a qualified ISO 27001 Lead Auditor and Lead Implementer, Stuart possesses distinct insight into the specific evidence standards required by certification bodies. He has successfully guided hundreds of organizations – from high-growth technology startups to enterprise financial institutions – through the audit lifecycle.

His toolkits represents the distillation of that field experience into a standardised framework. They move beyond theoretical compliance, providing a pragmatic, auditor-verified methodology designed to satisfy ISO/IEC 27001:2022 while minimising operational friction.

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