FedRAMP Moderate
CM - Configuration Management

FedRAMP Moderate CM-3: Configuration Change Control

Determine, document, and approve changes; track, review, audit; CAB or equivalent; analyze security impact.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 42 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 5 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 11.3.1.3 11.3.1.3 Internal scans after significant change
  • 11.5.2 11.5.2 Change detection on critical files
  • 6.5.1 6.5.1 Change control procedure for production

C5 (Germany) · 4 controls

  • C5-AM-03 Commissioning of Hardware
  • C5-DEV-03 Policies for changes to information systems
  • C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
  • C5-DEV-09 Approvals for provision in the production environment

SOC 2 · 4 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-PI1.3 PI1.3 Controls over system processing
  • SOC2-PI1.5 PI1.5 Controls over stored inputs, work in process and outputs
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • DS-6 Enforce security of workload throughout DevOps lifecycle
  • CFTC-SS-32 Timely Advance Notice of Material Planned Changes
  • CFTC-SS-4 Systems Operations Category

CIS Controls v8 · 2 controls

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.6 Securely Manage Enterprise Assets and Software

ISO 27002:2022 · 2 controls

  • 8.31 Separation of development, test and production environments
  • 8.32 Change management

NIST SP 800-218 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.32 Change management

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities
  • CM-3 CM-3 Configuration Change Control
  • CM-3 CM-3 Configuration Change Control

UK Cyber Essentials · 1 control

  • CE-FW.4 Approve and Document Inbound Rules

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CM - Configuration Management

You are reading one control. How much of FedRAMP Moderate have you already done?

FedRAMP Moderate CM-3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 348 were rejected on the ISO 27002:2022 pair alone.

Query this from an agent

The graph holds this control, the 42 it maps to, and the evidence behind each claim, over MCP and REST.