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

80 lines
3.5 KiB
YAML

name: Linux Service Started Or Enabled
id: e0428212-61b7-11ec-88a3-acde48001122
version: 3
date: '2024-05-29'
author: Teoderick Contreras, Splunk
status: production
type: Anomaly
description: The following analytic detects the creation or enabling of services on
Linux platforms using the systemctl or service tools. It leverages Endpoint Detection
and Response (EDR) logs, focusing on process names, parent processes, and command-line
executions. This activity is significant as adversaries may create or modify services
to maintain persistence or execute malicious payloads. If confirmed malicious, this
behavior could lead to persistent access, data theft, ransomware deployment, or
other damaging outcomes. Monitoring and investigating such activities are crucial
for maintaining the security and integrity of the environment.
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") OR Processes.process IN ("*systemctl *", "*service *")) Processes.process
IN ("* start *", "* enable *") AND NOT (Processes.os="Microsoft Windows" OR Processes.vendor_product="Microsoft
Windows") by Processes.dest Processes.user Processes.parent_process_name Processes.process_name
Processes.process Processes.process_id Processes.parent_process_id Processes.process_guid
| `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`
| `linux_service_started_or_enabled_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 commandline
for automation purposes. Please update the filter macros to remove false positives.
references:
- https://attack.mitre.org/techniques/T1543/003/
tags:
analytic_story:
- Linux Privilege Escalation
- Linux Persistence Techniques
- Linux Living Off The Land
- Scheduled Tasks
- Gomir
asset_type: Endpoint
confidence: 70
impact: 60
message: a commandline $process$ that may create or start a service on $dest
mitre_attack_id:
- T1053.006
- T1053
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: 42
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1053.006/service_systemd/sysmon_linux.log
source: Syslog:Linux-Sysmon/Operational
sourcetype: sysmon:linux