Investigation Cases
Why: The closest thing to the real L1 analyst job, and the highest signal per hour.
Full blue-team CTF investigations published as reports: timeline, IOCs, ATT&CK mapping, remediation.
Every case, listed and readable. The orbit on the homepage is the show — this is the record.
Why: The closest thing to the real L1 analyst job, and the highest signal per hour.
Full blue-team CTF investigations published as reports: timeline, IOCs, ATT&CK mapping, remediation.
Why: Experience on paper before the first job.
Build an AD network, attack it with Atomic Red Team, detect in Splunk, then investigate and report.
Why: The interview centrepiece: AI where the SOC actually hurts.
An AI analyst that triages alerts, maps ATT&CK, drafts incident reports, and suggests remediation.
Why: The red-team bridge employers love.
Run an atomic test, check if the SIEM alerts, write a detection if it misses, then tune it.
Why: The core detection-engineering workflow, end to end.
Data source to detection logic to validation with Atomic Red Team to deploy and monitor.
Why: Cloud-SOC skill and SC-200 revision in one.
Ingest telemetry into Microsoft Sentinel and write custom KQL analytics rules.
Why: The always-on detection playground.
Ship Sysmon endpoint telemetry into Wazuh with custom rules and ATT&CK mapping.
Why: A core defensive control every endpoint needs.
Watch critical files, hash them, and alert the moment one changes unexpectedly.
Why: Learn endpoint defence by hunting the threat directly.
Inspect processes and OS hooks to surface behaviour consistent with keylogging.
Why: A scripted end-to-end IR engagement, written up properly.
Work a ransomware PCAP through the full NIST IR lifecycle as a PDF report.
Why: A literal daily L1 task and a quick win.
Analyse 10-15 real phishing samples: headers, SPF/DKIM, detonation, IOCs, verdict.
Why: Shows the writing and communication managers prize.
Profile a threat actor, map TTPs in ATT&CK Navigator, write a BLUF intel report.
Why: Real attackers, real data.
Deploy an internet-facing honeypot on a VPS, log 7 days of activity, document IOCs and TTPs.
Why: The foundational recon tool, built not just used.
Scan hosts for open ports and grab service banners the way Nmap does under the hood.
Why: See the wire the way Wireshark does.
Capture and dissect live network packets, printing protocol and header detail.
Why: Understand detection by writing one from scratch.
A Python IDS that inspects live traffic against signature rules and logs alerts.
Why: Understand rule ordering and packet filtering by building the engine.
Apply a configurable ruleset to simulated traffic and show what gets allowed or dropped.
Why: The red-team angle: build it broken, break it, fix it.
Build an app with intentional vulns, exploit every OWASP Top 10 class, then patch and verify.
Why: The offensive complement to the OWASP lab.
Crawl a target site and probe for common SQLi and XSS injection points.
Why: Stops the attack most breaches start with.
Score URLs on lexical and WHOIS features with a classifier to flag phishing pages.
Why: Understand why weak hashes fall, so you can defend them.
Run dictionary and brute-force attacks against common hash types.
Why: Applied cryptography you can message on.
A chat app with RSA key exchange and AES message encryption over WebSockets.