ISO 27001 Annex A 5.23 Information security for use of cloud services
What it says
Processes for acquisition, use, management and exit from cloud services shall be established in accordance with the organization's information security requirements.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEstablish processes for acquiring, using, managing and exiting cloud services, each in accordance with your organisation's information security requirements.
Your organisation must establish processes for four stages of its cloud services, in accordance with its own information security requirements:
- Acquisition: choosing and buying a service.
- Use: how people and systems may use it.
- Management: running it, including which controls the provider handles and which you handle.
- Exit: leaving it, including getting your information out.
The requirements come first: a provider's standard offer does not replace them. Cloud services include software you subscribe to online, not only hosted infrastructure.
Free. Save your status, tasks and notes.
Why it matters
A cloud service can start on a credit card with nobody checking its security terms, and if each side assumes the other runs a control, nobody runs it. Established processes make someone decide these things early, including how your information comes back at exit.
How to implement
Write the security requirements every cloud service must meet.
Base them on your risks and information classification (Annex A 5.12). Cover where information may be stored, access, logging, backup, incident notice, subcontracting and the return of information. Annex A 5.20 covers agreeing requirements with each supplier.
Set the process for acquiring a service.
Route every service through one approval, new ones (including free trials) and existing ones. Assess the risks, then compare the provider's agreement and assurance reports with your requirements. Cloud terms are often fixed: for any gap, add your own safeguard, choose another service or have a named person accept the remaining risk.
Record who manages each control, service by service.
Start from the provider's shared responsibility documents. Where a control is shared, name each side's part. Write down what you must configure yourself, such as access rules (Annex A 5.15), logging and backup, because a provider's default settings may not meet your requirements.
Set rules for use and ongoing management.
State what information may go in each service and who may administer it. Say who reads provider change notices, how incidents involving the provider are handled and how the service is monitored (Annex A 5.22). If you use several providers, say how controls and connections between them are managed.
Write the exit process, with a plan for each service you cannot quickly replace.
For every service, cover getting information, configuration and code out, and removing accounts and data. In each plan, add the export format, how long the provider keeps the service open after notice and what replaces it. Try an export before relying on the plan.
Keep it running
Re-check a service when the provider changes its terms, data location or subcontractors, or when more sensitive information goes into it. On a schedule you set, search expense claims and web traffic logs for services that skipped the acquisition process.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The cloud service list, matched to expense records and web traffic or single sign-on logs.
Look at
Whether services in use are missing, and whether each went through the acquisition process.
Good evidence
Every cloud service found in those sources is on the list, with a recorded approval against your information security requirements.
- Check 2 of 5What an auditor asks for
Ask for
The rules for using a sampled service, with its live sharing and administrator settings.
Look at
Whether the settings match the rules on what information may go in and who may administer it.
Good evidence
The live settings match the rules, and no administrator or sharing setting falls outside them.
- Check 3 of 5What an auditor asks for
Ask for
The responsibility record for a sampled service, with live settings for the controls assigned to you.
Look at
Whether every control is assigned to you, to the provider, or to both with each part named, and whether your parts are switched on in the service.
Good evidence
No control or part of one is left unassigned, and everything assigned to you is active in the service.
- Check 4 of 5What an auditor asks for
Ask for
A recent provider change notice and what was done with it.
Look at
Whether someone assessed the change against your requirements.
Good evidence
The notice has a recorded assessment and decision by the person the process names.
- Check 5 of 5What an auditor asks for
Ask for
The exit process and the plan for a service you cannot quickly replace, with a recent test export and the records of any service you have left.
Look at
Whether the export was complete and usable, whether the plan covers a replacement, and whether any service you left still holds your accounts or data.
Good evidence
The export opened and was complete, the plan states what replaces the service, and any service you left has no active accounts and a record that your data was removed.
Mappings
Closest match in ASD Information Security Manual: ISM-1437, Utilising cloud providers for hosting online services, which this control covers in full and more.
ASD Information Security Manual: 3 mappings
This control is broader than ISM-1437.
ISM-1437 requires cloud service providers to be used for hosting online services. Adopting cloud hosting brings those services within the processes for acquiring, using, managing and exiting cloud services that Annex A 5.23 requires, so those processes govern how the ISM-1437 arrangement is set up and managed securely. Annex A 5.23 covers the whole cloud service life cycle for any use, while ISM-1437 is a specific decision about where online services are hosted.
- ISM-1529Only community or private clouds for outsourced SECRET and TOP SECRET servicesPartially overlaps
This control partially overlaps ISM-1529.
ISM-1529 requires that outsourced SECRET and TOP SECRET cloud services are only delivered using community or private cloud deployment models. Annex A 5.23 requires the organisation to establish processes for acquisition, use, management and exit from cloud services in accordance with information security requirements, which is where an organisation would define and enforce cloud selection criteria (including any permitted deployment models). However, Annex A 5.23 does not itself mandate classification-based deployment restrictions (e.g. banning public cloud for SECRET/TOP SECRET), so it only partially covers the governance mechanism that could implement ISM-1529's stricter requirement.
This control supports ISM-1638.
ISM-1638 requires documenting outsourced cloud services and key governance attributes such as purpose, data classification, contractual arrangements, and next security assessment due date. Annex A 5.23 requires establishing processes for acquisition, use, management and exit from cloud services in line with information security requirements, and a cloud service register supports those lifecycle processes by providing traceability of what services exist and who owns/uses them. Annex A 5.23 is broader (lifecycle control design and execution), while ISM-1638 is a specific record that helps operationalise those processes.
ASD Essentials for enterprise IT: 2 mappings
- IT.GOV-11.1Base supplier selection on proportionate cyber supply chain risk assessmentsPartially overlaps
This control partially overlaps IT.GOV-11.1.
IT.GOV-11.1 requires suppliers of software, hardware and services to be selected and engaged on the basis of a proportionate cyber supply chain risk assessment, with assurance evidence retained. For cloud service providers this directly forms part of the acquisition process that ISO/IEC 27001 Annex A 5.23 requires to be established in line with the organisation's information security requirements. IT.GOV-11.1 applies to all supplier types but only at selection, while Annex A 5.23 is limited to cloud services and also covers their use, management and exit.
This control partially overlaps IT.GOV-11.2.
IT.GOV-11.2 requires ongoing assurance that suppliers continue to meet their cyber security commitments, with action taken when assurance lapses or supplier risk changes. For cloud service providers this forms part of the use and management processes that ISO/IEC 27001 Annex A 5.23 requires to align with the organisation's information security requirements. IT.GOV-11.2 applies to all suppliers but only to ongoing assurance, while Annex A 5.23 is limited to cloud services and also covers acquisition and exit.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.
Get help with this control
ISO 27001 training
Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.




