Setuid / Setgid Bit Set via chmodedit

An adversary may add the setuid or setgid bit to a file or directory in order to run a file with the privileges of the owning user or group. An adversary can take advantage of this to either do a shell escape or exploit a vulnerability in an application with the setuid or setgid bit to get code running in a different user’s context. Additionally, adversaries can use this mechanism on their own malware to make sure they’re able to execute in elevated contexts in the future.

Rule type: query

Rule indices:

  • auditbeat-*

Severity: low

Risk score: 21

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 33


  • Elastic
  • Host
  • Linux
  • macOS
  • Threat Detection
  • Privilege Escalation

Version: 7 (version history)

Added (Elastic Stack release): 7.8.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule queryedit

event.category:process AND event.type:(start OR process_started) AND AND process.args:("+s" OR "u+s" OR /4[0-9]{3}/ OR
g+s OR /2[0-9]{3}/)

Threat mappingedit


Rule version historyedit

Version 7 (7.12.0 release)
  • Rule name changed from: Setuid Bit Set via chmod
  • Updated query, changed from:

    event.category:process AND event.type:(start or process_started) AND AND process.args:(u+s OR /4[0-9]{3}/) AND NOT
Version 6 (7.11.2 release)
  • Formatting only
Version 5 (7.11.0 release)
  • Formatting only
Version 4 (7.10.0 release)
  • Formatting only
Version 3 (7.9.1 release)
  • Formatting only
Version 2 (7.9.0 release)
  • Updated query, changed from:

    event.action:(executed OR process_started) AND AND
    process.args:(u+s OR /4[0-9]{3}/) AND NOT