Content library
C2M2: MIL1
RESPONSE-2: Analyze Cybersecurity Events and Declare Incidents

Requirement description

MIL1 requirements
a. Criteria for declaring cybersecurity incidents are established, at least in an ad hoc manner
b. Cybersecurity events are analyzed to support the declaration of cybersecurity incidents, at least in an ad hoc manner

MIL2 requirements
c. Cybersecurity incident declaration criteria are formally established based on potential impact to the function
d. Cybersecurity events are declared to be incidents based on established criteria
e. Cybersecurity incident declaration criteria are updated periodically and according to defined triggers, such as organizational changes, lessons learned from plan execution, or newly identified threats
f. There is a repository where cybersecurity events and incidents are documented and tracked to closure
g. Internal and external stakeholders (for example, executives, attorneys, government agencies, connected organizations, vendors, sector organizations, regulators) are identified and notified of incidents based on situational awareness reporting requirements (SITUATION-3d)

MIL3 requirements
h. Criteria for cybersecurity incident declaration are aligned with cyber risk prioritization criteria (RISK-3b)
i. Cybersecurity incidents are correlated to identify patterns, trends, and other common features across multiple incidents

How to fill the requirement

C2M2: MIL1

RESPONSE-2: Analyze Cybersecurity Events and Declare Incidents

Task name
Priority
Status
Theme
Policy
Other requirements
Defining cyber security metrics for cyber security breaches
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
4
requirements

Examples of other requirements this task affects

RESPONSE-2: Analyze Cybersecurity Events and Declare Incidents
C2M2
Article 17: ICT-related incident management process
DORA
17.9: Establish and Maintain Security Incident Thresholds
CIS 18
See all related requirements and other information from tasks own page.
Go to >
Defining cyber security metrics for cyber security breaches
1. Task description

The organization has defined metrics that can be monitored and are related to cyber security incident management. At its best, good metrics help detect weaknesses in incident detection.

Possible metrics include:

  • Number of security incidents and relationship to disruptions
  • Number of disruptions by service, department, severity or type provided
  • Time required for incident identification, investigation and handling
  • Deviations from documented practices
Defining threshold for cyber security breach
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
6
requirements

Examples of other requirements this task affects

DE.AE-5: Incident alert thresholds
NIST
RESPONSE-2: Analyze Cybersecurity Events and Declare Incidents
C2M2
Article 17: ICT-related incident management process
DORA
DE.AE-5: Incident alert thresholds are established.
CyberFundamentals
DE.AE-08: Incidents declaration criteria
NIST 2.0
See all related requirements and other information from tasks own page.
Go to >
Defining threshold for cyber security breach
1. Task description

The organization must define the threshold at which a security incident becomes a cyber security breach.

Ensuring sorting of cyber security events
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
7
requirements

Examples of other requirements this task affects

DE.AE-2: Analyze detected events
NIST
RESPONSE-2: Analyze Cybersecurity Events and Declare Incidents
C2M2
Article 17: ICT-related incident management process
DORA
DE.AE-2: Detected events are analysed to understand attack targets and methods.
CyberFundamentals
RS.MA-02: Incident reports
NIST 2.0
See all related requirements and other information from tasks own page.
Go to >
Ensuring sorting of cyber security events
1. Task description

The organization shall define procedures for clearly sorting detected security events. Sorting must enable the prioritizing of events according to severity and potential impact.

Sorting is intended to enhance the investigation and evaluation of security events so that, for example, a response to a disruption can be initiated quickly.

Procedures can consist of common processes, technical tools, or algorithms that utilize machine learning. Procedures need to be reviewed regularly to ensure that they work and are appropriate for their needs.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.