C5 (Germany) C5-SIM-03: Documentation and reporting of security incidents

What else in your programme already covers this

This control maps to 46 controls across 28 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.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-CC7.5 CC7.5 Recovering from security incidents
SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches

CIS Controls v8 · 3 controls

CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
CIS-17.6 Define Mechanisms for Communicating During Incident Response

FedRAMP High · 3 controls

IR-5 Incident Monitoring
IR-6 Incident Reporting
IR-6(1) Automated Reporting

FedRAMP Moderate · 3 controls

IR-5 Incident Monitoring
IR-6 Incident Reporting
IR-6(1) Automated Reporting

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
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

APRA CPS 234 · 2 controls

CPS234-35 APRA Notification of Material Incidents within 72 Hours
CPS234-P25 Response Plan Content and Escalation Mechanisms

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-SEF-01 Security Incident Management Policy and Procedures
CCM-SEF-07 Security Breach Notification

DORA · 2 controls

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

ISO 27001:2022 · 2 controls

5.26 Response to information security incidents
5.28 Collection of evidence

ISO 27002:2022 · 2 controls

5.26 Response to information security incidents
5.28 Collection of evidence

NIS2 Directive · 2 controls

Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients
Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-5 IR-5 Incident Monitoring
NIST800-IR-6 IR-6 Incident Reporting

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

AWS Well-Architected Security Pillar · 1 control

SEC10-BP08 Establish a framework for learning from incidents

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-7 Post-incident activity - conduct lesson learned and retain evidence

CMMC 2.0 · 1 control

IR.L2-3.6.2 Incident Reporting

GDPR · 1 control

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

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

NIST SP 800-161 Rev 1 · 1 control

161R1-IR-6 Incident Reporting

NIST SP 800-171 Rev 3 · 1 control

03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-218 · 1 control

SP800-218-RV.3.4 Document Lessons Learned

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 C5 (Germany) have you already done?

C5 (Germany) C5-SIM-03 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.178.5% covered · 26 gaps If you hold NIST SP 800-53 Rev 572.7% covered · 33 gaps If you hold FedRAMP Moderate71.1% covered · 35 gaps If you hold ISO 27002:202267.8% covered · 39 gaps If you hold ISO 27001:202257% covered · 52 gaps If you hold NIST SP 800-171 Rev 350.4% covered · 60 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. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

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