IT to OT, level by level
The Purdue model from the enterprise down to the field. Open a level to see what I do there and the tools I publish for it.
Levels 4 and 5: Enterprise IT identity, campus, cloud
- Cisco ISE design, upgrades and rescue; 802.1X EAP-TLS, TrustSec, PKI
- SD-Access and Catalyst Center; Secure Firewall; SD-WAN and BGP to the cloud
Conduit: firewall and jump host. Nothing from IT reaches operations directly.
Level 3.5: OT DMZ the only way between IT and OT
- Jump hosts, patch relay, historian replica
- Vendor remote access through a jump host with MFA
- Every conduit modelled and checked against real traffic
Conduit: firewall and monitoring, only the services the conduit allows.
Level 3: Operations control center
- Security groups across train control, SCADA, fire alarm, elevators, fare collection and CCTV, mapped to IEC 62443
- NDR sensors and flow analytics, tuned until the alarms mean something
Security groups and closed-mode MAB between operations and the stations.
Level 2: Supervisory stations and HMIs
- Closed-mode MAB for devices that cannot run 802.1X, one site at a time
- AAA hardening on thousands of switches, checked before it can lock anyone out
- Discovery of devices nobody had on a list
One way out through a data diode. Nothing comes back in.
Levels 1 and 0: Control and field train control, PLCs, signals
- Safety systems stay agentless
- Visibility through passive TAPs cut in during one overnight window, no service disruption