Screen Capture

Screen Capture
Technique
ID	T0852
Tactic	Collection
Data Sources	API monitoring, Process monitoring, File monitoring
Asset	Human-Machine Interface

Description

Adversaries may attempt to perform screen capture of devices in the control system environment. Screenshots may be taken of workstations, HMIs, or other devices that display environment-relevant process, device, reporting, alarm, or related data. These device displays may reveal information regarding the ICS process, layout, control, and related schematics. In particular, an HMI can provide a lot of important industrial process information.1 Analysis of screen captures may provide the adversary with an understanding of intended operations and interactions between critical devices.

Procedure Examples

ALLANITE has been identified to collect and distribute screenshots of ICS systems such as HMIs.21
APT33 utilize backdoors capable of capturing screenshots once installed on a system.34
Dragonfly has been reported to take screenshots of the GUI for ICS equipment, such as HMIs.1

Mitigations

Mitigation Limited or Not Effective - Preventing screen capture on a device may require disabling various system calls supported by the operating systems (e.g., Microsoft WindowsGraphicsCaputer APIs), however, these may be needed for other critical applications.

References

v · d · e Adversary Techniques

Initial Access	Data Historian Compromise Drive-by Compromise Engineering Workstation Compromise Exploit Public-Facing Application External Remote Services Initial Access Internet Accessible Device Replication Through Removable Media Spearphishing Attachment Supply Chain Compromise Wireless Compromise

Execution	Change Program State Command-Line Interface Execution Execution through API Graphical User Interface Man in the Middle Program Organization Units Project File Infection Scripting User Execution

Persistence	Hooking Module Firmware Persistence Program Download Project File Infection System Firmware Valid Accounts

Evasion	Evasion Exploitation for Evasion Indicator Removal on Host Masquerading Rogue Master Device Rootkit Spoof Reporting Message Utilize/Change Operating Mode

Discovery	Control Device Identification Discovery I/O Module Discovery Network Connection Enumeration Network Service Scanning Network Sniffing Remote System Discovery Serial Connection Enumeration

Lateral Movement	Default Credentials Exploitation of Remote Services External Remote Services Lateral Movement Program Organization Units Remote File Copy Valid Accounts

Collection	Automated Collection Collection Data from Information Repositories Detect Operating Mode Detect Program State I/O Image Location Identification Monitor Process State Point & Tag Identification Program Upload Role Identification Screen Capture

Inhibit Response Function	Activate Firmware Update Mode Alarm Suppression Block Command Message Block Reporting Message Block Serial COM Data Destruction Denial of Service Device Restart/Shutdown Inhibit Response Function Manipulate I/O Image Modify Alarm Settings Modify Control Logic Program Download Rootkit System Firmware Utilize/Change Operating Mode

Impair Process Control	Brute Force I/O Change Program State Impair Process Control Masquerading Modify Control Logic Modify Parameter Module Firmware Program Download Rogue Master Device Service Stop Spoof Reporting Message Unauthorized Command Message

Impact	Damage to Property Denial of Control Denial of View Impact Loss of Availability Loss of Control Loss of Productivity and Revenue Loss of Safety Loss of View Manipulation of Control Manipulation of View Theft of Operational Information

Description

Procedure Examples

Mitigations

References

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

ATT&CK™

Questions?

Tools