# NIST SP 800-53 Rev. 5 SA-10(5) — Mapping Integrity For Version Control - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-10-5-mapping-integrity-for-version-control - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › SA — System and Services Acquisition - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SA-10(5)`·high·Component: **System and Services Acquisition** ## What this control requires > Require developers to maintain the integrity of mappings between master build data and on-site master copies of security-relevant hardware, software, and firmware. This ensures consistency across development and operational environments. This control supports the Master Mapping Integrity Framework capability within the System and Services Acquisition family. > > — NIST SP 800-53 Rev. 5, Control SA-10(5) ### In plain English Require developers to maintain the integrity of mappings between master build data and on-site master copies of security-relevant hardware, software, and firmware. In practice, this means you can prove you security-relevant system-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **System and Services Acquisition**, the assessor will trace your implementation back to the catalogue reference (Control SA-10(5)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Security-Relevant.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Hardware.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Scope:** system, application, hardware, software, firmware, environments, review, services. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Mapping Integrity For Version Control. ## Common pitfalls - CI security checks set to warn-only; the merge button is faster than the security feedback. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.8.28** — Secure coding](https://support.icompaas.com/compliance/iso-27001-2022/a-8-28-secure-coding) - [**NIST SP 800-171 Rev. 3 3.13.13** — Mobile Code](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-13-13-mobile-code) - [**CIS Controls v8 16.9** — Train Developers in Application Security Concepts and Secure Coding](https://support.icompaas.com/compliance/cis-controls-v8/16-9-train-developers-in-application-security-concepts-and-secure-coding) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-11(9)** — Interactive Application Security Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-9-interactive-application-security-testing) - [**Control SA-18(1)** — Multiple Phases Of System Development Life Cycle](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-18-1-multiple-phases-of-system-development-life-cycle) - [**Control SA-5(5)** — Source Code](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-5-5-source-code) - [**Control SA-20** — Customized Development Of Critical Components](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-20-customized-development-of-critical-components) - [**Control SI-7(6)** — Cryptographic Protection](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-7-6-cryptographic-protection) - [**Control CM-8(7)** — Centralized Repository](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-8-7-centralized-repository) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control SA-10(5)` Topics: application securitysecure developmentcode review testingdevsecops ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.