This search looks for flags passed to schtasks.exe on the command-line that indicate that a forced reboot of system is scheduled.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2020-12-07
- Author: Bhavin Patel, Splunk
- ID: 1297fb80-f42a-4b4a-9c8a-88c066437cf6
Kill Chain Phase
- Actions on Objectives
- CIS 3
1 2 3 4 5 6 | tstats `security_content_summariesonly` values(Processes.process) as process min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name=schtasks.exe Processes.process="*shutdown*" Processes.process="*/create *" 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_used_for_forcing_a_reboot_filter`
The SPL above uses the following Macros:
schtasks_used_for_forcing_a_reboot_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the
Endpoint datamodel in the
Processes node. In addition, confirm the latest CIM App 4.20 or higher is installed and the latest TA for the endpoint product.
Known False Positives
Administrators may create jobs on systems forcing reboots to perform updates, maintenance, etc.
Associated Analytic Story
|56.0||70||80||A schedule task process $process_name$ with force reboot commandline $process$ in host $dest$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 4