SA-4 Acquisition Process
Puts security and supply chain requirements into the contract, including the evidence the supplier must provide.
4
artefacts
0
held by a system
0
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Contract templates carrying security and C-SCRM requirements · Vendor register / contract repository
- Evidence of requirements in executed contracts · Vendor register / contract repository
- Acceptance criteria tied to those requirements · Document repository
- Supplier deliverables such as documentation and bills of materials · Vendor register / contract repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- requirements in the template but absent from signed contracts
- no acceptance criteria so requirements are unenforceable
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 sheetSA-3 System Development Life Cycle · SA-5 System Documentation