Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-SEF-01: Security Incident Management Policy and Procedures

What else in your programme already covers this

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

APRA CPS 234 · 3 controls

CPS234-32 Annual Review and Testing of Response Plans
CPS234-P24 Information Security Response Plans
CPS234-P25 Response Plan Content and Escalation Mechanisms

Azure Security Benchmark · 3 controls

ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
ASBv3-IR-1 Preparation - update incident response plan and handling process
ASBv3-IR-4 Detection and analysis - investigate an incident

AWS Well-Architected Security Pillar · 2 controls

SEC10-BP02 Develop incident management plans
SEC10-BP03 Prepare forensic capabilities

C5 (Germany) · 2 controls

C5-SIM-01 Policy for security incident management
C5-SIM-03 Documentation and reporting of security incidents

CIS Controls v8 · 2 controls

CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
CIS-17.4 Establish and Maintain an Incident Response Process

ISO 27001:2022 · 2 controls

5.24 Information security incident management planning and preparation
6.8 Information security event reporting

ISO 27002:2022 · 2 controls

5.24 Information security incident management planning and preparation
6.8 Information security event reporting

SOC 2 · 2 controls

SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

APPI · 1 control

APPI-A26 Report of Leakage to the Commission and Notification to the Person

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-1 Written security and access policy

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

CFTC-SS-16 Security Incident Response Plan and Testing

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

DORA · 1 control

DORA-Art.17 ICT-related incident management process

FedRAMP High · 1 control

IR-8 Incident Response Plan

HIPAA Security Rule · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-1 Policy and Procedures

NIST SP 800-171 Rev 3 · 1 control

03.06.05 Incident Response Plan

NIST SP 800-218 · 1 control

SP800-218-RV.3.4 Document Lessons Learned

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-1 IR-1 Policy and Procedures

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

PCI DSS 4.0 · 1 control

12.10.1 12.10.1 Incident response plan ready for activation

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-SEF-01 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