OT Cybersecurity
Asset inventory in ICS environments - the foundation of OT cybersecurity
ICS/OT asset inventory - methods (manual, passive discovery, active scanning), tools, IEC 62443 and NIST requirements. How to build an OT asset register step by step.
Józef Sulwiński
Michał StępieńPublished Updated 11 min read

Contents
When a vendor publishes a patch for a controller, the plant has to establish quickly how many of those controllers are running and where they stand. Without an up-to-date asset register that is not possible.
In OT environments, industrial control systems (ICS) operate for decades. Over that time, installations undergo upgrades, component replacements, and integrations with new systems, and documentation does not keep up with the changes.
Asset inventory of hardware and software is the first step of an OT cybersecurity program. The asset register shows whether a new vulnerability affects devices in the installation. It is the basis for designing network segmentation that matches the actual topology and remote access policies that fit the environment. The register is also the basis for meeting IEC 62443 and NIS2 (the EU directive on network and information security, transposed into national law in each member state).
A few numbers
| Value | What it means | Source |
|---|---|---|
| 50% | Half of organizations (50%) invested in OT asset inventory and visibility in 2025. | SANS, State of OT Security 2025 (Dragos summary) |
| 31% | In 31% of organizations there is no centralized inventory of OT remote access points. | SANS, State of OT Security 2025 (Dragos summary) |
| 14 | The guidance defines 14 highest-priority OT asset attributes that a register should contain. | CISA, Asset Inventory Guidance 2025 |
Why OT asset inventory is harder than in IT
In corporate networks, a directory service, endpoint management systems and agents on computers automate the inventory. In OT, standard IT tools do not work, and attempting to use them can disrupt the production process. Main challenges:
| Challenge | Description | Consequence |
|---|---|---|
| No agents | PLCs, RTUs and measurement devices do not support software agents | Inventory software cannot be installed on OT devices |
| Serial buses and fieldbus | Many devices communicate over serial buses (Modbus RTU, PROFIBUS) that are not visible on the Ethernet network | Listening to network traffic will not detect devices below the Ethernet layer |
| Sensitivity to scanning | Active scanning can cause older PLCs to crash | Active inventory methods require careful planning and a maintenance window |
| Long lifecycle | Devices typically operate for 10-15 years, often longer; documentation from installation time is outdated | Firmware versions, network configuration and IP addresses may have changed multiple times |
| Isolated segments | Some OT subnets have no connectivity to the corporate network (air gap) | Automated tools cannot reach all segments |
Three methods of asset inventory
The choice of method depends on the inventory goal, the acceptable level of intrusiveness, and available resources. In practice all three methods are combined, because each one sees a different part of the installation.
Manual inventory (physical walkdown)
A physical walkdown is the only method that reaches all devices: also those on fieldbus networks (Modbus RTU, PROFIBUS, HART), standalone devices, and components without network communication. It requires presence on site and familiarity with process and instrumentation diagrams (P&ID).
TIP
For a physical walkdown, prepare a form tailored to the installation. It should contain:
- device name, manufacturer, model and serial number;
- hardware version and firmware version (read from the device or from the engineering software);
- network address (IP or fieldbus address);
- physical location (building, cabinet, slot) and function in the process.
Photos of nameplates document the model, serial number and hardware version.
A physical walkdown is complete, has no impact on the process, and allows the physical condition of devices to be verified. It is time-consuming, requires physical access, and the collected data becomes outdated quickly.
Automatic passive discovery
Passive discovery aggregates and analyzes network traffic without initiating communication with devices. The monitoring tool connects to a mirror port (SPAN) on the switch and listens to packets. Based on headers, metadata and protocols, it builds a list of devices communicating on the network.
The traffic reveals IP and MAC addresses, protocols in use (including industrial ones: Modbus TCP, OPC, S7comm, EtherNet/IP), headers with manufacturer and model information, and communication patterns between devices.
NOTE
Passive discovery only detects devices that communicated during the analysis period. Dormant devices, those communicating infrequently, or those connected to separate segments will not be detected. The listening period should cover at least one full operating cycle of the installation, including rare operations such as weekly reports or backups.
The passive method is non-intrusive, does not require a maintenance window, and builds a communication baseline that is useful for an intrusion detection system (IDS). It detects only active devices, does not establish firmware versions, and requires switch reconfiguration (SPAN port).
Automatic active scanning (selective)
Active scanning sends queries to individual OT devices, using interfaces and protocols intended for parameterization (the same ones used by engineering software). This yields significantly more complete information: model, serial number, firmware version, configured services, diagnostic data and logs.
WARNING
Active scanning is more intrusive than passive discovery. Before running an active scan:
- obtain the process operator’s approval;
- test on an identical device in a lab environment;
- schedule a maintenance window;
- prepare a rollback procedure;
- have contact information for the controller vendor’s support team.
Active scanning gives complete version information, which vulnerability management needs, and detects devices that do not generate traffic. It requires a maintenance window, may affect older devices, and does not cover serial or fieldbus devices.
Method comparison
| Criterion | Manual | Passive | Active |
|---|---|---|---|
| Completeness | Covers all devices, including fieldbus | Detects only active network devices | Detects network devices, including dormant ones |
| Detail level | Depends on the form | Basic: IP and MAC addresses and protocols | Full: firmware, configuration and logs |
| Intrusiveness | No impact on the process | Minimal, requires a SPAN port | Moderate, devices respond to queries |
| Automation | None, manual work | Continuous | Periodic |
| Maintenance window | Not needed | Not needed, but the switch must be configured | Needed |
| Use case | Baseline and physical verification | IDS, continuous monitoring and traffic baseline | Vulnerability management and audit |
Tools for automatic OT asset inventory
The market for OT asset inventory tools has grown since 2020. Vendors usually combine passive listening with selective, active data collection from chosen devices.
| Tool type | Method | Purpose |
|---|---|---|
| Passive sensor | Listening to traffic from a SPAN port | Detects network devices, protocols and communication patterns without affecting the process. |
| Sensor with selective active queries | Passive listening and queries to chosen devices | Adds model, serial number and firmware version. |
| OT vulnerability scanner | Inventory data matched against vulnerability databases | Shows which devices are affected by published vulnerabilities. |
TIP
Before choosing a tool, check three things:
- whether the tool supports the protocols used in the installation (for example PROFIBUS, and BACnet in building systems);
- whether the vendor has tested the active method with devices from specific controller manufacturers;
- whether the tool integrates with the existing SIEM/SOC.
Before purchase, request a trial on a test segment, in a test environment or on a small production segment.
Standards and regulatory requirements
IEC 62443
IEC 62443-2-1:2024 describes the security program of an IACS owner (industrial automation and control system). The standard obliges the owner to identify the IACS and to maintain knowledge of its devices. IEC 62443-3-2 imposes the obligation to assign every asset to a zone or conduit and to describe it with its classification, criticality and business value.
NIST SP 800-82 Rev. 3 and CISA Asset Inventory Guidance
NIST SP 800-82 Rev. 3 identifies asset inventory as the foundation of an OT security program. On 13 August 2025, CISA published the guidance “Foundations for OT Cybersecurity: Asset Inventory Guidance”. It was co-authored by EPA, NSA, FBI and agencies from Australia, Canada, Germany, the Netherlands and New Zealand.
The guidance defines 14 highest-priority attributes for every OT asset:
| No. | Attribute | Description |
|---|---|---|
| 1 | Active/Supported Communication Protocols | Communication protocols used by the asset |
| 2 | Asset Criticality | Criticality of the asset to the process |
| 3 | Asset Number | Unique identifier |
| 4 | Asset Role/Type | Role in the process (PLC, HMI, RTU, switch) |
| 5 | Hostname | Network hostname |
| 6 | IP Address | IP address |
| 7 | Logging | Event logging configuration |
| 8 | MAC Address | Physical address |
| 9 | Manufacturer | Manufacturer |
| 10 | Model | Device model |
| 11 | Operating System | Operating system or firmware |
| 12 | Physical Location/Address | Physical location (building, cabinet, slot) |
| 13 | Ports/Services | Open ports and services |
| 14 | User Accounts | User accounts with access |
TIP
The CISA guidance was developed in eight working sessions with 33 participants from about 14 organizations. It is non-binding. It was co-authored by, among others, the German BSI and the Dutch NCSC, so it also works as a model in Europe. The 14 attributes are good industry practice and a starting point for an OT asset register.
NIS2
Under the NIS2 Directive (EU 2022/2555), essential and important entities must implement asset management and a risk analysis policy. Risk analysis needs an asset register, because without it there is no basis for the assessment. During an audit, the entity shows this register as the basis of its risk assessment.
CIS Controls v8.1
CIS Controls v8.1 opens with Control 1 (Inventory and Control of Enterprise Assets). For OT, this means maintaining a register of all devices connected to the network and identifying unauthorized and unmanaged devices.
WARNING
The asset register shows whether a published vulnerability affects devices in the installation. According to the Dragos report (February 2026), in 2025 25% of vulnerabilities from ICS-CERT and NVD had incorrect CVSS scores, and 26% of advisories contained no patch or mitigation from vendors. Vulnerability priority can be set only when the firmware version is known; active inventory provides it most fully, supplemented by a physical walkdown.
How to build an OT asset inventory program - step by step
| Phase | Action | Outcome | Tools |
|---|---|---|---|
| 1. Physical walkdown | On-site visit, P&ID documentation review, inventory form | Baseline: list of all devices | Spreadsheet, photos, forms |
| 2. Passive discovery | Connect a sensor to the SPAN port and listen for at least one full operating cycle of the installation | Network communication map, detected Ethernet devices | Passive sensor |
| 3. Active scanning | Selective scanning during a maintenance window | Complete firmware version, configuration and vulnerability data | Sensor with active queries, OT vulnerability scanner |
| 4. Consolidation | Merge data from the three methods, fill gaps | Complete OT asset register | CMDB or dedicated tool |
| 5. Classification | Assign assets to IEC 62443 zones, determine criticality and map to MITRE ATT&CK for ICS techniques | Assets classified by risk and exposure to attack scenarios | Criticality matrix |
| 6. Maintenance | Continuous passive monitoring, periodic active scans and a change registration procedure | Up-to-date asset register | Automation and a management of change (MOC) process |
TIP
The OT asset register should contain at minimum: identifier, physical location, manufacturer, model and serial number, firmware or OS version, network address, IEC 62443 zone, criticality, date of last verification and asset owner. For fieldbus devices, add the bus address, protocol type and master or slave role. Update the register with every change, following the management of change (MOC) procedure.
NIST SP 800-53 control mapping
| Action | NIST SP 800-53 control | Description |
|---|---|---|
| Hardware asset register | CM-8 | System Component Inventory |
| Software register | CM-8 | System Component Inventory |
| Unauthorized device detection | CM-8(3), IA-3 | Automated Unauthorized Component Detection; Device Identification and Authentication |
| Criticality classification | RA-2 | Security Categorization |
| Change management | CM-3 | Configuration Change Control |
| Vulnerability management | RA-5, SI-2 | Vulnerability Monitoring, Flaw Remediation |
| Network access control (NAC) | AC-3, IA-3 | Access Enforcement, Device I&A |
Source: NIST SP 800-53 Rev. 5.
Sources
- Foundations for OT Cybersecurity: Asset Inventory Guidance for Owners and Operators - CISA (accessed: )
- 2025 SANS State of OT Security: 5 Takeaways - Dragos (accessed: )
- Dragos 2026 OT Report Shows Surge in Threat Groups and Ransomware - Dragos (accessed: )
- Asset Visibility - Dragos (accessed: )
- Guide to Operational Technology (OT) Security, NIST SP 800-82 Rev. 3 - NIST (accessed: )
- IEC 62443-2-1:2024 - Security for industrial automation and control systems - Part 2-1: Security program requirements for IACS asset owners - IEC (accessed: )
- Security and Privacy Controls for Information Systems and Organizations, NIST SP 800-53 Rev. 5 - NIST (accessed: )
- Directive (EU) 2022/2555 (NIS2) - EUR-Lex (accessed: )
Need help in this area?
Our experts will help you assess the risk and plan next steps.