cm-11-user-installed-software

name	CM-11_user-installed-software
description	Establish [organization-defined] governing the installation of software by users;
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","cm-11","cm"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-16"]
chains_with	["AC-3","AU-6","CM-2","CM-3","CM-5","CM-6","CM-7","CM-8","PL-4","SI-4"]
prerequisites	[]
severity_boost	{"AC-3":"Chain with AC-3 for comprehensive security coverage","AU-6":"Chain with AU-6 for comprehensive security coverage","CM-2":"Chain with CM-2 for comprehensive security coverage"}

CM-11 User-installed Software

High-Level Description

Family: Configuration Management (CM) Framework: NIST SP 800-53 Rev 5

If provided the necessary privileges, users can install software in organizational systems. To maintain control over the software installed, organizations identify permitted and prohibited actions regarding software installation. Permitted software installations include updates and security patches to existing software and downloading new applications from organization-approved "app stores." Prohibited software installations include software with unknown or suspect pedigrees or software that organizations consider potentially malicious. Policies selected for governing user-installed software are organization-developed or provided by some external entity. Policy enforcement methods can include procedural methods and automated methods.

What to Check

• Verify CM-11 User-installed Software is documented in SSP
• Validate all 3 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CM-11

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for CM-11 implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness

Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.

Tools

Tool	Purpose	Usage
cloud-audit-mcp	Check configuration baselines	cloud_audit_config
AWS CLI	Review Config rules	aws configservice describe-config-rules

Remediation Guide

Control Statement

Establish [organization-defined] governing the installation of software by users; Enforce software installation policies through the following methods: [organization-defined] ; and Monitor policy compliance [organization-defined].