TotulDigital
EN
Client Portal Get Started
HELP ARTICLE • Updated 8 October 2026

Incidents and the NIS2 reporting clock

When something serious happens, two things matter: understanding it quickly, and telling the authority on time if the law requires it. The portal helps with both; the decision and the report are yours.

PART 01

The first hour

  1. Detect

    A high or critical alert

    It appears on the Overview, in the live stream and in Events. Every alert carries its MITRE ATT&CK technique and the frameworks it touches.

  2. Scope

    Which machines, which accounts

    Open the event: its source address shows every other host it reached in the last 30 days. Topology shows what that host exposes.

  3. Contain

    Act on the systems

    Block the address, disable the account, isolate the machine — on your systems. The portal reads; it does not change your servers.

  4. Record

    Keep the evidence

    Export the events (CSV or JSON) as they are. The audit trail records who looked at what in the portal.

PART 02

The NIS2 Article 23 clock

If your organisation is an essential or important entity under NIS2, a significant incident must be reported to your CSIRT or competent authority in stages:

DeadlineWhat is dueContent
24 hoursEarly warningWhether it is suspected to be unlawful or malicious, and whether it could have a cross-border impact.
72 hoursIncident notificationUpdates the early warning: an initial assessment of severity and impact, and indicators of compromise.
On requestIntermediate reportStatus updates the authority asks for.
1 monthFinal reportDetailed description, the type of threat or root cause, mitigation applied, cross-border impact.

The Compliance screen keeps this clock: from the first high or critical detection it shows the three deadlines running, and "Quiet" when there is nothing to report. Drafting starts from the security report for the period.

Recording the decision is not available yetWhether an incident is significant is your judgement. The button to record that decision on the clock is shown but not available yet; keep the decision and its reasons in your incident record.

What makes an incident significant, and the thresholds the Implementing Regulation sets for digital providers, are explained in the NIS2 guide.

KEEP READING

Related

NIS2 explainedArticle 23 in full. ReportsThe security report for the period.
SUPPORT

Still stuck?

Write to us with what you tried and what you saw. A person answers, in writing, on business days.