NIS2 Incident Radar – cyber security incident records under NIS2 (ZoKB)
The NIS2 Directive and the new Czech Cyber Security Act (ZoKB, No. 264/2025 Coll.) require regulated organisations to record and assess security incidents and report them within strict deadlines. NIS2 Incident Radar by Extend IT, s.r.o. covers these obligations on the proven open-source helpdesk Znuny (the successor of OTRS) – without expensive licences and adaptable to your processes.
Book a NIS2 Incident Radar demo Does it apply to me?
What NIS2 Incident Radar covers
- a single incident register – every security event and incident in one place, with a unique number and an owner, instead of e-mails and spreadsheets,
- statutory deadline tracking – early warning within 24 hours, incident notification within 72 hours and a final report within 1 month; the system alerts you before a deadline expires,
- classification according to NÚKIB – assessing the impact on availability, confidentiality and integrity and deciding whether an incident is significant (reportable),
- a managed response process – playbooks from detection through mitigation and recovery to reporting to the regulator, so nothing gets lost even when people change,
- asset links – incidents linked to a specific server, database or network device, with the incident and vulnerability history of each asset,
- evidence for audits – a complete audit trail of communication, decisions and changes for NÚKIB, internal audit and management,
- reporting – incident overviews and statistics for management and for evaluating the measures taken.
How Znuny meets the NIS2 (ZoKB) requirements
With tickets, SLAs and managed processes, Znuny is a natural fit for recording cyber security incidents. NIS2 Incident Radar addresses the key requirements of NIS2 and the ZoKB as follows:
| NIS2 (ZoKB) requirement | How NIS2 Incident Radar (Znuny) handles it |
|---|---|
| Incident records and audit trail | Every incident is a ticket with a unique number and a complete history of communication and state changes. Records cannot be deleted without the appropriate permissions. |
| Categorisation and impact (severity) | Dynamic fields for classification according to the NÚKIB decrees – impact on availability, confidentiality and integrity, affected critical assets. |
| 24 h / 72 h / 1 month deadlines | Built-in SLA management tracks the deadlines for the early warning, the notification and the final report and escalates to the security team (CSIRT, security manager / CISO) in advance. |
| Workflows (playbooks) | The built-in Process Management defines the exact incident handling procedure – from detection through mitigation and recovery to notifying the regulator. |
| Asset links (CMDB) | The ITSM Configuration Management module (ITSMConfigItem) links an incident to a specific infrastructure item and keeps the incident and vulnerability history of that asset. |
How we work
- Initial consultation – whether and under which regime the Act applies to you, and how you handle incidents today.
- Tailored setup – classification, deadlines, escalations, roles and playbooks according to your processes and security documentation.
- Integration – importing assets into the CMDB, receiving events from e-mail, monitoring or SIEM and connecting other systems via API, extended with add-on packages where needed.
- Training and operation – we train the security team, run the system on your premises or in our cloud and take care of updates.
Already using Znuny or OTRS as a helpdesk? We add NIS2 Incident Radar to it, so incidents can be taken over directly from user requests. Ask for a demo using the form below – the NIS2 Incident Radar category is preselected.