
Summary
The detector flags successful linux auditd execve events that spawn an interactive shell (identified by a TTY) when executed by accounts that typically do not log in or are system/service accounts. It filters for common interactive shells (bash, sh, zsh, etc.) and requires a non-null TTY. It extracts the audit_user from the event (via UID or user field), normalizes to lowercase, and converts UID to a number. The rule triggers when UID is between 1 and 999 or when audit_user matches a predefined list of well-known service accounts (daemon, bin, sys, www-data, sshd, postgres, mysql, etc.). Results are aggregated by destination host to surface who launched a shell, the associated UID/EUID, the shell executable, and the TTY within the time window. The detection is intended to identify password-bypass attempts or unauthorized interactive access on Linux endpoints where auditd is deployed. It maps to MITRE ATT&CK techniques T1078.003 (Valid Accounts: Local Accounts) and T1059.004 (Command Shell). The rule includes drilldown searches for per-host results and a 7-day risk context, and provides intermediate findings such as a message indicating a shell was executed as a non-user account. It relies on ingesting auditd data (SYSCALL, EXECVE, PROCTITLE) and normalizing to the Splunk CIM for cross-source consistency. The rule also notes potential false positives, including legitimate administrator automation running shells under service accounts and legacy UID ranges that may differ by distribution. References and implementation guidance focus on using the Splunk Add-on for Unix and Linux for proper parsing and CIM alignment.
Categories
- Linux
- Endpoint
Data Sources
- Kernel
ATT&CK Techniques
- T1078
- T1059
- T1078.003
- T1059.004
Created: 2026-11-16