Files
splunk-security_content/detections/endpoint/linux_auditd_doas_tool_execution.yml
2024-09-04 15:43:55 +05:30

71 lines
2.9 KiB
YAML

name: Linux Auditd Doas Tool Execution
id: 91b8ca78-f205-4826-a3ef-cd8d6b24e97b
version: 1
date: '2024-09-04'
author: Teoderick Contreras, Splunk
status: production
type: Anomaly
description: The following analytic detects the execution of the 'doas' tool on a
Linux host. This tool allows standard users to perform tasks with root privileges,
similar to 'sudo'. The detection leverages data from Linux Auditd, focusing on process names and command-line executions. This activity
is significant as 'doas' can be exploited by adversaries to gain elevated privileges
on a compromised host. If confirmed malicious, this could lead to unauthorized administrative
access, potentially compromising the entire system.
data_source:
- Linux Auditd Syscall
search: '`linux_auditd` type=SYSCALL comm=doas | rename host as dest | stats count
min(_time) as firstTime max(_time) as lastTime by comm exe SYSCALL UID ppid pid
success dest | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`|
`linux_auditd_doas_tool_execution_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 execute this command.
Please update the filter macros to remove false positives.
references:
- https://wiki.gentoo.org/wiki/Doas
- https://www.makeuseof.com/how-to-install-and-use-doas/
tags:
analytic_story:
- Linux Privilege Escalation
- Linux Persistence Techniques
- Compromised Linux Host
asset_type: Endpoint
confidence: 70
impact: 70
message: A SYSCALL - [$comm$] event was executed on host - [$dest$] to execute the "doas" tool.
mitre_attack_id:
- T1548.003
- T1548
observable:
- name: dest
type: Endpoint
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- comm
- exe
- SYSCALL
- UID
- ppid
- pid
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/T1548.003/linux_auditd_doas/linux_auditd_doas.log
source: /var/log/audit/audit.log
sourcetype: linux:audit