Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
LOG - Logging & Monitoring

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-LOG-07: Logging Scope

Decide, document and implement which system events and metadata are to be logged, and revisit that scope at least annually and whenever the threat picture changes.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 7 controls

  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.1.2 10.2.1.2 Logs capture all administrative actions
  • 10.2.1.4 10.2.1.4 Logs capture invalid logical access attempts
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.2.1.7 10.2.1.7 Logs capture creation and deletion of system-level objects
  • 5.3.4 5.3.4 Anti-malware audit logs enabled and retained

CIS Controls v8 · 4 controls

  • CIS-3.14 Log Sensitive Data Access
  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.2 Collect Audit Logs
  • CIS-8.5 Collect Detailed Audit Logs

FedRAMP High · 4 controls

  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-2 Event Logging

FedRAMP Moderate · 4 controls

  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • ASBv3-DS-7 Enable logging and monitoring in DevOps
  • LT-3 Enable logging for security investigation
  • LT-4 Enable network logging for security investigation

C5 (Germany) · 3 controls

  • C5-OPS-10 Logging and Monitoring - Concept
  • C5-OPS-11 Logging and Monitoring - Metadata Management Concept
  • C5-OPS-13 Logging and Monitoring - Identification of Events

NIST SP 800-161 Rev 1 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-APP-ML2 Application Control (ML2)
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • MYHR-SBD-3 Record keeping for sharing with the My Health Record system
  • MYHR-SEC-3 Audit logging and access monitoring

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • ASD37-33 Capture network traffic (Limited)
  • SEC04-BP01 Configure service and application logging

DORA · 1 control

EU AI Act · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring

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 LOG - Logging & Monitoring

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-LOG-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 49 it maps to, and the evidence behind each claim, over MCP and REST.