C5 (Germany) C5-SIM-02: Processing of security incidents

What else in your programme already covers this

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

NIST Cybersecurity Framework 2.0 · 8 controls

NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
NIST-CSF-RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated
NIST-CSF-RS.MA-02 Incident reports are triaged and validated
NIST-CSF-RS.MA-03 Incidents are categorized and prioritized
NIST-CSF-RS.MI-01 Incidents are contained
NIST-CSF-RS.MI-02 Incidents are eradicated

AWS Well-Architected Security Pillar · 4 controls

SEC10-BP01 Identify key personnel and external resources
SEC10-BP02 Develop incident management plans
SEC10-BP03 Prepare forensic capabilities
SEC10-BP04 Develop and test security incident response playbooks

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

CCM-CEK-19 Key Compromise
CCM-LOG-13 Failures and Anomalies Reporting
CCM-SEF-02 Service Management Policy and Procedures
CCM-SEF-06 Event Triage Processes

PCI DSS 4.0 · 4 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.3 10.7.3 Respond promptly to critical security control failures
12.10.3 12.10.3 Incident response personnel available 24/7
12.10.5 12.10.5 Plan covers alerts from security monitoring systems

Azure Security Benchmark · 3 controls

ASBv3-IR-4 Detection and analysis - investigate an incident
ASBv3-IR-5 Detection and analysis - prioritize incidents
ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

FedRAMP High · 3 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes
IR-5 Incident Monitoring

FedRAMP Moderate · 3 controls

IR-4 Incident Handling
IR-4(1) Automated Incident Handling Processes
IR-5 Incident Monitoring

NIS2 Directive · 3 controls

Art.21.2.b Incident handling
Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise
Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running

APRA CPS 234 · 2 controls

CPS234-30 Detection and Response Mechanisms
CPS234-P25 Response Plan Content and Escalation Mechanisms

CIS Controls v8 · 2 controls

CIS-17.1 Designate Personnel to Manage Incident Handling
CIS-17.4 Establish and Maintain an Incident Response Process

DORA · 2 controls

DORA-Art.17 ICT-related incident management process
DORA-Art.18 Classification of ICT-related incidents and cyber threats

ISO 27001:2022 · 2 controls

5.25 Assessment and decision on information security events
5.26 Response to information security incidents

ISO 27002:2022 · 2 controls

5.25 Assessment and decision on information security events
5.26 Response to information security incidents

NIST SP 800-161 Rev 1 · 2 controls

161R1-IR-4 Incident Handling
161R1-IR-7 Incident Response Assistance

SOC 2 · 2 controls

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

ACSC Essential Eight · 1 control

E8-APP-ML2 Application Control (ML2)

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

CBPR-PR-32 Detection, prevention and response measures

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-28 Continuous incident detection and response (Excellent)

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

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

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

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)

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-218 · 1 control

SP800-218-RV.3.1 Analyze Vulnerabilities to Identify Root Causes

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-4 IR-4 Incident Handling

NIST SP 800-66 Rev 2 · 1 control

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

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