This analytic identifies suspicious series of attempt to kill multiple services on a system using either
sc.exe. This technique is use by adversaries to terminate security services or other related services to continue there objective and evade detections.
- Type: Anomaly
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint- Datasource: Splunk Add-on for Sysmon
- Last Updated: 2021-05-04
- Author: Teoderick Contreras, Splunk
- ID: ae8d3f4a-acd7-11eb-8846-acde48001122
Kill Chain Phase
1 2 3 4 5 6 7 | 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 `process_net` OR Processes.process_name = "sc.exe" OR Processes.process_name = "net1.exe" AND Processes.process="*stop*" OR Processes.process="*delete*" by Processes.process_name Processes.original_file_name Processes.parent_process_name Processes.dest Processes.user _time span=1m | where count >=5 | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `excessive_service_stop_attempt_filter`
The SPL above uses the following Macros:
Note that excessive_service_stop_attempt_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
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
Associated Analytic story
|80.0||80||100||An excessive amount of $process_name$ was executed on $dest$ attempting to disable services.|
source | version: 2