IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Potential SharpRDP Behavior Potential Windows Error Manager Masquerading »
Elastic Docs ›Elastic Security Solution [7.16] ›Detections and alerts ›Prebuilt rule reference

Potential Shell via Web Server

edit

Potential Shell via Web Server

edit

Identifies suspicious commands executed via a web server, which may suggest a vulnerability and remote shell access.

Rule type: query

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

References:

Tags:

  • Elastic
  • Host
  • Linux
  • Threat Detection
  • Persistence

Version: 9 (version history)

Added (Elastic Stack release): 7.6.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

Network monitoring or management products may have a web server component that runs shell commands as part of normal behavior.

Rule query

edit
event.category:process and event.type:(start or process_started) and
process.name:(bash or dash) and user.name:(apache or nginx or www or
"www-data")

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 9 (7.12.0 release)
  • Formatting only
Version 8 (7.11.2 release)
  • Formatting only
Version 7 (7.11.0 release)
  • Formatting only
Version 6 (7.10.0 release)
  • Formatting only
Version 5 (7.9.1 release)
  • Formatting only
Version 4 (7.9.0 release)

  • Updated query, changed from:

    process.name:(bash or dash) and user.name:(apache or nginx or www or
"www-data") and event.action:executed
Version 3 (7.8.0 release)

  • Updated query, changed from:

    process.name:bash and user.name:(apache or www or www-data) and
event.action:executed
Version 2 (7.6.1 release)

  • Updated query, changed from:

    process.name: bash and user.name: (apache or www or "wwww-data") and
event.action:executed
« Potential SharpRDP Behavior Potential Windows Error Manager Masquerading »