FedRAMP High
CM - Configuration Management

FedRAMP High 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 40 controls across 18 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 Changes to NSC reviewed and approved
  • 10.2.1 Audit logs enabled on system components
  • 11.3.1.3 Internal scans after significant changes
  • 11.5.2 Change detection mechanism (FIM)
  • 6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval

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 Detection and monitoring procedures for security events are in place
  • SOC2-CC8.1 Change management processes are in place
  • SOC2-PI1.3 System processing is complete, valid, accurate, timely, and authorized
  • SOC2-PI1.5 Inputs are processed completely, accurately, and timely for stored data
  • 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

  • NIST800-CM-3 Configuration change control
  • NIST800-SR-4 Provenance. Document, monitor, and maintain valid provenance of the following systems, system components, and associated data: [organization-defined]

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

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 High have you already done?

FedRAMP High CM-3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High 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. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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