Incidents
Management of the security incident lifecycle, with tracking of regulatory notification obligations.
Creating an incident
- Click New Incident
- Fill in:
- Title, Description
- Type: Data Breach, Outage, Unauthorised Access, Malware, Phishing, Ransomware, etc.
- Severity: Critical / High / Medium / Low
- Detection date
- Mandatory notification?: if it involves personal data or critical infrastructure
Notification obligations
When notification is mandatory, the system shows automatic countdowns:
| Authority | Legal deadline | Indicator |
|---|---|---|
| CNCS (Cybersecurity) | 24 hours | Red badge with hours remaining |
| CNPD (Data Protection) | 72 hours | Orange badge with hours remaining |
When the deadline is at risk or has expired, the incident is highlighted on the main dashboard with a critical alert.
NIS2 deadlines (Art. 23): the incident detail now distinguishes 3 independent time milestones (early warning (24h), intermediate notification (72h) and final report (1 month)), each with its own deadline and submission recorded separately (CNCS/ANACOM/CNPD), instead of a single checkbox covering all three.
Data breaches: moment of awareness
In the data breach notification form, the Date/time of awareness of the breach field records when the organisation became aware of the breach (GDPR Art. 33 and NIS2). The legal deadlines (CNPD 72 hours, CNCS 24 hours) count from that moment; if you leave it empty, the detection time is used. You can correct it later, and active deadlines are recalculated. Incidents created by Wazuh (shown with "Wazuh Integration") follow the same deadlines as those recorded by hand.
Status lifecycle
Open → Under Investigation → Closed