| name | CM-7(6)_confined-environments-with-limited-privileges |
| description | Require that the following user-installed software execute in a confined physical or virtual machine environment with limited privileges: [organizatio |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cm-7-6","cm","enhancement"] |
| tech_stack | ["aws","azure","gcp","linux","windows"] |
| cwe_ids | ["CWE-16"] |
| chains_with | ["CM-11","SC-44"] |
| prerequisites | ["CM-7"] |
| severity_boost | {"CM-11":"Chain with CM-11 for comprehensive security coverage","SC-44":"Chain with SC-44 for comprehensive security coverage"} |
CM-7(6) Confined Environments with Limited Privileges
Enhancement of: CM-7
High-Level Description
Family: Configuration Management (CM)
Framework: NIST SP 800-53 Rev 5
Organizations identify software that may be of concern regarding its origin or potential for containing malicious code. For this type of software, user installations occur in confined environments of operation to limit or contain damage from malicious code that may be executed.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CM-7(6) 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
Require that the following user-installed software execute in a confined physical or virtual machine environment with limited privileges: [organization-defined].
Implementation Guidance
Organizations identify software that may be of concern regarding its origin or potential for containing malicious code. For this type of software, user installations occur in confined environments of operation to limit or contain damage from malicious code that may be executed.