What evidence do auditors commonly ask for on STA-05 SSRM Control Ownership?

Control-by-control ownership matrix covering all CCM controls (provider, customer or shared); Completed CAIQ or STAR submission showing SSRM ownership per question; Record of the last review of the ownership assignments; Customer-facing summary of ownership boundaries.

What is the most common gap auditors find on STA-05?

Ownership assigned for some domains only

CSA CCM v4.1 · STA - Supply Chain Management, Transparency, and Accountability

`STA-05` SSRM Control Ownership

The organisation states, for every CSA CCM control, who owns it and how it applies under the shared security responsibility model.

Source: CSA CCM v4.1, STA-05. 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.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Record of the last review of the ownership assignments · Document repository

governing documentDocuments that govern the control

Control-by-control ownership matrix covering all CCM controls (provider, customer or shared) · Policy repository / GRC workspace
Completed CAIQ or STAR submission showing SSRM ownership per question · Document repository
Customer-facing summary of ownership boundaries · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Ownership assigned for some domains only
Shared controls not split into who does which part
Matrix not updated after service architecture changes

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

STA-04 SSRM Guidance · STA-06 SSRM Documentation Review