How a Regional Utility Gained Full Visibility Across Its Legacy SCADA Network
A regional electric utility serving 2.4 million customers across the southeastern United States
Challenge
Aging SCADA infrastructure spanning 15+ substations with zero network visibility, multiple unpatched RTUs, and growing regulatory pressure under NERC CIP.
Solution
FlintX passive deployment across OT network segments — deep packet inspection of DNP3 and IEC 61850 traffic, automated asset discovery, and anomaly detection without disrupting operations.
Results
340+ previously unknown assets discovered, mean-time-to-detect reduced from weeks to under 4 hours, full NERC CIP audit readiness achieved within 90 days.
When you have been running substations the same way for two decades, the idea that someone could be sitting inside your network — watching, learning, waiting — does not feel real. It feels theoretical. Something that happens to other utilities, in other countries, on the news.
That was the mindset at a regional electric utility in the southeastern United States. They served 2.4 million customers. They had 15 substations, a mix of legacy RTUs from three different vendors, and a SCADA system that had been expanded piecemeal over 18 years. It worked. Mostly.
What they did not have was any way to see what was actually happening on their OT network.
The Problem Nobody Wanted to Talk About
The utility's IT security team had built a reasonably mature program on the enterprise side. Firewalls, EDR, a SIEM that somebody actually looked at. But the OT network was a different world. Different protocols. Different priorities. Different people.
The substation engineers had a saying: "If it is not broken, do not touch it." And for years, that philosophy kept the lights on. But it also meant that nobody knew how many devices were on the OT network. Nobody knew which RTUs were running firmware from 2011. Nobody knew whether the contractor who set up a cellular modem at a remote substation in 2019 had ever changed the default password.
The honest answer to "What is on our OT network?" was: "We are not entirely sure."
Then came the NERC CIP audit notice. And suddenly, "not entirely sure" was not going to cut it.
Why Traditional IT Tools Were Not the Answer
The first instinct was to extend the existing IT security stack into the OT environment. Run vulnerability scans. Deploy agents. Pipe everything into the SIEM.
The substation engineers shut that down immediately — and they were right to. Active scanning on a DNP3 network is not the same as scanning an office LAN. A poorly timed scan can cause an RTU to fault. In a substation, a faulted RTU can mean a protection relay that does not trip when it should. That is not a theoretical risk. It is a safety issue.
They needed something that could watch without touching. Something that understood the difference between a legitimate DNP3 read request and an anomalous write command. Something that could map the network without sending a single packet.
Deploying FlintX: Week One
FlintX was deployed passively — SPAN ports at each substation's network switch, mirroring traffic to a local sensor. No inline devices. No agents. No changes to the SCADA architecture.
Within the first 72 hours, the platform had identified 340 devices on the OT network. The utility's asset inventory had listed 187.
The delta was not subtle. Among the 153 previously unknown assets were:
- 14 unmanaged Ethernet switches that had been installed during various expansion projects
- 8 engineering workstations with direct connections to both the OT and corporate networks
- 3 cellular modems providing remote access to substation equipment — one with default credentials still active
- A Windows XP machine running HMI software that had not received a patch since 2014
Nobody had put these devices there maliciously. They had accumulated over years of expansion, vendor installations, and operational shortcuts. But each one represented an unmonitored entry point into a network that controlled power distribution for 2.4 million people.
Understanding What Normal Looks Like
Asset discovery was the first step. The second — and arguably more important — step was understanding what normal OT traffic patterns looked like.
FlintX's protocol-aware engine began building behavioral baselines for every device on the network. It learned which RTUs communicated with which master stations. It learned the typical polling intervals for DNP3 requests. It learned that IEC 61850 GOOSE messages between protection relays followed predictable timing patterns.
Two weeks in, the platform flagged its first anomaly: an engineering workstation at a remote substation was initiating DNP3 write commands outside of any scheduled maintenance window. Investigation revealed that a contractor had left a diagnostic session open after a routine firmware update. No malice — just human error. But exactly the kind of activity that, if left undetected, could mask a genuine intrusion.
From Blind Spots to Audit Readiness
The NERC CIP audit required the utility to demonstrate, among other things, that they had a complete and accurate inventory of all Cyber Assets and BES Cyber Systems, that they could detect unauthorized access attempts, and that they had documented network topology for their Electronic Security Perimeters.
Before FlintX, preparing for that audit would have taken months of manual effort — engineers walking substations with clipboards, tracing cables, comparing serial numbers against spreadsheets that may or may not have been updated since the last audit.
With FlintX, the utility generated a complete, verified asset inventory in under a week. Network topology maps were auto-generated from observed traffic flows. Anomaly detection provided continuous evidence of monitoring capability.
They passed the audit. Not by scrambling to assemble documentation, but by pointing to a system that had been doing the work continuously since deployment.
What Changed — and What Did Not
The substation engineers still run their equipment the same way. Nobody asked them to change their workflows or learn a new tool. The SCADA system was not modified. The RTUs were not updated (though the utility did start a firmware lifecycle program based on FlintX's vulnerability findings).
What changed was awareness. The utility's security team now knows what is on their OT network — not what should be on it, but what actually is. They know when something new appears. They know when communication patterns deviate from baseline. They know within hours, not weeks.
Mean-time-to-detect went from an estimated 14+ days to under 4 hours. Not because the threats got easier to find, but because someone was finally looking.
"We went from hoping nothing bad was happening on our OT network to actually knowing what was happening. That sounds simple, but for a utility our size, it was transformational." — Director of Cybersecurity