Detection of Unconstrained Delegation Discovery via PowerShell
Adversaries are utilizing the Get-ADComputer PowerShell cmdlet to enumerate Active Directory objects configured for unconstrained delegation, a reconnaissance step often preceding ticket-based credential theft.
This threat brief identifies reconnaissance activity targeting Active Directory configurations. Attackers leverage the Get-ADComputer cmdlet to scan for machines with specific attributes that indicate unconstrained delegation. Unconstrained delegation allows a server to impersonate a domain user to any other service in the forest, making these systems high-value targets for attackers seeking to escalate privileges or move laterally through the domain. By identifying these computers, an attacker can plan credential harvesting operations, such as capturing TGTs from a compromised service account. Defenders should monitor PowerShell Script Block logs for queries specifically filtering for delegation-related LDAP flags or properties. This activity is a common precursor to advanced lateral movement and credential access techniques in Windows environments.
Attack Chain
- Attacker establishes initial access on a domain-joined machine.
- Attacker loads the ActiveDirectory PowerShell module.
- Attacker executes Get-ADComputer with flags to query TrustedForDelegation properties.
- Attacker parses output to identify specific high-value targets.
- Attacker attempts to compromise the identified service account or host.
- Attacker harvests credentials or impersonates users via the delegation vulnerability.
- Attacker proceeds to lateral movement or further domain privilege escalation.
Impact
Successful discovery leads to the identification of critical infrastructure in a Windows domain environment. If exploited, attackers can gain the ability to impersonate domain users, leading to widespread unauthorized access, privilege escalation, and potential full domain compromise.
Recommendation
- Enable PowerShell Script Block Logging (Event ID 4104) across all domain-joined Windows endpoints.
- Deploy the provided Sigma rule to detect suspicious Get-ADComputer cmdlet usage focused on delegation properties.
- Audit high-privilege service accounts and limit the use of unconstrained delegation where not strictly required by application architecture.
Immediate actions
Enable PowerShell Script Block Logging (Event ID 4104) across all domain-joined assets.
Threat Hunt
Search for Event ID 4104 logs containing Get-ADComputer with parameters related to delegation.
Data: PowerShell Script Block logs
Detection coverage 1
Detect Unconstrained Delegation Discovery via Get-ADComputer
mediumDetects the use of the Get-ADComputer cmdlet in order to identify systems which are configured for unconstrained delegation.
Detection queries are available on the platform. Get full rules →