Welcome
Every alert a SOC analyst triages started somewhere — a rule someone wrote, tested, and shipped because a real attack technique needed a real answer. This blog is that story, one technique at a time.
Cyber Threat Analyzer (CTA) is a Windows-native detection and investigation platform, and this series walks through what it can catch and how it catches it — the event IDs, the logic, the MITRE ATT&CK mapping, and the reasoning behind each detection. If you're building detections of your own, triaging alerts for a living, or just curious what's actually watching your endpoints, this is written for you.
What CTA actually does
WTA isn't a single detection — it's a full pipeline, and each stage of that pipeline is its own detection surface:
- 120+ built-in rules spanning credential access, lateral movement, persistence, defense evasion, and process injection, each mapped to a MITRE ATT&CK technique.
- A behavioral rule engine that scores events instead of just matching them — a single suspicious event rarely triggers an alert on its own, but the right combination of signals does. Process ancestry, unusual DLL loads, and LSASS access attempts are all scored this way, not just flagged on sight.
- Credential attack detection: DCSync, DCShadow (rogue domain controller detection), AS-REP roasting, NTLM relay and downgrade abuse, and account spraying across single and multiple hosts.
- Lateral movement detection: admin share access, remote service creation, WMI/WinRM remote execution, and RDP host-hopping.
- File Integrity Monitoring with real-time ransomware behavior detection — watching for the rate and pattern of file changes that separate an attacker's encryption routine from a backup job.
- A continuous Registry Persistence Monitor, watching the keys attackers actually use to survive a reboot, as they're written — not on a scheduled sweep.
- An on-demand Autoruns-style persistence sweep for the startup locations a live monitor alone won't catch retroactively.
- A Network Threat Monitor, including LLMNR/NBT-NS poisoning detection at the packet level.
- Sigma rule ingestion, so the community detection engineering ecosystem plugs directly into WTA instead of stopping at the door.
- Kill-chain visualization and an investigation workspace that pulls the surrounding evidence — related events, process trees, network activity — around an alert automatically, so triage starts with context instead of a blank search bar.
- Case management and PDF reporting to take an alert from "detected" to "documented," in the same place it was caught.
- A central-server/agent architecture, for teams running this across more than one endpoint rather than one analyst on one machine.
That's the toolbox. Each entry in this series takes one piece of it — one technique, one rule, one detection — and shows the attack, the telemetry it leaves behind, and exactly how CTA turns that telemetry into an alert.
Who this is for
Detection engineers, SOC analysts, and anyone who'd rather understand why an alert fired than just acknowledge it and move on. Some entries will get technical — event IDs, field values, the actual scoring logic — because that's the level triage actually happens at.
New entries go up regularly. If there's a technique you want covered sooner, say so in the comments.
CTA is evolving very fast so stay tuned to this blog for updates and tutorials.
No comments:
Post a Comment