What evidence do auditors commonly ask for on STA-11 Primary Service and Contractual Agreement?

Standard customer or supplier agreement template with each listed term located; Contract review checklist mapping the ten required terms to clauses; Sample of signed agreements checked against the checklist; Data processing addendum and exit or termination schedule; Operational resilience clauses such as recovery objectives and continuity commitments.

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

Agreements silent on data location or termination assistance

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

`STA-11` Primary Service and Contractual Agreement

Service agreements must contain, as a minimum, agreed terms on: the scope, nature and location of the relationship and services; security requirements including the shared responsibility split; change management; logging and monitoring; incident handling and communication; audit rights and third-party assessment; ending the service; interoperability and portability; data privacy; and operational resilience.

Source: CSA CCM v4.1, STA-11. 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 signed agreements checked against the checklist · Vendor register / contract repository

governing documentDocuments that govern the control

Standard customer or supplier agreement template with each listed term located · Vendor register / contract repository
Contract review checklist mapping the ten required terms to clauses · Vendor register / contract repository
Data processing addendum and exit or termination schedule · HR system / LMS
Operational resilience clauses such as recovery objectives and continuity commitments · 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

Agreements silent on data location or termination assistance
Right to audit replaced by reliance on certifications without agreement
Operational resilience term missing from contracts signed before the 4.1 update

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-10 Supply Chain Risk Management · STA-12 Supply Chain Agreement Review