Join our Newsletter — 33% off our NHI Course
Home› Guides› ATT&CK for ICS Evasion Tactic Guide: Catch Adversaries…
Guide OT & IoT Security

ATT&CK for ICS Evasion Tactic Guide: Catch Adversaries Hiding in Trusted OT Tools

PDF for newsletter subscribers · free to read online

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

Evasion is the ATT&CK for ICS tactic in which an adversary avoids technical defences and operator suspicion inside an industrial environment, by hiding in trusted vendor software, removing traces, exploiting flaws in security checks or sending messages that look legitimate. MITRE describes TA0103 as the adversary "trying to avoid security defenses" and notes that ICS evasion methods "are often more passive in nature", including masquerading as master devices or native software. The tactic matters because OT environments rely heavily on trust: an engineering workstation, a vendor DLL or a message from the SCADA master is accepted without question. This hub covers all seven techniques and two sub-techniques ATT&CK v20 lists under Evasion, how they appeared in Stuxnet, Triton and the Ukraine grid attacks, which mitigations MITRE maps to them and how to detect them. It is written for OT security engineers, SOC analysts and control engineers, and builds on the MITRE ATT&CK for ICS Guide.

Key takeaways

  • ICS Evasion is not Enterprise Defense Evasion. ATT&CK for ICS keeps a single Evasion tactic (TA0103). Enterprise ATT&CK v19 split its old tactic into Stealth and Defense Impairment (TA0112), so cross-domain mappings need care.
  • Trust is the target. Masquerading (T0849), System Binary Proxy Execution (T0894) and Unauthorized Message (T1692) all work by looking like legitimate vendor software, system tools or protocol traffic.
  • Integrity baselines are the strongest control. Code Signing (M0945) and Execution Prevention (M0938) cover the host techniques, and MITRE analytics hinge on hashes and paths that differ from the vendor-signed baseline.
  • Source allowlists catch protocol evasion. Unauthorized command and reporting messages are structurally valid; the analytics detect them by sender identity, not content.
  • Controllers lie when compromised. Stuxnet's rootkit hid malicious PLC code from engineering software, and Triton disabled a firmware consistency check, so verify devices with independent measurements and out-of-band integrity checks.

What Evasion means in OT

In IT, evasion usually means beating antivirus or EDR. In OT the defences being evaded are wider: operators who might notice odd values, engineers who might see unexpected logic, controller self-checks, and the limited security tooling on Windows hosts in the control network. The ATT&CK for ICS technique descriptions show four approaches:

  • Look legitimate: Masquerading (T0849) disguises malware as vendor executables or configuration files, and System Binary Proxy Execution (T0894) runs malicious content through signed or trusted binaries, including ICS vendor binaries.
  • Hide and clean up: Rootkit (T0851) intercepts calls that report system information, and Indicator Removal on Host (T0872) overwrites, deletes or covers up changes.
  • Break the checks: Exploitation for Evasion (T0820) exploits vulnerabilities to disable or circumvent security features, including on embedded devices.
  • Abuse the process itself: Change Operating Mode (T0858) moves a controller into a mode that permits changes, and Unauthorized Message (T1692) sends command or reporting messages that make it appear "everything is working correctly when it isn't".

Three techniques are shared with other tactics: Rootkit with Inhibit Response Function, Change Operating Mode with Execution, and Unauthorized Message with Impair Process Control. A control placed for one of these tactics often covers Evasion as well. See the ATT&CK for ICS Inhibit Response Function Tactic Guide and the ATT&CK for ICS Impair Process Control Tactic Guide.

Every technique in the tactic (ATT&CK v20)

The table lists every technique and sub-technique under TA0103 in ATT&CK v20, checked against the v20 STIX data and the live tactic page in November 2026.

