OT Asset Discovery: How to Inventory PLCs, HMIs and SCADA

OT Asset Discovery: How to Build an Inventory of PLCs, HMIs, SCADA and Engineering Workstations

You cannot secure an industrial environment properly if you do not know what is connected to it.

That sounds simple, but OT environments are rarely static. Equipment is replaced, engineering workstations are added, temporary connections appear during maintenance, firmware changes over time and older systems can remain in operation long after their original documentation has disappeared.

The result is often a gap between the asset inventory an organization believes it has and the environment that actually exists.

OT asset discovery is the process of identifying those systems and establishing enough information about them to support security, maintenance, risk management and operational decision making.

What Is OT Asset Discovery?

OT asset discovery is the process of identifying operational technology devices, systems, software, communication relationships and other components that form part of an industrial environment.

The scope can include programmable logic controllers, human machine interfaces, SCADA servers, engineering workstations, industrial switches, firewalls, remote access systems, historians, servers and other supporting infrastructure.

Discovery answers a basic question: what exists?

Asset management goes further. It asks who owns the asset, what it does, where it is located, how important it is, what software or firmware it runs, how it communicates and how changes to it are controlled.

Why an OT Asset Inventory Matters

An incomplete inventory creates uncertainty across almost every part of an OT security program.

If an organization does not know that a device exists, it becomes difficult to determine whether it has been patched, whether it is supported, whether it is exposed, whether it should communicate with other systems or whether it should be included in an incident response plan.

NIST identifies asset management as a foundational cybersecurity capability and recommends maintaining inventory information as assets are added, removed, changed, patched or replaced.

NIST’s 2026 OT asset management project goes further by describing complete asset management and visibility as foundational for risk assessment, network segmentation, vulnerability management, incident response, zero trust architectures and technology modernization.

What Should Be Included in an OT Asset Inventory?

A useful inventory should contain enough information to distinguish assets, understand their function and support security decisions.

Asset InformationWhy It Matters
Asset identifierProvides a consistent way to identify and track the device.
ManufacturerSupports product identification and vendor research.
ModelHelps distinguish equipment and determine technical characteristics.
Serial numberSupports physical identification and lifecycle management.
LocationShows where the asset operates.
IP and network informationHelps establish network relationships and exposure.
Software and firmwareSupports vulnerability, compatibility and lifecycle assessment.
Operational functionExplains what the asset does within the process.
OwnerIdentifies who is responsible for the asset.
CriticalityHelps prioritize security and maintenance decisions.

NIST SP 800-82 Rev. 3 specifically recommends maintaining information such as unique identifiers, hardware details, location, vendor and model information, software and firmware versions, vendor information and documented roles and responsibilities.

Start With the Physical Environment

OT asset discovery should not be treated as an IP address exercise.

Industrial assets exist in physical locations and perform physical functions. A security assessment should therefore connect the logical network identity of an asset with its physical and operational context.

For example, an inventory entry for a PLC becomes much more useful when it identifies the production area, control cabinet, process function and responsible engineering team in addition to its network address.

This relationship helps engineers understand the potential consequence of a security issue and helps security teams avoid treating every device as though it has the same operational importance.

Identify PLCs and Controllers

PLCs and other controllers are among the most important assets to identify in an industrial environment because they can directly participate in controlling physical processes.

Where available, the inventory should record:

  • Manufacturer
  • Model
  • Controller identifier
  • Location
  • Firmware version
  • Network address
  • Associated engineering workstation
  • Controlled process or equipment
  • Responsible engineering team
  • Backup status

The exact information available will depend on the controller family and the organization’s documentation.

Identify HMIs and Operator Stations

Human machine interfaces provide another important part of the OT asset picture.

An HMI may communicate with one or more controllers and provide operators with information or control functions. Its operating system, application software, network connections and user access should therefore be considered during inventory development.

The inventory should establish which HMI belongs to which process and which control systems it communicates with.

Identify SCADA Servers and Historians

SCADA servers, historians and related infrastructure can sit at important points within an industrial architecture.

These systems may collect process information, provide supervisory interfaces or support operational analysis.

The inventory should capture their operating system, application or platform, network location, dependencies, communication relationships and responsible owners where that information is available.

Identify Engineering Workstations

