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-2G
C2M2-RESPONSE-2GActive

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)

Statement

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)

Location

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

Practice Details

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

Help Text

Incidents that have been declared and that require a response must be communicated to stakeholders whose involvement is necessary in implementing, managing, and bringing to closure an appropriate and timely solution. Event and incident notification should be guided by the reporting requirements defined in SITUATION-3d. Miscommunications or inaccurate information about organizational incidents can have dire effects that far exceed the potential damage caused by an incident itself. Therefore, the function must proactively manage communications when incidents are detected and throughout their life cycle.

Related Practices · Dependency: Implementing this practice depends upon prior implementation of SITUATION-3d. · Information Sharing: This practice is part of a group of cross-domain practices that enable information sharing with organizational stakeholders. These include: THREAT-1i, THREAT-2h, THREAT-2k, RISK-1c1d, SITUATION-3a, SITUATION-3c, SITUATION-3d, SITUATION-3e, RESPONSE-2g, RESPONSE-3c, RESPONSE-3f.

AESCSF
AESCSF-RESPONSE-2gequivalentvia 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