Detect Boot or Logon Autostart Execution in IBM QRadar
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/
QRadar Detection Query
SELECT DATEFORMAT(devicetime, 'yyyy-MM-dd HH:mm:ss') AS event_time,
sourceip,
username,
QIDNAME(qid) AS event_name,
"RegistryKey",
"RegistryValueName",
"RegistryValueData",
"ProcessName",
"ProcessCommandLine",
LOGSOURCENAME(logsourceid) AS log_source
FROM events
WHERE LOGSOURCETYPENAME(devicetype) = 'Microsoft Windows Security Event Log'
AND qid IN (
SELECT qid FROM QIDmap WHERE name LIKE '%Registry%'
)
AND LOWER("RegistryKey") MATCHES '.*\\(currentversion\\run|currentversion\\runonce|currentversion\\runonceex|currentversion\\runservices|currentversion\\runservicesonce|currentversion\\policies\\explorer\\run|currentversion\\winlogon|active setup\\installed components|control\\lsa|control\\print\\monitors|control\\print\\environments|services\\w32time\\timeproviders|explorer\\shell folders|explorer\\user shell folders).*'
AND LOGSOURCETYPENAME(devicetype) IN ('Microsoft Windows Security Event Log', 'Sysmon')
AND devicetime > (CURRENT_TIMESTAMP - 86400000)
ORDER BY devicetime DESC Detects creation and modification of Windows autostart registry keys associated with T1547 persistence techniques. Queries Windows Security Event Log and Sysmon sources in QRadar for registry events targeting Run keys, Winlogon, LSA packages, Print Monitors, and Shell Folder paths.
Data Sources
Required Tables
False Positives & Tuning
- Software deployment tools such as SCCM or Intune may write to RunOnce keys to schedule post-reboot installation steps, generating high volumes of benign alerts during patch cycles
- Security agents (EDR, antivirus) frequently register themselves in HKLM Run keys upon installation or version upgrade, which will match this detection
- Legitimate IT automation scripts (PowerShell DSC, Ansible) managing Winlogon notification packages or LSA security packages will match when run by privileged accounts
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