Linux Privilege Capability Discovery via getcap

Flags Linux executions of /getcap with -r to recursively enumerate file capabilities during discovery.

FreeReviewedSigma · Low · v3
Product
linux
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-12-28
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 process executions of the getcap binary, specifically when the command line includes ' -r ' to enumerate file capabilities recursively. Attackers commonly use this to discover misconfigurations that may be leveraged for privilege escalation or further local discovery. Telemetry relies on Linux process creation events including the image path and command-line arguments.

Related detections9 linkedT1083 — drag to rearrange
Possible Nagios XI Path Traversal via Graphtemplates Directory Parameter
Suspicious Credential String Enumeration via findstr to Temp Directory
Suspicious ipconfig Reconnaissance Output Redirected to CentreStack Log File
Possible osTicket PHP Filter Chain Injection via Anonymous Ticket Endpoints (via webserver)
Possible Local File Inclusion Path Traversal Targeting CentreStack Web.config
PUA: TruffleHog Execution on Windows via trufflehog.exe Process Launch
Linux Process Execution of TruffleHog with Secret-Scanning Platforms
Windows: Notepad Password File Discovery via Process Creation
Linux process execution of shell via nice utility
Linux Privilege Capability Discovery via getcap
Pivot detection · T1083 · 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.