Wireshark for OT Security: How to Analyze Industrial Network Traffic
Industrial networks generate a continuous stream of communication between PLCs, HMIs, engineering workstations, SCADA systems, servers, switches and other operational technology components. When that communication needs to be investigated, packet analysis can provide evidence that cannot always be obtained from an asset list or network diagram.
Wireshark is one of the most widely used tools for inspecting network traffic at packet level. In an OT environment, it can help an analyst understand which systems are communicating, which protocols are being used, what communication patterns look normal and where unexpected activity deserves further investigation.
The important part is not simply capturing packets. The real value comes from interpreting the traffic in the context of the industrial process.
What Is Wireshark?
Wireshark is a network protocol analyzer that allows analysts to capture and inspect network traffic at packet level.
It can display information about individual packets and help users examine protocols, endpoints, conversations, fields and communication behavior.
For security engineers, this provides a way to move from a high level statement such as “these two systems communicate” to a more detailed understanding of what communication is actually taking place.
Why Packet Analysis Matters in OT
An OT network diagram describes the intended architecture. A packet capture can provide evidence about observed communication.
This difference matters when investigating an industrial environment because documentation can become outdated while network behavior changes over time.
Packet analysis can help answer questions such as:
- Which systems are communicating?
- Which protocols are being used?
- Which endpoints communicate frequently?
- Are there unexpected connections?
- Are systems communicating across intended security boundaries?
- Are new endpoints appearing in the traffic?
- Are there unusual connection attempts?
- Does observed traffic match the expected operational behavior?
These questions can support both security assessment and incident investigation.
OT Security Is Not Just About Packets
A packet capture is evidence, not an explanation.
An unusual connection may be legitimate maintenance activity. A repeated request may be part of normal industrial communication. A protocol that looks insecure from an IT perspective may be required by an older control system.
The analyst therefore needs operational context before deciding whether observed traffic represents a security concern.
What Can Wireshark Help You See?
Depending on the capture point and network architecture, packet analysis can provide visibility into several useful characteristics.
- Source and destination addresses
- Communication frequency
- Network protocols
- Ports and services
- Connection attempts
- Protocol fields
- Packet timing
- Conversation relationships
- Unexpected endpoints
- Changes in communication patterns
The amount of information available depends heavily on where the traffic was captured and what visibility exists within the network.
Start With the Capture Point
Before analyzing a PCAP file, determine where the traffic was captured.
This is one of the most important pieces of context in network analysis.
A capture taken near a PLC may show a very different communication pattern from a capture taken at an industrial firewall or an enterprise to OT boundary.
The capture point affects what the analyst can and cannot conclude.
| Capture Location | Potential Visibility |
|---|---|
| Control network | Communication between control system components. |
| Engineering network | Engineering workstation and maintenance related traffic. |
| Industrial DMZ | Traffic crossing important boundaries. |
| Network perimeter | Selected external and internal communication. |
| SPAN or mirror port | Traffic visible to the configured monitoring point. |
A packet capture should therefore never be presented as a complete representation of the entire OT network unless the capture architecture actually supports that conclusion.
Build a Baseline Before Looking for Anomalies
One of the weakest approaches to packet analysis is searching for anything that looks unusual without first understanding normal communication.
Industrial systems often communicate repeatedly and predictably. A PLC may communicate with a particular HMI or controller according to the requirements of the process. Engineering workstations may have specific maintenance relationships with control equipment.
A useful assessment therefore begins by asking what normal traffic looks like.
- Which systems communicate regularly?
- Which protocols are expected?
- Which destinations are expected?
- How frequently does communication occur?
- Which systems initiate connections?
- Which systems normally receive connections?
Once a baseline exists, unexpected communication becomes easier to identify and investigate.
Identify the Main Communication Relationships
One of the first useful tasks in a PCAP investigation is understanding which endpoints communicate with each other.
Instead of examining individual packets immediately, start by looking at conversations and communication relationships.
A simplified relationship might look like:
HMI → PLC
Normal control related communication
Engineering workstation → PLC
Potential maintenance or programming activity
SCADA server → PLC
Supervisory communication
OT system → unknown external destination
Requires investigation
The last example is not automatically malicious. It is simply a relationship that needs an explanation.
Examine Industrial Protocols
Industrial environments can use protocols designed specifically for control and automation systems. The exact protocols depend on the industry, equipment vendors and architecture.
When Wireshark recognizes a protocol, an analyst can often examine additional protocol fields rather than treating the traffic as an anonymous stream of packets.
This can provide useful context about the type of communication taking place.
However, protocol recognition should not be confused with understanding the industrial process. A protocol tells you how systems communicate. The engineer still needs to understand why that communication exists.
Look for Unexpected Endpoints
An unexpected endpoint can be one of the most useful findings in an OT traffic review.
For example, a capture may show a system communicating with an address that is not present in the documented architecture or asset inventory.
The correct response is investigation rather than immediate classification.
- Is the endpoint part of the organization?
- Is it a legitimate vendor system?
- Is it a recently added device?
- Is it part of an approved remote access system?
- Is it an Internet service?
- Is the communication required by the process?
- Was the communication expected during the capture period?
This approach prevents legitimate operational activity from being incorrectly reported as an incident.
Investigate New or Unusual Communication
A change in communication behavior can be more meaningful than a single unusual packet.
Examples that may deserve investigation include a previously unseen endpoint, a new communication path, unusual connection frequency, unexpected protocol usage or traffic leaving an OT environment for an unfamiliar destination.
These observations should be compared with maintenance schedules, engineering activity, architecture documentation and known system behavior before assigning a security conclusion.
Use Packet Timing Carefully
Timing can provide useful context during network analysis.
Regular communication patterns may reflect normal control activity. Sudden bursts, repeated connection attempts or unexpected timing changes may deserve additional investigation.
But timing alone is rarely enough to establish malicious behavior. Network maintenance, system restarts, process changes and other operational events can also change traffic patterns.
Examine Cleartext and Sensitive Traffic
Some industrial environments contain legacy protocols that were not designed around modern confidentiality and authentication requirements.
Where traffic is visible in cleartext, packet analysis may reveal information about the systems communicating and the nature of the exchange.
The security significance depends on the protocol, network position, access controls, segmentation and operational role of the affected systems.
The correct finding is therefore not simply “cleartext traffic exists.” A stronger assessment explains where the traffic exists, who can observe it, what information is exposed and whether compensating controls reduce the practical risk.
Use Wireshark to Validate Other Evidence
Packet analysis becomes more valuable when it is compared with other sources of information.
| Evidence | What It Tells You |
|---|---|
| Asset inventory | What the organization believes exists. |
| Network diagram | How the environment is intended to be structured. |
| Firewall configuration | Which communication paths are permitted. |
| Wireshark PCAP | What traffic was observed at the capture point. |
| Maintenance records | What operational activity was expected. |
| Security logs | What systems recorded about relevant events. |
When these sources disagree, the discrepancy itself can become an investigation point.
What Wireshark Cannot Tell You
Packet analysis is powerful, but it has clear limitations.
- A PCAP does not automatically represent the entire OT network.
- A captured packet does not automatically indicate malicious activity.
- An unknown endpoint does not automatically represent an attacker.
- A vulnerable protocol does not automatically mean the system is compromised.
- Absence of suspicious traffic does not prove that an environment is secure.
- Encrypted traffic may limit what can be determined from packet contents.
A professional report should state these limitations clearly.
How to Analyze an OT PCAP Step by Step
A structured workflow makes packet analysis easier to reproduce and explain.
- Confirm the source and capture location.
- Record the capture date and operational context.
- Identify the visible endpoints.
- Review conversations between major systems.
- Identify the protocols in use.
- Establish expected communication relationships.
- Look for unknown or unexpected endpoints.
- Investigate unusual communication patterns.
- Compare findings against network documentation.
- Compare findings against maintenance and operational records.
- Validate important observations using other evidence.
- Document findings, limitations and recommended actions.
This workflow keeps the investigation evidence driven and reduces the risk of drawing conclusions from isolated packets.
What an OT PCAP Security Review Should Deliver
A professional PCAP review should produce findings that engineers and security teams can understand and act upon.
- Capture scope and location
- Visible endpoints
- Observed communication relationships
- Protocol summary
- Unexpected communication
- Potentially exposed sensitive traffic
- Changes from an established baseline
- Relevant security observations
- Evidence supporting each important finding
- Assessment limitations
- Recommended next steps
The report should distinguish between an observed fact, an interpretation and a confirmed security finding.
When Wireshark Is Most Useful in OT Security
Wireshark is particularly useful when an organization needs to understand actual network communication rather than relying entirely on documentation.
It can support OT security assessments, network troubleshooting, incident investigation, protocol analysis and validation of expected communication flows.
CISA also identifies network traffic capture and analysis as useful capabilities for industrial control system incident response and describes tools that can isolate traffic by applications, conversations, domains, endpoints and protocols.
Why Packet Analysis Should Be Combined With OT Engineering Knowledge
OT security cannot be separated completely from the industrial process.
An analyst may identify a communication pattern that looks unusual from a network perspective. An automation engineer may recognize it as a normal part of a production sequence, maintenance activity or control strategy.
The strongest assessment combines cybersecurity evidence with engineering context.
This is particularly important when analyzing traffic involving PLCs, HMIs, SCADA systems and other components that directly support physical processes.
Final Perspective
Wireshark can turn an OT network from an abstract architecture diagram into observable communication evidence.
Its greatest value is not simply seeing packets. It is understanding relationships between systems, establishing normal communication, identifying unexpected behavior and validating whether the observed network activity matches the intended industrial architecture.
A strong OT packet analysis process therefore follows a simple principle: capture carefully, establish context, analyze systematically, validate findings and explain the operational significance.
For organizations that need deeper visibility into their industrial network, a structured PCAP review can provide useful evidence without requiring broad active scanning of production systems.
Need an Independent OT Network Traffic Review?
Cautivra provides focused OT network traffic and PCAP security reviews for organizations that need help understanding industrial communication patterns, investigating unexpected traffic or validating network security observations.
The review can be based on authorized packet captures and supporting network documentation, with findings presented in a practical format for engineering and security teams.
Request an OT PCAP Security Review
Sources and Further Reading
- Wireshark official documentation and resources
- NIST SP 800-82 Rev. 3, Guide to Operational Technology Security
- CISA Industrial Control Systems Cybersecurity Initiative resources
- CISA ICS monitoring and incident response guidance
