# NIST SP 800-53 Rev. 5 SA-10(2) — Alternative Configuration Management Processes - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-10-2-alternative-configuration-management-processes - 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(2)`·medium·Component: **System and Services Acquisition** ## What this control requires > Provide alternate configuration management using organizational personnel when a dedicated developer team is unavailable. Ensure proposed changes are reviewed, approved, and analyzed for security and privacy impacts before implementation. This control supports the Organizational Change Review Protocol capability within the System and Services Acquisition family. > > — NIST SP 800-53 Rev. 5, Control SA-10(2) ### In plain English Provide alternate configuration management using organizational personnel when a dedicated developer team is unavailable. In practice, this means you can prove you policy management-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. ## 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(2)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Configuration Management **Policy-as-code.** Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises. **IaC.** Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production. **Drift.** Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. #### 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. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Changes.** Document the trigger, the owner and the cadence. - **Scope:** management, privacy, system, personnel, configuration, review, services, capability. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Signed policy or standard documents the safeguard. Focus: Alternative Configuration Management Processes. ## Common pitfalls - Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - 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. - [**NIST SP 800-171 Rev. 3 3.4.1** — Baseline Configuration](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-1-baseline-configuration) - [**ISO/IEC 27001:2022 A.8.29** — Security testing in development and acceptance](https://support.icompaas.com/compliance/iso-27001-2022/a-8-29-security-testing-in-development-and-acceptance) - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**BSI C5:2020 AM-02** — Acceptable Use and Safe Handling of Assets Policy](https://support.icompaas.com/compliance/bsi-c5-2020/am-02-acceptable-use-and-safe-handling-of-assets-policy) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-15** — Development Process, Standards, And Tools](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-15-development-process-standards-and-tools) - [**Control SA-15(2)** — Security And Privacy Tracking Tools](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-15-2-security-and-privacy-tracking-tools) - [**Control SA-15(6)** — Continuous Improvement](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-15-6-continuous-improvement) - [**Control CM-9(1)** — Assignment Of Responsibility](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-9-1-assignment-of-responsibility) - [**Control SA-4(3)** — Development Methods, Techniques, And Practices](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-4-3-development-methods-techniques-and-practices) - [**Control SA-10(7)** — Security And Privacy Representatives](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-10-7-security-and-privacy-representatives) ## 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(2)` Topics: governance riskconfiguration managementpolicy managementprivacy managementsecure development ## 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.