Incident Register

Digital Navigation: Automated decision support and workflow acceleration

Upon logging in, the system automatically classifies incident severity and determines whether it qualifies as “major” under DORA or “significant” under NIS2. This automated assessment enables you to:

• Validate reporting obligations instantly to ensure regulatory compliance.
• Optimise resource allocation by prioritising high-impact incidents.
• Eliminate misclassification risks.

Real-Time Validation: Effective regulatory reporting

Reduce incident assessment time. Instantly determine whether you’re dealing with a serious incident that will require about four hours of reporting, or whether it’s not serious.

Classify, assess, and record ICT incidents, and report them to regulatory authorities. The real-time validation engine matches your data against official templates to:

• Eliminate formal errors that lead to report rejection.
• Mitigate risk regarding financial penalties and reputational damage.
• Ensure predictability and operational calm during high-pressure crises.

Filtering Related Data: Accuracy and consistency

Access all incident data from a single, centralised repository. Every report follows a uniform structure, simplifying risk analysis and ensuring you are always audit-ready. Filter critical data points in seconds and generate comprehensive reports on demand.

If you use an incident register integrated with the Risk Analysis module, you can easily utilise incident information to assess likelihood in your risk analysis. You can instantly see exactly what impact specific incidents have on your organisation’s assets. This makes it easy to review procedures and justify the budget for necessary security measures.

Built-in drop-down lists

Use DORA-compliant drop-down lists to eliminate error risk. ​ Instead of entering data into a report (e.g., incident type, effects, classification, status, source of threat), select a value from a predefined list developed in accordance with official DORA guidelines and supervision authorities’ templates.

Smart links

Save time with automatic filters and describe incidents efficiently. ​ Select a specific incident type (e.g. core banking system failure), and the system automatically:

• suggests the most likely consequences (e.g. service unavailability, impact on customers),
• filters the drop-down lists to show only those options that make sense in the given context,
• suggests a classification in accordance with DORA principles.

Incident classification

Enter the necessary data, and the system will classify the incident for you in accordance with the criteria set out in the regulation. The system analyses the data for you according to the ‘1+2’ rule from DORA:

• mandatory condition: Does the incident concern critical services?
• at least 2 out of 7 additional criteria: e.g. impact on customers, reputation, data, geographical scope, etc.


On this basis, the application automatically classifies the incident as:

• “Serious” – triggers the obligation to report within 4 hours.
• “Minor” – does not require immediate reporting, but may be analysed internally.

Documentation

Store all reported incidents in one place, with a full history of changes, reports and statuses.
Access always up-to-date documentation of the incident lifecycle.
From the initial report through preliminary, interim, and final reports, to root cause analysis and corrective actions – everything is organised and accessible.