CM-7 Least Functionality
Control
Configure the system to provide only [Assignment: mission-essential capabilities] ; and
Prohibit or restrict the use of the following functions, ports, protocols, software, and/or services: [Assignment: organization-defined prohibited or restricted functions, system ports, protocols, software, and/or services].
Discussion
Systems provide a wide variety of functions and services. Some of the functions and services routinely provided by default may not be necessary to support essential organizational missions, functions, or operations. Additionally, it is sometimes convenient to provide multiple services from a single system component, but doing so increases risk over limiting the services provided by that single component. Where feasible, organizations limit component functionality to a single function per component. Organizations consider removing unused or unnecessary software and disabling unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of components, transfer of information, and tunneling. Organizations employ network scanning tools, intrusion detection and prevention systems, and end-point protection technologies, such as firewalls and host-based intrusion detection systems, to identify and prevent the use of prohibited functions, protocols, ports, and services. Least functionality can also be achieved as part of the fundamental design and development of the system (see [SA-8](#sa-8), [SC-2](#sc-2) , and [SC-3](#sc-3)).
Control enhancements (9)
- CM-7(1)Periodic ReviewMODERATEHIGH
- CM-7(2)Prevent Program ExecutionMODERATEHIGH
- CM-7(3)Registration Compliance
- CM-7(4)Unauthorized Software — Deny-by-exception
- CM-7(5)Authorized Software — Allow-by-exceptionMODERATEHIGH
- CM-7(6)Confined Environments with Limited Privileges
- CM-7(7)Code Execution in Protected Environments
- CM-7(8)Binary or Machine Executable Code
- CM-7(9)Prohibiting The Use of Unauthorized Hardware
Related controls
Need CM-7 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.
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.
