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

SA-10(5) Developer Configuration Management | Mapping Integrity for Version Control

Require the developer of the system, system component, or system service to maintain the integrity of the mapping between the master build data describing the current version of security-relevant hardware, software, and firmware and the on-site master copy of the data for the current version.

Source: NIST SP 800-53 Rev 5, SA-10(5). 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
3
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
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
  • Change control records · Document repository
  • Configuration management records · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • 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

Start with the 3 of 10 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one 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-10(4) Developer Configuration Management | Trusted Generation · SA-10(6) Developer Configuration Management | Trusted Distribution