Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
CCC - Change Control & Configuration Management

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-07: Detection of Baseline Deviation

Detect drift away from the approved configuration baseline and raise a proactive notification to the responsible party rather than waiting for the next review.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 37 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 5 controls

  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • CM-6(1) Automated Management, Application, and Verification
  • CM-8(3) Automated Unauthorized Component Detection
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

FedRAMP Moderate · 5 controls

  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • CM-6(1) Automated Management, Application, and Verification
  • CM-8(3) Automated Unauthorized Component Detection
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

PCI DSS 4.0 · 5 controls

  • 1.2.8 1.2.8 NSC configuration files secured and consistent
  • 10.3.4 10.3.4 File integrity monitoring on audit logs
  • 11.5.2 11.5.2 Change detection on critical files
  • 11.6.1 11.6.1 Payment page tamper detection
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources
  • PV-2 Audit and enforce secure configurations
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

C5 (Germany) · 1 control

  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 1 control

  • CIS-4.1 Establish and Maintain a Secure Configuration Process

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.9 Configuration management

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

NIST SP 800-172 · 1 control

  • 3.4.2e Automated Detection and Remediation of Unauthorized Software

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CCC - Change Control & Configuration Management

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-07 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 37 it maps to, and the evidence behind each claim, over MCP and REST.