Engineering workstations deserve particular attention because they can have privileged relationships with industrial control equipment.

Depending on the environment, an engineering workstation may be used for controller programming, configuration, diagnostics, maintenance or vendor support.

The inventory should therefore identify not only the workstation itself but also the industrial systems it can access.

  • Hostname
  • IP address
  • Operating system
  • Engineering software
  • Software versions
  • Connected controllers
  • Administrator or privileged users
  • Remote access capability
  • Physical location
  • Responsible team

Do Not Forget Network Infrastructure

Industrial switches, routers, firewalls and remote access systems are sometimes excluded from OT asset inventories because they are considered networking equipment rather than operational assets.

That distinction can create blind spots.

Network infrastructure determines how systems communicate and where security boundaries are enforced. A firewall with an undocumented rule or an unmanaged industrial switch can therefore affect the security posture of many other assets.

Manual Discovery vs Automated Discovery

There is no single discovery method that works equally well in every OT environment.

Manual discovery can use engineering documentation, maintenance records, configuration files, switch information, firewall records and physical inspection.

Automated discovery can use network monitoring, asset management platforms and carefully controlled network discovery techniques.

NIST’s current OT asset management work explicitly considers both automated and manual discovery because OT environments can have legacy systems, geographically distributed assets, diverse communication protocols and operational constraints.

Why Active Discovery Requires Care

Automated does not always mean risk free.

Some asset discovery tools use active network traffic to identify systems and characteristics. In a conventional enterprise environment this may be routine. In OT, the collection method needs to be evaluated against the equipment and operational requirements.

NIST recommends considering whether automated collection methods, including active scanning, could negatively affect OT systems. It also recommends testing automated asset management tools on offline systems or components before deploying them in an OT production environment where appropriate.

When active discovery is not appropriate, manual processes and passive sources can still contribute to maintaining a current inventory.

Use Multiple Sources to Build the Inventory

The strongest OT inventories are normally built by reconciling multiple sources rather than trusting one system.

SourceUseful Information
Network diagramsExpected architecture and communication boundaries.
Switch informationNetwork connectivity and connected devices.
Firewall recordsPermitted communication paths.
Engineering documentationProcess function and control relationships.
Maintenance recordsEquipment changes and replacements.
Configuration filesSystem and device details.
Passive monitoringObserved network communication.
Controlled discoveryAdditional network and service information.
Physical inspectionLocation and equipment identity.

When two sources disagree, do not simply choose one. Investigate the discrepancy.

Find the Unknown Assets

One of the most valuable outcomes of an asset discovery exercise is identifying systems that were not previously documented.

An unknown asset can have several explanations. It may be legitimate equipment that was never added to the inventory, a temporary maintenance system, a replacement device, an old system that should have been removed or an unmanaged device.

The correct response is investigation.

For each unknown system, determine:

  • What is it?
  • Where is it?
  • Who owns it?
  • What process does it support?
  • How does it communicate?
  • Why was it missing from the inventory?
  • Does it require continued access?

Connect Assets to Network Zones

An asset inventory becomes more useful when every important asset is associated with its network location and security zone.

For example, an organization may distinguish between enterprise systems, an industrial DMZ, operations networks, control networks and engineering environments.

This allows security teams to ask more useful questions.

  • Which assets are directly exposed to enterprise systems?
  • Which assets can communicate across the industrial DMZ?
  • Which engineering workstations can reach control systems?
  • Which devices are located in sensitive control zones?
  • Which assets have remote access?

Asset identity without network context leaves an important part of the risk picture incomplete.

Add Software and Firmware Information

Knowing that a PLC or workstation exists is not enough for vulnerability management.

Where practical, the inventory should also record relevant software and firmware versions.

This information can help security teams identify unsupported versions, investigate security advisories, understand compatibility constraints and plan future upgrades.

NIST specifically recommends software and firmware inventory information as part of OT asset management.

Track Ownership and Responsibility

An inventory should not become a database that nobody is responsible for maintaining.

Each important asset should have clearly documented responsibility where possible.

  • Asset owner
  • Operations responsibility
  • Maintenance responsibility
  • Engineering responsibility
  • Cybersecurity responsibility
  • Vendor or integrator contact

