Posts

Showing posts with the label Industrial Control Systems

PLCs, HMIs and the Purdue Model: How Industrial Networks Are Structured

Industrial control systems have their own vocabulary, their own network architecture and their own priorities, and applying IT assumptions to them produces advice that gets ignored. This is the structural picture; the exposure problem it creates is covered under exposed OT and IoT . The components A PLC is a ruggedised computer that reads sensors and drives actuators according to a program, on a deterministic cycle measured in milliseconds. It opens valves, starts motors, and controls a physical process. Reliability expectations are measured in years of continuous operation, and its program is the thing that must not be altered. An RTU serves the same role in remote locations — a pipeline valve station, a substation — with telemetry back to a central system. An HMI is the operator's interface: the screen showing process state and allowing setpoint changes. Usually a conventional computer, frequently running an old operating system because the vendor's software requir...

Exposed OT and IoT: What Device Search Engines Keep Finding

Device search engines index every responsive host on the internet, and the most alarming category they consistently return is not web servers — it is industrial control equipment, building systems and unmanaged devices that were never designed to face a network at all. The general technique is covered under internet-wide scanning ; this is about what it finds and why. Why these devices are exposed Rarely by decision. The recurring causes are mundane. A vendor needs remote support, so a device is given a public address or a port is forwarded, and the arrangement outlives the engagement. A site adds a cellular router for convenience and it routes more than intended. An engineer connects a programmable controller to a network for diagnostics and it is never disconnected. A building management system is installed by a contractor who was never told about network policy, because facilities and IT do not share a reporting line. The unifying condition is that nobody owns the device. ...