Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1
SEF - Security Incident Management, E-Discovery & Cloud Forensics

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-SEF-06: Event Triage Processes

Triage security-related events through a defined process so real incidents are separated from noise and routed to the right response.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

FedRAMP High · 4 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 4 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-5 Incident Monitoring
  • SI-7(7) Integration of Detection and Response
  • ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts
  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • ASBv3-IR-5 Detection and analysis - prioritize incidents

NIST SP 800-161 Rev 1 · 3 controls

CIS Controls v8 · 2 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

DORA · 2 controls

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

EU AI Act · 2 controls

  • EUAI-Art.73 Reporting of serious incidents
  • EUAI-Art.87 Reporting of infringements and protection of reporting persons

PCI DSS 4.0 · 2 controls

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems
  • E8-APP-ML3 Application Control (ML3)
  • ANSSI-HYG-40 Define a Security Incident Management Procedure
  • CPS230-27 Identification and Escalation of Incidents and Near Misses

APRA CPS 234 · 1 control

  • ASD37-28 Continuous incident detection and response (Excellent)

C5 (Germany) · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing

CMMC 2.0 · 1 control

GDPR · 1 control

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

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

ISO 27001:2022 · 1 control

  • 5.25 Assessment and decision on information security events

ISO 27002:2022 · 1 control

  • 5.25 Assessment and decision on information security events

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

NIS2 Directive · 1 control

NIST SP 800-172 · 1 control

  • 3.6.1e Establish Security Operations Center (SOC)

SOC 2 · 1 control

  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

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 SEF - Security Incident Management, E-Discovery & Cloud Forensics

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

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.

Query this from an agent

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