CMMC Practice Number: CM.L2-3.4.9
CMMC Level: 2 CMMC Domain: Configuration Management (CM)
Practice Summary:
Control and monitor user-installed software.
Contents:
CMMC Practice Implementation |
Assessment Objectives
Determine if:
[a] a policy for controlling the installation of software by users is established;
[b] installation of software by users is controlled based on the established policy; and
[c] installation of software by users is monitored.
Practice Clarification (DOD, CMU)
Software that users have the ability to install is limited to items that the organization approves. When not controlled, users could install software that can create unnecessary risk. This risk applies both to the individual machine and to the larger operating environment. Policies and technical controls reduce risk to the organization by preventing users from installing unauthorized software [b].
Example
You are a system administrator. A user calls you for help installing a software package. They are receiving a message asking for a password because they do not have permission to install the software. You explain that the policy prohibits users from installing software without approval [a]. When you set up workstations for users, you do not provide administrative privileges. After the call, you redistribute the policy to all users ensuring everyone in the company is aware of the restrictions.
Potential Assessment Considerations
• Are user controls in place to prohibit the installation of unauthorized software [a]?
• Is all software in use on the information systems approved [b]?
• Is there a mechanism in place to monitor the types of software a user is permitted to download (e.g., is there a white list of approved software) [c]?
Where To Look
- Configuration management policy;
- procedures addressing user installed software;
- configuration management plan;
- system security plan;
- system design documentation;
- system configuration settings and associated documentation;
- list of rules governing user-installed software;
- system monitoring records;
- system audit logs and records;
- continuous monitoring strategy;
- other relevant documents or records.
Who To Talk To
- Personnel with responsibilities for governing user-installed software;
- personnel operating, using, or maintaining the system;
- personnel monitoring compliance with user-installed software policy;
- personnel with information security responsibilities;
- system or network administrators.
Perform Test On
- Organizational processes governing user-installed software on the system;
- mechanisms enforcing rules or methods for governing the installation of software by users;
- mechanisms monitoring policy compliance.
Additional Information
Approaches to meeting this requirement to control and monitor software installed by users can include policies and procedures. Policies should fully describe what is allowed and procedures should be in place to check that the policy is not violated.
Companies should identify software that may be of greater concern regarding origin or potential for containing malicious code. This requirement is necessary to protect the overall system processing CUI; it is not about software used to actually process CUI.
CMMC Practice Background and References (DOD, CMU) |
Practice Discussion:
DISCUSSION FROM SOURCE: DRAFT NIST SP 800-171 R2
Users can install software in organizational systems if provided the necessary privileges. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation through policies. Permitted software installations include updates and security patches to existing software and applications from organization-approved “app stores.” Prohibited software installations may include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. The policies organizations select governing user-installed software may be organization-developed or provided by some external entity. Policy enforcement methods include procedural methods, automated methods, or both.
CMMC References:
· NIST SP 800-171 Rev 1 3.4.9
· CIS Controls v7.1 2.1, 2.2, 2.6
· NIST CSF v1.1 DE.CM-3
· CERT RMM v1.2 MON:SG2.SP3
· NIST SP 800-53 Rev 4 CM-11