EvidenceSheet
NIST SP 800-53 Rev 5 · SA - System and Services Acquisition

SA-10 Developer Configuration Management

Require the developer of the system, system component, or system service to: a. Perform configuration management during system, component, or service Selection (one or more): design; development; implementation; operation; disposal; b. Document, manage, and control the integrity of changes to organization-defined configuration items under configuration management; c. Implement only organization-approved changes to the system, component, or service; d. Document approved changes to the system, component, or service and the potential security and privacy impacts of such changes; and e. Track security flaws and flaw resolution within the system, component, or service and report findings to organization-defined personnel.

Source: NIST SP 800-53 Rev 5, 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-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

10
artefacts
2
held by a system
2
at each review
hard
to go live
Document 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

  • Procedures addressing system developer configuration management · Cloud console / configuration management
  • System change authorization records · Document repository

periodic reviewEvidence produced at each review

  • Security flaw and flaw resolution tracking records · Document repository
  • Test of Organizational processes for monitoring developer configuration management; mechanisms supporting and/or implementing the monitoring of developer configuration management · SIEM / log platform

governing documentDocuments that govern the control

  • System and services acquisition policy · Policy repository / GRC workspace
  • Solicitation documentation · Document repository
  • Acquisition documentation · Document repository
  • Service level agreements · Vendor register / contract repository
  • Acquisition contracts for the system, system component, or system service · Vendor register / contract repository
  • System developer configuration management plan · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 2 system-held artefacts from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

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

SA-9(8) External System Services | Processing and Storage Location: U.S. Jurisdiction · SA-10(1) Developer Configuration Management | Software and Firmware Integrity Verification