
SCADA Security: Harden HMIs, Historians, Engineering PCs
Udemy ยท English
About this course
- Language
- English
- Category
- Provider
- Udemy
- Data updated
Between the operator and the physical process sit three hosts: the HMI, the historian and the engineering workstation. They are where most plant intrusions land, because they run ordinary operating systems, carry default credentials and hold the one thing an attacker needs most โ a path to the controller. This course is about hardening exactly those hosts, end to end, on a bench you build yourself. You start by standing up a complete plant bench with open-source components: an OpenPLC Runtime v4 soft PLC running a water-cell program, a FUXA HMI bound to it over Modbus TCP, an InfluxDB historian fed by Telegraf every second, and a Grafana trend screen for the business side. Then you measure the default state as it ships โ no HMI login, an unclaimed PLC, an open historian setup and root on the PLC and HMI โ so that every later control has a clear before and after. The method follows NIST SP 800-82 Rev. 3 (with the Rev. 4 draft) and ISA/IEC 62443. Inventory comes first: hosts, versions, listening ports and owners, an SBOM for the HMI image with Syft, vulnerability scans with Grype read the way an OT engineer reads them, and a configuration baseline kept in Git. Then accounts: claiming the PLC at deploy time, turning on FUXA security, role-based access, and scoped historian tokens that are write-only for the collector and read-only for the business. Host hardening is done on the bench, not on slides. The HMI runs as a non-root user with a read-only filesystem and dropped capabilities behind an Nginx TLS proxy, with Lynis audits before and after. AIDE and a signed hash manifest catch unapproved changes to HMI screens and project files. A ClamAV sheep-dip station with a quarantine-and-release log handles removable media. The engineering workstation keeps every PLC program change reviewed and signed in Git, compares the running program with the approved version, and reaches the PLC only during an approved change. The network and its data flows get thโฆ











