These systems perform different functions and have different relationships with the production process.
That makes OT visibility a broader requirement than maintaining an asset list. Organizations need to understand the systems operating across the environment, how those systems interact, who or what can reach them, and the role they perform in manufacturing.
Asset discovery and communication-flow mapping are foundational capabilities for understanding connected manufacturing environments. (Source: Technology Record, Apr 2026)
An inventory tells you what exists. OT visibility shows how the environment fits together.
The Components of the Manufacturing OT Attack Surface
Manufacturing OT environments are made up of several technology layers. Each layer supports a different part of production and interacts with other systems.
Understanding these layers establishes the environment that needs to be mapped.
Control Layer: PLCs, DCS and Field Devices
Programmable Logic Controllers (PLCs), Distributed Control Systems (DCS), and field devices sit close to the physical manufacturing process.
PLCs execute control logic, while DCS platforms coordinate industrial processes. Sensors, actuators, drives, valves, and other field devices interact with physical equipment.
A simplified relationship is:
Field Devices → PLC/DCS → Manufacturing Process
The control layer provides the foundation for understanding what directly interacts with the physical process. Visibility should identify the systems connected to these controllers, the workstations used to configure them, and the applications that depend on their data.
Supervisory Layer: SCADA and HMI
Supervisory Control and Data Acquisition (SCADA) systems and Human-Machine Interfaces (HMI) provide monitoring and interaction above the direct control layer.
They display equipment states, alarms, and process information to operators while interacting with underlying industrial systems.
The relationship can be represented as:
PLC/DCS → SCADA/HMI → Operator
SCADA and HMI need to be mapped with the controllers, applications, and users that interact with them.
The useful information is the relationship between the supervisory systems and the systems around them.
Engineering Layer: Engineering Workstations
Engineering workstations support controller programming, industrial application configuration, maintenance, troubleshooting, and diagnostics.
Their position within the environment depends on the systems they can access and configure.
Organizations need visibility into:
- Which engineering workstations exist
- Which industrial systems they interact with
- Which controllers they can configure
- Which applications they host
- Who uses them and for what purpose
The workstation’s connections and configuration capabilities provide important information about its role within the OT environment.
Manufacturing and Data Layer: MES and Historians
Manufacturing Execution Systems (MES) and historians sit above direct machine control while remaining closely connected to production environments.
MES platforms support manufacturing workflows and production activities. Historians collect and retain operational information used for monitoring, analysis and process understanding.
Relevant visibility information includes:
- Where operational data originates
- Which systems exchange information with MES
- Which applications consume historian data
- Which users and systems access these platforms
- How these systems relate to the production environment
The architecture needs to reflect how each plant actually operates.
Connectivity Layer: IT/OT and External Connections
Connectivity can extend beyond the production floor.
Manufacturing OT environments can interact with enterprise systems, cloud platforms, remote maintenance services, suppliers, and other external technologies.
These connections add systems, users, and services to the environment that need to be understood.
Organizations need visibility into:
- Which IT systems connect with OT
- Which external systems connect with OT
- Which users or services can access those connections
- Which systems can be reached through them
- Which connections are temporary, permanent, or unknown
Connectivity needs to be included in the OT environment map because it affects the systems and users that can interact with production technology.
Where Asset Inventory Falls Short
An asset inventory provides a record of known equipment and systems. It does not necessarily contain the information needed to understand how those assets operate within a wider environment.
For example, an inventory can identify a PLC without documenting:
- Its connected SCADA system
- The engineering workstation used to configure it
- Applications consuming its data
- Users or services that can reach it
- The production function it supports
The same issue applies to other OT systems.
A SCADA server can be listed without its controller relationships. An engineering workstation can be recorded without its configuration access. A historian can appear in the inventory without the systems that supply or consume its data.
The missing information sits in the relationships surrounding the asset.
Asset Inventory vs. OT Attack-Surface Visibility
| Asset inventory | OT visibility |
| PLCs and controllers | Systems communicating with them |
| SCADA and HMI | Controllers, applications, and users interacting with them |
| Engineering workstations | Industrial systems they configure or access |
| MES and historians | Connected systems and data relationships |
| Remote connections | Systems and environments reachable through them |
| OT assets | Operational role and surrounding context |
A complete OT view requires information about the assets and the environment around them.
The Gaps in a Manufacturing OT Environment
Four visibility gaps commonly appear around OT assets: assets, relationships, access and operational context.
Each represents a different visibility requirement.
Asset Visibility Gaps
Manufacturing plants can contain long-lived industrial systems alongside newer equipment, applications and connected technologies.
An organization needs to account for the OT assets operating across its facilities and understand where the asset picture is incomplete.
Relevant information includes:
- Asset identity
- Asset type
- Location
- Function
- Plant or production area
- Current status
Asset visibility defines the scope of the environment to be understood.
Relationship Visibility Gaps
Relationships describe how systems interact.
A manufacturing environment can contain controllers, supervisory systems, engineering workstations, applications and data platforms that depend on one another.
Useful relationship information includes:
- System-to-system communication
- Controller and supervisory relationships
- Engineering workstation connections
- Application dependencies
- IT/OT connections
- Data flows between manufacturing systems
Without this information, teams can see individual assets without understanding the architecture connecting them.
Relationship visibility provides the structure between individual OT assets.
Access Visibility Gaps
Access can involve operators, engineers, administrators, equipment manufacturers, maintenance providers and other external parties.
System-to-system connections also create access relationships.
Organizations need to establish:
- Who has access
- Which systems they can reach
- Which assets they can interact with
- What type of access exists
- Which services or applications have access
- Where access information remains unclear
Access visibility identifies the people, systems and services that can interact with OT assets.
Operational Context Gaps
Technical information alone does not explain how an asset supports manufacturing.
Two PLCs can have similar technical characteristics while performing different production functions. Engineering workstations can also support different processes and applications.
Operational context usually comprises:
- Production function
- Process role
- System dependency
- Plant or production area
- Relationship to other OT systems
Operational context helps teams understand the significance of an asset within manufacturing operations.
Visibility gaps become harder to identify when asset, relationship, access
and operational information is maintained across disconnected views.
How the OT Attack Surface Changes Around Existing Assets
Manufacturing environments change as equipment is connected, applications are introduced, configurations are modified, and access relationships evolve.
The asset itself can remain in service while its surrounding environment changes.
Some examples are:
- A new engineering workstation connecting to an existing PLC
- An additional application exchanging data with a SCADA server
- A remote maintenance connection reaching an existing OT system
- A historian supplying data to another platform
- An MES interface connecting with another manufacturing application
These changes can alter the relationships and access associated with existing assets.
What Can Change Around an Existing OT Asset?
| Existing asset | Relationship that can change |
| PLC | New engineering workstation or connected application |
| SCADA server | New controller, application or user connection |
| Engineering workstation | New user, tool or remote connection |
| Historian | New data source or data consumer |
| MES | New production, enterprise or application interface |
OT visibility therefore needs to account for changes around existing assets, not just newly deployed assets.
What Recent Cases Reveal About the OT Attack Surface
Recent manufacturing cases illustrate two different visibility challenges: understanding connections across the OT environment and accounting for technologies surrounding production systems.
IT/OT Connections
Dark Reading’s coverage of Asahi discusses manufacturing environments where corporate IT and OT are increasingly connected. The reporting also addresses visibility across access points, users and connected technologies. (Source: Dark Reading, Nov 2025)
For OT visibility, the relevant lesson is the need to understand the connections between environments.
Organizations need to identify the systems communicating across IT and OT and the users or services that can reach those systems.
The IT/OT boundary needs to be represented as part of the environment map.
Beyond Plant-Floor Assets
An Opportimes report describes manufacturing environments involving remote access, cloud integration, AI analytics and vendor connectivity alongside PLCs, CNC systems and SCADA. (Source: Opportimes, Feb 2026)
The visibility implication is the range of technologies surrounding production systems.
Understanding PLCs and SCADA alone does not describe all of the systems connected to manufacturing operations. Remote services, cloud technologies and vendor relationships also form part of the environment that organizations need to account for.
The OT environment can extend beyond the immediate production floor.
Recent manufacturing cases show why OT visibility needs to include both the connections
between environments and the technologies surrounding production systems.
A practical test is whether security, engineering, operations, and IT can work from a consistent view of the manufacturing environment.
Security may maintain the asset inventory. Engineering may hold controller dependencies. Operations may understand production relationships. IT may manage enterprise and external connections.
Those views need to be connected.
A useful OT visibility program should allow teams to answer the same questions about assets, relationships, access, and operational context.
Five Questions Every Manufacturing Organization Should Be Able to Answer
- What OT and OT-connected assets exist across each plant?
- How do those assets communicate with one another?
- Which users, systems, and third parties can reach them?
- What manufacturing function does each asset support?
- Where are asset relationships or access details still uncertain?
These questions provide a practical test of the organization’s current visibility.
If teams cannot answer them consistently, parts of the manufacturing OT environment remain unclear.
Know the Environment Before Securing It
Manufacturing OT visibility requires more than identifying equipment.
Organizations need information about the systems supporting production, the relationships connecting them, the access surrounding them, and the role each system performs.
That information provides the foundation for understanding the actual manufacturing OT environment and determining where visibility remains incomplete.
The first step is to establish a reliable view of the environment.
How Prudent Strengthens Manufacturing OT Visibility
Prudent helps manufacturing organizations develop visibility across their OT environments by bringing together assets, relationships, access and operational context.
The approach covers controllers, supervisory systems, engineering workstations, manufacturing applications, historians and surrounding IT or external connections.
This provides organizations with a clearer basis for identifying:
- Known OT assets
- System relationships
- Access relationships
- Operational roles
- Areas where environment information remains incomplete
The focus is on strengthening visibility across the manufacturing OT environment before organizations determine how to secure it.
Get Visibility Into Your Manufacturing OT Environment
Your OT environment extends beyond PLCs and SCADA.
Effective visibility requires an understanding of what exists, how systems connect, who or what can reach them, and what role they perform in manufacturing operations.
Prudent helps manufacturing organizations strengthen visibility across connected OT environments.
