Why one path instead of three procedures
A typical industrial site runs three parallel regimes: occupational safety with an accident investigation team, physical security with an alarm procedure, and IT or automation with a cyber incident procedure. Each has its own form, its own notification channel and its own owner. An event rarely stays in one drawer: a turbine trip after an unauthorised command on the control network is at once a cyber incident, an operational event and a potential hazard to people on the floor.
The cost of having no shared path can be counted. The first minutes go on the question of who is in charge rather than on action. Records are created in three places and cannot be merged into one timeline, so after the event nobody can show when it was detected. That moment is critical, because the statutory deadlines run from it.
What an accident, a security alarm and a cyber incident have in common
In all three cases the same elements are needed: a detection source, a severity assessment, a named person in command, a circle of people to notify and a durable record. Only the content of the assessment differs: for an accident it is the health of people, for a security alarm control of the premises, for cyber the continuity of the process and data. It therefore makes sense to build one skeleton and keep the differences in classification cards.
Legal basis and the deadlines that set the rhythm
The Act of 23 January 2026 amending the Polish National Cybersecurity System Act (Journal of Laws 2026, item 252) has applied since 3 April 2026. It transposes the NIS2 Directive (EU) 2022/2555. Three reporting deadlines matter for response procedures: an early warning without undue delay and no later than 24 hours after detecting a significant incident; a notification without undue delay and no later than 72 hours after detection; and a final report within one month of the notification. Reports go through the S46 system to the competent CSIRT.
The transition schedule sets the time frame. Obligations from chapter 3 of the Act, including the information security management system and incident procedures, must be met by entities covered on the day it entered into force by 3 April 2027. The first cybersecurity audit of an essential entity falls on 3 April 2028, and financial penalties can in principle be imposed from the same date. The most serious infringements are an exception.
- 24 hours from detection: early warning to the CSIRT
- 72 hours from detection: notification of a significant incident
- 1 month from notification: final report
- By 3 April 2027: incident procedures and documentation in the security management system
- From 3 April 2028: first audit of an essential entity and penalties under Article 35
The 2026–2028 window is the time to build evidence
No penalties until April 2028 does not mean a period without risk. Penalties can also be imposed for earlier infringements, and an auditor will ask for records from the whole period. A site that starts keeping an event register only in 2028 cannot show a history. The practical conclusion: launch the response path now and collect evidence from day one.
Deadlines in the response path for a significant incident
Four stages of the path: detection, classification, escalation, register
A path makes sense when every stage has one owner, an input, an output and a time limit. The split below is an example and must be adapted to the size of the site and to the shift pattern.
Stage 1: detection and reporting
Anyone can report an event: an employee, a contractor, security staff, a control system operator or network monitoring. Reporting has a single entry point, for example a duty phone number and a form, and contains the minimum: who, where, what, when it was noticed. The time of noticing is recorded separately from the time of reporting, because the difference can matter when assessing the 24-hour deadline.
Stage 2: classification within a few minutes
The shift supervisor, assisted by the duty safety or OT officer, assigns the event to a category and a severity level. Three levels are proposed: informational, requiring shift action, requiring the crisis team to be activated. A separate control question concerns cyber: could the event be a significant incident within the meaning of the KSC Act. A positive answer starts the reporting clock and names a contact person.
Stage 3: escalation by explicit criteria
Escalation should not depend on the courage of the person on duty. The criteria are written down in advance: danger to life, an installation stoppage, loss of control over a control system, an unauthorised person entering a critical zone, a suspected data leak. Meeting any one criterion means mandatory notification of the plant director and the CISO within a defined time.
Stage 4: register and closure
There is one register, with fields common to all event types: identifier, times (noticed, reported, classified, escalated, closed), location, category, severity, people, actions taken, the decision on reporting to the CSIRT, corrective actions. Closing an event requires an entry on the post-event analysis and conclusions.
An example division of roles
The division below is an example for a site with shift work. Every role has a deputy on the night shift, and the list of duty numbers is available outside the plant network.
- Plant director: decides on activating the crisis team, on stopping the installation and on external communication
- Shift supervisor: first in command, classifies the event and starts escalation
- Safety specialist: assesses the hazard to people, liaises with the accident investigation team
- Security manager: access control, securing the scene, the list of people on site
- CISO or OT administrator: assesses cyber impact, isolates segments, liaises with the CSIRT
- Two contact persons for entities of the national cybersecurity system: a statutory requirement
- Event recorder: keeps the timeline in the register from the first minute
The recorder role is often overlooked
One person who only writes down times and decisions shortens the later analysis by hours. The person in command has no capacity for note-taking, and reconstruction from memory after a day is unreliable. The recorder can be the duty dispatcher or the deputy shift supervisor.
What data an event record must contain
The auditor and the CSIRT ask the same things: when it was detected, who made the decision, what was done and how the outcome was confirmed. Evidence fields are therefore more important than a narrative description. The recommended minimum includes timestamps accurate to the minute, the identifier of the person making decisions, a list of those notified with the time of notification, and attachments: photos, screenshots from systems, printouts of attendance lists.
For events involving people, it helps to know who was in the zone at the time. A site that controls entry and keeps a list of people on site has that evidence at hand. Access control and event reporting systems provide such evidence for an audit, but they do not replace the commander's decision.
How to check that the path works
An untested procedure is a hypothesis. Twice a year it is worth running a tabletop exercise on a mixed scenario, for example a suspected unauthorised access to a controller during maintenance work with contractors on site. Four times are measured: from noticing to reporting, from reporting to classification, from classification to notifying the director, and from notification to the decision on reporting to the CSIRT.
Example calculation: the assumptions are a target of 60 minutes from noticing to the reporting decision and 24 hours for the early warning. If the exercise shows 150 minutes to the decision, the margin against 24 hours is still large, but an event on a Friday night into Saturday shortens it in practice, because decision makers are missing. The measured result is what justifies deputies and duty rosters.
Video
Frequently asked questions
When does the 24-hour deadline start?
From detection of the significant incident. That is why the register should have separate fields for the time of noticing and the time of internal reporting. Confirm the interpretation in a specific case with a legal adviser.
Must a safety event also be reported to the CSIRT?
No. Only significant incidents within the meaning of the KSC Act are reported to the CSIRT. A safety event goes into the shared register, and if it has a cyber component, the path triggers an assessment for reporting.
How many contact persons does the Act require?
At least two persons for contact with entities of the national cybersecurity system. In practice, people from different shifts are named.
Does one register not mix sensitive data?
It does not have to. Common fields are visible to all roles, and detailed fields, for example health data, are restricted by permissions.
Sources
Let us talk about a shared event path
We will show how event reports, notifications and the list of people on site combine into one evidence record. Book a conversation or a demo.
Let's talk