Windows PowerView AD Access Control List Enumeration

Try in Splunk Security Cloud

Description

The following analytic detects the execution of PowerView PowerShell cmdlets Get-ObjectAcl or Get-DomainObjectAcl, which are used to enumerate Access Control List (ACL) permissions for Active Directory objects. It leverages Event ID 4104 from PowerShell Script Block Logging to identify this activity. This behavior is significant as it may indicate an attempt to discover weak permissions in Active Directory, potentially leading to privilege escalation. If confirmed malicious, attackers could exploit these permissions to gain unauthorized access or escalate their privileges within the network.

• Type: TTP

• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

• Last Updated: 2024-05-17
• Author: Mauricio Velazco, Splunk
• ID: 39405650-c364-4e1e-a740-32a63ef042a6

Annotations

ATT&CK

ATT&CK

ID	Technique	Tactic
T1078.002	Domain Accounts	Defense Evasion, Persistence, Privilege Escalation, Initial Access

T1069

Permission Groups Discovery

Discovery

Kill Chain Phase

• Exploitation
• Installation
• Delivery

NIST

• DE.CM

CIS20

• CIS 10

CVE

Search

 `powershell` EventCode=4104  (ScriptBlockText=*get-objectacl* OR ScriptBlockText=*Get-DomainObjectAcl* ) 
| stats count min(_time) as firstTime max(_time) as lastTime by Opcode Computer UserID EventCode ScriptBlockText 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `windows_powerview_ad_access_control_list_enumeration_filter`

Macros

The SPL above uses the following Macros:

• powershell
• security_content_ctime

windows_powerview_ad_access_control_list_enumeration_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

• _time
• EventCode
• ScriptBlockText
• Opcode
• UserID

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 may leverage PowerView for legitimate purposes, filter as needed.

Associated Analytic Story

• Active Directory Discovery
• Active Directory Privilege Escalation
• Rhysida Ransomware

RBA

Risk Score	Impact	Confidence	Message
20.0	40	50	PowerView AD acccess control list enumeration detected on $Computer$

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

• https://attack.mitre.org/techniques/T1078/002/
• https://medium.com/r3d-buck3t/enumerating-access-controls-in-active-directory-c06e2efa8b89
• https://www.ired.team/offensive-security-experiments/active-directory-kerberos-abuse/abusing-active-directory-acls-aces
• https://powersploit.readthedocs.io/en/latest/Recon/Get-DomainObjectAcl/

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2