Try in Splunk Security Cloud


The following hunting analytic assists with identifying suspicious tasks that have been registered and ran in Windows using EventID 200 (action run) and 201 (action completed). It is recommended to filter based on ActionName by specifying specific paths not used in your environment. After some basic tuning, this may be effective in capturing evasive ways to register tasks on Windows. Review parallel events related to tasks being scheduled. EventID 106 will generate when a new task is generated, however, that does not mean it ran. Capture any files on disk and analyze.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-10-19
  • Author: Michael Haag, Splunk
  • ID: b3632472-310b-11ec-9aab-acde48001122


ID Technique Tactic
T1053.005 Scheduled Task Execution, Persistence, Privilege Escalation
`wineventlog_task_scheduler` EventCode IN ("200","201") 
| rename ComputerName as dest 
| stats count min(_time) as firstTime max(_time) as lastTime by Message dest EventCode category 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `winevent_windows_task_scheduler_event_action_started_filter`

Associated Analytic Story

How To Implement

Task Scheduler logs are required to be collected. Enable logging with inputs.conf by adding a stanza for [WinEventLog://Microsoft-Windows-TaskScheduler/Operational] and renderXml=false. Note, not translating it in XML may require a proper extraction of specific items in the Message.

Required field

  • _time
  • TaskName
  • ActionName
  • EventID
  • dest
  • ProcessID

Kill Chain Phase

  • Exploitation

Known False Positives

False positives will be present. Filter based on ActionName paths or specify keywords of interest.


Risk Score Impact Confidence Message
80.0 80 100 A Scheduled Task was scheduled and ran on $dest$.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1