Cyber security | 12 November 2026
NIS2 and OT Security: Could You Demonstrate Control?
Published by Asset Guardian
The EU's NIS2 Directive strengthens requirements for cyber security risk management and incident reporting. Discover what this means for industrial operators and how accurate OT asset records, configuration management and reliable backups can help demonstrate control and support cyber resilience.
Imagine a cyber security incident affecting a critical industrial control system. Your team needs to establish which assets are affected, whether their configurations have changed and what impact the incident could have on operations.
The investigation is underway, but the information is spread across engineering workstations, spreadsheets, maintenance records and different departments. Before anyone can confidently assess the impact, they need to establish which records are accurate.
For organisations subject to the EU's NIS2 Directive, this presents a particular challenge. Significant incidents carry strict reporting deadlines, and operators need to be able to explain what has happened, which services may be affected and how the situation is being managed.
How quickly could your OT team establish those facts?
Who does NIS2 apply to?
NIS2 strengthens cyber security requirements for organisations operating in sectors considered essential or important to the EU economy and society. These include energy (including oil and gas), transport, water, healthcare and certain manufacturing activities.
Whether an organisation falls within scope depends on factors including its activities, size, location and the national legislation implementing the directive. Operators with facilities in multiple countries may need to consider different national requirements.
For UK operators, the distinction matters. NIS2 is an EU directive and does not automatically apply to UK operations. The UK has its own Network and Information Systems Regulations 2018, with further changes proposed through the Cyber Security and Resilience (Network and Information Systems) Bill, which was still progressing through Parliament at the time of writing.
For businesses operating across both jurisdictions, understanding which requirements apply to each operation is the first thing to check.
The reporting clock starts before you have all the answers
Article 23 of NIS2 establishes a staged reporting process for significant incidents.
In general, affected organisations must provide an early warning within 24 hours of becoming aware of a significant incident, followed by an incident notification within 72 hours. A final report is generally required within one month of the 72-hour notification, subject to the directive's provisions.
The 72-hour notification must include an initial assessment of the incident's severity and impact, plus indicators of compromise where available.
The report itself is usually filed by the security or compliance team, but the facts it depends on come from OT. Producing that assessment may depend on answering some difficult questions.
Which control systems are affected? What software versions are installed? Have configurations changed recently? Which operational processes depend on those systems? Are there other assets running the same vulnerable software?
Consider an incident involving an engineering workstation used to maintain several production systems. The immediate concern may be the workstation itself, but the investigation also needs to establish which controllers it can access, whether any project files have been modified and whether other systems could be affected.
If the asset inventory is incomplete or configuration records are held in different locations, establishing the potential impact becomes much harder.
NIS2 does not prescribe a particular asset management platform. However, reliable information about industrial assets and their configurations can help organisations assess incidents and support timely reporting.
Can you explain why a known vulnerability remains unresolved?
Article 21 of NIS2 requires appropriate and proportionate technical, operational and organisational measures to manage cyber security risks. These include policies and procedures for assessing the effectiveness of risk management measures, alongside requirements relating to vulnerability handling and disclosure.
For industrial operators, vulnerability management rarely comes down to simply applying every available patch.
A control system may be running software that is no longer supported. A vendor may require extensive compatibility testing before approving an update. A production schedule may prevent changes until the next planned shutdown.
Those constraints are familiar to engineering teams, but they also create decisions that need to be understood and documented.
Suppose a vulnerability is identified in a component supporting a critical production process. The operator decides that immediate patching would introduce an unacceptable operational risk and implements alternative safeguards until the next maintenance window.
Could the organisation demonstrate which assets are affected, why the decision was made, what compensating measures were introduced and who approved the approach?
Maintaining that information provides a clearer record of how the risk is being managed. It also makes the decision easier to review when circumstances change, whether through a new vulnerability disclosure, a software update or a change in operational criticality.
For more on the operational constraints involved, see OT Patch Management: How to Secure Systems You Can't Patch.
Could you recover the system from a trusted backup?
Article 21 also explicitly addresses business continuity, including backup management, disaster recovery and crisis management.
In an industrial environment, restoring a system can involve considerably more than recovering files.
An operator may need the correct controller configuration, approved software version, application files and supporting documentation. Those records must also correspond to the system's intended operating state.
Imagine a controller needs to be restored following a cyber incident. The engineering team finds several backup copies, but cannot immediately determine which is the latest approved version. One was created before a maintenance shutdown, another is stored on an engineering laptop and a third has no associated change record.
Even where a backup exists, uncertainty over its contents can delay recovery.
The relevant question is whether the organisation can identify a trusted, approved backup and demonstrate that its recovery arrangements are effective.
Configuration management, version control and documented change histories help engineering teams establish what should be restored and provide a record against which the recovered system can be checked.
What could you demonstrate today?
NIS2 also places responsibility on management bodies to approve and oversee cyber security risk management measures under Article 20.
For senior leaders, that creates a need for reliable information about how cyber risks are being managed across the organisation. For engineering and OT security teams, it reinforces the importance of maintaining records that support those decisions.
An operator may already have established processes for managing vulnerabilities, approving engineering changes and maintaining backups. The difficulty often arises when someone needs to bring the supporting information together.
A useful starting point is to select one critical industrial system and establish whether your team could readily retrieve:
- Its current software versions and approved configuration.
- Any known vulnerabilities and the decisions made to manage them.
- Its latest approved backup and evidence of recovery testing.
If retrieving that information requires contacting several departments, searching through multiple spreadsheets or comparing unverified files, that is your gap.
Asset Guardian helps industrial operators maintain OT asset information, manage configurations and software versions, track changes and keep controlled backups, with vulnerability and obsolescence information held alongside. These capabilities can support the evidence and operational processes organisations rely on when managing cyber security risks.
NIS2 asks for much more than asset records, but you can’t evidence much of it without them.
If a significant incident affected one of your critical control systems tomorrow, how quickly could you establish what was running, what had changed and what could be safely restored?
Strengthen Your OT Cyber Resilience
Asset Guardian helps industrial operators maintain accurate OT asset records, manage configuration changes and keep track of vulnerabilities and approved backups.