Engineering Workstation (EWS) Security: Protecting PLC Access

How do you protect the engineering workstation that loads programs onto PLCs? Windows hardening, project file hash checks, PLC protection levels and access logging.
Technical summary
Technology
Windows hardening, AppLocker/WDAC, BitLocker, SHA-256, PLC access protection
Topic
Holistic security for engineering workstations that program PLCs
Level
Intermediate–advanced
Prerequisites
  • A list of EWSs in the OT asset inventory
  • Knowledge of Windows group policy and local security policy
  • Knowledge of the engineering software for the PLC platforms in use
In this article8 sections

The engineering workstation (EWS) is the computer that can load programs onto a PLC, change parameters and put the controller into STOP mode. This authority makes it one of the most valuable targets on the OT network. In practice, though, in most plants the EWS is a Windows machine in the corner of the control room, with email open and not updated for years. In this guide we treat the EWS as a whole: the usage model, operating system hardening, project file integrity, protection features on the PLC side and access logging.

The value of the EWS to an attacker

An attacker who compromises an HMI generally does what the operator can do. One who compromises the EWS changes the logic of the process. The difference is big. Public analyses have documented that Stuxnet targeted Siemens Step 7 project files and the communication between the engineering software and the PLC, and hid the modified code from the operator. This example shows the three main gains of an attack on the EWS:

  • Program modification: Adding a malicious block to the PLC logic or changing the existing logic.
  • Credential and password information: PLC access passwords saved in project files or the software, network configurations and the addresses of other devices.
  • Attack with a legitimate tool: Because the change is made with the vendor’s own software, it can look like normal engineering activity in network monitoring.

That’s why EWS security isn’t just a Windows hardening job; from an enterprise cybersecurity perspective, it’s the job of protecting the integrity of the PLC program.

Fixed and portable EWS models

Two models are common in plants: fixed stations in the control room or IDMZ, and laptops that maintenance engineers carry onto the floor. Most plants have both. The right question isn’t “which one?” but which control fits each model’s risk.

Criterion Fixed EWS Portable EWS
Network location A defined OT zone, fixed IP Varies with the cell or cabinet it connects to
Access scope Usually multiple lines Limited to the cell it connects to
Main risk Remote compromise, wide impact Loss, connecting to other networks, carrying infection
Critical control Network access restriction, sessions with MFA Disk encryption, a device dedicated to OT
Monitoring Central log collection is easy Logs are collected after synchronization

If you use a portable EWS, dedicate the device to OT work only: it shouldn’t connect to the corporate network or the internet, it should be kept in a locked cabinet when not in use, and a checkout–return record should be kept. A common situation is the same laptop connecting to the corporate Wi-Fi in the office on weekdays and to a PLC cabinet during a weekend shutdown. This device carries one network into the other. A vendor arriving on site with their own laptop is a separate risk item; for this scenario, apply the procedures in the vendor remote access and USB and removable media control articles.

Operating system and application hardening

EWSs are mostly tied to a specific Windows version supported by the engineering software. Make hardening decisions according to the vendor’s compatibility list, and try every change first on a test station built with the same image. The basic steps:

  1. Single-purpose use: No everyday work with an email client, office suite and web browser. Documentation needs are met from a separate computer.
  2. Internet egress blocked: The EWS’s internet egress is blocked on the firewall; software updates come through the controlled transfer path in the IDMZ.
  3. Application allowlist: With AppLocker or Windows Defender Application Control (WDAC), only approved engineering software and tools are allowed to run. Start the allowlist in audit mode and move to enforcement after reviewing the events. If you start with enforcement directly, a driver update gets blocked at the first shutdown and the rule gets removed.
  4. Account structure: Engineers do daily work with a standard user; a separate administrator account is used for installation. Personal accounts are defined instead of a shared “engineer” account. If the EWS is a domain member, local administrator passwords are made different and rotating on each station with Windows LAPS; the migration steps are in the migrating to Windows LAPS article.
  5. Local firewall: Inbound connections are closed; outbound connections are allowed only to PLC subnets and the required license/update server.
  6. Disk encryption: BitLocker is mandatory on portable stations; recovery keys are kept in a separate vault accessible to OT management.
  7. Malware protection: A product and exclusion list whose compatibility the PLC vendor has approved is used.

Licenses fall within this scope too. Engineering software licenses are often tied to the station or a hardware key. Keep in the inventory which license is on which station; don’t let moving licenses during a breakdown lead to uncontrolled copies. Adapting server and client hardening templates to OT can be handled together with system and server security hardening work.

Integrity and version control of PLC project files

Knowing that the program running on the PLC is the same as the approved version is a basic need both in incident response and in daily maintenance. If there’s no answer to “which program is on site?” during a midnight breakdown call, the engineer loads whatever file looks newest. For this we recommend a three-layer approach:

  • Central repository: Approved project files are kept in a single version repository; local copies on EWSs are working copies. The repository keeps the version history and who loaded what and when.
  • Hash records: File hashes are recorded for each approved version and compared periodically.
  • Online comparison: Most engineering software offers a function to compare the program on the PLC with the version in the project. Add this comparison to the planned maintenance cycle.

