huntrule

Windows Registry: Clearing RDP Client Connection History via MRU and Server Keys Deletion

Flags registry deletions that remove Windows RDP client connection history from Terminal Server Client MRU and Servers keys.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_delete
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-10-19
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Persistence → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects Windows registry value and key deletions tied to Terminal Server Client connection history, specifically entries under the Default\MRU and Servers paths. Clearing these records can be used to reduce forensic visibility of previously accessed remote desktop hosts and sessions. It relies on registry deletion telemetry indicating either DeleteValue or DeleteKey events targeting matching registry paths.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious PlugX Self-Cleanup Batch Execution
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Suspicious Choice Command Self-Destruct Delete Loop via Command Line
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Windows Registry: Clearing RDP Client Connection History via MRU and Server Keys Deletion
Pivot detection · T1112 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.