Screen Capture T1113
Tactic: Collection
Adversaries may attempt to take screen captures of the desktop to gather information over the course of an operation. Screen capturing functionality may be included as a feature of a remote access tool used in post-compromise operations. Taking a screenshot is also typically possible through native utilities or API calls, such as CopyFromScreen, xwd, or screencapture.
Events covered
10 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Sysmon | Event ID 7 | Image loaded |
| Sysmon | Event ID 11 | FileCreate |
| Sysmon | Event ID 12 | RegistryEvent (Object create and delete) |
| Sysmon | Event ID 13 | RegistryEvent (Value Set) |
| Sysmon | Event ID 14 | RegistryEvent (Key and Value Rename) |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| ESF | exec | Process Execution (Notify) |
| Linux-Auditd | Event ID 1309 | EXECVE |
| PowerShell | Event ID 4104 | Creating Scriptblock text (MessageNumber of MessageTotal). |
Authoring guide
Patterns shared across the 24 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (26 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (113 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (8 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 13 rules
- Periodic Backup For System Registry Hives Enabled
- RDP shadow session configuration enabled (registry)
- RDP shadow session started (command)
- RDP shadow session started (native)
- Screen Capture - macOS
- Screen Capture Activity Via Psr.EXE
- Screen Capture with Import Tool
- Screen Capture with Xwd
- System Drawing DLL Load
- Windows Recall Feature Enabled - DisableAIDataAnalysis Value Deleted
- Windows Recall Feature Enabled - Registry
- Windows Recall Feature Enabled Via Reg.EXE
- Windows Screen Capture with CopyFromScreen
Elastic 3 rules
- Linux Video Recording or Screenshot Activity Detected
- Potential Remote Desktop Shadowing Activity
- PowerShell Suspicious Script with Screenshot Capabilities
Splunk 7 rules
- NirCmd Execution (Sysmon)
- NirCmd Execution (Windows Event Log)
- Remcos RAT File Creation in Remcos Folder
- Suspicious Image Creation In Appdata Folder
- Suspicious WAV file in Appdata Folder
- Windows Screen Capture in TEMP folder
- Windows Screen Capture Via Powershell