Hash records don’t need additional software. The PowerShell example below produces the SHA-256 digest of the project folder and compares it with the previous record:

# Create a reference record for the approved version
$project = 'D:\PLC_Projects\Line3'
Get-ChildItem -Path $project -Recurse -File |
  Get-FileHash -Algorithm SHA256 |
  Select-Object Hash, Path |
  Export-Csv 'D:\Reference\Line3_v12.csv' -NoTypeInformation -Encoding UTF8

# Later, compare the current state with the reference
$ref  = Import-Csv 'D:\Reference\Line3_v12.csv'
$current = Get-ChildItem -Path $project -Recurse -File |
  Get-FileHash -Algorithm SHA256 | Select-Object Hash, Path
Compare-Object $ref $current -Property Hash, Path

Every line in the output is an added, deleted or changed file. Keep the reference CSV file not on the EWS itself but in a read-only location. Whoever compromises the station changes the reference too. Engineering software may update some temporary files when a project is opened; on the first runs, note which files change by themselves and exclude them from the comparison.

PLC protection levels and access passwords

However well the EWS is protected, the PLC’s own protection features are the second line of defense. Vendors offer different mechanisms:

  • Access levels: On the Siemens S7-1200 and S7-1500 series, levels such as full access, read access, HMI access and no access are defined through TIA Portal; access above the selected level (for example writing while read access is selected) requires a password. For most PLCs in production, protect write access with a password and connect HMIs only with the level they need.
  • Physical mode key: On Rockwell Logix controllers, program download and online editing can’t be done while the key is in the RUN position. Keeping the key in RUN normally and moving it to REM or PROG only with a change work order is an effective physical control against remote program loading. The key may be seen left in the REM position for long periods.
  • Block and copy protection: Features such as know-how protection protect intellectual property; they don’t replace an integrity check.

Password management is the most neglected part. Typical mistakes: the same password on all PLCs, the password saved in the project file, a password shared with a vendor never being changed. Keep PLC passwords in a password vault, change them after vendor work, and record in the inventory which PLC is at which protection level. Because level names and behaviors can vary by firmware version, base things on the vendor’s current security manual.

Logging EWS access

When a program change is detected, you should be able to answer “who, from which station, when.” For this, logs are collected from two sides:

  • EWS side: Windows sign-in events (4624, 4625), process creation (4688, with command line logging on), PowerShell script block logging (4104) and external device connection events (6416, with “Audit Plug and Play Events” on) are sent to the central log server.
  • Network and PLC side: The OT network monitoring sensor detects program downloads, mode changes and write commands. Some controllers also keep these events in their own diagnostic buffer or change log; verify the feature exists in the product documentation.

When you match the two sources by timestamp, you tell authorized maintenance work apart from unauthorized changes. The prerequisite is the EWS and the sensor getting time from the same NTP source; if clocks have drifted by minutes, matching turns into guesswork. A program download event that happens without a work order should be a high-priority alarm; the setup of these alarms is described in the OT attack detection and anomaly monitoring article.

Checklist

  • All EWSs (fixed, portable, vendor) are in the inventory, recorded with their owner and location
  • No email, web browsing or office work on EWSs; internet egress is blocked
  • The application allowlist is in enforcement mode; exceptions are documented
  • Personal accounts; the administrator account isn’t used for daily work
  • Disk encryption is on for portable EWSs, and a checkout–return record is kept
  • Approved project versions are in the central repository; hash references are in a read-only location
  • Write access on PLCs is password-protected; passwords are in the vault and changed after vendor work
  • Physical mode keys are in RUN normally; changes are tied to a work order
  • EWS and OT network monitoring logs are collected centrally and correlated

To run this list together with the other steps of the OT security program, see the OT/ICS and industrial cybersecurity service page. For general OT security guidance, CISA’s industrial control systems resources are also a reference point.

Frequently asked questions

Does installing antivirus or EDR on the EWS break PLC communication?

It can; some agents conflict with the drivers and communication components of engineering software. Before choosing a product, check the PLC vendor’s compatibility list or approval, install on a test station first and keep real-time scan exclusions limited to the scope the vendor recommends.

Is a PLC protection password enough on its own?

No. The password makes it harder for an unauthorized station to load a program; but it doesn’t prevent a load done from a compromised EWS where the password is saved. Use the password together with EWS hardening, network access restrictions, the physical key position and change detection.

Is using a portable EWS always riskier?

Not always. A portable station carries the risk of connecting to different networks and being lost; but it can also present a narrower attack surface than a single fixed station that reaches all lines. What matters is that the device is dedicated to OT only, has disk encryption, has internet egress blocked and has a usage log.

Can we keep PLC project files on the corporate Git server?

You can. However, because most engineering software stores the project in a binary format, you can’t get line-by-line diffs; version history and hash checks, however, are provided. Place the repository on the OT or IDMZ side, make access role-based and prevent project files from being copied to general shares on the corporate network.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Cybersecurity

Firewall, VPN, endpoint security and threat prevention. We reduce the attack surface and measure and report the risks.

Knowledge Center

Other articles