STA-12 Supply Chain Agreement Review
The organisation reviews its supply chain agreements every year at minimum and also whenever significant changes occur.
Source: CSA CCM v4.1, STA-12. 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
- Contract review schedule and log · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of agreement reviews with outcome and amendments · Vendor register / contract repository
- Evidence of review triggered by a significant change such as a merger or new regulation · Vendor register / contract repository
- Contract management system report of overdue reviews · Vendor register / contract repository
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Contracts auto-renew without review
- Reviews done only for top suppliers
- No trigger to review after a significant change
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 sheetSTA-11 Primary Service and Contractual Agreement · STA-13 Supply Chain Compliance Assessment