SA-10 Developer Configuration Management
Requires the developer or supplier to manage configuration of what they deliver, and to prove it.
Source: NIST SP 800-161 Rev 1 (supply chain), SA-10. 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 NIST SP 800-161 Rev 1 (supply chain) in the compliance library.
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
- 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
- Developer configuration management requirements in contract · Vendor register / contract repository
- Integrity verification of delivered items · Document repository
First move
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