STA-02 SSRM Supply Chain
Apply and manage the shared security responsibility model along the whole supply chain behind the cloud service, and document how it is applied.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document 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
- Evidence of management activity, such as periodic confirmation with suppliers · Vendor register / contract repository
governing documentDocuments that govern the control
- Documentation of the model applied to each supply chain tier · Document repository
- Identification of where responsibility passes between parties · Document repository
- Gaps identified and how they are closed · Document 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
- Model applied to the direct relationship only, with fourth parties unexamined
- Responsibility boundaries assumed rather than agreed
- Documentation produced at onboarding and never revisited
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