NIST SP 800-53 Rev. 5 SI-7(12) — Integrity Verification

What this control requires

Verify the integrity of user-installed software before execution to minimize the risk of running malicious or error-prone software. This control supports the Integrity Verification Tools capability within the System and Information Integrity family.

In plain English

Verify the integrity of user-installed software before execution to minimize the risk of running malicious or error-prone software. 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 Information Integrity, the assessor will trace your implementation back to the catalogue reference (Control SI-7(12)) and look for objective evidence on the latest two assessment cycles.

How to implement

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.
• Information. 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.
• Verification. Document the trigger, the owner and the cadence.
• Scope: management, information, system, software, capability, tools, verification, policy.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Integrity Verification.

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.

• ISO/IEC 27001:2022 A.8.13 — Information backup
• HIPAA (45 CFR Part 164) 164.312(e)(2)(i) — Transmission Security - Integrity Controls
• NIST SP 800-171 Rev. 3 3.15.3 — Rules of Behavior
• SOC 2 (2017 TSC) C1.2 — Confidential Information Disposal
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions

Related controls in NIST SP 800-53 Rev. 5

• Control SI-7(3) — Centrally Managed Integrity Tools
• Control SI-2(6) — Removal Of Previous Versions Of Software And Firmware
• Control SI-7(16) — Time Limit On Process Execution Without Supervision
• Control SI-4(1) — System-Wide Intrusion Detection System
• Control SI-7(5) — Automated Response To Integrity Violations
• Control SI-2(4) — Automated Patch Management Tools

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SI-7(12)

Topics: governance riskpolicy management