What evidence do auditors commonly ask for on STA-10 Supply Chain Risk Management?

Supplier risk assessments with dates and scores; Review schedule by supplier tier; Records of reassessment triggered by supplier incidents or changes; Risk register entries for material supplier risks.

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

Risk assessed at onboarding only

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

`STA-10` Supply Chain Risk Management

The organisation reviews the risk factors attached to its supply chain relationships at regular intervals.

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

Vendor register / contract 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

Supplier risk assessments with dates and scores · Vendor register / contract repository
Records of reassessment triggered by supplier incidents or changes · Vendor register / contract repository

governing documentDocuments that govern the control

Review schedule by supplier tier · Vendor register / contract repository
Risk register entries for material supplier risks · Vendor register / contract 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

Risk assessed at onboarding only
Review interval not defined by tier
Findings not fed into the risk register

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-09 Service Bill of Material (BOM) · STA-11 Primary Service and Contractual Agreement