Why the asset register is the starting point
Article 21 of the NIS2 Directive lists among risk management measures, among others, a risk analysis policy, business continuity, supply chain security, access control and asset management. Poland implemented the directive with the Act of 23 January 2026 amending the National Cybersecurity System Act (KSC), Journal of Laws 2026, item 252, which has applied since 3 April 2026. In the catalogue of obligations of the information security management system, the Act lists asset analysis, risk estimation and continuous monitoring.
In practice each of these activities starts with a list: what do we have, where does it stand, who is responsible for it and what does it depend on. Without that list risk analysis rests on guesswork, and an incident ends with the question of whether the affected device was known to the team at all. The asset register supports meeting the Article 21 requirement and provides audit evidence, but it guarantees nothing by itself: it has value when it is current and has an owner.
Scope: what goes into the OT register
Start with the boundary. In an industrial plant the register covers everything that takes part in controlling the process or can affect it. It is better to define the scope broadly and set priorities later than to leave out a device that turns out to be a bridge to the controllers.
- PLC controllers, input and output modules, regulators and drives with network communication.
- Operator stations, SCADA and DCS servers, historian servers, engineering stations.
- Switches, routers, firewalls, industrial gateways, modems and remote service access links.
- Sensors and IIoT devices with a network or radio interface.
- Auxiliary systems that touch the OT network: uninterruptible power supplies, building systems, cameras, access control.
- Software: firmware versions, operating systems, control applications and licences.
IEC 62443-3-3 foundational requirements (FR) and SL levels
Register fields: the minimum that works
A register with so many columns that nobody fills it in is worse than a simple, living one. It is therefore worth choosing a minimum set of fields that answers the questions of the auditor and the response team, and adding the rest as the process matures.
Identification fields
A unique asset identifier, name, type, manufacturer, model, serial number, firmware or software version, network address and the physical address of the interface. Add the physical location: building, floor, cabinet, and in sprawling plants also coordinates or a point on the map.
Organisational and risk fields
Business owner and technical owner, the process the asset serves, criticality for production continuity, zone and communication conduit (the division from IEC 62443-3-2), the method of remote access, the date of the last review and the manufacturer's support status. These are the fields that turn a list of devices into a tool for risk analysis.
How to collect the data: four sources instead of one
No single source gives the full picture. Design documentation is out of date after the first modernisation, and a network scan shows only what responds. A reliable inventory is built by comparing at least four perspectives.
The first is documentation: diagrams, I/O lists, modernisation orders and acceptance records. The second is a physical walk-through with a checklist, which discovers devices that have no entry. The third is passive observation of OT network traffic, for example from a switch mirror port, which shows the addresses and protocols that actually communicate. The fourth is the knowledge of people: automation engineers, maintenance staff and integrators know devices that appear in no list.
A practical note: in industrial networks you do not run aggressive scanners from the IT toolbox. Older controllers may react to unexpected traffic by restarting or going into a stopped state, so data collection starts with passive methods, and active queries are made in agreed service windows against an approved list of devices.
Tying the register to NIS2 risk assessment
The asset register is an input to the risk estimation policy. The IEC 62443-3-2 standard describes dividing an installation into zones and conduits and assessing risk for each zone; this supports the Article 21 NIS2 requirement for measures proportionate to risk. In order: assign each asset a zone, assess the consequence of its unavailability for the process, assess vulnerabilities and exposure (remote access, connectivity to the office network), and record the result as a criticality level in the register.
The IEC 62443-3-3 standard works with security levels SL 1–4 and seven foundational requirements. The target level for a zone follows from the risk assessment, and the register shows which assets do not yet meet it. This arrangement gives management a clear picture: a list of assets, their criticality and the gaps to close, with an assigned owner and deadline.
Maintaining the register: change is the rule
A register loses value on the day it stops keeping up with change. Build a register update step into the plant's change procedure: every modernisation, controller replacement, new remote access or software version change ends with an entry. Once a quarter compare the register with passive network observation and a walk-through of a selected zone, and treat discrepancies as events to be explained.
For assets spread over a large site it helps to link an entry to a place on the plant map. The InnerWeb location module and plant map work on signals from many BLE beacons, without GPS, and show buildings, floors and work areas on a 2.5D map. Such a spatial reference makes it quicker to find the device named in the register and to check who is working in that area at the moment.
Checklist
Video
Frequently asked questions
Is an OT asset register mandatory under NIS2?
Article 21 of the directive requires risk management measures, and the KSC Act as worded in 2026 lists asset analysis among the elements of the information security management system. The register is therefore a practical way of showing that this analysis was carried out.
Can a network scanner be used in an OT environment?
With care. Start with passive methods, and make active queries in agreed service windows against an approved list of devices, because some older controllers tolerate unexpected traffic badly.
How many fields should a register have?
At the start a dozen or so fields are enough, answering questions about location, owner, criticality and support. A small register that gets updated is better than an elaborate one that dies out.
How often should the register be updated?
With every change in the installation, and additionally compare the register each quarter with network observation and a walk-through of a selected zone. Treat discrepancies as events to be explained.
Sources
Let us talk about the asset register in your plant
We will show how a spatial reference to the plant map supports the inventory and evidence for the auditor. Book a short conversation with the InnerWeb team.
Let's talk