See every way into the plant, then take them off the board.
An interactive Purdue model of an electric power generation plant. Watch how data crosses from the internet to the turbine on an ordinary day, count the attack paths that two-way firewalls leave open, and trace the routes that real incidents took.
Electric power generation
Three views of the same plant. Switch between them, harden a crossing, pick an incident.
Illustrative reference architecture. Node names are generic; incident summaries are from public reporting.
Three lessons the diagram makes obvious
Every two-way firewall is a path, not a wall
A firewall permits a live session in both directions. Whatever rides that session, from a vendor's stolen VPN credential to a poisoned patch, arrives inside the plant with the same permissions as the legitimate traffic.
Hardware-enforced crossings change the count
Unidirectional gateways, hardware-enforced remote access and protocol-enforced inbound gateways remove the return path. The risk view counts the ways in; each hardened crossing takes one off the board.
The incidents that mattered used the ordinary paths
BlackEnergy rode remote access. Triton walked from IT through the DMZ to the safety system. Colonial Pipeline never touched OT and still stopped the pipeline. The known attacks view traces each one through this plant.
Want this drawn for your plant?
We map your actual crossings, count the paths, and give you a prioritised hardening plan with the business case for each gateway.
Talk to an Architect