CM-7(5) Authorized Software — Allow-by-exception

Control enhancement of CM-7 Least Functionality

Control

(a)

Identify [Assignment: software programs];

(b)

Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and

(c)

Review and update the list of authorized software programs [Assignment: frequency].

Discussion

Authorized software programs can be limited to specific versions or from a specific source. To facilitate a comprehensive authorized software process and increase the strength of protection for attacks that bypass application level authorized software, software programs may be decomposed into and monitored at different levels of detail. These levels include applications, application programming interfaces, application modules, scripts, system processes, system services, kernel functions, registries, drivers, and dynamic link libraries. The concept of permitting the execution of authorized software may also be applied to user actions, system ports and protocols, IP addresses/ranges, websites, and MAC addresses. Organizations consider verifying the integrity of authorized software programs using digital signatures, cryptographic checksums, or hash functions. Verification of authorized software can occur either prior to execution or at system startup. The identification of authorized URLs for websites is addressed in [CA-3(5)](#ca-3.5) and [SC-7](#sc-7).

Related controls

Need CM-7(5) implemented and evidenced?

We assess where you stand against this control, document the gap, and build the remediation plan your auditor and your board will both accept.

Request an assessment

Control catalog and framework text on this page is reproduced from official NIST publications — a public-domain work of the U.S. Government (17 U.S.C. §105). Maverc commentary, groupings, and readiness guidance are our own and are not part of any NIST publication.