OpenParable
Skip to content
← Back to skills

CM-4(2)_verification-of-controls

Testing & Quality

CM-4(2)_verification-of-controls 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.

After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regar

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-4(2)_verification-of-controls/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cm-4-2-verification-of-controls, 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-4(2) Verification of Controls

Enhancement of: CM-4

High-Level Description

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

Implementation in this context refers to installing changed code in the operational system that may have an impact on security or privacy controls.

What to Check

  • Verify CM-4(2) Verification of Controls is documented in SSP
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for CM-4(2)
  • Verify enhancement builds upon base control CM-4

How to Test

Step 1: Review Documentation

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

After system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system.

Implementation Guidance

Implementation in this context refers to installing changed code in the operational system that may have an impact on security or privacy controls.

Risk Assessment

FindingSeverityImpact
CM-4(2) Verification of Controls not implementedMediumConfiguration Management
CM-4(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 (SA-11, SC-3, SI-6) reviewed