Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-SEF-07: Security Breach Notification

What else in your programme already covers this

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

SOC 2 · 4 controls

SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches
SOC2-P6.5 P6.5 Vendor commitments to report unauthorised disclosures
SOC2-P6.6 P6.6 Notifying breaches and incidents

EU AI Act · 3 controls

EUAI-Art.20 Corrective actions and duty of information
EUAI-Art.55 Obligations of providers of GPAI models with systemic risk
EUAI-Art.73 Reporting of serious incidents

FedRAMP High · 3 controls

IR-6 Incident Reporting
IR-6(1) Automated Reporting
SR-8 Notification Agreements (SR-8)

FedRAMP Moderate · 3 controls

IR-6 Incident Reporting
IR-6(1) Automated Reporting
SR-8 Notification Agreements (SR-8)

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging
NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders

C5 (Germany) · 2 controls

C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents
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.6 Define Mechanisms for Communicating During Incident Response

DORA · 2 controls

DORA-Art.14 Communication
DORA-Art.19 Reporting of major ICT-related incidents

GDPR · 2 controls

GDPR-Art.33 Notification of a personal data breach to the supervisory authority
GDPR-Art.34 Communication of a personal data breach to the data subject

ISO 27001:2022 · 2 controls

5.26 Response to information security incidents
5.5 Contact with authorities

ISO 27002:2022 · 2 controls

5.26 Response to information security incidents
5.5 Contact with authorities

NIST SP 800-161 Rev 1 · 2 controls

161R1-IR-6 Incident Reporting
161R1-SR-8 Notification Agreements

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-6 IR-6 Incident Reporting
NIST800-SR-8 SR-8 Notification Agreements

ACSC Essential Eight · 1 control

E8-APP-ML2 Application Control (ML2)

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-P33 APRA Notification of Operational Risk Incidents within 72 Hours

APRA CPS 234 · 1 control

CPS234-35 APRA Notification of Material Incidents within 72 Hours

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-ENF-1 Mandatory data breach notification

Azure Security Benchmark · 1 control

ASBv3-IR-2 Preparation - setup incident notification

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

CFTC-SS-19 Prompt Notification to the Commission

CMMC 2.0 · 1 control

IR.L2-3.6.2 Incident Reporting

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

SEF-08 Security Breach Notification

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

NIS2 Directive · 1 control

Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

NIST SP 800-171 Rev 3 · 1 control

03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

PCI DSS 4.0 · 1 control

12.10.7 12.10.7 Response procedures for PAN found in unexpected locations

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

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