Try in Splunk Security Cloud


The following analytc 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
  • Datamodel: Endpoint
  • Last Updated: 2021-11-22
  • Author: Teoderick Contreras, Mauricio Velazco, Splunk
  • ID: 429141be-8311-11eb-adb6-acde48001122


ID Technique Tactic
T1569 System Services Execution
T1569.002 Service Execution Execution
 `wineventlog_system` EventCode=7045  Service_File_Name = "*\.exe" NOT (Service_File_Name IN ("C:\\Windows\\*", "C:\\Program File*", "C:\\Programdata\\*", "%systemroot%\\*")) 
| stats count min(_time) as firstTime max(_time) as lastTime by EventCode Service_File_Name Service_Name Service_Start_Type Service_Type 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_service_created_with_suspicious_service_path_filter`

Associated Analytic Story

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.

Required field

  • EventCode
  • Service_File_Name
  • Service_Type
  • _time
  • Service_Name
  • Service_Start_Type

Kill Chain Phase

  • Privilege Escalation
  • Lateral Movement

Known False Positives

Legitimate applications may install services with uncommon services paths.


Risk Score Impact Confidence Message
56.0 70 80 A service $Service_File_Name$ was created from a non-standard path using $Service_Name$


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: 2