Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-LOG-08: Log Records

What else in your programme already covers this

This control maps to 36 controls across 21 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 · 4 controls

AC-6(9) Log Use of Privileged Functions
AU-12 Audit Record Generation
AU-3 Content of Audit Records
AU-3(1) Additional Audit Information

FedRAMP Moderate · 4 controls

AC-6(9) Log Use of Privileged Functions
AU-12 Audit Record Generation
AU-3 Content of Audit Records
AU-3(1) Additional Audit Information

C5 (Germany) · 3 controls

C5-OPS-11 Logging and Monitoring - Metadata Management Concept
C5-OPS-15 Logging and Monitoring - Accountability
C5-PSS-04 Error handling and Logging Mechanisms

Azure Security Benchmark · 2 controls

ASBv3-IR-4 Detection and analysis - investigate an incident
LT-3 Enable logging for security investigation

CIS Controls v8 · 2 controls

CIS-8.2 Collect Audit Logs
CIS-8.5 Collect Detailed Audit Logs

CMMC 2.0 · 2 controls

AU.L2-3.3.1 System Auditing
AU.L2-3.3.2 User Accountability

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved

NIST SP 800-161 Rev 1 · 2 controls

161R1-AU-10 Non-repudiation
161R1-AU-3 Content of Audit Records

NIST SP 800-53 Rev 5 · 2 controls

NIST800-AU-12 AU-12 Audit Record Generation
NIST800-AU-3 AU-3 Content of Audit Records

PCI DSS 4.0 · 2 controls

10.2.1 10.2.1 Audit logging enabled on all system components
10.2.2 10.2.2 Required details recorded for each auditable event

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-31 Hunt to discover incidents (Very Good)

AWS Well-Architected Security Pillar · 1 control

SEC04-BP01 Configure service and application logging

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-6 Emergency access controls

EU AI Act · 1 control

EUAI-Art.12 Record-keeping (logs)

HIPAA Security Rule · 1 control

164.312(b) Audit Controls (Standard)

NIST SP 800-171 Rev 3 · 1 control

03.03.02 Audit Record Content

NIST SP 800-66 Rev 2 · 1 control

164.312(b) Audit Controls (Standard)

SOC 2 · 1 control

SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)

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-08 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