CHG-04.4: Dual Approval For High-Impact Environments
Mechanisms exist to require dual approval for any changes that might result in a serious incident that could adversely impact: (1) Business processes; and/or (2) Technology Assets, Applications, Services and/or Data (TAASD).
Code reused: In SCF 2025.4 and earlier, CHG-04.4 was Permissions To Implement Changes. That control is now CHG-04.2.
Control Question: Does the organization require dual approval for any changes that might result in a serious incident that could adversely impact: (1) Business processes; and/or (2) Technology Assets, Applications, Services and/or Data (TAASD)?
General (1)
| Framework | Mapping Values |
|---|---|
| IEC 62443-4-2 2019 | CR 2.1(4) |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Saudi Arabia OTCC-1 2022 | 2-2-1-6 |
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
Change Management (CHG) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). 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. ▪ Standardized Operating Procedures (SOP) associated with CHG domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with CHG domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Change management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Change management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Business stakeholders and process owners ensure changes to Technology Assets, Applications and/or Services (TAAS) within the System Development Lifecycle (SDLC) are controlled through formal change control procedures.
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 require dual approval for any changes that might result in a serious incident that could adversely impact: (1) Business processes; and/or (2) Technology Assets, Applications, Services and/or Data (TAASD).
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
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
- CHG-04.4_A01 business processes where a proposed change might result in a serious incident that could adversely impact operations are identified as requiring dual approval.
- CHG-04.4_A02 Technology Assets, Applications, Services and/or Data (TAASD) where a proposed change might result in a serious incident that could adversely impact operations are identified as requiring dual approval.
- CHG-04.4_A03 processes and/or technologies are implemented to require dual approval for changes that might result in a serious incident that could adversely impact operations.
Technology Recommendations
Micro/Small
- Inventory embedded devices and document security settings
Small
- Embedded device inventory
- Default credential change policy
Medium
- Embedded/IoT device security program
- Network segmentation for IoT
Large
- IoT/OT security program
- Network segmentation
- IoT security platform (e.g., Claroty, Armis)
Enterprise
- Enterprise IoT/OT security platform (e.g., Claroty, Armis, Dragos)
- Zero-trust IoT architecture