cm-5-4-dual-authorization

name	CM-5(4)_dual-authorization
description	Enforce dual authorization for implementing changes to [organization-defined].
category	configuration
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","cm-5-4","cm","enhancement"]
tech_stack	["aws","azure","gcp","linux","windows"]
cwe_ids	["CWE-16"]
chains_with	["AC-2","AC-5","CM-3"]
prerequisites	["CM-5"]
severity_boost	{"AC-2":"Chain with AC-2 for comprehensive security coverage","AC-5":"Chain with AC-5 for comprehensive security coverage","CM-3":"Chain with CM-3 for comprehensive security coverage"}

CM-5(4) Dual Authorization

Enhancement of: CM-5

High-Level Description

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

Organizations employ dual authorization to help ensure that any changes to selected system components and information cannot occur unless two qualified individuals approve and implement such changes. The two individuals possess the skills and expertise to determine if the proposed changes are correct implementations of approved changes. The individuals are also accountable for the changes. Dual authorization may also be known as two-person control. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals. System-level information includes operational procedures.

What to Check

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

How to Test

Step 1: Review Documentation

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

Enforce dual authorization for implementing changes to [organization-defined].

Implementation Guidance

Organizations employ dual authorization to help ensure that any changes to selected system components and information cannot occur unless two qualified individuals approve and implement such changes. The two individuals possess the skills and expertise to determine if the proposed changes are correct implementations of approved changes. The individuals are also accountable for the changes. Dual authorization may also be known as two-person control. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals. System-level information includes operational procedures.