Skip to main content

CHG-11: Post Configuration Change Reviews

CHG 3 — Low Detect

Mechanisms exist to perform after-the-fact reviews of configuration change logs to discover any unauthorized changes.

Renumbered: Formerly CHG-04.1 in SCF 2025.4.

Control Question: Does the organization perform after-the-fact reviews of configuration change logs to discover any unauthorized changes?

General (15)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC8.1-POF10 CC8.1-POF11
CSA CCM 4.1.0 CCC-04 CCC-09
GovRAMP CM-05(01)
GovRAMP Core CM-05(01)
GovRAMP Moderate CM-05(01)
GovRAMP High CM-05(01)
NIST 800-53 R4 CM-5(1)
NIST 800-53 R5.2 CM-05(01)
NIST 800-53B R5 (high) (source) CM-05(01)
NIST 800-82 R3 CM-05(01)
NIST 800-82 R3 HIGH OT Overlay CM-05(01)
NIST 800-161 R1 CM-5(1)
NIST 800-161 R1 Level 3 CM-5(1)
NIST 800-171 R3 (source) 03.04.03.d
NIST 800-171A R3 (source) A.03.04.03.d[01] A.03.04.03.d[02]
US (5)
EMEA (2)
Framework Mapping Values
EMEA Germany C5 2026 DEV-08.02B DEV-08.01AC
EMEA Saudi Arabia OTCC-1 2022 1-5-3-5
Americas (2)

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

Level 3 — Well Defined

Change Management (CHG) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with CHG domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with CHG domain capabilities are well-documented and kept current by process owners. ▪ A centralized Change Management Office (CMO), or similar function, is appropriately staffed and supported to implement and maintain CHG domain capabilities. ▪ Technical procedures (e.g., ITIL change enablement) are utilized along with change management governance capabilities (e.g., Change Advisory Board (CAB)) to ensure successful, efficient and secure change management operations. ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CHG domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to perform after-the-fact reviews of configuration change logs to discover any unauthorized changes.

Level 4 — Quantitatively Controlled

Change Management (CHG) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. CHG-11_A01 mechanisms used to automate the enforcement of access restrictions are defined.
  2. CHG-11_A02 access restrictions for change are enforced using organization-defined automated mechanisms.
  3. CHG-11_A03 audit records of enforcement actions are automatically generated.

Technology Recommendations

Micro/Small

  • Configuration Management Database (CMDB)

Small

  • Configuration Management Database (CMDB)

Medium

  • Configuration Management Database (CMDB)
  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Large

  • Configuration Management Database (CMDB)
  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Enterprise

  • Configuration Management Database (CMDB)
  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.