Try in Splunk Security Cloud


The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify suspicious PowerShell execution. Script Block Logging captures the command sent to PowerShell, the full command to be executed. Upon enabling, logs will output to Windows event logs. Dependent upon volume, enable on critical endpoints or all.
This analytic identifies the usage of Get-WMIObject Win32_Group, which is typically used as a way to identify groups on the endpoint. Typically, by itself, is not malicious but may raise suspicion based on time of day, endpoint and username.
During triage, review parallel processes using an EDR product or 4688 events. It will be important to understand the timeline of events around this activity. Review the entire logged PowerShell script block.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2021-09-14
  • Author: Michael Haag, Splunk
  • ID: 69df7f7c-155d-11ec-a055-acde48001122


ID Technique Tactic
T1069 Permission Groups Discovery Discovery
T1069.001 Local Groups Discovery
`powershell` EventCode=4104 Message = "*Get-WMIObject*" AND Message = "*Win32_Group*" 
| stats count min(_time) as firstTime max(_time) as lastTime by  Message OpCode ComputerName User EventCode
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `get_wmiobject_group_discovery_with_script_block_logging_filter`

Associated Analytic Story

How To Implement

To successfully implement this analytic, you will need to enable PowerShell Script Block Logging on some or all endpoints. Additional setup here

Required field

  • _time
  • EventCode
  • Message
  • ComputerName
  • User

Kill Chain Phase

  • Reconnaissance

Known False Positives

False positives may be present. Tune as needed.


Risk Score Impact Confidence Message
15.0 30 50 System group discovery enumeration on $dest$ by $user$.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1