The safest way to build an OT asset inventory is to layer methods: walk the floor, listen to network traffic passively, read device configurations, and use active queries only on tested equipment during planned maintenance windows. No single method produces a complete list, and the wrong one can stop a production line. This guide shows how each method works, where it fails, and how a Wisconsin manufacturer can get from "we think we know what's out there" to a living inventory that supports security, compliance and uptime.
OT means operational technology: the PLCs, HMIs, sensors, drives and controllers that run your machines and processes, as opposed to the laptops, servers and email that make up IT. Asset discovery is the work of finding those devices. The inventory is the organized list you keep afterward.
TL;DR
- Use several methods together. Physical inspection, passive monitoring, configuration analysis and carefully controlled active discovery each cover gaps the others leave.
- Make passive network monitoring your default. Active scanning that is routine on office networks can knock older control devices offline.
- Record the 14 attributes CISA lists as high priority, starting with IP address, MAC address, manufacturer, model, operating system and criticality.
- Start with the lines and systems where downtime or a security incident would hurt most, then expand.
- An inventory only helps if someone owns it and keeps it current. Assign that owner before you start.
Table of Contents
- What an OT asset inventory actually is
- The four core discovery methods
- Why a hybrid approach wins
- Build the inventory in a structured process
- Finding legacy, unmanaged and hidden devices
- Using the inventory once you have it
- A realistic first 30 days for a Wisconsin plant
- Where Collett Systems fits
- Our perspective
- FAQ
- Sources
What an OT asset inventory actually is
CISA's August 2025 guidance, written with the EPA, NSA, FBI and international partners, defines an asset inventory as an organized, regularly updated list of an organization's systems, hardware and software. On top of that list sits a taxonomy: a way of categorizing and prioritizing assets by function and criticality. A taxonomy answers questions like "which of these devices stops the line if it fails?" and "which ones touch the outside network?"
Why bother? The NIST National Cybersecurity Center of Excellence describes asset management and visibility as foundational to risk assessment, segmentation, vulnerability management and incident response. Without it, you cannot say which controllers run unsupported firmware, which machines a vendor can reach remotely, or what to replace first.
The problem is common. A SANS white paper reports that asset identification was the number one concern among 338 ICS security professionals surveyed in 2019, and that more than half of ICS operators spend 20 to 80% of their time just finding and validating plant information. Plants grow by accretion: a machine bought in 2004, a retrofit from an integrator who has since closed, a vendor's modem nobody documented. The inventory is how you take that history back under control.
The four core discovery methods
SANS groups ICS asset identification into four techniques: physical inspection, passive discovery, configuration analysis and active discovery. Here is how they compare.
| Method | How it works | Strength | Weakness |
|---|---|---|---|
| Physical inspection | Someone walks the plant and records what is installed, down to nameplates and cabinets | The most comprehensive picture | The most labor-intensive, and out of date the day after |
| Passive discovery | Monitors network traffic without sending anything | Safe for running processes; works well at Purdue Model Level 2 and above | Misses field devices and devices behind NAT |
| Configuration analysis | Reads configuration files and backups from switches, firewalls and controllers | Scales across a plant in a few staff hours | A snapshot only; will not reveal rogue devices |
| Active discovery | Sends queries to devices and reads the answers | Can find dormant devices that never talk | Can lock up older non-compliant equipment or exhaust CPU |
The Purdue Model is the standard way of describing industrial network layers, from the physical process at the bottom (Level 0) through controllers (Level 1) and supervisory systems such as HMIs (Level 2) up to the business network. That is why passive monitoring does well at Level 2 and above, where traffic is plentiful, and poorly at the sensor and actuator level.
Physical inspection
This is the method everyone skips because it is tedious, and it is the one that catches what software cannot: a standalone controller with no network connection, a serial-connected drive, a cabinet added by a contractor. CISA's guidance directs organizations to conduct a physical inspection in addition to the logical survey, because the inventory scope should cover assets found in both documentation and physical inspection.
Where it goes wrong: inconsistent notes. If one person writes "Allen-Bradley PLC" and another writes "AB ControlLogix L73", you cannot sort or search later. Decide the fields and naming before anyone picks up a clipboard.
Passive discovery
Passive discovery uses a SPAN port (a switch feature that mirrors traffic to a monitoring port) or a network TAP (a small hardware device that copies traffic) to observe communications. According to a Cloud Security Alliance research note on CISA's zero trust guidance for OT, passive monitoring is the safe default because it generates no queries that could disrupt control processes.
Where it goes wrong: coverage. A sensor only sees the traffic that crosses it. The NCCoE project description notes that passive collection may have coverage gaps if sensors are inadequately deployed, and devices that rarely communicate can go unseen for weeks.
Configuration analysis
Switch configs, firewall rules, PLC project files and backup archives list the devices and connections they know about. SANS notes this can be done across a plant in a few staff hours. It is a quick way to build a first draft, and it tells you what is supposed to be connected. It cannot tell you what was plugged in last Tuesday.
Active discovery
Active discovery asks devices to identify themselves. In the office that is routine. On the plant floor it is the riskiest option, because protocols like Modbus, DNP3 and EtherNet/IP were never designed to handle unexpected queries and can be destabilized by them. SANS warns that active discovery can lock up older equipment or exhaust its CPU, and recommends testing on representative equipment before production use.
If you use it, use it narrowly: a defined list of target devices, a maintenance window, written approval from operations, and a rollback plan.
Why a hybrid approach wins
Each method fails somewhere different, which is exactly why they work together. NCCoE's OT asset management project is built on this idea: its draft description says active querying could negatively affect operations, passive collection can leave gaps, and manual collection may not keep pace with change, so it demonstrates a hybrid of passive, active and manual approaches. SANS reaches the same conclusion: mature programs combine multiple techniques because no single approach produces a complete inventory.
A practical sequence for a plant:
- Configuration analysis first. Pull switch, firewall and controller configurations. In a few hours you have a draft list and a map of what is expected.
- Passive monitoring second. Place TAPs or SPAN ports at aggregation points, such as the switch that connects a production cell to the plant network, and let them run long enough to see normal traffic cycles, including shift changes and batch runs.
- Physical walk-down third. Compare the draft against what is actually on the floor. Anything on the floor but not on the network is a standalone device. Anything on the network but not on the floor is a question to answer fast.
- Targeted active queries last. Only for gaps, only on devices you have tested, and only during a maintenance window.
That order puts the least risky, most scalable work first and saves the risky work for the small number of devices that need it.
Build the inventory in a structured process
Methods are only half the job. CISA's guidance lays out a process, and its first steps are worth following even in a small plant.
Step 1: Define scope and objectives
CISA's first step covers three things: governance, roles, and scope. Governance means identifying who requires the inventory and which positions are responsible for it or benefit from it. Roles means assigning who collects data and who validates it. Scope means setting boundaries such as specific zones, facilities, systems and a timeline, and deciding what counts as an "asset" for your purposes.
The authoring agencies also admit that a definitive record of all OT systems is complex and time consuming, and recommend prioritizing by business impact, third-party connections that can change configurations or control processes, and overall exposure. For a manufacturer, that usually means your highest-revenue line, anything a vendor can reach remotely, and anything connected to the business network.
Step 2: Identify assets and collect attributes
This is where the methods above come in: a physical inspection plus a logical survey, collecting digital and network information about each component. CISA lists 14 high-priority attributes to capture where possible:
- Active and supported communication protocols
- Asset criticality
- Asset number
- Asset role or type
- Hostname
- IP address
- Logging
- MAC address
- Manufacturer
- Model
- Operating system
- Physical location or address
- Ports and services
- User accounts
You will not get all 14 for every device on day one. Older controllers often have no hostname and no logging. Record what you have, mark what is unknown, and fill gaps over time. Recording model numbers pays off later: NIST notes that it allows you to locate and replace specific devices when needed.
Step 3: Create a taxonomy
Group assets by function and criticality. CISA's guidance includes conceptual taxonomies for oil and gas, electricity, and water and wastewater, and Federal News Network reported that sector-specific terms matter because different industries name their systems differently. Manufacturers do not have a ready-made template there, so build a simple one: by production line or cell, by device role (controller, HMI, drive, switch, remote access point), and by criticality (stops production, degrades production, no production impact).
Step 4: Add data sources and centralize
The guidance's fourth step directs organizations to identify additional data sources for each asset and establish and secure a centralized asset management database. Vendor documentation, engineering drawings, maintenance records and purchasing history all help fill the blanks. Secure the database itself: the September 2025 definitive-view guidance points out that the record is valuable to threat actors too.
Step 5: Keep it current
The guidance ends with ongoing maintenance, and this is where most inventories die. Name an owner. CISA and EPA recommend identifying inventory owners to oversee updates and validate classifications, and developing reporting to track performance, maintenance and policy compliance.
Finding legacy, unmanaged and hidden devices
Legacy equipment is the hard part. The CSA note explains that older OT systems rely on proprietary protocols with no authentication or encryption, produce minimal logs, and often cannot run agent-based security software because of constrained hardware, warranty restrictions or tight coupling between application and operating system. So you cannot install an agent on a 15-year-old controller or safely poke it with a scanner.
What works instead:
- Accept partial automation in segmented areas. In highly segmented or air-gapped environments, automated tools will produce only partial results. The CSA note advises planning sensor placement around the largest or highest-risk segments rather than chasing full coverage at prohibitive cost.
- Lean on physical inspection for anything that cannot be seen on the wire.
- Use vendor and integrator records to confirm models, firmware and serial numbers.
- Treat every unknown device as a finding. If you cannot say who installed it and what it does, put it on a list to resolve.
Segmentation helps both discovery and defense: a well-designed network makes it clear where sensors belong and limits the damage from anything you missed. Our guide to network segmentation basics covers the fundamentals.
Using the inventory once you have it
An inventory is not a deliverable. It is a working tool.
- Patching. CISA and EPA recommend reviewing maintenance plans against vulnerability findings and scheduling patches in maintenance windows, and comparing downtime costs against replacing legacy systems or adding compensating controls. See our OT patch management guide for manufacturers for the practical side.
- Maintenance and spares. The same guidance suggests analyzing your spare parts stock to confirm it covers critical assets. NIST also notes that asset management helps determine which assets belong in preventive maintenance.
- Incident response and recovery. SANS states that comprehensive inventories directly reduce mean time to recovery. When a controller fails at 2 a.m., knowing its model, firmware and last good backup is the difference between an hour and a day.
- Compliance and reporting. The CISA guidance arrived ahead of U.S. cyber incident reporting requirements under CIRCIA, the Cyber Incident Reporting for Critical Infrastructure Act, as noted by a law firm analysis. If you handle controlled unclassified information for defense customers, our NIST 800-171 self-assessment guide shows how an accurate inventory supports your score.
- Ongoing guidance. On September 29, 2025, CISA, the FBI, the UK NCSC and international partners published guidance on creating and maintaining a definitive view of OT architecture, building on the August inventory guidance. It frames the inventory as a continually updated "definitive record".
A realistic first 30 days for a Wisconsin plant
You do not need a six-figure project to start. Here is a plan sized for a small or mid-sized manufacturer:
- Week 1: Name an owner and a backup. Pick one production line or area as scope. Agree on the fields and naming conventions.
- Week 2: Collect configurations and backups, and sketch the network. Walk the line with the draft in hand.
- Week 3: Deploy passive monitoring at the aggregation point for that area. Let it capture a full production cycle.
- Week 4: Reconcile the three sources. Flag unknowns, rank by criticality, and decide which gaps justify an active query in a maintenance window.
Then repeat for the next area. The same discipline applies to the office side: our 90-day IT asset inventory roadmap covers laptops, servers and cloud apps, and OT and IT inventories should eventually share one view. Our article on identity-first OT and IT security explains why one coordinated approach beats separate ones.
The Cloud Security Alliance also stresses that IT-centric approaches cannot be applied wholesale to OT: availability demands, decades-long equipment lifecycles and legacy protocols call for genuine partnership between OT engineers, IT architects and security professionals. In practice, your maintenance and controls people must be in the room from day one.
Where Collett Systems fits
For many Southeastern Wisconsin manufacturers, the obstacle is not knowing the methods. It is finding the time, and having one accountable party that keeps the list current after the first pass. Collett Systems provides managed IT for small and mid-sized businesses with fixed per-user pricing, 24/7 monitoring, proactive support and compliance documentation, and more than 150 local organizations work with us.
The natural first move is our IT & Security Assessment, a paid, upfront review that gives you a scored picture of your environment and a prioritized list of what to fix. If you want a quick read first, the free IT Risk Score takes about 60 seconds.
If your internal team wants to keep ownership of day-to-day operations, our co-managed IT services work alongside them, and our Managed IT Services cover full infrastructure management. A documented, current environment is also the foundation of the checklists in our security assessment guide and IT documentation checklist.
Our perspective
Most plants we talk to do not have an inventory problem. They have an ownership problem. Someone built a spreadsheet once, it was accurate for a quarter, and then a vendor swapped a controller and nobody updated it.
We treat IT as infrastructure, not as an expense, and infrastructure has to be owned continuously. That is why we run a standardized, fully loaded stack with a fixed cost per user, defined SLAs and proactive monitoring. Strategic planning, audit readiness and automation improvements are part of the service, not add-ons you negotiate for later.
For manufacturers, that matters because the cost of not knowing is high: downtime, a security incident, or an audit where you cannot show what you run. Our advice is simple. Start with the line that hurts most when it stops, document it properly, and make sure a named person is responsible for keeping that record current. Then build outward. If you want a local team to share that responsibility, we are here, in Wisconsin, and we show up when you need us.
Dustin Collett
FAQ
What is the difference between OT asset discovery and an OT asset inventory?
Discovery is the activity: finding devices through inspection, network monitoring, configuration review or queries. The inventory is the result, an organized and regularly updated list of systems, hardware and software. Discovery happens repeatedly; the inventory is what you maintain between rounds.
Is passive discovery enough on its own?
Usually not. Passive monitoring is the safest default, but it can miss field devices, devices behind NAT and anything that rarely communicates. Pairing it with configuration analysis and a physical walk-down closes most of those gaps, as SANS and NCCoE both describe.
Can I run a network scanner on my plant floor?
Treat it as a last resort and a controlled exercise. Scans that are normal on office networks can lock up or destabilize older control devices. If you need active queries, test them first on representative equipment, schedule a maintenance window, and get written approval from operations.
Which devices should I inventory first?
Start with what would hurt most if it failed or were compromised: your highest-impact production lines, devices with third-party or remote connections, and systems exposed to the business network. CISA and its partners recommend prioritizing by business impact, third-party access and exposure.
How often should the inventory be updated?
Continuously where possible, and at minimum whenever equipment is added, replaced or reconfigured. Passive monitoring helps by flagging new traffic, and a named owner should validate changes. CISA describes the goal as a continually updated record rather than a one-time project.
Sources
- Foundations for OT Cybersecurity: Asset Inventory Guidance for Owners and Operators (CISA)
- Joint guide: Foundations for OT Cybersecurity Asset Inventory Guidance (EPA)
- Creating and Maintaining a Definitive View of Your OT Architecture (CISA)
- ICS Asset Identification: It's More Than Just Security (SANS)
- CISA Zero Trust for Operational Technology (Cloud Security Alliance research note)
- CSA research note on CISA zero trust for OT (PDF)
- Asset Management as a Foundation for Operational Technology (NIST NCCoE)
- NIST SP 1800-23: Energy Sector Asset Management
- New Guidance Calls on OT Operators to Create Continually Updated System Inventory (SecurityWeek)
- Latest CISA cyber guidance urges organizations to inventory OT assets (Federal News Network)
- CISA Publishes OT Asset Inventory Guidance for Critical Infrastructure (Inside Privacy)
