CM-5(5)_privilege-limitation-for-production-and-operation

CM-5(5) Privilege Limitation for Production and Operation

Enhancement of: CM-5

High-Level Description

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

In many organizations, systems support multiple mission and business functions. Limiting privileges to change system components with respect to operational systems is necessary because changes to a system component may have far-reaching effects on mission and business processes supported by the system. The relationships between systems and mission/business processes are, in some cases, unknown to developers. System-related information includes operational procedures.

What to Check

• Verify CM-5(5) Privilege Limitation for Production and Operation is documented in SSP
• Validate all 2 control requirements are implemented
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CM-5(5)
• Verify enhancement builds upon base control CM-5

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for CM-5(5) 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

Remediation Guide

Control Statement

Limit privileges to change system components and system-related information within a production or operational environment; and Review and reevaluate privileges [organization-defined].

Implementation Guidance

In many organizations, systems support multiple mission and business functions. Limiting privileges to change system components with respect to operational systems is necessary because changes to a system component may have far-reaching effects on mission and business processes supported by the system. The relationships between systems and mission/business processes are, in some cases, unknown to developers. System-related information includes operational procedures.

Risk Assessment

CWE Categories

References

• NIST SP 800-53 Rev 5 - CM-5(5)
• NIST SP 800-53A Rev 5 (Assessment Procedures)
• NIST SP 800-53 Rev 5 Full Catalog

Checklist

• Control documented in SSP
• Implementation evidence collected
• Operating effectiveness validated
• Continuous monitoring in place
• Related controls (AC-2) reviewed