IDTechniqueHow it evadesExamples recorded by ATT&CK
T0858ICS T0858 Change Operating ModeSwitches a controller to program, stop or remote mode to unlock engineering functions such as program downloadTriton, INCONTROLLER, PLC-Blaster
T0820T0820 Exploitation for EvasionExploits a vulnerability to disable or bypass a security featureTriton (disabled a firmware RAM/ROM consistency check)
T0872T0872 Indicator Removal on HostDeletes logs or restores devices to hide changesKillDisk, Triton, Triton Safety Instrumented System Attack
T0849T0849 MasqueradingDisguises malware as vendor or system filesStuxnet, Triton, EKANS, REvil, 2016 Ukraine Electric Power Attack
T0851T0851 RootkitHides programs, files and changes by intercepting system callsStuxnet
T0894T0894 System Binary Proxy ExecutionRuns malicious content through trusted binaries2022 Ukraine Electric Power Attack (MicroSCADA scilc.exe)
T1692T1692 Unauthorized MessageSends command or reporting messages from an unauthorised sourceSee sub-techniques
T1692.001Command MessageCommands that make assets act outside intended functionIndustroyer, Industroyer2, INCONTROLLER, CyberAv3ngers, Triton Safety Instrumented System Attack, Maroochy Water Breach, 2015 and 2022 Ukraine Electric Power Attacks
T1692.002Reporting MessageSpoofed telemetry that hides the true process stateMaroochy Water Breach

ID changes in v20: T0855 Unauthorized Command Message is revoked and replaced by T1692.001, and T0856 Spoof Reporting Message is revoked and replaced by T1692.002. Detection content and threat reports that still use the old IDs should be remapped.

How adversaries use Evasion

NHI Mgmt Group counted the groups, software and campaigns in the ATT&CK for ICS v20 STIX data that have a "uses" relationship to any ICS technique (41, excluding revoked and deprecated objects). 15 of them use at least one Evasion technique. Unauthorized Message: Command Message (T1692.001) is the most widely recorded, with 8 users, followed by Masquerading (T0849) with 5. Among those 15, the tactics used most often alongside Evasion are Inhibit Response Function, Execution, Impact and Impair Process Control, which fits the picture of evasion as cover for a physical attack.

Case in ATT&CKEvasion techniques recordedWhat the evasion achieved
Stuxnet (S0603)T0849, T0851Replaced s7otbxdx.dll, the library that handles communication with the PLC, so its own version intercepted calls and hid malicious code from read requests
Triton (S1009)T0820, T0849, T0858, T0872Masqueraded as trilog.exe, the Triconex log analysis software; disabled a firmware consistency check; halted and ran programs over TriStation; tried to restore the controller or write a dummy program if it failed
2022 Ukraine Electric Power Attack (C0034)T0894, T1692.001Used the MicroSCADA binary scilc.exe to send a predefined list of SCADA instructions to substation devices
2016 Ukraine Electric Power Attack (C0025)T0849Transferred executables as .txt and renamed them to .exe, likely to avoid extension tracking
Maroochy Water Breach (C0020)T1692.001, T1692.002Used a two-way radio system to send false data and instructions to pumping stations and the central computer
EKANS (S0605)T0849Masqueraded as update.exe, a common name for update services

The common thread is abuse of trusted components: vendor DLLs, vendor executables, the SCADA application itself and the protocol channel. See the ICS Malware History Guide.

Mitigations MITRE maps across the tactic

The counts are the number of Evasion techniques (parent level) each mitigation is mapped to in v20.

