Windows Process Creation: Outlook EnableUnsafeClientMailRules Security Setting Enabled

Flags Windows process command lines that reference Outlook’s EnableUnsafeClientMailRules security setting.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Markus Neis, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2018-12-27
Updated
2026-07-30

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies Windows process executions whose command line includes the path to the Outlook security setting EnableUnsafeClientMailRules. Enabling this setting reduces restrictions around client mail rules, which can help an attacker persist or execute unwanted behavior via Outlook. It relies on process creation telemetry and matches on a specific command-line substring referencing the Outlook security configuration.

Related detections9 linkedT1059 — drag to rearrange
Windows Execution of Renamed NirCmd.exe (nircmd.exe/nircmdc.exe) via PE OriginalFileName
Windows: Detect renamed PingCastle binary execution via PE metadata and scanner command-line
Windows Process Creation: Execution of Renamed curl.exe via PE Metadata
Windows: Detect ftp.exe Executed With -s or /s for Script-Based Command Execution
Windows Renamed ftp.exe Execution via OriginalFileName PE Metadata
Windows: Detect Runscripthelper.exe executing PowerShell scripts with 'surfacecheck'
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Windows Process Creation: Outlook EnableUnsafeClientMailRules Security Setting Enabled
Pivot detection · T1059 · 9 related

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