I'll start:
* Detect Kerberoasting:
trimarcsecurity.com/single-post/Tr…
* Detect PW Spraying:
trimarcsecurity.com/single-post/20…
#BlueTeam
adsecurity.org/?p=1790
microsoft.com/en-us/download…
github.com/microsoft/Aaro…
docs.microsoft.com/en-us/windows-…
Note: Not exactly simple, but effective. Ensure service supports GMSA config.
Restricts authentication to Kerberos AES, prevents specific credential caching on system, & protects against Kerberos delegation attacks (+others).
(does require some OS & DC support for full protection)
docs.microsoft.com/en-us/windows-…
docs.microsoft.com/en-us/windows-…
channel9.msdn.com/Events/Ignite/…
Preferably "Send NTLMv2 response only\refuse LM & NTLM"
Enable NTLM auditing to discover use:
docs.microsoft.com/en-us/windows/…
Fun Fact:
When @jaredhaight & I were working to create labs for our #DerbyCon training on Windows Security (ok, so 99.9% Jared), we noticed that many of the recon tools didn't work against 2016, but did for 2012R2.
For example: Newer Win10 versions prevent users from enumerating local Admin group membership.
gallery.technet.microsoft.com/SAMRi10-Harden…