Skip to main content

CFG-06: Approved Configuration Deviations

CFG 9 — Critical Protect

Mechanisms exist to document, assess and approve or deny deviations to secure baseline configurations.

Renumbered: Formerly AST-02.4 and CFG-02.7 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, CFG-06 was Configuration Enforcement. That control is now CFG-08.2.

Control Question: Does the organization document, assess risk and approve or deny deviations to standardized configurations?

General (26)
Framework Mapping Values
CSA CCM 4.1.0 AIS-02 CCC-08
GovRAMP CM-06
GovRAMP Core CM-06
GovRAMP Low CM-06
GovRAMP Low+ CM-06
GovRAMP Moderate CM-06
GovRAMP High CM-06
IEC TR 60601-4-5 2021 5.2
NIST 800-53 R4 CM-8(6) CM-6
NIST 800-53 R5.2 CM-06 CM-08(06)
NIST 800-53B R5 (low) (source) CM-06
NIST 800-53B R5 (moderate) (source) CM-06
NIST 800-53B R5 (high) (source) CM-06
NIST 800-82 R3 CM-06 CM-08(06)
NIST 800-82 R3 LOW OT Overlay CM-06
NIST 800-82 R3 MODERATE OT Overlay CM-06
NIST 800-82 R3 HIGH OT Overlay CM-06
NIST 800-161 R1 CM-6 CM-8(6)
NIST 800-161 R1 C-SCRM Baseline CM-6
NIST 800-161 R1 Flow Down CM-6
NIST 800-161 R1 Level 2 CM-6
NIST 800-161 R1 Level 3 CM-6 CM-8(6)
NIST 800-171 R3 (source) 03.04.01.a 03.04.02.b 03.04.06.a
NIST 800-171A R3 (source) A.03.04.01.a[01] A.03.04.02.a[02] A.03.04.02.b[01] A.03.04.02.b[02] A.03.04.06.a
NIST 800-207 NIST Tenet 5
SWIFT CSF 2025 2.10
US (13)
EMEA (3)
APAC (1)
Framework Mapping Values
APAC Singapore MAS TRM 2021 3.2.2 11.3.2
Americas (2)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.04.01.A 03.04.02.B 03.04.06.A
Americas Canada OSFI Self-Assessment Guidance 2.2.3 3.2.8

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

Configuration Management (CFG) 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 CFG domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with CFG 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 CFG domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Configuration management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Configuration management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Secure Baseline Configurations (SBC) are used to configure Technology Assets, Applications and/or Services (TAAS) according to the principles of least functionality and least privilege, mostly conforming to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides). ▪ Any deviations from approved baseline configurations are reviewed, approved and documented on a case-by-case basis by IT and/or cybersecurity personnel. ▪ Deviations to baseline configurations are required to have a risk assessment and the business process owner's acceptance of the risk(s) associated with the deviation.

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 document, assess risk and approve or deny deviations to standardized configurations.

Level 4 — Quantitatively Controlled

Asset Management (AST) 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

  1. CFG-06_A01 assessed component configurations are included in the system component inventory.
  2. CFG-06_A02 approved deviations to secure baseline configurations are documented in the system component inventory.
  3. CFG-06_A03 configuration settings that reflect the most restrictive mode consistent with operational requirements are established and documented for components employed within the system using common secure configurations.
  4. CFG-06_A04 changes to the configuration settings are controlled in accordance with organizational policies and procedures.
  5. CFG-06_A05 any deviations from established configuration settings are identified and documented.
  6. CFG-06_A06 any deviations from established configuration settings are approved.
  7. CFG-06_A07 common secure configurations to establish and document configuration settings for components employed within the system are defined.
  8. CFG-06_A08 system components for which approval of deviations is needed are defined.
  9. CFG-06_A09 operational requirements necessitating approval of deviations are defined.
  10. CFG-06_A10 changes to the configuration settings are monitored in accordance with organizational policies and procedures.
  11. CFG-06_A11 deviations to secure baseline configurations are assessed prior to being approved or denied.
  12. CFG-06_A12 the approval or denial decision for each deviation to secure baseline configurations is recorded.

Evidence Requirements

E-AST-33 Tailored Baselines

Documented evidence exists for tailored baseline configurations to address unique business and/or technical requirements (e.g., kiosk, hazardous environments, etc.).

Asset Management

Technology Recommendations

Micro/Small

  • Manual exception management process

Small

  • Manual exception management process

Medium

  • Manual exception management process
  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)
  • Netwrix Auditor (https://netrix.com)

Large

  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)
  • Netwrix Auditor (https://netrix.com)

Enterprise

  • CimTrak Integrity Suite (https://cimcor.com/cimtrak)
  • Netwrix Auditor (https://netrix.com)

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.