IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Potential Remote Desktop Tunneling Detected Potential SSH Brute Force Detected »
Elastic Docs ›Elastic Security Solution [8.3] ›Detections and alerts ›Prebuilt rule reference

Potential Reverse Shell Activity via Terminal

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Potential Reverse Shell Activity via Terminal

edit

Identifies the execution of a shell process with suspicious arguments which may be indicative of reverse shell activity.

Rule type: eql

Rule indices:

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

Severity: high

Risk score: 73

Runs every: 5 minutes

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

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Host
  • Linux
  • macOS
  • Threat Detection
  • Execution

Version: 2 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.2.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Config

If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define `event.ingested` and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate `event.ingested` to @timestamp for this rule to work.

Rule query

edit
process where event.type in ("start", "process_started") and
process.name in ("sh", "bash", "zsh", "dash", "zmodload") and
process.args:("*/dev/tcp/*", "*/dev/udp/*", "zsh/net/tcp",
"zsh/net/udp")

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 2 (8.2.0 release)
  • Formatting only
« Potential Remote Desktop Tunneling Detected Potential SSH Brute Force Detected »