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

PowerShell spawning Cmd

edit

PowerShell spawning Cmd

edit

Identifies a suspicious parent child process relationship with cmd.exe descending from PowerShell.exe.

Rule type: query

Rule indices:

  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

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: 100

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Execution

Version: 8 (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

Rule query

edit
event.category:process and event.type:(start or process_started) and
process.parent.name:powershell.exe and process.name:cmd.exe

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

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

  • Updated query, changed from:

    process.parent.name:powershell.exe and process.name:cmd.exe
Version 2 (7.7.0 release)
  • Formatting only
« Potential Windows Error Manager Masquerading Privilege Escalation via Named Pipe Impersonation »