What security convergence means in an industrial plant
Security convergence is the management of physical protection, occupational safety and cybersecurity under one risk assessment, with one view of events and one escalation path. It does not mean merging departments or buying everything from one vendor. It means shared event definitions, a shared division of roles and data that can be placed on a single timeline.
The reason is practical. An attack on the OT network is sometimes preceded by a person entering the site, and a failure of the access control system is sometimes the result of a digital attack. An unknown person entering the control room is at once a physical security event, an information security breach and a potential danger to people. If each of the three teams sees only its own fragment, none of them will recognise the whole within the reporting deadlines.
Three domains, one event
The physical domain covers gates, the guardhouse, access control, video monitoring and patrols. The EHS domain covers work permits, training, the list of people on site and evacuation. The cyber domain covers IT and OT networks, accounts, backups and event monitoring. Convergence joins them at the level of events, not devices: an entry scan, a no-motion alarm and an unusual login to an engineering station land in one view.
What follows from NIS2, the KSC Act and the CER Directive
Article 21 of the NIS2 Directive (EU) 2022/2555 requires risk management measures, including incident handling, business continuity, supply chain security, access control, asset management and training. Article 23 sets the deadlines: an early warning within 24 hours, an incident notification within 72 hours and a final report within one month. Article 34 provides for fines of up to EUR 10 million or 2% of worldwide turnover for essential entities and up to EUR 7 million or 1.4% for important entities.
In Poland the directive is implemented by the Act of 23 January 2026 amending the National Cybersecurity System Act (KSC), Journal of Laws 2026, item 252, in force since 3 April 2026. Entities that meet the criteria have 12 months to put in place system-level obligations such as an information security management system and incident procedures, and the first audit of an essential entity falls 24 months after entry into force. Most fines can be imposed from 3 April 2028, but the transition period does not change the deadlines for reporting serious incidents, which run from detection.
The CER Directive (EU) 2022/2557 concerns the resilience of critical entities. In Poland it is implemented by the Act of 29 May 2026 amending the Crisis Management Act (Journal of Laws 2026, item 815). It requires a risk assessment at least every 2 years and measures proportionate to the result: physical protection of buildings and grounds with access control, personnel security for employees and external suppliers, cybersecurity to the standard required of essential entities, business continuity, training and exercises. A significant incident is reported within 24 hours. Critical entities are at the same time essential entities under the KSC Act, so both regimes land on the same plant.
- NIS2 and KSC: digital risk, supply chain, access control, reporting at 24 h and 72 h.
- CER: antagonistic risk, physical protection with access control, personnel security, business continuity.
- Common denominator: one risk assessment, one asset list, one reporting path.
Incidents recorded by CERT Polska
Six steps to build a joint system
Order matters. Plants that start by buying an event correlation platform usually find after a few months that nobody has decided who is responsible for the decision to report. The sequence below starts with people and definitions and adds technology last.
Steps 1 and 2: assets and a joint risk assessment
List buildings, zones, gates, OT systems, servers, privileged accounts and external companies with access in a single table. Add an owner to each item. Then run one risk assessment in which the scenario 'an unknown person in the control room with a USB stick' is assessed as a whole rather than in three separate documents.
Steps 3 and 4: roles and an event catalogue
Name the person who decides whether an event is a serious incident, their deputy and the two contact persons required by the KSC Act. Write an event catalogue covering all three domains, for example a rejected gate scan, an SOS alarm, a worker with no motion, loss of communication with a controller and failed logins to an administrator account. For each event record the threshold at which it moves from the duty officer to the decision level.
Steps 5 and 6: data on one timeline and exercises
Collect events from the gates, the EHS system and IT in one place with a common timestamp. Start with a few sources of the highest evidential value rather than all of them. At least once a year, rehearse a combined scenario and measure how many minutes pass from the first signal to the decision to report. The result is audit evidence and a baseline for later exercises.
Segmentation and the boundaries between IT, OT and physical security
Convergence of events does not mean convergence of networks. The IEC 62443 series structures this by dividing an installation into zones and conduits (part 3-2) and defining seven foundational requirements, from identification and authentication to timely response to events (part 3-3). Data from the control zone should flow to the shared view one way or through a controlled intermediary, not by opening a new path to the controllers.
The same applies to physical protection systems. Access control and video monitoring are in practice IT devices on the plant network and themselves need segmentation, updates and named accounts. In a NIS2 audit, the absence of such measures may be assessed as a lack of adequate safeguards, even though the standard is voluntary.
Audit evidence: what should remain after an event
The auditor, the regulator and the insurer will ask the same thing: who detected it, when, what was done and who decided. A joint event system should leave a complete trail after every incident: the timestamp of the first signal, the list of people on site from entry and exit records, the classification decision with its justification, the text of the notification to the CSIRT and the final report. Such a trail supports meeting the documentation requirement and shortens the preparation of the report.
Training matters too. The head of an essential entity has a duty to complete cybersecurity training every year, and the act provides for personal financial liability of the head. A record of a combined exercise signed by the plant director is therefore useful evidence of oversight.
The scale of threats and what it means for a plant
CERT Polska recorded 260,783 incidents in 2025, 152% more than a year earlier. Most were computer fraud and phishing, but 3,438 involved malware, including 179 ransomware cases, and 1,732 concerned vulnerable services. For an industrial plant, what matters more than the overall number is that the first vector is often an employee or contractor account and the consequence is a stopped line. A shared view should therefore also cover account events and access by external companies.
Video
Frequently asked questions
Does convergence require a joint department?
No. It requires shared event definitions, one risk assessment and an agreed escalation path. Departments can stay separate if their data can be placed on a single timeline.
Is physical protection covered by NIS2?
The directive concerns the security of network and information systems, but Article 21 covers access control and asset management. Physical protection returns in full scope in the CER Directive, which applies to critical entities.
When can fines under the KSC Act be imposed?
The act has been in force since 3 April 2026, and most financial penalties can be imposed from 3 April 2028. This does not apply to the most serious breaches, and incident reporting deadlines apply during the transition period under the rules of the act.
Where to start in an existing plant?
With an asset table that names owners and an event catalogue covering the three domains. This takes weeks, requires no purchases and shows where data is scattered today.
Sources
Let us talk about a shared view of events
We will show how events from gates, EHS and location land on one plant map and how this supports documenting the requirements. Book a conversation or a demo.
Let's talk