5.23 Information security for use of cloud services
Requires processes for the acquisition, use, management and exit of cloud services to be established in line with the organisation's own information security requirements. Supporting material frames the aim as preserving
5
artefacts
1
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration and monitoring evidence for the controls the organisation is responsible for · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- The process covering cloud acquisition, use, management and exit, including who may acquire a cloud service · Policy repository / GRC workspace
- The register of cloud services in use, with data classification, owner and criticality per service · Policy repository / GRC workspace
- The shared responsibility position documented per service, showing which controls the provider operates and which the organisation must · Policy repository / GRC workspace
- The exit plan per material service, covering data extraction format, timescale and deletion confirmation · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Responsibility boundary assumed rather than documented, leaving controls neither party operates
- Register incomplete because services are bought on expense cards outside procurement
- Exit plan absent or untested, so extraction feasibility is unknown until the relationship fails
- Provider certifications relied on without checking the specific service and region are inside the certified scope
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet5.22 Monitoring, review and change management of supplier services · 5.24 Information security incident management planning and preparation