The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify the execution of the
Get-ADUser commandlet with specific parameters.
Get-ADUser is part of the Active Directory PowerShell module used to manage Windows Active Directory networks. As the name suggests,
Get-ADUser is used to query for domain users. With the appropiate parameters, Get-ADUser allows adversaries to discover domain accounts with Kerberos Pre Authentication disabled.\ Red Teams and adversaries alike use may abuse Get-ADUSer to enumerate these accounts and attempt to crack their passwords offline.
- Type: TTP
Product: Splunk Behavioral Analytics
- Last Updated: 2022-11-14
- Author: Michael Haag, Splunk
- ID: d57b4d91-fc91-4482-a325-47693cced1eb
Kill Chain Phase
- CIS 10
1 2 3 4 5 6 7 8 9 10 11 $main = from source | eval timestamp = time | eval metadata_uid = metadata.uid | eval device_hostname = device.hostname | eval process_file = process.file | eval process_file_path = process_file.path | eval process_uid = process.uid | eval process_cmd_line = process.cmd_line | eval actor_user = actor.user | eval actor_user_uid = actor_user.uid | where process_cmd_line LIKE "%4194304%" AND match(process_cmd_line, /(?i)get-aduser/)=true --finding_report--
The SPL above uses the following Macros:
windows_powershell_disabled_kerberos_pre-authentication_discovery_get-aduser_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
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/18.104.22.168/GetDataIn/AddPowerShell#Configure_module_logging_for_PowerShell.
Known False Positives
Administrators or power users may use search for accounts with Kerberos Pre Authentication disabled for legitimate purposes.
Associated Analytic Story
|54.0||60||90||Disabled Kerberos Pre-Authentication Discovery With Get-ADUser from $dest_device_id$|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1