CFG-08: Periodic Configuration Reviews
Mechanisms exist to periodically review Technology Assets, Applications and/or Services (TAAS) configurations to identify and disable unnecessary and/or non-secure functions, ports, protocols and services.
Renumbered: Formerly CFG-03.1 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, CFG-08 was Sensitive / Regulated Data Access Enforcement. That control is now IAC-49.
Control Question: Does the organization periodically review system configurations to identify and disable unnecessary and/or non-secure functions, ports, protocols and services?
General (27)
| Framework | Mapping Values |
|---|---|
| CSA CCM 4.1.0 | AIS-02 |
| GovRAMP | CM-07(01) |
| GovRAMP Moderate | CM-07(01) |
| GovRAMP High | CM-07(01) |
| ISO 27002 2022 | 8.8 8.27 |
| ISO 27017 2015 | 9.2.5 9.2.6 12.6.1 |
| ISO 27018 2025 | 8.8 8.27 |
| NIST 800-53 R4 | CM-7(1) |
| NIST 800-53 R5.2 | CM-07(01) |
| NIST 800-53B R5 (moderate) (source) | CM-07(01) |
| NIST 800-53B R5 (high) (source) | CM-07(01) |
| NIST 800-82 R3 | CM-07(01) |
| NIST 800-82 R3 MODERATE OT Overlay | CM-07(01) |
| NIST 800-82 R3 HIGH OT Overlay | CM-07(01) |
| NIST 800-161 R1 | CM-7(1) |
| NIST 800-161 R1 Level 2 | CM-7(1) |
| NIST 800-161 R1 Level 3 | CM-7(1) |
| NIST 800-171 R2 (source) | 3.4.7 |
| NIST 800-171 R3 (source) | 03.04.06.c 03.04.08.c |
| NIST 800-171A (source) | 3.4.7[a] 3.4.7[b] 3.4.7[c] 3.4.7[d] 3.4.7[e] 3.4.7[f] 3.4.7[g] 3.4.7[h] 3.4.7[i] 3.4.7[j] 3.4.7[k] 3.4.7[l] 3.4.7[m] 3.4.7[n] 3.4.7[o] |
| NIST 800-171A R3 (source) | A.03.04.06.ODP[06] A.03.04.06.c A.03.04.08.c |
| PCI DSS 4.0.1 (source) | 1.2.7 11.6.1 12.3.1 12.3.4 12.4.2 |
| PCI DSS 4.0.1 SAQ A (source) | 11.6.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 1.2.7 11.6.1 12.3.1 |
| PCI DSS 4.0.1 SAQ C (source) | 12.3.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 1.2.7 11.6.1 12.3.1 12.3.4 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 1.2.7 11.6.1 12.3.1 12.3.4 12.4.2 |
US (7)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | CM-7(1) CM-7(1).a CM-7(1).b |
| USA Federal CMMC 2.0 Level 2 | CML2.-3.4.7 |
| USA Federal CJIS Security Policy 6.0 | CM-7(1) |
| USA Federal FedRAMP R5 (moderate) | CM-07(01) |
| USA Federal FedRAMP R5 (high) | CM-07(01) |
| USA Federal IRS 1075 2021 | CM-7(CE-1) CM-7(CE-1).a CM-7(CE-1).b |
| USA Texas TX-RAMP Level 2 | CM-07 (01) |
EMEA (6)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | COS-03.05B |
| EMEA UK DEFSTAN 05-138 2024 | 2430 2507 |
| EMEA UK DEFSTAN 05-138 - L1 2024 | 2507 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 2430 2507 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 2430 2507 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-3-1-2 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC India SEBI CSCRF 2024 | DE.CM.S5 |
| APAC Singapore CCOP CII 2026 | 5.12.2 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.06.C 03.04.08.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 are reviewed only when new operating systems or versions of applications are released.
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 periodically review system configurations to identify and disable unnecessary and/or non-secure functions, ports, protocols and services.
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_A01 the frequency at which to review the system to identify unnecessary or nonsecure functions, ports, protocols, connections, or services is defined.
- CFG-08_A02 organization-defined functions, ports, protocols, software and services deemed to be unnecessary and/or non-secure are disabled or removed.
- CFG-08_A03 essential programs are defined.
- CFG-08_A04 essential functions are defined.
- CFG-08_A05 essential ports are defined.
- CFG-08_A06 essential protocols are defined.
- CFG-08_A07 essential services are defined.
- CFG-08_A08 the use of nonessential programs is defined.
- CFG-08_A09 the use of nonessential programs is restricted, disabled or prevented as defined.
- CFG-08_A10 the use of nonessential functions is defined.
- CFG-08_A11 the use of nonessential functions is restricted, disabled or prevented as defined.
- CFG-08_A12 the use of nonessential ports is defined.
- CFG-08_A13 the use of nonessential protocols is defined.
- CFG-08_A14 the use of nonessential ports is restricted, disabled or prevented as defined.
- CFG-08_A15 the use of nonessential protocols is restricted, disabled or prevented as defined.
- CFG-08_A16 the use of nonessential services is defined.
- CFG-08_A17 the use of nonessential services is restricted, disabled or prevented as defined.
- CFG-08_A18 functions to be disabled or removed when deemed unnecessary or non-secure are defined.
- CFG-08_A19 ports to be disabled or removed when deemed unnecessary or non-secure are defined.
- CFG-08_A20 protocols to be disabled or removed when deemed unnecessary or non-secure are defined.
- CFG-08_A21 software to be disabled or removed when deemed unnecessary or non-secure is defined.
- CFG-08_A22 services to be disabled or removed when deemed unnecessary or non-secure are defined.
- CFG-08_A23 Technology Assets, Applications and/or Services (TAAS) configurations are reviewed at the organization-defined frequency to identify unnecessary and/or non-secure functions, ports, protocols and services.
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
- 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