Join our Newsletter — 33% off our NHI Course
Home› Guides› Engineering Workstation Security Guide: Hardening the Machines That…
Guide OT & IoT Security

Engineering Workstation Security Guide: Hardening the Machines That Program Your Controllers

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

The engineering workstation (EWS) is the one machine in a plant that is trusted to change what controllers do, so an attacker who owns it can alter the physical process using the plant's own tools. Stuxnet infected Siemens STEP 7 project files and the library engineering software used to talk to PLCs; Triton ran on a safety system engineering station disguised as the vendor's log viewer; INCONTROLLER shipped a driver exploit aimed at engineering workstations and HMIs. Yet EWS are often ordinary Windows laptops that also travel, browse and receive email. This guide covers what an EWS holds, how it is attacked, a build standard, credential and project file protection, portable and vendor laptops, remote engineering, monitoring and metrics. It is for OT engineers, integrators and security teams. The PLC Security Guide covers controller-side protections such as the key switch; this page covers the workstation itself.

Key takeaways

  • The EWS is a Tier 0 OT asset. It holds programming software, project files, controller passwords, communication drivers and often licences; treat it like a domain controller, not a desktop.
  • Project files are an attack vector. ATT&CK for ICS lists Project File Infection (T0873); Stuxnet copied itself into STEP 7 projects so it ran when a project was opened, and vendor CVEs show malicious project files can run code on controllers.
  • Single purpose beats feature lists. A dedicated build with no email, no web browsing, application allowlisting and controlled USB removes most initial access paths before any security product is added.
  • Portable and vendor laptops are the weakest EWS. Treat them as transient cyber assets: scanned, time-limited, never dual-homed and never connected straight to a control network.
  • Prove logic integrity independently. Keep approved project versions with hashes in a controlled repository and compare controller contents against them, because a compromised EWS can hide what it downloaded.

What an engineering workstation holds and why attackers want it

Asset on the EWSWhy it mattersProtection
Programming and configuration software (for example STEP 7 or TIA Portal, Studio 5000, Control Expert, safety system tools)Can download, modify and upload controller logic and firmwareAllowlisting, version control of installers, restricted users
Project filesThe design of the process, including logic, tags, alarms and safety settings; can be infected or stolenRepository with access control, hashing and change records
Controller and project passwordsOften cached or saved in the software or in text filesVault, no saved passwords, unique per controller
Communication drivers and librariesStuxnet replaced the DLL responsible for PLC communication (s7otbxdx.dll) so it could intercept and hide logic changesIntegrity monitoring of vendor binaries, signed driver enforcement
Licences and donglesLost licences block recoveryInventory and backup of licence files
Network positionAllowed to reach controllers on engineering portsDedicated engineering zone; firewall rules naming EWS addresses only
Secure client identityWhere protocols such as CIP Security are in use, the EWS holds a trusted client identityCertificate lifecycle and protection of the private key

How EWS are attacked

  • Through the project: Stuxnet hooked the APIs that open project files and infected STEP 7 projects (T0873.001 Siemens Project File Format). CVE-2022-45788, published by Schneider Electric, describes code execution on Modicon controllers when a malicious project file is loaded.
  • Through the session: CVE-2024-8935 describes a man-in-the-middle position between the controller and the engineering workstation while a session is being established, and CVE-2024-8933 describes retrieval of a password hash while a user uploads or downloads a project. Network position next to the EWS is valuable to an attacker.
  • Through trust in the software: CVE-2021-22681 showed that the key Logix controllers used to verify genuine engineering software could be bypassed, letting an unauthenticated attacker authenticate as if they were the EWS. CISA added it to the Known Exploited Vulnerabilities Catalog in March 2026.
  • Through the operating system: INCONTROLLER included a tool exploiting CVE-2020-15368 in the AsrDrv103.sys driver, relevant to ASRock motherboards used in HMIs and engineering workstations, alongside a reconnaissance and command and control backdoor.
  • Through disguise: Triton was configured to masquerade as trilog.exe, the Triconex software for analysing safety system logs, and used the TriStation protocol on UDP 1502 to download programs to the safety controller.
  • Through people and media: spearphishing (T0865), removable media (T0847) and transient laptops (T0864 Transient Cyber Asset) are the usual ways in.

