Linux System Owner or User Discovery via Common Utility Execution

Flags execution of Linux user/system identification utilities such as whoami and id.

FreeReviewedSigma · Low · v3
Product
linux
Service
auditd
Author
Timur Zinniatullin, oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-21
Updated
2026-07-31

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies execution events for common Linux system owner and user discovery utilities such as whoami, hostname, id, uname, users, w, who, and last. Adversaries often run these commands during automated discovery to gather context about the host and current user, which can influence subsequent actions. The detection relies on Linux auditd telemetry capturing process execution (EXECVE) for the specified command names.

Related detections9 linkedT1033 — drag to rearrange
Suspicious Whoami Execution With Output Redirected to a File (via process_creation)
Possible Logged-On Session Discovery via Quser or Qwinsta (via process_creation)
Suspicious Reconnaissance Spawned by Injected SearchProtocolHost via process_creation
Windows Process Creation: whoami.exe Executed With /all for Full Identity Enumeration
Linux Process Execution of esxcli Network Commands for ESXi Network Discovery
Linux Process Execution of esxcli VM Listing Commands
Linux ESXi esxcli VSAN Information Discovery via esxcli Command
Linux Process Creation: ESXi esxcli system discovery via system namespace
Linux ESXi esxcli Storage Information Discovery via esxcli storage commands
Linux System Owner or User Discovery via Common Utility Execution
Pivot detection · T1033 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.