The following analytics uses Windows Event Id 7045,
New Service Was Installed, to identify the creation of a Windows Service where the service binary path path is located in a non-common Service folder in Windows. Red Teams and adversaries alike may create malicious Services for lateral movement or remote code execution as well as persistence and execution. The Clop ransomware has also been seen in the wild abusing Windows services.
- Type: TTP
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2022-11-14
- Author: Teoderick Contreras, Mauricio Velazco, Splunk
- ID: 429141be-8311-11eb-adb6-acde48001122
Kill Chain Phase
- CIS 10
1 2 3 4 5 `wineventlog_system` EventCode=7045 Service_File_Name = "*.exe" NOT (Service_File_Name IN ("*:\\Windows\\*", "*:\\Program File*", "*:\\Programdata\\*", "*%systemroot%\\*")) | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Service_File_Name Service_Name Service_Start_Type Service_Type dest user | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_service_created_with_suspicious_service_path_filter`
The SPL above uses the following Macros:
windows_service_created_with_suspicious_service_path_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 logs with the Service name, Service File Name Service Start type, and Service Type from your endpoints.
Known False Positives
Legitimate applications may install services with uncommon services paths.
Associated Analytic Story
|56.0||70||80||A service $Service_File_Name$ was created from a non-standard path using $Service_Name$|
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: 3