MitigationTechniques (count)What it looks like on site
M0945 Code SigningT0849, T0851 (2)Only vendor-signed binaries, libraries and firmware run or load; signatures checked against the vendor baseline
M0938 Execution PreventionT0849, T0894 (2)Application allowlisting on HMIs, engineering workstations and servers, including rules for trusted binaries that can proxy execution
M0922 Restrict File and Directory PermissionsT0849, T0872 (2)Vendor install directories and log files writable only by installers and the logging service
M0813 Software Process and Device Authentication, M0802 Communication AuthenticityT0858, T1692 (2 each)Authenticated sessions for mode changes and authenticated command and reporting messages where protocols support them
M0807 Network Allowlists, M0930 Network SegmentationT0858, T1692 (2 each)Only approved masters and engineering workstations can reach controllers and send commands
M0937 Filter Network TrafficT1692 (1)Protocol-aware filtering of command function codes at zone boundaries
M0818 Validate Program InputsT1692.001Controller logic that checks commands against process preconditions before acting
M0804 Human User Authentication, M0801 Access Management, M0800 Authorization EnforcementT0858 (1 each)Logins and role checks before an operating mode can change
M0947 AuditT0851 (1)Regular comparison of controller logic and host state with known good
M0951 Update Software, M0950 Exploit Protection, M0948 Application Isolation and Sandboxing, M0919 Threat Intelligence ProgramT0820 (1 each)Planned patching through ICS advisory triage, exploit mitigations on hosts, isolation of exposed services and tracking of relevant vulnerabilities

For the patching side see the ICS Advisory Triage and OT Vulnerability Management Guide. Where controllers cannot authenticate commands, segmentation and allowlists carry the protocol techniques.

Detection and measurement

ATT&CK v20 publishes a detection strategy for each technique. The analytics use an OT operational-fidelity gate: alert when activity violates an approved baseline (signer, hash, path or source), not because something is new.

TechniqueDetection strategySignal to monitorData source
T0849 MasqueradingDET0725A process named like an ICS vendor application whose hash or path does not match the vendor-signed baseline; a device whose protocol identity conflicts with the asset inventoryEDR or Sysmon, asset inventory, network monitoring
T0851 RootkitDET0780Process lists that differ between enumeration methods, kernel drivers from unexpected paths, device self-reports that disagree with an independent firmware fingerprintHost telemetry, integrity checks
T0872 Indicator Removal on HostDET0750Audit log clearing or vendor log truncation after other suspicious activity; syslog sequence gaps; device event logs cleared by protocol commandWindows Security log, syslog, OT network monitoring
T0894 System Binary Proxy ExecutionDET0793Signed system or vendor binaries run with arguments outside their documented purposeProcess creation with command lines
T0820 Exploitation for EvasionDET0795Malformed protocol exchanges to embedded devices, vendor process crashes after cross-process memory access, unexpected device restartsNetwork monitoring, host and device logs
T0858 Change Operating ModeDET0755A mode change command from a source not on the engineering workstation listProtocol-aware monitoring
T1692 Unauthorized MessageDET0902 (DET0794, DET0746 for sub-techniques)Valid command or reporting messages from a sender not in the approved baseline; unsolicited DNP3 or GOOSE frames from unexpected addresses; telemetry that disagrees with an independent measurementNetwork monitoring, independent sensors

The indicator removal analytic for Windows depends on audit log clearing being recorded (Security Event ID 1102) and logs being forwarded off the host before they can be deleted. See the OT Network Security Monitoring Guide.

Metrics that show coverage:

  • Percentage of HMIs, engineering workstations and OT servers with application allowlisting in enforce mode.
  • Percentage of OT hosts whose vendor binaries are hash-baselined, with drift reviewed weekly.
  • Percentage of OT host and network device logs forwarded to a collector outside the host.
  • Number of controller mode changes per month without a matching maintenance ticket (target zero).
  • Percentage of critical process variables with an independent measurement used to check reported values.
  • Detection rules mapped to all seven Evasion techniques using v20 IDs.

Where identity fits

Evasion in OT is often identity evasion: the adversary appears as a trusted process, device or master. Masquerading includes, in MITRE's words, masquerading "as master devices or native software", and the T1692 analytics are essentially checks of sender identity.

  • Device identity: keep an authoritative inventory of each device's address, vendor and model so that a device presenting conflicting protocol identity is flagged. See the OT Asset Visibility Guide.
  • Software identity: code signing and hash baselines are machine identity for executables and firmware.
  • Engineering accounts and sessions: mode changes and program operations should require named, authenticated sessions from approved workstations. See the OT and ICS Identity and Access Guide and the Engineering Workstation Security Guide.

