Try in Splunk Security Cloud

Description

This analytic looks for the execution of powershell.exe with command-line arguments utilized to query for local users. The Get-LocalUser commandlet is used to return a list of all local users. Red Teams and adversaries may leverage this commandlet to enumerate users for situational awareness and Active Directory Discovery.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-08-23
  • Author: Mauricio Velazco, Splunk
  • ID: 85fae8fa-0427-11ec-8b78-acde48001122

ATT&CK

ID Technique Tactic
T1087.001 Local Account Discovery

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where (Processes.process_name="powershell.exe") (Processes.process=*Get-LocalUser*) by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `getlocaluser_with_powershell_filter`

Associated Analytic Story

How To Implement

To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the Endpoint datamodel in the Processes node.

Required field

  • _time

Kill Chain Phase

  • Reconnaissance

Known False Positives

Administrators or power users may use this PowerShell commandlet for troubleshooting.

RBA

Risk Score Impact Confidence Message
15.0 30 50 Local user discovery enumeration using PowerShell on $dest$ by $user$

Reference

Test Dataset

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

source | version: 1