Monitor Process State

Adversaries may gather information about the physical process state. This information may be used to gain more information about the process itself or used as a trigger for malicious actions. The sources of process state information may vary such as, OPC tags, historian data, specific PLC block information, or network traffic.

ID: T0801
Sub-techniques:  No sub-techniques
Tactic: Collection
Platforms: Control Server, Data Historian, Field Controller/RTU/PLC/IED, Human-Machine Interface, Safety Instrumented System/Protection Relay
Version: 1.0
Created: 21 May 2020
Last Modified: 09 March 2023

Procedure Examples

ID Name Description
S0604 Industroyer

Industroyer's OPC and IEC 61850 protocol modules include the ability to send stVal requests to read the status of operational variables. [1]

S1072 Industroyer2

Industroyer2 uses a General Interrogation command to monitor the device’s Information Object Addresses (IOAs) and their IO state values.[2]

S0603 Stuxnet

Stuxnet examines fields recorded by the DP_RECV monitor to determine if the target system is in a particular state of operation. [3]


ID Mitigation Description
M0816 Mitigation Limited or Not Effective

This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.


ID Data Source Data Component Detects
DS0015 Application Log Application Log Content

Monitor applications logs for any access attempts to operational databases (e.g., historians) or other sources of operational data within the ICS environment. These devices should be monitored for adversary collection using techniques relevant to the underlying technologies (e.g., Windows, Linux).

DS0029 Network Traffic Network Traffic Content

Monitor ICS automation network protocols for functions related to reading an operational process state (e.g., "Read" function codes in protocols like DNP3 or Modbus). In some cases, there may be multiple ways to monitor an operational process’ state, one of which is typically used in the operational environment. Monitor for the operating mode being checked in unexpected ways.