Try in Splunk Security Cloud


This analytic identifies an on demand run of a Windows Schedule Task through shell or command-line. This technique has been used by adversaries that force to run their created Schedule Task as their persistence mechanism or for lateral movement as part of their malicious attack to the compromised machine.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-05-07
  • Author: Teoderick Contreras, Splunk
  • ID: bb37061e-af1f-11eb-a159-acde48001122




ID Technique Tactic
T1053 Scheduled Task/Job Execution, Persistence, Privilege Escalation
Kill Chain Phase
  • Exploitation
| tstats `security_content_summariesonly` values(Processes.process) as process values(Processes.process_id) as process_id count min(_time) as firstTime max(_time) as lastTime  from datamodel=Endpoint.Processes where Processes.process_name = "schtasks.exe" Processes.process = "*/run*" by Processes.process_name Processes.parent_process_name Processes.dest Processes.user 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `schtasks_run_task_on_demand_filter`


The SPL above uses the following Macros:

:information_source: schtasks_run_task_on_demand_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Supported Add-on (TA)

List of Splunk Add-on’s tested to work with the analytic.

Required fields

List of fields required to use this analytic.

  • _time
  • Processes.process
  • Processes.process_id
  • Processes.process_name
  • Processes.parent_process_name
  • Processes.dest
  • Processes.user

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA. Tune and filter known instances where renamed schtasks.exe may be used.

Known False Positives

Administrators may use to debug Schedule Task entries. Filter as needed.

Associated Analytic Story


Risk Score Impact Confidence Message
48.0 60 80 A "on demand" execution of schedule task process $process_name$ using commandline $process$ in host $dest$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


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