Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >C2M2
  3. >Event And Incident Response, Continuity Of Operations
  4. >Event And Incident Response, Continuity Of Operations - Objective 2
  5. >C2M2-RESPONSE-2C
C2M2-RESPONSE-2CActive

Cybersecurity incident declaration criteria are formally established based on potential impact to the function

Statement

Cybersecurity incident declaration criteria are formally established based on potential impact to the function

Location

Domain
Event and Incident Response, Continuity of Operations
Objective
Event and Incident Response, Continuity of Operations - Objective 2

Practice Details

Identifier
C2M2-RESPONSE-2C
Domain
Event and Incident Response, Continuity of Operations
Objective
Objective 2
Maturity Level
MIL-2

Help Text

Each organization has many unique factors that must be considered in determining when an event should be declared to be an incident. Through experience, an organization may have a baseline set of types of events that define standard incidents, such as a virus outbreak, unauthorized access to a user account, or a denial-of-service attack. However, in reality, incident declaration may occur on an event-by-event basis. To guide the organization in determining when to declare an incident (particularly if incident declaration is not immediately apparent), the organization must define incident declaration criteria. Incident declaration criteria should include factors that indicate the potential impact to the function, such as: • potential safety impacts • functional impact (priority and scope of impacted assets) • information impact (impact to information assets) • recoverability from the incident (resources necessary to recover from the incident) • the potential cause of the incident (malicious activity vs. unintentional actions) Additionally, incident declaration criteria should consider impact to the organization's cybersecurity goals, such as: • potential financial loss • number of customers affected • outage of major IT system • theft of customer information

Related Practices · Progression: This practice is part of a practice progression. Practice progressions are groups of related practices that represent increasingly complete or more advanced implementations of an activity. The practices in this progression include: RESPONSE-2a, RESPONSE-2c, RESPONSE-2e, RESPONSE-2h.

AESCSF
AESCSF-RESPONSE-2cequivalentvia derived-shared-practice-structure
View in graphReport an issue
← Back to Event and Incident Response, Continuity of Operations - Objective 2
Event and Incident Response, Continuity of Operations - Objective 29 controls
C2M2-RESPONSE-2ACriteria for declaring cybersecurity incidents are established, at least in an ad hoc mannerC2M2-RESPONSE-2BCybersecurity events are analyzed to support the declaration of cybersecurity incidents, at least in an ad hoc mannerC2M2-RESPONSE-2CCybersecurity incident declaration criteria are formally established based on potential impact to the functionC2M2-RESPONSE-2DCybersecurity events are declared to be incidents based on established criteriaC2M2-RESPONSE-2ECybersecurity incident declaration criteria are updated periodically and according to defined triggers, such as organizational changes, lessons learned from plan execution, or newly identified threatsC2M2-RESPONSE-2FThere is a repository where cybersecurity events and incidents are documented and tracked to closureC2M2-RESPONSE-2GInternal 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)C2M2-RESPONSE-2HCriteria for cybersecurity incident declaration are aligned with cyber risk prioritization criteria (RISK-3b)C2M2-RESPONSE-2ICybersecurity incidents are correlated to identify patterns, trends, and other common features across multiple incidents