# NIST SP 800-53 Rev. 5 SA-11(7) — Verify Scope Of Testing And Evaluation - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-7-verify-scope-of-testing-and-evaluation - 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(7)`·high·Component: **System and Services Acquisition** ## What this control requires > Require developers to verify that testing and evaluation fully cover all required controls at organization-defined breadth and depth. Use analytic techniques--from informal reviews to formal modeling--to demonstrate comprehensive control coverage. This control supports the Control Coverage Verification Protocol capability within the System and Services Acquisition family. > > — NIST SP 800-53 Rev. 5, Control SA-11(7) ### In plain English Require developers to verify that testing and evaluation fully cover all required controls at organization-defined breadth and depth. 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(7)) 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. - **Review.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Testing,.** Document the trigger, the owner and the cadence. - **Scope:** management, reviews, organization, system, controls, 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: Verify Scope Of Testing And Evaluation. ## 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. - [**SOC 2 (2017 TSC) PI1.3** — Processing Controls](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/pi1-3-processing-controls) - [**HIPAA (45 CFR Part 164) 164.312(b)** — Audit Controls](https://support.icompaas.com/compliance/hipaa/164-312-b-audit-controls) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-11(4)** — Manual Code Reviews](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-4-manual-code-reviews) - [**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 CP-4(3)** — Automated Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-4-3-automated-testing) - [**Control SA-11(5)** — Penetration Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-5-penetration-testing) - [**Control SA-5(1)** — Functional Properties Of Security Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-5-1-functional-properties-of-security-controls) - [**Control SA-5(4)** — Low-Level Design](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-5-4-low-level-design) ## 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(7)` 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.