mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Nasreddine Bencherchali
11c909f725
* Add YAML formatting and validation infrastructure - Add yamlfmt configuration (.yamlfmt) with 4-space indent, LF line endings - Add yamllint configuration (.yamllint) for syntax validation (detections/ only) - Add pre-commit hook for automatic YAML formatting - Add CI validation script with unified error output - Add GitHub Actions workflow for PR validation - Add documentation for setup and usage - Support custom yamlfmt binary path via --yamlfmt-path flag * comment yaml check from pre-commit * apply yamlfmt * Update yaml-validation.yml * Update yaml-validation.yml * application folder search formatting * cloud folder search formatting * web folder search formatting * network folder search formatting * endpoint folder search formatting * resolve first conflict * apply formatting * remove additional pipe * Update README.md * update versions * restore and update formatting (#3920) --------- Co-authored-by: Bhavin Patel <bhavin.j.patel91@gmail.com>
47 lines
2.6 KiB
YAML
47 lines
2.6 KiB
YAML
name: GetLocalUser with PowerShell Script Block
|
|
id: 2e891cbe-0426-11ec-9c9c-acde48001122
|
|
version: 10
|
|
date: '2026-02-25'
|
|
author: Mauricio Velazco, Splunk
|
|
status: production
|
|
type: Hunting
|
|
description: The following analytic detects the execution of the `Get-LocalUser` PowerShell commandlet using PowerShell Script Block Logging (EventCode=4104). This commandlet lists all local users on a system. The detection leverages script block text from PowerShell logs to identify this activity. Monitoring this behavior is significant as adversaries and Red Teams may use it to enumerate local users for situational awareness and Active Directory discovery. If confirmed malicious, this activity could lead to further reconnaissance, enabling attackers to identify potential targets for privilege escalation or lateral movement.
|
|
data_source:
|
|
- Powershell Script Block Logging 4104
|
|
search: |-
|
|
`powershell` EventCode=4104 (ScriptBlockText = "*Get-LocalUser*")
|
|
| fillnull
|
|
| stats count min(_time) as firstTime max(_time) as lastTime
|
|
BY dest signature signature_id
|
|
user_id vendor_product EventID
|
|
Guid Opcode Name
|
|
Path ProcessID ScriptBlockId
|
|
ScriptBlockText
|
|
| `security_content_ctime(firstTime)`
|
|
| `security_content_ctime(lastTime)`
|
|
| `getlocaluser_with_powershell_script_block_filter`
|
|
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://help.splunk.com/en/security-offerings/splunk-user-behavior-analytics/get-data-in/5.4.1/add-other-data-to-splunk-uba/configure-powershell-logging-to-see-powershell-anomalies-in-splunk-uba.
|
|
known_false_positives: Administrators or power users may use this PowerShell commandlet for troubleshooting.
|
|
references:
|
|
- https://attack.mitre.org/techniques/T1087/001/
|
|
- https://www.splunk.com/en_us/blog/security/hunting-for-malicious-powershell-using-script-block-logging.html
|
|
tags:
|
|
analytic_story:
|
|
- Active Directory Discovery
|
|
- Malicious PowerShell
|
|
asset_type: Endpoint
|
|
mitre_attack_id:
|
|
- T1059.001
|
|
- T1087.001
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1087.001/AD_discovery/windows-powershell-xml.log
|
|
source: XmlWinEventLog:Microsoft-Windows-PowerShell/Operational
|
|
sourcetype: XmlWinEventLog
|