
building @BreachLens (BEC forensics for M365) cybersecurity nerd who ships learning in public, breaking in private python stdlib only, zero dependencies
the internet
Joined June 2024
- Tweets515
- Following43
- Followers47
- Likes274
cogio retweeted
Since we all had a fuck you money week, I’ll reintroduce you to the three most life changing purchases I’ve ever made.
Thank me later. No ref links just straight alpha.
cogio retweeted
Interviewer:
An OTP is valid for 60 seconds, but the server never stores it.
How does it verify a code it doesn’t even 'know'?🤔
cogio retweeted
The Huntress SOC is observing the use of Nightmare-Eclipse's BlueHammer, RedSun, and UnDefend exploitation techniques.
Investigation by: @wbmmfq, @Curity4201, + @_JohnHammond 🧵👇
M365 forensics tip via @BreachLens: message trace logs only retain data for 10 days by default. if you start a BEC investigation after that window, your email flow evidence is gone. export early, investigate later. breachlens.io
3
157
BEC is the only $2.7B/year crime category where most investigations are done with the same tools you'd use to troubleshoot a printer. the tooling gap is wild and nobody in enterprise security seems embarrassed about it
126
DFIR question via @BreachLens: after closing a BEC case, do you go back and check for other compromised mailboxes in the same tenant? lateral movement inside M365 is underreported. breachlens.io
92
hot take: security vendors love selling dashboards. nobody sells you a tool that just answers 'what did the attacker do in this mailbox for the last 30 days'. that's the whole question
74
biggest competitive advantage as a solo founder: I can ship a fix in 20 minutes while enterprise vendors are still scheduling the triage meeting
69
M365 forensics tip via @BreachLens: always correlate inbox rule changes with MailItemsAccessed events. the rules show what attackers set up, the access logs show what they actually read. that combo is the full BEC story and most people miss half of it
77
parsing M365 audit logs is like reading a novel where every character has 3 aliases and the timeline is shuffled. built 6 parsers for @BreachLens to untangle this mess. stdlib only, no pip install prayer circles
45
M365 forensics tip via @BreachLens: delegate access lets attackers read mailboxes without triggering MailItemsAccessed in the victim's logs. always check Add-MailboxPermission events when scoping a BEC. breachlens.io
55
BEC stat via @BreachLens: attackers don't need malware. one stolen credential and one forwarding rule is enough to reroute six figures in wire transfers. your M365 logs already have the evidence. breachlens.io
47
the weirdest part of building DFIR tools is that your best test data comes from real breaches. sanitized enough to be legal, detailed enough to be useful. every fixture file has a story nobody can tell
28
every BEC investigation has the same bottleneck: not the analysis, the data wrangling. 6 different M365 log formats, 4 timestamp styles, zero consistency. @BreachLens normalizes all of it from one upload so you can focus on the actual investigation
41
funniest bug this month: risk scorer kept flagging IT admins as attackers because they log in from 3 cities in one day. turns out real humans also travel. added a velocity threshold and false positives dropped 80%
22
DFIR question via @BreachLens: what's your biggest frustration with M365 audit log exports — format inconsistencies, missing events, or retention gaps? building fixes for all three. breachlens.io
59
hot take: if your investigation tool needs an internet connection to parse a local log file, you've added a dependency to your incident response plan
22
most BEC cases end at "we reset the password and enabled MFA." that's containment, not investigation. rogue OAuth tokens, silent forwarding rules, delegate access — all survive a password reset. @BreachLens maps every persistence vector from one log upload
24







