Try in Splunk Security Cloud

Description

The following analytic utilizes Windows Event ID 1100 to identify when Windows event log service is shutdown. Note that this is a voluminous analytic that will require tuning or restricted to specific endpoints based on criticality. This event generates every time Windows Event Log service has shut down. It also generates during normal system shutdown. During triage, based on time of day and user, determine if this was planned. If not planned, follow through with reviewing parallel alerts and other data sources to determine what else may have occurred.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2021-06-17
  • Author: Mauricio Velazco, Splunk
  • ID: 2b85aa3d-f5f6-4c2e-a081-a09f6e1c2e40

ATT&CK

ID Technique Tactic
T1070.001 Clear Windows Event Logs Defense Evasion
(`wineventlog_security` EventCode=1100) 
| stats count min(_time) as firstTime max(_time) as lastTime by dest Message EventCode 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `suspicious_event_log_service_behavior_filter`

Associated Analytic Story

How To Implement

To successfully implement this search, you need to be ingesting Windows event logs from your hosts. In addition, the Splunk Windows TA is needed.

Required field

  • _time
  • EventCode
  • dest

Kill Chain Phase

  • Actions on Objectives

Known False Positives

It is possible the Event Logging service gets shut down due to system errors or legitimately administration tasks. Filter as needed.

RBA

Risk Score Impact Confidence Message
9.0 30 30 The Windows Event Log Service shutdown on $ComputerName$

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