NIST SP 800-53 Rev. 5 SA-11(4) — Manual Code Reviews

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.

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
• NIST SP 800-171 Rev. 3 3.1.5 — Least Privilege
• SOC 2 (2017 TSC) 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
• Control SA-8(4) — Partially Ordered Dependencies
• Control AC-3(15) — Discretionary And Mandatory Access Control
• Control SA-11(6) — Attack Surface Reviews
• Control SA-17(1) — Formal Policy Model
• Control SA-4(12) — Data Ownership

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SA-11(4)

Topics: governance riskcode review testingpolicy management