Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-LOG-13: Failures and Anomalies Reporting

What else in your programme already covers this

This control maps to 26 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.

PCI DSS 4.0 · 5 controls

10.2.1.6 10.2.1.6 Logs capture initialization and stopping of audit logs
10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.1 10.7.1 Service providers detect critical control failures (superseded)
10.7.2 10.7.2 Detect and alert on critical security control failures
10.7.3 10.7.3 Respond promptly to critical security control failures

C5 (Germany) · 2 controls

C5-OPS-17 Logging and Monitoring - Availability of the Monitoring Software
C5-SIM-02 Processing of security incidents

FedRAMP High · 2 controls

AU-5 Response to Audit Logging Process Failures
SI-4(5) System-Generated Alerts

FedRAMP Moderate · 2 controls

AU-5 Response to Audit Logging Process Failures
SI-4(5) System-Generated Alerts

Azure Security Benchmark · 1 control

ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-19 Prompt Notification to the Commission

CIS Controls v8 · 1 control

CIS-13.11 Tune Security Event Alerting Thresholds

CMMC 2.0 · 1 control

AU.L2-3.3.4 Audit Failure Alerting

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.1 · 1 control

LOG-14 Failures and Anomalies Reporting

DORA · 1 control

DORA-Art.10 Detection

HIPAA Security Rule · 1 control

164.308(a)(5)(ii)(C) Log-in Monitoring (Addressable)

ISO 27001:2022 · 1 control

6.8 Information security event reporting

ISO 27002:2022 · 1 control

6.8 Information security event reporting

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools

NIST SP 800-171 Rev 3 · 1 control

03.03.04 Response to Audit Logging Process Failures

NIST SP 800-172 · 1 control

3.14.2e Monitor Organizational Systems with Specialized Capabilities

NIST SP 800-53 Rev 5 · 1 control

NIST800-AU-5 AU-5 Response to Audit Logging Process Failures

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(5)(ii)(C) Log-in Monitoring (Addressable)

SOC 2 · 1 control

SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

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.

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

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 gaps

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.

See the released pairs, $299 each Browse the graph free