cm-2-6-development-and-test-environments

name	CM-2(6)_development-and-test-environments
description	Maintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","cm-2-6","cm","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-16"]
chains_with	["CM-4","SC-3","SC-7"]
prerequisites	["CM-2"]
severity_boost	{"CM-4":"Chain with CM-4 for comprehensive security coverage","SC-3":"Chain with SC-3 for comprehensive security coverage","SC-7":"Chain with SC-7 for comprehensive security coverage"}

CM-2(6) Development and Test Environments

Enhancement of: CM-2

High-Level Description

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

Establishing separate baseline configurations for development, testing, and operational environments protects systems from unplanned or unexpected events related to development and testing activities. Separate baseline configurations allow organizations to apply the configuration management that is most appropriate for each type of configuration. For example, the management of operational configurations typically emphasizes the need for stability, while the management of development or test configurations requires greater flexibility. Configurations in the test environment mirror configurations in the operational environment to the extent practicable so that the results of the testing are representative of the proposed changes to the operational systems. Separate baseline configurations do not necessarily require separate physical environments.

What to Check

• Verify CM-2(6) Development and Test Environments is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for CM-2(6)
• 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(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