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. >AESCSF
  3. >RESPONSE
  4. >Analyse Cybersecurity Events And Declare Incidents
  5. >AESCSF-RESPONSE-2a
AESCSF-RESPONSE-2aActive

Criteria for declaring cybersecurity incidents are established, at least in an ad hoc manner

Statement

Criteria for declaring cybersecurity incidents are established, at least in an ad hoc manner

Context and Guidance: Criteria for declaring cybersecurity incidents are used to determine whether an event should be treated as an incident and the potential severity of the event. A ranking scale, such as high, medium, and low, may help to communicate incident severity to stakeholders and aid in prioritising response actions to be taken.

Incident declaration criteria should be developed from experience and may partially be derived from risk evaluation criteria (such as impact thresholds) established as part of Risk Management domain activities. Criteria might be based on the type of event (such as unauthorised access), level of impact (e.g., local versus organisation-wide), type of impact (internal systems versus critical external services), compliance obligations (internal-only versus reportable event), or mean time to recovery. For some events, the time between event detection and incident declaration may be immediate, requiring little additional analysis. In other cases, the organisation may wish to leverage previously developed criteria to help guide incident declaration.

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.

Location

Domain
RESPONSE
Objective
Analyse Cybersecurity Events and Declare Incidents

Practice Details

Identifier
AESCSF-RESPONSE-2a
Type
Practice
Domain
RESPONSE
Objective
Analyse Cybersecurity Events and Declare Incidents

Maturity Level

MIL-1MIL-2MIL-3

Security Profile

SP-1SP-2SP-3
ISM
ISM-0043relatedvia aescsf-reference
C2M2
C2M2-RESPONSE-2Aequivalentvia derived-shared-practice-structure
ISO 27001
ISO27001-5.25relatedvia aescsf-reference
NIST CSF
NIST-CSF-DE.AE-5relatedvia aescsf-reference
NIST-CSF-RS.AN-4relatedvia aescsf-reference
View in graphReport an issue
← Back to Analyse Cybersecurity Events and Declare Incidents
Analyse Cybersecurity Events and Declare Incidents9 controls
AESCSF-RESPONSE-2aCriteria for declaring cybersecurity incidents are established, at least in an ad hoc mannerAESCSF-RESPONSE-2bCybersecurity events are analysed to support the declaration of cybersecurity incidents, at least in an ad hoc mannerAESCSF-RESPONSE-2cCybersecurity incident declaration criteria are formally established based on potential impact to the functionAESCSF-RESPONSE-2dCybersecurity events are declared to be incidents based on established criteriaAESCSF-RESPONSE-2eCybersecurity incident declaration criteria are updated periodically and according to defined triggers, such as organ...AESCSF-RESPONSE-2fThere is a repository where cybersecurity events and incidents are documented and tracked to closureAESCSF-RESPONSE-2gInternal and external stakeholders (for example, executives, attorneys, government agencies, connected organisations,...AESCSF-RESPONSE-2hCriteria for cybersecurity incident declaration are aligned with cyber risk prioritisation criteria (RISK-3b)AESCSF-RESPONSE-2iCybersecurity incidents are correlated to identify patterns, trends, and other common features across multiple incidents