OpenParable
Skip to content
← Back to skills

CM-1_policy-and-procedures

Business

CM-1_policy-and-procedures is an Agent Skill for business published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Develop, document, and disseminate to [organization-defined]: [organization-defined] configuration management policy that: Procedures to facilitate th

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-1_policy-and-procedures/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cm-1-policy-and-procedures, 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-1 Policy and Procedures

High-Level Description

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

Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

What to Check

  • Verify CM-1 Policy and Procedures is documented in SSP
  • Validate all 4 control requirements are implemented
  • Confirm control is operating effectively
  • Review evidence of continuous monitoring for CM-1

How to Test

Step 1: Review Documentation

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

Develop, document, and disseminate to [organization-defined]: [organization-defined] configuration management policy that: Procedures to facilitate the implementation of the configuration management policy and the associated configuration management controls; Designate an [organization-defined] to manage the development, documentation, and dissemination of the configuration management policy and procedures; and Review and update the current configuration management: Policy [organization-defined] and following [organization-defined] ; and Procedures [organization-defined] and following [organization-defined].

Implementation Guidance

Configuration management policy and procedures address the controls in the CM family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of configuration management policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission/business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to configuration management policy and procedures include, but are not limited to, assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

Risk Assessment

FindingSeverityImpact
CM-1 Policy and Procedures not implementedMediumConfiguration Management
CM-1 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 (PM-9, PS-8, SA-8, SI-12) reviewed