C5 (Germany)
C5: Security Incident Management

C5 (Germany) C5-SIM-04: Duty of the users to report security incidents to a central body

Inform employees and external business partners of their agreed or contractually imposed duty to report promptly, to one previously designated central office, any security event they learn of that relates to the cloud service, and confirm that mistaken reports carry no penalty.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

CIS Controls v8 · 3 controls

  • CIS-14.6 Train Workforce Members on Recognizing and Reporting Security Incidents
  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents

FedRAMP High · 3 controls

  • AT-2 Literacy Training and Awareness
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance

FedRAMP Moderate · 3 controls

  • AT-2 Literacy Training and Awareness
  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.02.01 Literacy Training and Awareness
  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-53 Rev 5 · 2 controls

  • ANSSI-HYG-02 Raise User Awareness of Basic Security Practice

APRA CPS 234 · 1 control

  • CPS234-P19 Policy Direction to All Responsible Parties
  • ASBv3-IR-2 Preparation - setup incident notification

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 6.8 Information security event reporting

ISO 27002:2022 · 1 control

  • 6.8 Information security event reporting

NIS2 Directive · 1 control

  • NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders

SOC 2 · 1 control

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)

UK Cyber Essentials · 1 control

  • CE-SC.8 Process for Compromised Passwords

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.

Other controls in C5: Security Incident Management

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-SIM-04 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.

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.

Query this from an agent

The graph holds this control, the 31 it maps to, and the evidence behind each claim, over MCP and REST.