What evidence do auditors commonly ask for on STA-14 Supply Chain Service Agreement Compliance?

Supplier security requirements policy or standard; Contract clauses or supplier code of conduct covering each requirement area; Sample of supplier contracts showing the clauses in place; Supplier attestations or assessment results against the requirements.

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

Requirements imposed on direct suppliers but not flowed down to their subcontractors

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

`STA-14` Supply Chain Service Agreement Compliance

The organisation enforces policies that oblige every service provider in its supply chain to meet its standards in these areas: security of information, confidentiality, control of access, privacy, audit rights, personnel practices, and service levels.

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

Sample of supplier contracts showing the clauses in place · Vendor register / contract repository
Supplier attestations or assessment results against the requirements · Vendor register / contract repository

governing documentDocuments that govern the control

Supplier security requirements policy or standard · Vendor register / contract repository
Contract clauses or supplier code of conduct covering each requirement area · Policy repository / GRC workspace

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

Requirements imposed on direct suppliers but not flowed down to their subcontractors
Personnel vetting expectations missing from supplier terms
Right to audit dropped during negotiation without risk acceptance

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-13 Supply Chain Compliance Assessment · STA-15 Supply Chain Governance Review