OPS-02 · Incident management and reporting
Catalogue · Operate & Protect
Incidents are detected, classified, handled, communicated and reported, including to authorities where required.
Typical activities
- Maintain an incident procedure with roles, classification criteria and escalation paths
- Log all incidents and track them to resolution
- Notify affected parties and authorities within the applicable deadlines
- Run post-incident reviews for significant incidents
Evidence an assessor would expect
- Incident procedure and classification matrix
- Incident log and reports
- Regulatory notification records and post-incident reviews
Capability scale
- 0 · Absent
- The practice is not performed, or happens so rarely that it produces no recognisable outcome.
- 1 · Initial
- The practice is performed informally and its results depend on the people involved.
- 2 · Repeatable
- The practice is planned, assigned and tracked, with basic records kept.
- 3 · Defined
- The practice follows a documented, organisation-wide approach with clear roles and measurable outputs.
- 4 · Measured
- The practice is managed with quantitative targets and its performance is monitored and reported.
- 5 · Optimising
- The practice is continuously improved using performance data, external comparison and automation.
Regulatory requirements
- supporting DORA Art. 11 · Response and recovery
- primary DORA Art. 17 · ICT-related incident management process
- primary DORA Art. 18 · Classification of ICT-related incidents and cyber threats
- primary DORA Art. 19 · Reporting of major ICT-related incidents
- primary NIS 2 Art. 21(2)(b) · Incident handling
- primary NIS 2 Art. 23 · Reporting obligations
Cross-references
- COBIT® 2019 DSS02
- ISO/IEC 27001:2022 A.5.24
- ISO/IEC 27001:2022 A.5.26
- NIST CSF 2.0 RS.MA
Identifiers only, for orientation. Consult the original publications for their content.