Investigating suspicious AI workflows in Microsoft Entra Agent ID: Autonomous agents, by @mattifestation
Part 1: https://t.co/X7JO1HvrZB
Part 2: https://t.co/E7FQmztOJm
MS AD Kerberos update active since April:
If there is no explicit msds-SupportedEncryptionTypes Active Directory attribute defined the DefaultDomainSupportedEncTypes will be AES-SHA1 (0x18).
This is significantly slower to crack as RC4.
@FlorianHeigl1@Enno_Insinuator Yes that is my understanding. The blocklist should take effect if they used a sig date. Unless we’re missing something obvious here. I feel gaslit half the time I’m trying to make sense of how signing rules are applied or rather misapplied haha.
I decided to publish my internal Azure Entra ID tool. There are a lot of these already available, but I've added some interesting features that have made a difference for me over the years. You can capture token through the browser using playwright
https://t.co/xiZaz0PKsC
#Azure
If you had FOMO during #SOCON2026 or you want to run back your favorite talk, the talk playlist is now available!
👀 Watch all currently available sessions: https://t.co/MrcmfXAmsZ
📊: Access the presentation slides: https://t.co/qSjOXlELgF
SMB share enumeration via ACLs with NetExec🔥
NetExec now detects share permissions via ACL enumeration, instead of trying to write a file. In addition, we can now detect if a user has indirect access to the share, e.g. by having ACL write permissions!
Made by @PytelJack🚀
Round two!
Yesterday was one report, here’s another: an unpatched NTLM coercion via the Windows Search (search-ms://) URI handler.
Same questions about how it got handled. It’s all in the writeup, timeline included.
https://t.co/eMbyEGbx8b
@FlorianHeigl1@Enno_Insinuator it's complicated, lol. Essentially yes, Microsoft-signed components get more implicit trust baked into the OS. But even signed third-party drivers (like the AMD PDFWKRNL.sys I used) can slip through if that specific version/hash isn't on Microsoft's blocklist yet.