
Scott Sutherland
2.1K posts

Scott Sutherland
@_nullbind
Security Researcher @NetSPI | PowerUpSQL Author







"Offense and defense aren't peers. Defense is offense's child." - @JohnLaTwC We built an LLM-powered AMSI provider and paired it against a red team agent. Then, @0xdab0 wrote a blog about it: dreadnode.io/blog/llm-power… A few observations from the experiment: >>> To advance, we must generate unique, ground-truth datasets. >>> Defenses will need to live at the edge. >>> The real potential lies in the interaction between red and blue. >>> This is a blueprint for generative adversarial reinforcement learning.





⚡️Huge announcement today! We are joining @CoalitionSec! Read more from co-founders @malcomvetter & @jreynoldsdev: wirespeed.co/posts/coalitio…














Recently, we looked at Active Directory built-in groups (x.com/PyroTek3/statu…) This week, we focus on Active Directory Group Policy Objects (GPOs). GPOs should be audited regularly to identify the configured owner as well as the permissions to ensure they are appropriate. In the provided script, I added a column called default, so you can look for the non-default owners and permissions to correct. Group Policy in Active Directory is very powerful, so it's important to understand who the owners are. The Group Policy Owner can change permissions on the GPO and get edit rights to the GPO. GPO Owner should only be set to "Domain Admins" or "Enterprise Admins". Changing the owner can be done by opening Active Directory Users and Computers (ADUC), going to the View menu option and selecting Advanced. Then browse down to System, Policies. Right-click on the desired GPO ID and select Properties. Then go to the Security tab and click on the Advanced button. Click on the Change option next to the owner and change the owner to "Domain Admins". Review the permissions that are flagged non-default in the script and ensure they are appropriate. No standard users should have Edit rights. Also, edit rights (& full control) on any GPOs linked to the Domain root and the Domain Controllers OU should only be configured for AD Admins (preferably "Domain Admins"). Script leveraging the Group Policy PowerShell module: github.com/PyroTek3/Misc/… #ActiveDirectorySecurityTip