Implementation roadmap

  1. Baseline software: record hashes, signers and install paths of vendor software on every OT Windows and Linux host, from a known-good build.
  2. Allowlist in audit mode: deploy application control in audit mode on HMIs and engineering workstations for several weeks, review what would be blocked with the vendor and operations, then move to enforce one host group at a time with a documented rollback (switch back to audit mode).
  3. Protect logs: forward host, application and network device logs to a collector outside the OT host, and alert on clearing and sequence gaps.
  4. Baseline senders: use passive monitoring to record which masters send which commands to which devices, then alert on new senders and mode changes.
  5. Harden controllers: keyswitches in run, mode change protection and passwords enabled where supported; authenticated protocols on new assets.
  6. Verify independently: add independent measurements or periodic integrity checks for critical controllers so a compromised controller cannot hide its own state.

Decision guidance: small sites with a few HMIs gain most from application allowlisting and log forwarding, which are cheap and well understood. Large operators should invest in central hash baselines and sender allowlists that scale across sites. Where vendor support agreements restrict changes to hosts, agree allowlisting with the vendor first and rely on network-level detection in the meantime.

Framework mapping

DefenceNIST SP 800-53 Rev. 5NIST CSF 2.0ATT&CK for ICS mitigation
Software and firmware integritySI-7, CM-14PR.PS-02M0945, M0947
Application allowlistingCM-7(5)PR.PS-05M0938
Protection of audit logsAU-9, AU-4(1)PR.PS-04M0922
Authenticated commands and mode changesIA-3, SC-8, AC-3PR.AA-03M0813, M0802, M0800
Boundary control of protocol trafficSC-7, AC-4PR.IR-01M0930, M0807, M0937
Vulnerability remediationSI-2, RA-5ID.RA-01M0951, M0919
Monitoring for evasion signalsSI-4, AU-6DE.CM-01, DE.CM-09Detection strategies above

See the NIST SP 800-82 OT Security Guide and the IEC 62443 Guide.

Common failure patterns

  • Trusting names: allowlists or exclusions based on file names such as update.exe or a vendor tool name, which Masquerading defeats. Use signer and hash.
  • Logs only on the host: when logs stay on the HMI, Indicator Removal and wipers erase the evidence.
  • Trusting engineering software views: Stuxnet showed that the engineering tool can be shown clean logic while the controller runs something else. Use independent integrity checks.
  • Broad EDR exclusions for vendor folders: excluding a whole vendor install directory from monitoring creates the exact hiding place Masquerading needs.
  • Alerting on content only: unauthorised commands are protocol-valid, so content inspection without sender baselines misses them.
  • Stale mappings: rules still tagged T0855 or T0856 after the v20 revocation, so coverage reports undercount T1692.

Practitioner checklist

  • Vendor software on OT hosts is hash and signer baselined from a known-good build.
  • Application allowlisting runs in enforce mode on HMIs and engineering workstations.
  • Host and network device logs are forwarded off-host; log clearing raises an alert.
  • EDR exclusions for vendor directories are narrow and reviewed.
  • Approved senders of commands and mode changes are documented per controller and monitored.
  • Controllers stay in run mode outside maintenance windows.
  • Critical process values are checked against independent measurements.
  • Detection content uses T1692.001 and T1692.002 instead of revoked T0855 and T0856.
  • ICS advisories are triaged for vulnerabilities that bypass security features.

Standards and references

Related NHI Mgmt Group resources: MITRE ATT&CK for ICS Guide · HMI and SCADA Server Hardening Guide · Engineering Workstation Security Guide · PLC Security 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 13 November 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.