Files
splunk-security_content/detections/endpoint/linux_stop_services.yml
2024-06-26 14:41:53 +00:00

77 lines
3.4 KiB
YAML

name: Linux Stop Services
id: d05204a5-9f1c-4946-a7f3-4fa58d76d5fd
version: 2
date: '2024-05-14'
author: Teoderick Contreras, Splunk
status: production
type: TTP
description: The following analytic detects attempts to stop or clear a service on
Linux systems. It leverages data from Endpoint Detection and Response (EDR) agents,
focusing on processes like "systemctl," "service," and "svcadm" executing stop commands.
This activity is significant as adversaries often terminate security or critical
services to disable defenses or disrupt operations, as seen in malware like Industroyer2.
If confirmed malicious, this could lead to the disabling of security mechanisms,
allowing attackers to persist, escalate privileges, or deploy destructive payloads,
severely impacting system integrity and availability.
data_source:
- Sysmon for Linux EventID 1
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.process_name IN ("systemctl",
"service", "svcadm") Processes.process ="*stop*" by Processes.parent_process_name
Processes.process_name Processes.process Processes.process_id Processes.parent_process_id
Processes.process_guid Processes.dest Processes.user | `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `linux_stop_services_filter`'
how_to_implement: The detection is based on data that originates from Endpoint Detection
and Response (EDR) agents. These agents are designed to provide security-related
telemetry from the endpoints where the agent is installed. To implement this search,
you must ingest logs that contain the process GUID, process name, and parent process.
Additionally, you must ingest complete command-line executions. These logs must
be processed using the appropriate Splunk Technology Add-ons that are specific to
the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
data model. Use the Splunk Common Information Model (CIM) to normalize the field
names and speed up the data modeling process.
known_false_positives: Administrator or network operator can use this application
for automation purposes. Please update the filter macros to remove false positives.
references:
- https://www.welivesecurity.com/2022/04/12/industroyer2-industroyer-reloaded/
- https://cert.gov.ua/article/39518
tags:
analytic_story:
- AwfulShred
- Data Destruction
- Industroyer2
asset_type: Endpoint
confidence: 70
impact: 70
message: An instance of $parent_process_name$ spawning $process_name$ was identified
attempting to stop services on endpoint $dest$ by $user$.
mitre_attack_id:
- T1489
observable:
- name: dest
type: Hostname
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.parent_process_name
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_id
risk_score: 49
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1489/linux_service_stop_disable/sysmon_linux.log
source: Syslog:Linux-Sysmon/Operational
sourcetype: sysmon:linux