SA-10 Developer Configuration Management
Requires the developer or supplier to manage configuration of what they deliver, and to prove it.
3
artefacts
2
held by a system
0
at each review
easy
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
- Developer configuration management requirements in contract · Vendor register / contract repository
- Evidence of the developer's configuration management such as version and change records · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Integrity verification of delivered items · Document repository
First move
Automate the pull from your Vendor register / contract repository. Vendor register with review dates and attached assurance reports; expiry-driven reminders, not an annual scramble.
Common gaps auditors find
- delivered builds not reproducible
- developer change records unavailable to the organization
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-9 External System Services · SA-11 Developer Testing and Evaluation