Try in Splunk Security Cloud

Description

This analytic will identify suspicious system event of services that was modified from start to disabled. This technique is seen where the adversary attempts to disable security app services, other malware services to evade the defense systems on the compromised host

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2022-04-04
  • Author: Teoderick Contreras, Splunk
  • ID: 9c2620a8-94a1-11ec-b40c-acde48001122

Annotations

ATT&CK
ID Technique Tactic
T1562.001 Disable or Modify Tools Defense Evasion
T1562 Impair Defenses Defense Evasion
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 3
  • CIS 5
  • CIS 16
CVE
1
2
3
4
5
`wineventlog_system` EventCode=7040  Message = "*service was changed from demand start to disabled." 
| stats count min(_time) as firstTime max(_time) as lastTime by ComputerName EventCode Message User Sid service service_name 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_event_for_service_disabled_filter`

Macros

The SPL above uses the following Macros:

Note that windows_event_for_service_disabled_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required field

  • _time
  • ComputerName
  • EventCode
  • Message
  • User
  • Sid

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

Windows service update may cause this event. In that scenario, filtering is needed.

Associated Analytic story

RBA

Risk Score Impact Confidence Message
36.0 60 60 Service was disabled on $Computer$

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2