Build standard for a fixed engineering workstation

  1. Dedicated hardware: one role per machine. No email client, no general web browser, no office productivity beyond what engineering needs. Remove or disable wireless adapters, Bluetooth and unused network interfaces.
  2. Vendor-supported OS image: build from the version the automation vendor validates, apply security patches as the vendor approves them, and record the image hash as a golden image. See the OT Backup, Recovery and Golden Image Guide.
  3. OT domain, not corporate: join the EWS to an OT domain or keep it standalone with local accounts managed centrally; never to the corporate domain. NIST SP 800-82 Rev. 3 recommends that OT accounts do not rely on corporate user accounts.
  4. No standing local admin: engineers log on with standard accounts and elevate only for installation; manage local administrator passwords with a rotation tool. See the Local Administrator Password Solution (LAPS) Guide.
  5. Application allowlisting: allow the vendor's engineering tools, communication drivers and approved utilities by publisher and path, and block everything else, including scripting hosts where the tools do not need them. Start in audit mode for several weeks of normal engineering. See the Application Allowlisting Guide.
  6. Driver control: enforce signed drivers and block known vulnerable drivers, given INCONTROLLER's use of a vulnerable motherboard driver. See the Bring Your Own Vulnerable Driver and EDR Killers Guide.
  7. Removable media control: allow only registered, encrypted USB devices, and route other media through a scanning kiosk. See the Removable Media and USB Control Guide.
  8. Endpoint protection validated by the vendor: install EDR or anti-malware versions the automation vendor supports, with exclusions kept to the minimum the vendor documents.
  9. Local firewall: allow outbound engineering protocols only to the controller zones this EWS serves, and inbound only from management and backup systems.
  10. Disk encryption and physical security: encrypt disks, set firmware passwords and keep fixed EWS in locked rooms or cabinets.

Testing and rollback

Validate every hardening change on a spare EWS against a test controller or simulator: open, compile, download and go online with each project type the station supports. Keep the previous golden image so the station can be restored within an hour if a change breaks engineering during an outage.

Protecting credentials and project files

  • Controller passwords: set unique passwords per controller or per area where the platform supports them, store them in a vault and check them out for the task. Do not save them in the engineering software or in spreadsheets on the EWS.
  • Named engineering accounts: shared "engineer" logins make every change anonymous. Use named accounts on the EWS and in any engineering software user management, separated from operator roles.
  • Project repository: keep approved project versions in a version-controlled repository on an OT server, with read access for engineers and write access only through a change process. Record a hash for each approved version. See the OT and ICS Identity and Access Guide.
  • Open only trusted projects: treat a project file from a vendor, integrator or email as untrusted code. Open it first on an isolated station and compare it with the last approved version before it reaches a production EWS.
  • Compare controller contents: periodically upload logic from controllers through a separate, trusted path (or use asset management tools that do this) and compare with the repository, because a compromised EWS can show engineers what they expect to see, as Stuxnet's rootkit did.
  • Back up offline: keep offline copies of projects, firmware, licences and EWS images so the plant can be rebuilt if every EWS is encrypted by ransomware.

Portable, vendor and integrator laptops

OptionBenefitRiskWhen to use
Fixed EWS in the engineering zoneControlled build, stays inside OTEngineers must be on site or use remote accessDefault for routine engineering
Site-owned portable EWS kept on siteNeeded for field work at cabinetsCan be lost, misused or connected elsewhereCommissioning and fault finding; signed out and checked in
Vendor or integrator laptopBrings specialist tools and licencesUnknown build, used at many customers, often holds other customers' projectsOnly with pre-connection scanning, a transient zone and supervision
Remote engineering through a jump hostNo foreign hardware on site; recordedJump host becomes a high-value targetVendor support and out-of-hours work
  • Transient zone: connect portable and vendor laptops to a dedicated port or VLAN that reaches only the controllers in scope, never to a general control network and never with a second interface on another network.
  • Check before connection: malware scan, patch level and a statement of what software and projects are on the machine. Reject laptops that are also used for email and browsing on the customer site.
  • Time limits: enable the port or account for the work window only and remove it afterwards.

Remote engineering access

Remote engineering should reach an EWS or engineering jump host in the OT network through the industrial DMZ, never connect a remote laptop directly to controllers. Require named accounts with phishing-resistant MFA, approval per session, session recording and a time-boxed window, and keep programming rights on the jump host separate from monitoring rights. NIST SP 800-82 Rev. 3 recommends MFA for remote access to OT. See the OT Remote Access Guide and the Privileged Access Workstations Guide.

Where identity fits

An EWS concentrates human and non-human identities: the engineer's account, local administrator accounts, service accounts for licence and communication servers, saved controller credentials and, increasingly, client certificates for secure industrial protocols. Each needs an owner, storage in a vault or protected key store, rotation and removal when a person or vendor leaves. The engineering software's own trust in controllers is also an identity relationship; CVE-2021-22681 showed what happens when that trust rests on a static key.

