CFG-08.2: Integrity Assurance & Enforcement (IAE)
Automated mechanisms exist to: (1) Identify unauthorized deviations from an approved secure baseline configuration; and (2) Implement automated resiliency actions to remediate the unauthorized change.
Renumbered: Formerly CFG-06 and CFG-06.1 in SCF 2025.4.
Control Question: Does the organization use automated mechanisms to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change?
General (16)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 2.3 2.4 |
| CIS CSC 8.1 IG1 | 2.3 |
| CIS CSC 8.1 IG2 | 2.3 2.4 |
| CIS CSC 8.1 IG3 | 2.3 2.4 |
| CSA IoT SCF 2 | CCM-03 |
| IEC 62443-4-2 2019 | HDR 3.11(1) NDR 3.11(1) |
| NIST 800-53 R5.2 | CM-03(03) CM-03(05) CM-03(08) CM-11(03) |
| NIST 800-82 R3 | CM-03(03) CM-03(05) CM-03(08) |
| NIST 800-161 R1 | CM-3(8) |
| NIST 800-161 R1 Level 2 | CM-3(8) |
| NIST 800-161 R1 Level 3 | CM-3(8) |
| NIST 800-171 R3 (source) | 03.04.02.a 03.04.02.b 03.04.03.a |
| NIST 800-171A R3 (source) | A.03.04.02.a[01] A.03.04.02.b[01] A.03.04.03.a |
| NIST 800-172 R3 | 03.14.11E |
| NIST 800-172A R3 | A.03.04.02E.ODP[01] DS-A.03.14.11E |
| NIST 800-207 | NIST Tenet 5 |
US (3)
| Framework | Mapping Values |
|---|---|
| USA Federal CMMC 2.0 Level 3 | CM.L3-3.4.2E |
| USA Federal FFIEC ITEH 2016 | II.C.10.a |
| USA Federal IRS 1075 2021 | CM-8(CE-3).b |
EMEA (3)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | OPS-05.02AC OPS-05.03AC OPS-26.05B OPS-26.06B OPS-26.05AS OPS-30.01B.3 SSO-05.01AC.1 COM-03.01AC COM-03.01AC.1 |
| EMEA EU DORA RTS 2024 | Article 11.2(f)(ii) |
| EMEA Saudi Arabia OTCC-1 2022 | 1-5-3-5 |
APAC (4)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | PRO-04 |
| APAC Australia ISM June 2026 | ISM-1471 |
| APAC India SEBI CSCRF 2024 | PR.DS.S6 |
| APAC Singapore Cyber Hygiene Practice 2019 | 4.3(b) |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.02.A 03.04.02.B 03.04.03.A |
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
Configuration Management (CFG) 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 CFG 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 CFG domain capabilities are well-documented and kept current by process owners. ▪ A configuration management team, or similar function, is appropriately staffed and supported to implement and maintain CFG domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of configuration management operations (e.g., Configuration Management Database (CMBD) Asset Management solution). ▪ 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 CFG 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 automatically identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.
Level 4 — Quantitatively Controlled
Configuration Management (CFG) 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
Configuration Management (CFG) 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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- CFG-08.2_A01 the circumstances under which changes are to be prevented or restricted are defined.
- CFG-08.2_A02 changes to the configuration of the system are prevented or restricted under organization-defined circumstances.
- CFG-08.2_A03 automated mechanisms used to remediate unauthorized deviations from approved secure baseline configurations are defined.
- CFG-08.2_A04 automated mechanisms used to identify unauthorized deviations from approved secure baseline configurations are defined.
- CFG-08.2_A05 compliance with software installation policies is enforced using automated mechanisms.
- CFG-08.2_A06 compliance with software installation policies is monitored using automated mechanisms.
- CFG-08.2_A07 unauthorized deviations from an approved secure baseline configuration are identified by automated mechanisms.
- CFG-08.2_A08 automated resiliency actions are implemented to remediate identified unauthorized deviations from the approved secure baseline configuration.
Evidence Requirements
- E-CFG-01 Configuration Review & Unauthorized Change Response Records
-
Documented evidence of periodic configuration reviews and responses to detected unauthorized configuration changes (e.g., integrity assurance alerts and remediation).
Asset Management
Technology Recommendations
Micro/Small
- Document baseline configurations for key systems
Small
- Configuration baseline documentation
- CIS Benchmark hardening guides
Medium
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)
Large
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)
Enterprise
- CimTrak Integrity Suite (https://cimcor.com/cimtrak)