Detection: Linux Auditd Whoami User Discovery

Description

The following analytic detects the suspicious use of the whoami command, which may indicate an attacker trying to gather information about the current user account on a compromised system. The whoami command is commonly used to verify user privileges and identity, especially during initial stages of an attack to assess the level of access. By monitoring for unusual or unauthorized executions of whoami, this analytic helps in identifying potential reconnaissance activities, enabling security teams to take action before the attacker escalates privileges or conducts further malicious operations.

Search

1`linux_auditd` type=SYSCALL comm=whoami OR exe= "*/whoami" 
2| rename host as dest 
3| stats count min(_time) as firstTime max(_time) as lastTime by comm exe  SYSCALL UID ppid pid dest success 
4| `security_content_ctime(firstTime)` 
5| `security_content_ctime(lastTime)`
6| `linux_auditd_whoami_user_discovery_filter`

Data Source

Name	Platform	Sourcetype	Source
Linux Auditd Syscall	Linux	'linux:audit'	'/var/log/audit/audit.log'

Macros Used

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

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.

Associated Analytic Story

• Compromised Linux Host

• Linux Living Off The Land

• Linux Persistence Techniques

• Linux Privilege Escalation

Risk Based Analytics (RBA)

References

• https://www.splunk.com/en_us/blog/security/deep-dive-on-persistence-privilege-escalation-technique-and-detection-in-linux-platform.html

• https://github.com/peass-ng/PEASS-ng/tree/master/linPEAS

Detection Testing

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 2