--- title: "GetLocalUser with PowerShell Script Block" excerpt: "Account Discovery , Local Account " categories: - Endpoint last_modified_at: 2021-08-23 toc: true toc_label: "" tags: - Account Discovery - Local Account - Discovery - Discovery - Splunk Enterprise - Splunk Enterprise Security - Splunk Cloud --- [Try in Splunk Security Cloud](https://www.splunk.com/en_splunk_app_enrichmentus/cyber-security.html){: .btn .btn--success} #### Description The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify the execution of the `Get-LocalUser` commandlet. 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](https://github.com/splunk/security_content/wiki/Detection-Analytic-Types) - **Product**: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud - **Last Updated**: 2021-08-23 - **Author**: Mauricio Velazco, Splunk - **ID**: 2e891cbe-0426-11ec-9c9c-acde48001122 #### Annotations
ATT&CK
| ID | Technique | Tactic | | -------------- | ---------------- |-------------------- | | [T1087](https://attack.mitre.org/techniques/T1087/) | Account Discovery | Discovery | | [T1087.001](https://attack.mitre.org/techniques/T1087/001/) | Local Account | Discovery |
Kill Chain Phase
* Reconnaissance
NIST
CIS20
CVE
#### Search ``` `powershell` EventCode=4104 (Message = "*Get-LocalUser*") | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Message ComputerName User | `security_content_ctime(firstTime)` | `getlocaluser_with_powershell_script_block_filter` ``` #### Macros The SPL above uses the following Macros: * [powershell](https://github.com/splunk/security_content/blob/develop/macros/powershell.yml) * [security_content_ctime](https://github.com/splunk/security_content/blob/develop/macros/security_content_ctime.yml) Note that **getlocaluser_with_powershell_script_block_filter** is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL. #### Required field * _time #### 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 https://docs.splunk.com/Documentation/UBA/5.0.4.1/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell. #### Known False Positives Administrators or power users may use this PowerShell commandlet for troubleshooting. #### Associated Analytic story * [Active Directory Discovery](/stories/active_directory_discovery) #### RBA | Risk Score | Impact | Confidence | Message | | ----------- | ----------- |--------------|--------------| | 15.0 | 30 | 50 | Local user discovery enumeration using PowerShell on $dest$ by $user$ | #### Reference * [https://attack.mitre.org/techniques/T1087/001/](https://attack.mitre.org/techniques/T1087/001/) #### Test Dataset Replay any dataset to Splunk Enterprise by using our [replay.py](https://github.com/splunk/attack_data#using-replaypy) tool or the [UI](https://github.com/splunk/attack_data#using-ui). Alternatively you can replay a dataset into a [Splunk Attack Range](https://github.com/splunk/attack_range#replay-dumps-into-attack-range-splunk-server) * [https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1087.001/AD_discovery/windows-powershell.log](https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1087.001/AD_discovery/windows-powershell.log) [*source*](https://github.com/splunk/security_content/tree/develop/detections/endpoint/getlocaluser_with_powershell_script_block.yml) \| *version*: **1**