Tampering of Bash Command-Line History

edit

Adversaries may attempt to clear or disable the Bash command-line history in an attempt to evade detection or forensic investigations.

Rule type: eql

Rule indices:

  • auditbeat-*
  • logs-endpoint.events.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

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

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Host
  • Linux
  • Threat Detection
  • Defense Evasion

Version: 6 (version history)

Added (Elastic Stack release): 7.9.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
process where event.type in ("start", "process_started") and (
(process.args : ("rm", "echo") and process.args : (".bash_history",
"/root/.bash_history", "/home/*/.bash_history")) or (process.name :
"history" and process.args : "-c") or (process.args : "export" and
process.args : ("HISTFILE=/dev/null", "HISTFILESIZE=0")) or
(process.args : "unset" and process.args : "HISTFILE") or
(process.args : "set" and process.args : "history" and process.args :
"+o") )

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 6 (7.12.0 release)
  • Rule name changed from: Deletion of Bash Command Line History
  • Updated query, changed from:

    event.category:process AND event.type:(start or process_started) AND
    process.name:rm AND
    process.args:/\/(home\/.{1,255}|root)\/\.bash_history/
Version 5 (7.11.2 release)
  • Formatting only
Version 4 (7.11.0 release)
  • Formatting only
Version 3 (7.10.0 release)
  • Formatting only
Version 2 (7.9.1 release)
  • Formatting only