Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts WMI Lateral Movement Detection Guide

security analyst security skill risk: medium

WMI Lateral Movement Detection Guide

Outlines steps to parse Windows Event ID 4688 and Sysmon Event ID 1 logs for WmiPrvSE.exe child processes, analyze command lines, and check WMI-Activity events to detect lateral mo…

SKILL 4 files · 2 folders

SKILL.md
---
name: hunting-for-lateral-movement-via-wmi
description: "Detect WMI-based lateral movement by analyzing Windows Event ID 4688 process creation and Sysmon Event ID 1 for"
---
# Hunting for Lateral Movement via WMI

## Overview

Windows Management Instrumentation (WMI) is commonly abused for lateral movement via `wmic process call create` or Win32_Process.Create() to execute commands on remote hosts. Detection focuses on identifying WmiPrvSE.exe spawning child processes (cmd.exe, powershell.exe) in Windows Security Event ID 4688 and Sysmon Event ID 1 logs, along with WMI-Activity/Operational events (5857, 5860, 5861) for event subscription persistence.


## When to Use

- When investigating security incidents that require hunting for lateral movement via wmi
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques

## Prerequisites

- Windows Security Event Logs with Process Creation auditing enabled (Event 4688 with command line)
- Sysmon installed with Event ID 1 (Process Creation) configured
- Python 3.9+ with `python-evtx`, `lxml` libraries
- Understanding of WMI architecture and WmiPrvSE.exe behavior

## Steps

### Step 1: Parse Process Creation Events
Extract Event ID 4688 and Sysmon Event 1 entries from EVTX files.

### Step 2: Detect WmiPrvSE Child Processes
Flag processes where ParentImage/ParentProcessName is WmiPrvSE.exe, indicating remote WMI execution.

### Step 3: Analyze Command Line Patterns
Identify suspicious command lines matching WMI lateral movement patterns (cmd.exe /q /c, output redirection to admin$ share).

### Step 4: Check WMI Event Subscriptions
Parse WMI-Activity/Operational log for event consumer creation indicating persistence.

## Expected Output

JSON report with WMI-spawned processes, suspicious command lines, WMI event subscription alerts, and timeline of lateral movement activity.

REQUIRED CONTEXT

  • Windows Security Event Logs (Event 4688)
  • Sysmon Event ID 1 logs
  • WMI-Activity/Operational logs

TOOLS REQUIRED

  • python-evtx
  • lxml

EXPECTED OUTPUT

Format
json
Schema
json · WMI-spawned processes, suspicious command lines, WMI event subscription alerts, timeline of lateral movement activity
Constraints
  • include WMI-spawned processes
  • include suspicious command lines
  • include WMI event subscription alerts
  • include timeline of lateral movement activity

CAVEATS

Dependencies
  • Windows Security Event Logs with Process Creation auditing enabled (Event 4688 with command line)
  • Sysmon installed with Event ID 1 (Process Creation) configured
  • Python 3.9+ with `python-evtx`, `lxml` libraries
  • Understanding of WMI architecture and WmiPrvSE.exe behavior
Missing context
  • Exact parsing logic or code examples
  • Concrete command-line patterns or regex
  • Detailed output JSON schema
Ambiguities
  • Description field is truncated mid-sentence ('for')

QUALITY

OVERALL
0.60
CLARITY
0.75
SPECIFICITY
0.55
REUSABILITY
0.65
COMPLETENESS
0.50

IMPROVEMENT SUGGESTIONS

  • Complete the truncated description sentence
  • Add concrete examples (e.g., sample queries or Python snippets) under each step
  • Define the exact structure of the expected JSON report

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR SECURITY ANALYST