In this guide
For significant incidents, NIS2 provides for an early warning within 24 hours of the entity becoming aware, an incident notification within 72 hours and a final report no later than one month after notification. Putting this into practice requires monitoring, clear incident classification, a contact matrix, evidence collection, runbooks and a tested escalation process. UniLoud can implement this operational framework and connect it to the business’s Managed IT and security monitoring.
Detection comes before the reporting deadline
An incident cannot be reported promptly if the business does not know it is happening. The first practical issue is visibility: which systems are monitored, which logs are retained, who reviews alerts and how a technical fault is distinguished from a potential cyber incident.
NIS2 concerns significant incidents and provides for staged reporting. An internal triage method is therefore needed to turn technical data into a decision: what was affected, how many users or services are affected, whether malicious activity may be involved and who should be informed.
What should be ready before an incident
- An asset inventory with critical systems, owners, dependencies and technical contact details.
- Centralised or sufficiently accessible logs for endpoints, Microsoft 365, firewalls, servers, VPNs, virtualisation and critical applications.
- An incident severity matrix so that the team knows when an event becomes significant and requires escalation.
- A contact matrix for management, IT, DPO/compliance, legal advisers, suppliers and external technicians.
- Runbooks for ransomware, account compromise, data exfiltration, outages, supplier incidents and loss of access.
- An evidence pack template: timestamps, affected assets, indicators of compromise, actions taken, screenshots or log extracts and business impact.
- A tested backup and restore process and alternative operation for critical services.
Turning 24h / 72h into an operational workflow
- 0–2 hours: detection, initial confirmation, containment where safe and creation of an incident record.
- 2–6 hours: triage, scope, business impact, evidence collection and activation of the appropriate owners.
- 6–12 hours: a severity decision and preparation of the core information needed by management and compliance.
- Within 24 hours: an early warning to the competent CSIRT or authority when the relevant conditions are met.
- Within 72 hours: an incident notification with an updated picture, an initial severity assessment and available indicators of compromise.
- After containment: root cause analysis, restoration, lessons learned and verification that corrective measures have been applied.
- Within one month after incident notification: support for the final report with technical evidence, impact, root cause and mitigation actions.
What UniLoud can implement
- A baseline assessment of logging, monitoring, backup, incident handling and technical ownership.
- Centralisation of alerts and technical events from infrastructure, Microsoft 365, endpoints, firewalls and telephony where relevant.
- Incident runbooks and technical checklists adapted to the customer’s actual infrastructure.
- A contact and escalation matrix and workflow with clear handover from Helpdesk/Monitoring to senior engineers and management.
- Evidence collection templates and secure storage of technical incident information.
- Tabletop exercises and simulated incident drills to test the workflow before an actual event.
- Post-incident review and a remediation plan: hardening, patching, segmentation, identity controls, backup/DR and monitoring improvements.
UniLoud organises technical readiness alongside compliance
The decision on whether an incident is reportable and official communication with the competent authorities must follow the applicable national framework and the organisation’s procedures. UniLoud can ensure the technical side is ready: accurate information, correct timestamps, retained logs, recorded actions and a team that knows what to do under time pressure.
Frequently asked questions
Do the 24- and 72-hour deadlines apply to every technical event?
No. NIS2 sets these deadlines for significant incidents. The business needs a classification process to distinguish a routine IT incident from an event that triggers regulatory escalation.
Can the Helpdesk be the first point of detection?
Yes, provided there is a clear escalation path. Many incidents start with “I cannot sign in”, “I received a strange email” or “The system is slow”. The Helpdesk must know when routine troubleshooting should give way to incident response.
Do we need a SIEM to be ready?
Not necessarily in every environment. Sufficient visibility, logging, alerting and a process are needed. The architecture is chosen according to size, risk and existing platforms.
Note: This material is informational and technical. It is not legal advice. Final applicability, official notifications and contractual requirements should be confirmed with the responsible management, compliance team and legal advisers.
Related services and guides
- UniLoud Monitoring
- UniLoud Protection
- Helpdesk & user support
- UniLoud Backup
- UniLoud Disaster Recovery
- Technical support for compliance
Discuss your next step with UniLoud
Want to know what will happen in the first 60 minutes of a real incident? UniLoud can organise a NIS2 Incident Readiness Workshop and deliver a practical runbook, contact matrix and technical action plan for your infrastructure.
