Passive OT / ICS network visibility

See exactly what's talking to your PLCs — before someone else finds out first.

OT Analyzer reads a network capture from your plant floor and tells you what's really on it: every asset, every industrial protocol conversation, and every security finding worth a plant manager's attention — with nothing installed on the OT network itself.

topology.json — SCADA-40.1 neighborhood from a real capture
172.24.55.26 HMI 172.24.55.1 SCADA SERVER 10.194.170.107 PLC / RTU 10.194.170.131 PLC / RTU 172.17.81.151 FIELD DEVICE EtherNet/IP · 2 CIP sessions
Real subgraph pulled from an actual topology export — one SCADA server and four of its nearest neighbors. IPs are anonymized for this sample; the roles, protocols, and relationships are exactly as captured.
30+
Security rules
10
Protocols parsed
5
Stage pipeline
100%
Offline output
Protocol coverage Modbus/TCP EtherNet/IP · CIP DNP3 ARP DNS SNMP TLS HTTP FTP SMB
Why it's different

Built for how OT networks actually behave — not adapted from IT security.

Most tools in this space either need agents on hardware you can't touch, or bolt ICS support onto an IT product. OT Analyzer starts from a capture file and a rules engine designed around real plant-floor traffic.

Fully passive, no agents

Point it at a packet capture from a SPAN or mirror port you already have — nothing gets installed on a PLC, HMI, or engineering workstation, and nothing touches the OT network live.

Deterministic, testable rules engine

Every asset and flow is evaluated against fixed, explainable logic — the same capture always produces the same findings. No black-box scoring, no opaque model deciding what's a risk.

Engineered against real capture artifacts

Mirrored traffic misbehaves — RSPAN re-tags frames with its own VLAN ID as they cross the network. OT Analyzer checks each VLAN's device subnets for that pattern automatically, instead of reporting a false segmentation problem.

Deliverables that don't need the cloud

A client-ready PDF report and a self-contained, interactive topology map — zero external scripts, zero CDN calls. Opens offline, which matters when the environment you're reporting on is air-gapped.

What it does

From a capture file to a finished security assessment.

Every stage below runs from the same pipeline — asset discovery, protocol parsing, classification, detection, and reporting stay in sync because they're the same run, not separate tools stitched together.

01

Asset discovery & classification

Automatically identifies PLCs, HMIs, SCADA servers, and engineering workstations from observed traffic — no manual asset inventory to keep up to date.

02

Deep protocol parsing

Purpose-built parsers for Modbus, EtherNet/IP (CIP), and DNP3 — plus the surrounding IT protocols (ARP, DNS, SNMP, TLS, HTTP, FTP, SMB) that show up on the same segments.

03

30+ security rules

Checks for insecure legacy protocols reaching control assets, cleartext credentials, unexpected control masters, weak segmentation, default community strings, and more.

04

Automatic topology mapping

Builds the network diagram from the traffic itself — segments, assets, and the relationships between them — so the map reflects what's actually on the wire.

05

Actionable findings, not raw alerts

Every finding ships with the evidence behind it and a concrete remediation step — written for someone running a plant, not sifting through a SOC queue.

06

Client-ready output

A formatted PDF report and an offline interactive topology view are generated on every run — ready to hand to a plant manager or attach to an audit.

Real output, not a mockup

This is an actual topology view from a real capture.

108 assets across 4 network segments, mapped automatically from a single packet capture — no manual diagramming, no live access to the network it describes. Pan, zoom, and click into it below.

108
Assets identified
45
PLCs / RTUs
4
Network segments
200
Mapped relationships
topology.html — generated offline, fully self-contained Open full sample ↗
How it works

One pipeline, five stages.

Capture your traffic once. Everything downstream — assets, findings, diagrams, and the report — comes from that same run.

STAGE 1

Capture

Bring a .pcap from an existing SPAN/mirror port. No new hardware, no live traffic injection.

STAGE 2

Parse

Protocol-aware parsers reconstruct flows, device identities, and industrial-protocol activity.

STAGE 3

Classify

Assets are assigned roles — PLC, HMI, SCADA server, workstation — from how they actually behave.

STAGE 4

Detect

The rules engine evaluates every asset and flow against 30+ OT-specific security checks.

STAGE 5

Report

A PDF report and an offline interactive topology map are written out automatically.

Sample findings

What a run actually surfaces.

Every finding is tied to real evidence — a specific flow, protocol, and pair of assets — not a generic vulnerability score.

OT-003 Medium
Workstation communicating directly with a PLC
Engineering workstation ENG-WS-04 reached PLC-104 directly, bypassing SCADA-SRV.
Modbus/TCP
OT-004 High
Insecure Telnet traffic to a PLC
Unencrypted management traffic reached a control asset — credentials and commands travel in the clear.
Telnet
OT-006 High
Cleartext credentials observed in FTP traffic
An FTP PASS command was captured on the wire. Credential values are never included in the report itself.
FTP
OT-007 High
Remote administration (RDP) exposed to a PLC
A remote-desktop session reached a control-system asset that shouldn't be directly RDP-accessible.
RDP
OT-011 Medium
SMB traffic directed at a PLC
File-sharing traffic reached a device classified as a PLC — worth confirming this is expected engineering activity.
SMB
OT-014 Low
External NTP communication observed
An internal OT asset is time-syncing against a server outside the network.
NTP
Get a demo

See it run against a capture from your own environment.

We'll walk through a live run — asset discovery, the rules engine, and the topology output — and talk through where it fits alongside what you're already running.

30-minute walkthrough, no obligation.
Bring your own capture, or we'll use a sample one.
We'll size a pilot for your site if it's a fit.
We'll only use this to schedule your demo.

Request received

Thanks — someone from OT Secure Systems will reach out within one business day to schedule your walkthrough.