STA-05 SSRM Documentation Review
Review and validate the shared responsibility documentation for every cloud service the organisation itself consumes.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Vendor register / contract repository
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
- Review records of each provider's shared responsibility documentation · Vendor register / contract repository
- Validation evidence, such as confirmation that customer-side duties are actually performed · Vendor register / contract repository
governing documentDocuments that govern the control
- The inventory of cloud services consumed · Vendor register / contract repository
- Actions raised where a customer-side duty was unowned · Vendor register / contract repository
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
- Provider documentation collected but never read against the organisation's own controls
- Shadow cloud services absent from the inventory
- Customer-side responsibilities identified with nobody assigned to perform them
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 sheetSTA-04 SSRM Control Ownership · STA-06 SSRM Control Implementation