Detection and measurement

SignalSourceATT&CK for ICS
New process or binary not in the allowlist, especially from user or temp foldersAllowlisting logs, EDR, Windows event 4688T0863 User Execution; T0849 Masquerading
Changes to vendor engineering binaries and communication DLLsFile integrity monitoringT0874 Hooking
New service or driver installedWindows event 7045, EDRT0890 Exploitation for Privilege Escalation
USB device connectedWindows event 6416, device control logsT0847 Replication Through Removable Media
Remote interactive logonsWindows event 4624 logon type 10, jump host recordsT0886 Remote Services
Program download, online edit or mode change from the EWS outside a change windowOT network monitoring, controller logsT0843 Program Download; T0889 Modify Program; T0858 Change Operating Mode
Project files modified outside the repository workflowRepository and file auditT0873 Project File Infection
Bulk copying of project filesFile audit, data loss preventionT0882 Theft of Operational Information

Metrics

  • Percentage of EWS on the approved golden image with allowlisting in enforce mode.
  • Number of EWS with email, web browsing or corporate domain membership (target zero).
  • Percentage of controller downloads matched to an approved change and repository version.
  • Percentage of controllers whose running logic was compared with the repository in the last quarter.
  • Vendor laptop connections that passed pre-connection checks, and time from end of work to port and account removal.
  • Time to rebuild an EWS from offline image and restore projects in an exercise.

Framework mapping

ControlNIST SP 800-53 Rev. 5NIST CSF 2.0MITRE D3FEND
Application allowlisting and least functionalityCM-7(5) Authorized Software, Allow-by-exception; CM-11 User-installed SoftwarePR.PS-05D3-EAL Executable Allowlisting
Golden image and baselineCM-2 Baseline ConfigurationPR.PS-01None mapped
Removable media controlMP-7 Media UsePR.PS-05None mapped
No standing local admin; named accountsAC-6(5) Privileged Accounts; IA-2 Identification and AuthenticationPR.AA-05None mapped
Controller password vaultingIA-5 Authenticator ManagementPR.AA-01None mapped
Project and binary integritySI-7 Software, Firmware, and Information IntegrityDE.CM-09D3-FH File Hashing
Malware protectionSI-3 Malicious Code ProtectionDE.CM-09None mapped
Remote engineering accessAC-17 Remote AccessPR.AA-03None mapped
Offline project and image backupsCP-9 System BackupPR.DS-11None mapped

In IEC 62443 terms, the EWS belongs in its own zone or a tightly controlled conduit to controller zones; see the OT Network Segmentation, Purdue Model and IEC 62443 Zones and Conduits Guide. CIS Controls v8.1 Control 2 (inventory and control of software assets) and Control 10 (malware defences) also apply.

Common failure patterns

  • The EWS is also the engineer's laptop: email, web browsing, personal files and VPN to the office on the same machine that programs safety controllers.
  • Dual-homed EWS: one network card on the office network and one on the control network, bypassing every firewall in the design.
  • Saved controller passwords: passwords stored in the engineering software or a text file on the desktop, so anyone on the EWS can program any controller.
  • No source of truth for logic: the latest project lives only on whichever laptop last went online, so nobody can tell if running logic was changed.
  • Safety system key left in program mode: combined with an EWS on the safety network, this is the pattern described in Triton's attack on a Triconex safety system.
  • Integrator laptops treated as trusted: a contractor laptop that visits many sites is plugged into a control switch with no scan and no transient zone.

Practitioner checklist

  • Inventory every EWS, fixed and portable, with software versions, projects, licences and the controllers it can reach.
  • Rebuild EWS as dedicated, vendor-validated golden images with no email or browsing and no corporate domain membership.
  • Remove standing local admin, use named accounts and rotate local administrator passwords.
  • Enforce application allowlisting, signed and non-vulnerable drivers, and registered USB devices only.
  • Vault controller passwords and stop saving them in engineering software.
  • Keep approved projects with hashes in a controlled repository and compare running logic with it every quarter.
  • Put portable and vendor laptops through scanning and a transient zone, and time-limit their access.
  • Route remote engineering through a DMZ jump host with phishing-resistant MFA and session recording.
  • Monitor EWS process, driver, USB and logon events and controller downloads outside change windows.
  • Keep offline images, projects, firmware and licences, and rehearse a full EWS rebuild.

Standards and references

Related NHI Mgmt Group resources: PLC Security Guide · OT and ICS Identity and Access Guide · Privileged Access Workstations Guide · OT Remote Access Guide · Siemens SIMATIC S7 and TIA Portal Hardening Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.