Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
A.5.23 Information security for use of cloud services
Not mandatory by default – decided in your SoA
What it means in plain language
New in 2022: define how you select, use, manage and exit cloud services securely, including shared responsibilities.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
Cloud use must be governed across selection, configuration, shared responsibility, and exit. Remember that the control is about active management of cloud-specific risk, not simply approving a vendor, and that responsibilities must be explicit across the service model and tenancy boundaries.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Cloud services are approved informally, but no shared-responsibility matrix exists for identity, logging, backup, encryption, patching, or incident handling.
Tenant settings are left at defaults, so MFA, retention, region, guest access, or audit logging expectations are not documented, reviewed, or evidenced.
Exit planning is absent, leaving no tested method to export data, revoke access, recover configurations, or transition services without loss of availability or records.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Use the Cloud Services Security Policy to require a pre-use review that covers business purpose, data classification, residency constraints, legal obligations, integration dependencies, and support model. The approval should identify whether the service is SaaS, IaaS, or PaaS, because the organization’s control responsibilities change with the model.
Create a shared-responsibility matrix for each critical cloud platform. Assign who controls identity, privileged access, backup scope, log retention, encryption keys, vulnerability patching, admin audit, and incident response. Reconcile the matrix with contracts, architecture diagrams, and actual administrative roles so responsibility gaps are visible.
Define secure baseline settings and review them after material change. Examples include MFA enforcement, conditional access, approved regions, admin separation, guest user restrictions, logging export, alerting, and retention periods. Validate the baseline during onboarding and after provider feature changes, administrative reorganizations, or new integrations.
Maintain exit plans for important cloud services that describe data export format, retention handover, credential revocation, deletion confirmation, and replacement service onboarding. Test the plan on a risk-based cadence using a small restore or export exercise, and keep records of results, failures, and follow-up actions.
What an auditor will ask to see
Approved cloud service review with data classification, residency, and integration risk documented.
Shared-responsibility matrix naming internal owners, provider duties, and exception approvals.
Screenshots or configuration exports showing MFA, logging, retention, region, and access settings.
Exit plan records, export test results, and evidence of deletion or access revocation after service termination.
Baseline documents in the kit
These free kit documents help you document or evidence A.5.23. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.