Skip to main content

CFG-02: Configuration Management Program

CFG 9 — Critical Govern

Mechanisms exist to facilitate the implementation of configuration management controls.

Renumbered: Formerly CFG-01 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, CFG-02 was Secure Baseline Configurations. That control is now CFG-04.

Control Question: Does the organization facilitate the implementation of configuration management controls?

General (48)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) S7.1-POF8
AICPA TSC 2017:2022 (used for SOC 2) (source) CC7.1 CC7.1-POF1 CC8.1-POF6 CC8.1-POF12
CIS CSC 8.1 2.0 4.0 4.1 4.2
CIS CSC 8.1 IG1 4.1 4.2
CIS CSC 8.1 IG2 4.1 4.2
CIS CSC 8.1 IG3 4.1 4.2
COBIT 2019 BAI10.01
CSA CCM 4.1.0 UEM-03 UEM-07
CSA IoT SCF 2 CCM-02 CCM-08
GovRAMP CM-01 CM-09
GovRAMP Core CM-09
GovRAMP Low CM-01
GovRAMP Low+ CM-01 CM-09
GovRAMP Moderate CM-01 CM-09
GovRAMP High CM-01 CM-09
IEC TR 60601-4-5 2021 4.2 5.1
ISO 27002 2022 8.3 8.9 8.12
ISO 27017 2015 9.4.1
ISO 27018 2025 8.9 8.12
NIST 800-53 R4 CM-1 CM-9
NIST 800-53 R5.2 CM-01 CM-09
NIST 800-53B R5 (low) (source) CM-01
NIST 800-53B R5 (moderate) (source) CM-01 CM-09
NIST 800-53B R5 (high) (source) CM-01 CM-09
NIST 800-53B R5 (privacy) (source) CM-01
NIST SP 800-66 R2 164.308(a)(1)
NIST 800-82 R3 CM-01 CM-09
NIST 800-82 R3 LOW OT Overlay CM-01
NIST 800-82 R3 MODERATE OT Overlay CM-01 CM-09
NIST 800-82 R3 HIGH OT Overlay CM-01 CM-09
NIST 800-161 R1 CM-1 CM-9
NIST 800-161 R1 C-SCRM Baseline CM-1
NIST 800-161 R1 Flow Down CM-9
NIST 800-161 R1 Level 1 CM-1
NIST 800-161 R1 Level 2 CM-1 CM-9
NIST 800-161 R1 Level 3 CM-1 CM-9
NIST 800-171 R2 (source) NFO - CM-1 NFO - CM-9
NIST 800-171 R3 (source) 03.04.01.a 03.04.03.a
NIST 800-171A R3 (source) A.03.04.01.a[02] A.03.04.03.a
NIST 800-207 NIST Tenet 5
NIST CSF 2.0 (source) PR.PS PR.PS-01 PR.PS-05
NIST Privacy Framework 1.0 PR.PO-P1
OWASP Top 10 2025 A05:2025
PCI DSS 4.0.1 (source) 2.1 2.2 8.5
SCF DPMP 2026 7.12
SPARTA 4.0 CM0023
SWIFT CSF 2025 1.3 2.3
TISAX ISA 6.0.3 5.3.1
US (19)
EMEA (6)
Framework Mapping Values
EMEA Spain CCN-STIC 825 op.exp.2 op.exp.3
EMEA EU DORA 2023 Article 9.3(a) Article 9.3(b) Article 9.3(c) Article 9.3(d)
EMEA EU NIS2 Annex 2024 6.3.1 6.3.2
EMEA UK CAF 4.0 B4 B4.c
EMEA LUX CCSF 22/806 2022 138.b.v
EMEA Saudi Arabia CSCC-1 2019 2-3-1-6
APAC (5)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0912
APAC India SEBI CSCRF 2024 PR.IP.S3
APAC Malaysia RMiT 2025 A10-B2(c)
APAC New Zealand NZISM 3.9 4.3.19.C.01 12.2.5.C.01 12.2.5.C.02 12.2.6.C.01 12.2.6.C.02 17.9.38.C.03 18.1.10.C.01 18.1.10.C.02 18.1.10.C.03 18.1.10.C.04 20.2.14.C.02
APAC Singapore MAS TRM 2021 7.2.1
Americas (4)
Framework Mapping Values
Americas Bermuda BMACCC 2020 6.1-BP1
Americas Canada ITSP-10-171 2025 03.04.01.A 03.04.03.A
Americas Canada OSFI B-13 2022 3.2.8
Americas Canada PIPEDA 2000 P7-4.7.3(c)

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

Configuration Management (CFG) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with CFG domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Configuration management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Configurations mostly conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides).

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).

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 facilitate the implementation of configuration management controls.

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

  1. CFG-02_A01 the scope for the configuration management plan is organization-wide.
  2. CFG-02_A02 the types of changes to the system that are configuration-controlled are defined.
  3. CFG-02_A03 a configuration management plan for systems, applications and services is developed and documented.
  4. CFG-02_A04 a configuration management plan for systems, applications and services is implemented.
  5. CFG-02_A05 the current configuration management policy is reviewed / updated organization-defined frequency.
  6. CFG-02_A06 the current configuration management policy is reviewed / updated following organization-defined events.
  7. CFG-02_A07 personnel or roles to review and approve the configuration management plan is/are defined.
  8. CFG-02_A08 the configuration management plan addresses roles.
  9. CFG-02_A09 the configuration management plan addresses responsibilities.
  10. CFG-02_A10 the configuration management plan addresses configuration management processes and procedures.
  11. CFG-02_A11 the configuration management plan establishes a process for identifying configuration items throughout the system development life cycle.
  12. CFG-02_A12 the configuration management plan establishes a process for managing the configuration of the configuration items.
  13. CFG-02_A13 the configuration management plan defines the configuration items for the system.
  14. CFG-02_A14 the configuration management plan places the configuration items under configuration management.
  15. CFG-02_A15 the configuration management plan is reviewed and approved by organization-defined personnel or roles.
  16. CFG-02_A16 the configuration management plan is protected from unauthorized disclosure.
  17. CFG-02_A17 the configuration management plan is protected from unauthorized modification.
  18. CFG-02_A18 configuration management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
  19. CFG-02_A19 resources are provided to support configuration management operations, including at a minimum: people, processes, technologies, data and facilities.
  20. CFG-02_A20 responsibility and authority for the performance of configuration management-related activities are assigned to designated personnel.
  21. CFG-02_A21 personnel performing configuration management-related activities have the skills and knowledge needed to perform their assigned duties.

Evidence Requirements

E-AST-27 Configuration Management

Documented evidence of standardized configuration management practices.

Asset Management

Technology Recommendations

Micro/Small

  • Configuration Management (CM) program
  • Change control program

Small

  • Configuration Management (CM) program
  • Change control program

Medium

  • Configuration Management (CM) program
  • Change control program

Large

  • Configuration Management (CM) program
  • Change control program

Enterprise

  • Configuration Management (CM) program
  • Change control program

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.