NIST recommends documenting roles and responsibilities associated with asset ownership, operation, maintenance and cybersecurity.

Record Asset Criticality

Not every asset has the same operational importance.

A workstation used for general engineering documentation may not have the same consequence profile as a controller responsible for a critical production process.

Criticality should therefore be recorded using the organization’s own risk methodology and operational understanding.

Possible factors include:

  • Production impact
  • Safety relevance
  • Environmental consequence
  • Process dependency
  • Recovery difficulty
  • Availability requirements
  • Potential impact of compromise

Keep the Inventory Current

A one time inventory becomes outdated surprisingly quickly.

Equipment changes, firmware upgrades, network modifications, maintenance replacements and new remote access arrangements can all change the security picture.

NIST recommends updating inventory information when components are added, removed or changed, including changes such as patches, firmware installation and component replacement during maintenance.

The inventory should therefore become part of the organization’s change management process rather than remaining a document created for a single security project.

Use the Inventory for Security Decisions

The purpose of an OT inventory is not to collect as many fields as possible.

The purpose is to create useful visibility.

A reliable inventory can support:

  • Risk assessments
  • Vulnerability management
  • Network segmentation
  • Incident response
  • Patch and upgrade planning
  • Obsolescence tracking
  • Backup planning
  • Change management
  • Remote access review
  • Security monitoring

This is why asset visibility should be treated as a security capability rather than an administrative spreadsheet.

Common OT Asset Inventory Mistakes

  • Keeping only IP addresses without asset identity.
  • Ignoring physical location.
  • Failing to record firmware and software versions.
  • Leaving engineering workstations out of the inventory.
  • Ignoring industrial network infrastructure.
  • Not documenting vendor access.
  • Failing to record ownership.
  • Using an inventory that is never updated.
  • Relying entirely on active scanning.
  • Relying entirely on manual documentation.
  • Failing to reconcile conflicting sources.
  • Recording assets without recording their operational purpose.

What a Good OT Asset Discovery Report Should Deliver

A professional discovery exercise should leave the organization with a clearer and more defensible understanding of its environment.

  • Confirmed asset inventory
  • Unknown or undocumented asset list
  • Asset ownership information
  • Physical and logical location
  • Network zone mapping
  • Software and firmware information where available
  • Communication relationships
  • Criticality information
  • Inventory gaps
  • Data quality limitations
  • Recommended actions for maintaining the inventory

The report should also clearly state what could not be confirmed. An inventory containing unknown fields is more trustworthy than one filled with assumptions.

OT Asset Discovery Is the Beginning, Not the End

Knowing what exists does not automatically make an OT environment secure.

But without reliable asset visibility, many other security activities become harder to perform accurately.

You cannot confidently assess a vulnerability on an unknown device. You cannot properly segment a system you have not identified. You cannot build a reliable incident response plan around assets that are missing from the inventory.

That is why asset discovery belongs near the beginning of an OT cybersecurity program.

Final Perspective

An OT asset inventory is more than a list of PLCs, HMIs and IP addresses.

A useful inventory connects each important asset to its identity, physical location, network position, operational function, software or firmware, ownership and criticality.

The strongest approach combines manual records, engineering knowledge, passive evidence and carefully controlled technical discovery. No single source should automatically be treated as complete.

Most importantly, the inventory needs to remain current. An accurate inventory today that becomes obsolete after the next maintenance cycle does not provide durable security visibility.

For organizations building an OT security program, asset discovery is one of the most practical places to start because it creates the visibility needed for the security decisions that follow.

Need an Independent OT Asset Discovery Assessment?

Cautivra provides focused OT asset discovery and inventory assessments for organizations that need a clearer understanding of their industrial environment, including connected systems, network context, asset information and inventory gaps.

The assessment can combine available engineering documentation with authorized technical evidence and carefully controlled discovery methods, depending on the operational environment.

Request an OT Asset Discovery Assessment

Sources and Further Reading

  • NIST SP 800-82 Rev. 3, Guide to Operational Technology Security
  • NIST NCCoE, Operational Technology Asset Management
  • NIST, Asset Management as a Foundation for Operational Technology Cybersecurity
  • CISA, Foundations for OT Cybersecurity: Asset Inventory Guidance

Leave a Reply