OpenParable
Skip to content
← Back to skills

CM-3(2)_testing-validation-and-documentation-of-changes

Testing & Quality

CM-3(2)_testing-validation-and-documentation-of-changes is an Agent Skill for testing & quality published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Test, validate, and document changes to the system before finalizing the implementation of the changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-53_rev5/CM_configuration-management/CM-3(2)_testing-validation-and-documentation-of-changes/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cm-3-2-testing-validation-and-documentation-of-changes, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

CM-3(2) Testing, Validation, and Documentation of Changes

Enhancement of: CM-3

High-Level Description

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

Changes to systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6 . Organizations ensure that testing does not interfere with system operations that support organizational mission and business functions. Individuals or groups conducting tests understand security and privacy policies and procedures, system security and privacy policies and procedures, and the health, safety, and environmental risks associated with specific facilities or processes. Operational systems may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls.

What to Check

  • Verify CM-3(2) Testing, Validation, and Documentation of Changes is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for CM-3(2)
  • Verify enhancement builds upon base control CM-3

How to Test

Step 1: Review Documentation

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

ToolPurposeUsage
cloud-audit-mcpCheck configuration baselinescloud_audit_config
AWS CLIReview Config rulesaws configservice describe-config-rules

Remediation Guide

Control Statement

Test, validate, and document changes to the system before finalizing the implementation of the changes.

Implementation Guidance

Changes to systems include modifications to hardware, software, or firmware components and configuration settings defined in CM-6 . Organizations ensure that testing does not interfere with system operations that support organizational mission and business functions. Individuals or groups conducting tests understand security and privacy policies and procedures, system security and privacy policies and procedures, and the health, safety, and environmental risks associated with specific facilities or processes. Operational systems may need to be taken offline, or replicated to the extent feasible, before testing can be conducted. If systems must be taken offline for testing, the tests are scheduled to occur during planned system outages whenever possible. If the testing cannot be conducted on operational systems, organizations employ compensating controls.

Risk Assessment

FindingSeverityImpact
CM-3(2) Testing, Validation, and Documentation of Changes not implementedMediumConfiguration Management
CM-3(2) partially implementedLowIncomplete Configuration Management

CWE Categories

CWE IDTitle
CWE-16Configuration

References

Checklist

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