ISO 27001:2022 Annex A 5.23 – Information Security for Use of Cloud Services Explained

Cloud services change the control boundary, not the responsibility.

Annex A 5.23 exists to ensure organisations define, manage, and maintain information security when using cloud services, recognising that control is shared between the organisation and the cloud service provider.

This control is preventative in nature. It focuses on ensuring cloud services are selected, used, and exited in a way that remains aligned with the organisation’s information security requirements.

ISO 27001

Quick Guide: Annex A 5.23 at a Glance

Annex A 5.23 of ISO 27001:2022 focuses on information security for the use of cloud services.

At a practical level, this means:

  • Defining information security requirements for cloud services
  • Understanding shared responsibility between the organisation and the provider
  • Managing security across the cloud service lifecycle
  • Ensuring cloud usage aligns with organisational risk and obligations
  • Planning for change, exit, and transition from cloud services

The control does not require bespoke cloud contracts or full control over provider environments. It expects organisations to make informed, risk-based decisions about how cloud services are adopted and governed.

In-Depth Guide to Annex A 5.23

What Is Annex A 5.23 and Why Does It Matter?

Cloud services are widely adopted because they offer:

  • Scalability
  • Availability
  • Reduced operational overhead
  • Speed of deployment

However, they also introduce challenges:

  • Limited contractual flexibility
  • Reduced visibility of underlying infrastructure
  • Shared responsibility for security controls
  • Dependency on provider resilience and governance

Annex A 5.23 ensures organisations do not assume security is automatically handled by the cloud provider, and instead define how security responsibilities are split, managed, and assured.

This control builds directly on supplier and ICT supply chain controls but addresses cloud-specific characteristics.

How to Implement Annex A 5.23 Effectively

A pragmatic approach to Annex A 5.23 typically includes the following elements.

1. Define Cloud-Specific Information Security Requirements

Organisations should define security requirements relevant to their use of cloud services, considering:

  • Confidentiality, integrity, and availability needs
  • Legal and regulatory obligations
  • Industry-specific expectations
  • Business criticality of the service

Requirements may differ between business functions or service types.

2. Understand and Document Shared Responsibility

Cloud services operate on shared responsibility models.

Organisations should clearly understand:

  • Which security controls are managed by the provider
  • Which controls remain the organisation’s responsibility
  • Where responsibilities overlap

Clarity here prevents gaps and false assumptions.

3. Apply Risk-Based Cloud Provider Selection and Use

Before adopting a cloud service, organisations typically consider:

  • Provider security capabilities and assurances
  • Data storage and processing locations
  • Access control and identity integration
  • Resilience, backup, and recovery arrangements

Risk assessment should inform how the service is used, not just whether it is adopted.

4. Address Incident Management for Cloud Services

Cloud services introduce specific incident considerations.

Organisations often define:

  • How cloud-related incidents are identified and escalated
  • Roles and responsibilities during cloud incidents
  • Provider notification and cooperation expectations

Incident handling should reflect shared responsibility.

5. Manage Change Across Cloud Services

Cloud environments change frequently.

This includes:

  • Platform updates
  • Configuration changes
  • New features or services
  • Changes to provider architecture

Annex A 5.23 expects organisations to consider how such changes affect information security and risk.

6. Plan for Exit and Transition

Cloud dependency introduces exit risk.

Organisations should consider:

  • How information is retrieved or transferred
  • Support during transition or decommissioning
  • Removal of access and credentials
  • Ongoing confidentiality obligations

Exit planning reduces lock-in risk and residual exposure.

Common Challenges and How to Overcome Them

  • Assuming cloud providers handle all security
  • Understand and document shared responsibility
  • Applying a single cloud policy to all services
  • Use topic- or function-specific approaches where appropriate
  • Ignoring exit and migration considerations
  • Plan for transition before adoption
  • Lack of visibility into provider changes
  • Define expectations for notification and communication

Cloud risk increases when responsibility boundaries are unclear.

Final Recommendations

Annex A 5.23 is about retaining governance when control is shared.

When cloud services are managed deliberately:

  • Security responsibilities are clear
  • Risks are understood and accepted consciously
  • Incidents are handled more effectively
  • Cloud adoption supports, rather than undermines, the ISMS

Cloud services are a strategic enabler. Annex A 5.23 ensures they are also a governed and secure choice.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls