Sanitized and composite where needed. No client names, no environment details, just the shape of the work.
Live right now · Identity is the target
The attacker asks nicely now
The fastest-growing intrusions I work start with a person being talked into something: pasting a command, accepting a chat, or resetting an MFA method for someone they think is a coworker. No exploit, no malware at the door. These are the three I handle most.
ClickFix
A fake CAPTCHA or "fix this error" page tells the user to paste a command into the Run box.
look for explorer.exe spawning PowerShell or mshta, RunMRU entries, a download cradle seconds later
Teams vishing
An external Teams chat or call posing as IT support, steering the user toward remote access.
what we did blocked inbound calls from external Teams tenants, which removes the opening move entirely
Help desk impersonation
A caller convinces the service desk to reset MFA or a password, then takes over the account.
what I built a caller-verification decision tree, scenario by scenario, so a convincing story alone cannot reset a password or MFA
Dark web · CrowdStrike Falcon Recon
The credential that came from a cracked download
Falcon Recon, which I run, flagged a user credential for sale on a criminal marketplace. Rather than stop at a password reset, I traced it back: commodity infostealer malware, delivered through cracked software on a personal device that was never part of the managed fleet.
outcome root cause found off the managed fleet, affected user briefed directly
Intrusion analysis · C2
Cobalt Strike, decoded
Beacons hide well in busy Windows estates. I found them through Windows event logging and host artifacts, decoded the embedded payloads to recover the C2 configuration, and contained the activity with hash bans and endpoint isolation.
outcome C2 configuration recovered from the payload itself, intrusion contained
Hunting at scale · Carbon Black to Sentinel
Osquery at fleet scale, hunted in the SIEM
Osquery answers are snapshots, and a snapshot only means something next to everyone else's. I directed a feed of Carbon Black osquery results into Microsoft Sentinel, then built the KQL hunts and dashboard on top: LOLBin and process baselines across every client tenant, tuned often so the outliers stood out instead of drowning in normal. Alongside it, I reviewed aggregated Surveyor reports across every client for all known LOLBins plus the binaries and command lines specific to each case.
outcome one dashboard for the whole client base; outliers surfaced daily, noise tuned out as it appeared
Telemetry engineering · Falcon Data Replicator
From alerts only to full fidelity
Our managed detection provider was receiving an alert-only feed from CrowdStrike, so it could only ever see what had already fired. I upgraded the feed to Falcon Data Replicator, streaming full endpoint telemetry instead of alert summaries.
outcome feed volume up by orders of magnitude; the provider hunts raw events, not just alerts