Our team had a great time at this month’s SecKC meetup! Tom Pohl shared insights on Microsoft CA exploits, showing how small misconfigurations can lead all the way to full domain admin takeover.
Big thanks to the SecKC community for the warm welcome and for making cybersecurity even more fun with a Halloween costume party twist.
Learn more about SecKC: https://www.seckc.org/
After my recent post searching for a Hacker group on DMR, I landed on the @sec_kc TalkGroup at 312752.
After some failed QSOs, I decided to look for a means to notify myself via Discord when someone keyed up the TalkGroup.
Enter n8acl's/bm_monitor script. It needed a few updates and tweaks, which lead to me forking the project and then eventually breaking my fork and establishing a new root.
I'm just a hacker, so things work but may not be beautiful by proper standards.
Sharing here for reach
> For too long Incident Response has relied on industry experience, consultants, or 4000 page compliance frameworks that are too hard digest.
> I am going to fix this. I am writing a fully open-source "Awesome Incident Response guide".
- hevnsnt
https://github.com/hevnsnt/Awesome_Incident_Response
#infosec #incidentresponse #seckc