New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Unusual Process Execution Path - Alternate Data Stream Unusual Process Extension »
Elastic Docs ›Elastic Security Solution [8.10] ›Detections and alerts ›Prebuilt rule reference

Unusual Process Execution on WBEM Path

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

Unusual Process Execution on WBEM Path

edit

Identifies unusual processes running from the WBEM path, uncommon outside WMI-related Windows processes.

Rule type: eql

Rule indices:

  • logs-endpoint.events.process-*
  • logs-system.security*
  • winlogbeat-*
  • logs-windows.*
  • endgame-*

Severity: low

Risk score: 21

Runs every: 60m

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

Maximum alerts per execution: 100

References: None

Tags:

  • Domain: Endpoint
  • OS: Windows
  • Use Case: Threat Detection
  • Tactic: Defense Evasion
  • Data Source: Elastic Defend
  • Rule Type: BBR
  • Data Source: Elastic Endgame

Version: 2

Rule authors:

  • Elastic

Rule license: Elastic License v2

Rule query

edit
process where host.os.type == "windows" and event.type == "start" and
  process.executable : ("?:\\Windows\\System32\\wbem\\*", "?:\\Windows\\SysWow64\\wbem\\*") and
  not process.name : (
    "mofcomp.exe",
    "scrcons.exe",
    "unsecapp.exe",
    "wbemtest.exe",
    "winmgmt.exe",
    "wmiadap.exe",
    "wmiapsrv.exe",
    "wmic.exe",
    "wmiprvse.exe"
  )

Framework: MITRE ATT&CKTM

« Unusual Process Execution Path - Alternate Data Stream Unusual Process Extension »

On this page

Was this helpful?
Feedback