cyberstrikeus CM-2(4) Unauthorized Software
Enhancement of: CM-2
High-Level Description
Family: Configuration Management (CM) Framework: NIST SP 800-53 Rev 5
No description available.
What to Check
- Verify CM-2(4) Unauthorized Software is documented in SSP
- Confirm control is operating effectively
- Review evidence of continuous monitoring for CM-2(4)
- Verify enhancement builds upon base control CM-2
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CM-2(4) 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
Refer to NIST SP 800-53 Rev 5 for the full control statement.
Implementation Guidance
Implement this control per organizational risk assessment and system categorization.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| CM-2(4) Unauthorized Software not implemented | Medium | Configuration Management |
| CM-2(4) partially implemented | Low | Incomplete Configuration Management |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-16 | Configuration |
References
- NIST SP 800-53 Rev 5 - CM-2(4)
- 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 (none) reviewed