NIS 2 incident notification
A guided flow to prepare the early warning, the incident notification and the final report within the NIS 2 deadlines.
Voucher MIMIT code VCCFA2600000933-D9How it works
We guide you through the process and make it faster: Cyber Console classifies the incident and fills in the fields ACN requires, your CSIRT contact reviews them and enters them on the ACN portal within the deadlines.
The console in action
A tour of the console, then tasks from start to finish, on the screens you will use. Each recording is split into chapters: pick one to start from there.
7 steps from incident to notification
One flow to handle every security incident, from detection to closure.
Data ingestion
The incident is entered in Cyber Console or through the APIs, with the information collected.
AI Analysis
Classification against the ACN taxonomy, with an AI proposal that your team reviews.
CIA Assessment
Impact analysis on Confidentiality, Integrity and Availability of systems.
ACN forms filled in
The ACN notification forms are filled in from the data already collected and wait for review.
Review
The security team reviews and approves the content of the notification before it is filed.
Phase management
Handling of the three phases: early warning, incident notification and final report.
Filing and archiving
The entity files the notification with the CSIRT on the ACN portal; the documentation stays archived for audit and compliance.
NIS 2 notification timeline
The NIS 2 Directive sets precise deadlines for notifying incidents to the CSIRT. In Cyber Console a guided procedure takes your contact through each communication, with the text ready to copy into the ACN portal, where filing stays with you.
Early warning
Preliminary notification to CSIRT within 24 hours of significant incident detection.
Incident notification
Update with initial assessment, severity, impact and indicators of compromise.
Final report
Closing report with root cause analysis, the mitigation measures applied and the lessons learned.
ACN incident taxonomy
Every incident is classified under the taxonomy of ACN, the Italian National Cybersecurity Agency.
Baseline Characterization
Threat type
Threat actor
Additional Context
Significance flags
IS_1 - Confidentiality loss · IS_2 - Integrity loss · IS_3 - Service level violation · IS_4 - Unauthorised access or abuse of privileges
From the information collected to the ACN portal
Incident notification insights
Guides and insights on security incident management and NIS 2 notification obligations.
Made with AI
12 Oct 2026
CRA Article 14: reporting duties for manufacturers
Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities and severe incidents under Article 14 of the Cyber Resilience Act. What counts, the 24 hour, 72 hour and final report deadlines, ENISA's single reporting platform and the coordinating CSIRT (CSIRT Italia for Italian manufacturers), products already on the market, components, fines and a readiness checklist.
Made with AI
02 Oct 2026
ECCC COORDPREP 2027: Funding for Coordinated Cyber Preparedness Testing
The COORDPREP topic funds coordinated preparedness testing and wider preparedness services, led by designated public cybersecurity bodies with private partners in support. The two tracks, the testing method, the KPIs and the evidence to plan.
Made with AI
15 Apr 2026
ACN NIS Platform Roles, Access, and User Association
The ACN platform determination defines a governed role model for NIS compliance: point of contact, substitute, CSIRT contact, segreteria, and operator. Authentication is via personal CIE/SPID, and association to the subject is validated through the digital domicile.