CFG-06.1: Integrity Assurance & Enforcement (IAE)

There is no evidence of a capability to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.

C|P-CMM1 is N/A, since a structured process is required to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.

C|P-CMM2 is N/A, since a well-defined process is required to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.

Configuration Management (CFG) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

• The configuration management function is formally assigned with defined roles and responsibilities.
• An IT infrastructure team, or similar function, ensures that statutory, regulatory and contractual cybersecurity and data privacy obligations are addressed to ensure secure configurations are designed, built and maintained.
• Configuration management is centralized for all operating systems, applications, servers and other configurable technologies.
• Technologies are configured to protect data with the strength and integrity commensurate with the classification or sensitivity of the information and conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides), including test, development, staging and production environments.
• Configurations conform to industry-recognized standards for hardening (e.g., DISA STIGs, CIS Benchmarks or OEM security guides) for test, development, staging and production environments.
• Deviations to baseline configurations are required to have a risk assessment and business process owner approval of the risk(s) associated with the deviation.
• Special baseline configurations are created for higher-risk environments or for systems, applications and services that store, process or transmit sensitive/regulated data.
• An IT Asset Management (ITAM) function, or similar function, ensures compliance with requirements for asset management.
• Logical Access Control (LAC) is used to limit the ability of non-administrators from making configuration changes to systems, applications and services, including the of installation of unauthorized software.
• A Security Incident Event Manager (SIEM), or similar automated tool, monitors for unauthorized activities, accounts, connections, devices and software.
• Unauthorized configuration changes are responded to in accordance with an Incident Response Plan (IRP) to determine if the unauthorized configuration is malicious in nature.
• Unauthorized configuration changes are immediately reverted to approved configurations.
• Configuration monitoring software monitors, reports on and enforces configurations for endpoint devices.
• An Identity & Access Management (IAM) function, or similar function, centrally manages permissions and implements “least privileges” practices the management of user, group and system accounts, including privileged accounts.
• ITAM leverages a Configuration Management Database (CMDB), or similar tool, as the authoritative source of IT assets.
• A formal Change Management (CM) program ensures that no unauthorized changes are made, all changes are documented, services are not disrupted and that resources are used efficiently.

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to identify unauthorized deviations from an approved baseline and implement automated resiliency actions to remediate the unauthorized change.