mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
research-bot
70 lines
2.9 KiB
YAML
70 lines
2.9 KiB
YAML
name: Linux Auditd Stop Services
|
|
id: 43bc9281-753b-4743-b4b7-60af84f085f3
|
|
version: 1
|
|
date: '2024-09-04'
|
|
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 Linux Auditd, 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:
|
|
- Linux Auditd Service Stop
|
|
search: '`linux_auditd` type=SERVICE_STOP | rename host as dest | stats count min(_time)
|
|
as firstTime max(_time) as lastTime by type pid UID comm exe dest | `security_content_ctime(firstTime)`|
|
|
`security_content_ctime(lastTime)`| `linux_auditd_stop_services_filter`'
|
|
how_to_implement: To implement this detection, the process begins by ingesting auditd
|
|
data, that consist SYSCALL, TYPE, EXECVE and PROCTITLE events, which captures command-line
|
|
executions and process details on Unix/Linux systems. These logs should be ingested
|
|
and processed using Splunk Add-on for Unix and Linux (https://splunkbase.splunk.com/app/833),
|
|
which is essential for correctly parsing and categorizing the data. The next step
|
|
involves normalizing the field names to match the field names set by the Splunk
|
|
Common Information Model (CIM) to ensure consistency across different data sources
|
|
and enhance the efficiency of data modeling. This approach enables effective monitoring
|
|
and detection of linux endpoints where auditd is deployed
|
|
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:
|
|
- Industroyer2
|
|
- Data Destruction
|
|
- AwfulShred
|
|
- Compromised Linux Host
|
|
asset_type: Endpoint
|
|
confidence: 70
|
|
impact: 70
|
|
message: A service event - [$type$] event occured on host - [$dest$] to stop or disable a service.
|
|
mitre_attack_id:
|
|
- T1489
|
|
observable:
|
|
- name: dest
|
|
type: Endpoint
|
|
role:
|
|
- Victim
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
required_fields:
|
|
- _time
|
|
- type
|
|
- pid
|
|
- UID
|
|
- comm
|
|
- exe
|
|
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_auditd_service_stop/linux_auditd_service_stop.log
|
|
source: /var/log/audit/audit.log
|
|
sourcetype: linux:audit
|