Linux auditd: getcap scanning for setuid/setgid-capable files under root

Flags getcap command-line usage scanning / for Linux capability-bearing files via auditd.

FreeReviewedSigma · Low · v3
Product
linux
Service
auditd
Author
Pawel Mazur (SigmaHQ), DRL 1.1
Published
2021-11-28
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags executions of the getcap command that query with the options `-r /`, indicating a recursive scan of the root filesystem for capability-bearing files. Such discovery can help an attacker identify privilege-escalation opportunities from binaries that have elevated capabilities. It relies on Linux auditd telemetry capturing process execution events with the specific command-line arguments `getcap -r /`.

Related detections9 linkedT1548 — drag to rearrange
Possible Nagios XI Path Traversal via Graphtemplates Directory Parameter
Suspicious Credential String Enumeration via findstr to Temp Directory
Malicious Sapphire Sleet TCC Privacy Database Tampering via sqlite3 (via process_creation)
Suspicious storagekitd Spawning Third-Party Filesystem Binary from Library Filesystems (via process_creation)
Malicious Switch User to Rogue Root-Equivalent Account troot (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Suspicious ipconfig Reconnaissance Output Redirected to CentreStack Log File
Possible osTicket PHP Filter Chain Injection via Anonymous Ticket Endpoints (via webserver)
Possible GTFOBins Shell Breakout via Unix Utilities
Linux auditd: getcap scanning for setuid/setgid-capable files under root
Pivot detection · T1548 · 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.