The following analytic utilizes PowerShell Script Block Logging (EventCode=4104) to identify commandlets used by the PowerView hacking tool leveraged to discover Windows endpoints with Kerberos Constrained Delegation. Red Teams and adversaries alike may leverage use this technique for situational awareness and Active Directory Discovery.
- Type: TTP
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2022-03-31
- Author: Mauricio Velazco, Splunk
- ID: 86dc8176-6e6c-42d6-9684-5444c6557ab3
|T1018||Remote System Discovery||Discovery|
Kill Chain Phase
- CIS 3
- CIS 5
- CIS 16
1 2 3 4 5 `powershell` EventCode=4104 (Message = "*Get-DomainComputer*" OR Message = "*Get-NetComputer*") AND (Message = "*-TrustedToAuth*") | stats count min(_time) as firstTime max(_time) as lastTime by EventCode Message ComputerName User | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_powerview_constrained_delegation_discovery_filter`
The SPL above uses the following Macros:
Note that windows_powerview_constrained_delegation_discovery_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
The following analytic requires PowerShell operational logs to be imported. Modify the powershell macro as needed to match the sourcetype or add index. This analytic is specific to 4104, or PowerShell Script Block Logging.
Known False Positives
Administrators or power users may leverage PowerView for system management or troubleshooting.
Associated Analytic story
|35.0||50||70||Suspicious PowerShell Get-DomainComputer was identified on endpoint $ComputerName$|
source | version: 1