Detect Boot or Logon Autostart Execution in Sumo Logic CSE
Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems. Operating systems may have mechanisms for automatically running a program on system boot or account logon, including automatically executing programs that are placed in specially designated directories or are referenced by repositories that store configuration information, such as the Windows Registry. An adversary may achieve the same goal by modifying or extending features of the kernel. Since some boot or logon autostart programs run with higher privileges, an adversary may leverage these to elevate privileges.
MITRE ATT&CK
- Tactic
- Persistence Privilege Escalation
- Technique
- T1547 Boot or Logon Autostart Execution
- Canonical reference
- https://attack.mitre.org/techniques/T1547/
Sumo Detection Query
_sourceCategory="windows/sysmon" OR _sourceCategory="windows/security"
| where EventID in ("12", "13", "14", "4657")
| where TargetObject matches "*\\CurrentVersion\\Run*"
OR TargetObject matches "*\\CurrentVersion\\RunOnce*"
OR TargetObject matches "*\\CurrentVersion\\RunOnceEx*"
OR TargetObject matches "*\\CurrentVersion\\RunServices*"
OR TargetObject matches "*\\CurrentVersion\\RunServicesOnce*"
OR TargetObject matches "*\\CurrentVersion\\Policies\\Explorer\\Run*"
OR TargetObject matches "*\\CurrentVersion\\Winlogon*"
OR TargetObject matches "*\\Active Setup\\Installed Components*"
OR TargetObject matches "*\\Control\\Lsa\\Authentication Packages*"
OR TargetObject matches "*\\Control\\Lsa\\Security Packages*"
OR TargetObject matches "*\\Control\\Print\\Monitors*"
OR TargetObject matches "*\\Control\\Print\\Environments*"
OR TargetObject matches "*\\Services\\W32Time\\TimeProviders*"
OR TargetObject matches "*\\Explorer\\Shell Folders*"
OR TargetObject matches "*\\Explorer\\User Shell Folders*"
| eval action = if(EventID == "12", "KeyCreated", if(EventID == "13", "ValueSet", if(EventID == "14", "KeyRenamed", "RegistryModified")))
| fields _messageTime, Computer, action, TargetObject, Details, Image, User
| sort by _messageTime desc Detects Sysmon registry events (EventID 12/13/14) and Windows Security Event 4657 targeting known autostart execution registry paths used in T1547 persistence. Covers Run keys, Winlogon, LSA authentication/security packages, Print Monitors, and Explorer Shell Folders.
Data Sources
Required Tables
False Positives & Tuning
- Windows Update and Windows Installer (msiexec.exe) routinely modify RunOnce keys to schedule cleanup or completion tasks after patch installation, producing high false positive volumes during Patch Tuesday windows
- Enterprise software such as Microsoft Teams, Zoom, or Slack silently adds or updates Run key entries for auto-launch on user login, generating benign events at scale
- IT asset management and remote support tools (e.g., Dameware, Bomgar) may register themselves in Winlogon notification packages and Active Setup keys during deployment
Other platforms for T1547
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Add Registry Run Key for Persistence
Expected signal: Sysmon Event ID 13: Registry value set on HKCU\Software\Microsoft\Windows\CurrentVersion\Run with value name 'df00tech-test'. DeviceRegistryEvents with ActionType 'RegistryValueSet'.
- Test 2Drop File in Startup Folder
Expected signal: Sysmon Event ID 11: FileCreate in the Startup directory. DeviceFileEvents with ActionType 'FileCreated' in the Startup folder path.
- Test 3Modify Winlogon Shell Value
Expected signal: Sysmon Event ID 13: Registry value set on Winlogon\Shell. DeviceRegistryEvents with RegistryKey containing 'Winlogon' and RegistryValueName 'Shell'.
References (6)
- https://attack.mitre.org/techniques/T1547/
- https://learn.microsoft.com/en-us/windows/win32/setupapi/run-and-runonce-registry-keys
- https://technet.microsoft.com/en-us/sysinternals/bb963902
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1547/T1547.md
- https://github.com/SigmaHQ/sigma/tree/master/rules/windows/registry_set
- https://web.archive.org/web/20160214140250/http://blog.cylance.com/windows-registry-persistence-part-2-the-run-keys-and-search-order
Unlock Pro Content
Get the full detection package for T1547 including response playbook, investigation guide, and atomic red team tests.
Related Detections
Sub-techniques (14)
- T1547.001Registry Run Keys / Startup Folder
- T1547.002Authentication Package
- T1547.003Time Providers
- T1547.004Winlogon Helper DLL
- T1547.005Security Support Provider
- T1547.006Kernel Modules and Extensions
- T1547.007Re-opened Applications
- T1547.008LSASS Driver
- T1547.009Shortcut Modification
- T1547.010Port Monitors
- T1547.012Print Processors
- T1547.013XDG Autostart Entries
- T1547.014Active Setup
- T1547.015Login Items