SCOPE.2 Cloud Services in Scope
All cloud services (IaaS, PaaS, SaaS) used by the organisation must be in scope and the applicant retains responsibility for CE controls regardless of cloud provider.
3
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- List of SaaS/IaaS/PaaS services · Policy repository / GRC workspace
- Responsibility matrix per service · Policy repository / GRC workspace
- Admin account list per cloud · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- SaaS apps overlooked
- responsibility wrongly delegated to provider
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 sheet