NIST 800-171 3.4.7Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services
Overview
This control requires organizations to restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. It is part of the Configuration Management family and is one of the 110 NIST SP 800-171 Rev. 2 requirements DFARS 252.204-7012 obliges contractors handling CUI to implement — the requirement set CMMC Level 2 assesses. Implementing it protects CUI and supports the score you self-report to SPRS.
Assessment Objectives
- 1Determine if the organization has defined policies and procedures to restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services
- 2Determine if the organization implements mechanisms to restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services
- 3Verify that the implementation is consistent with organizational policies and NIST 800-171 requirements
Implementation Guidance
Implement this control by establishing documented policies and procedures, deploying appropriate technical controls, and maintaining evidence of ongoing compliance. Regularly review and test the implementation to ensure effectiveness and address any gaps identified during assessments.
Common Audit Gaps
Related DFARS Clauses
Frequently Asked Questions
What is NIST 800-171 control 3.4.7?
NIST 800-171 control 3.4.7 requires organizations to restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. This control is part of the Configuration Management family and is one of the 110 requirements DFARS 252.204-7012 obliges contractors handling CUI to implement — the requirement set CMMC Level 2 assesses.
How do you implement NIST 800-171 3.4.7?
To implement control 3.4.7, establish documented policies, deploy technical controls to restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services, and maintain evidence of compliance. Regular testing and monitoring are essential.
What evidence is needed for NIST 800-171 3.4.7?
Evidence for control 3.4.7 typically includes written policies and procedures, system configuration documentation, audit logs showing enforcement, and records of periodic reviews. Assessors will look for both documentation and technical implementation.
Related Controls
3.4.6|Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities
Configuration Management
3.4.8|Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software
Configuration Management
3.11.1|Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI
Risk Assessment
More in Configuration Management
Related Guides
Free Compliance Tools
Check your compliance for 3.4.7
Run our free CUI Auditor to see if your tools meet this control's requirements.
Audit Your Tech Stack FreeTurn this gap analysis into a remediation plan
This 3.4.7 control breakdown is the start, not the answer. Book a 25-minute compliance assessment — you leave with a prioritized roadmap and a fixed-fee implementation quote.
Book a 25-min assessmentRelated: how much CMMC certification costs — DoD’s own priced figures
Discussion
Share your experience implementing this in your organization.
Join the Club to unlock joining discussions
Free membership — access intelligence, save your work, and more.
Create free account