STA-03 SSRM Supply Chain
The organisation puts the shared security responsibility model into practice along its whole supply chain, records how it is applied and manages it on an ongoing basis.
Source: CSA CCM v4.1, STA-03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Review records of how responsibilities flow from sub-processors to customers · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Responsibility matrices for upstream providers and downstream customers · Document repository
- Supplier contracts or schedules that set out the split of security duties · Vendor register / contract repository
- Exceptions where a supplier cannot meet its share and the compensating measures · Vendor register / contract repository
First move
Common gaps auditors find
- Responsibility split documented for the organisation's own service but not for upstream providers
- Matrices not refreshed when suppliers change
- No link between the responsibility model and supplier contracts
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