# NIST SP 800-53 Rev. 5 SA-11(4) — Manual Code Reviews - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-4-manual-code-reviews - 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-11(4)`·high·Component: **System and Services Acquisition** ## What this control requires > Require developers to manually review organization-defined critical code using specified processes and techniques. Focus on identifying context-specific weaknesses, verifying access control matrices, and assessing cryptographic implementations. This control supports the Contextual Manual Review Protocol capability within the System and Services Acquisition family. > > — NIST SP 800-53 Rev. 5, Control SA-11(4) ### In plain English Require developers to manually review organization-defined critical code using specified processes and techniques. 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. 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-11(4)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. #### 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. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **Access Control.** Document the trigger, the owner and the cadence. - **Cryptographic.** Document the trigger, the owner and the cadence. - **Scope:** management, access control, reviews, organization, system, review, services, capability. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Manual Code Reviews. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**HIPAA (45 CFR Part 164) 164.310(a)(2)(iii)** — Facility Access Controls - Access Control and Validation Procedures](https://support.icompaas.com/compliance/hipaa/164-310-a-2-iii-facility-access-controls-access-control-and-validation-procedures) - [**NIST SP 800-171 Rev. 3 3.1.5** — Least Privilege](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-5-least-privilege) - [**SOC 2 (2017 TSC) A1.3** — Testing of System Recovery Procedures](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/a1-3-testing-of-system-recovery-procedures) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-11(7)** — Verify Scope Of Testing And Evaluation](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-7-verify-scope-of-testing-and-evaluation) - [**Control SA-8(4)** — Partially Ordered Dependencies](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-8-4-partially-ordered-dependencies) - [**Control AC-3(15)** — Discretionary And Mandatory Access Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-3-15-discretionary-and-mandatory-access-control) - [**Control SA-11(6)** — Attack Surface Reviews](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-6-attack-surface-reviews) - [**Control SA-17(1)** — Formal Policy Model](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-17-1-formal-policy-model) - [**Control SA-4(12)** — Data Ownership](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-4-12-data-ownership) ## 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-11(4)` Topics: governance riskcode review testingpolicy management ## 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.