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
- Last Updated: 2021-06-17
- Author: Mauricio Velazco, Splunk
- ID: 2b85aa3d-f5f6-4c2e-a081-a09f6e1c2e40
Kill Chain Phase
- Actions on Objectives
- CIS 3
- CIS 5
- CIS 6
1 2 3 4 5 (`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`
The SPL above uses the following Macros:
Note that suspicious_event_log_service_behavior_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 Windows event logs from your hosts. In addition, the Splunk Windows TA is needed.
Known False Positives
It is possible the Event Logging service gets shut down due to system errors or legitimately administration tasks. Filter as needed.
Associated Analytic story
|9.0||30||30||The Windows Event Log Service shutdown on $ComputerName$|
source | version: 1