SOC analyst practice cases
Each case starts with an escalated alert. Hunt the logs, find the root cause and choose the response. Free, in your browser.
Start a case22 cases · KQL and SPL · 13 learning paths
Endpoint
A CAPTCHA that asked you to paste something
The Adobe update that came with remote access
The coding assistant read an SSH key
Mass file modification on file server
Certutil and PowerShell bypass on many machines at night
Fake PDF viewer installs a hidden scheduled task
Aggressive scanning and a blocked LSASS access
Exposed RDP, credential dumping and shadow copies deleted
Identity
A service desk call, a new MFA method, and then?
A Teams call from "the help desk", then Quick Assist
Impossible-travel sign-in flagged by the rule
Phished user, token replay and internal phishing
Device code phishing and mailbox theft
Cloud
npm install, and then the cloud keys moved
A new workflow ran once, and the deploy key moved
Illicit OAuth app reading mail and cloud files
Network
Exploit attempts on the VPN appliance: did one get in?
SSH switched on for a production hypervisor
VPN account brute forced, admin access to file server
Web shell on the public web server, pivot to SQL
Insider
Learning paths
A set of lessons and cases on one theme, in the right order.
- This year’s attacksThe patterns 2026 incident response saw most: help desk calls, ClickFix, fake updates with remote access, npm worms, exploited VPN appliances, fake IT workers, hypervisor takeovers, hijacked AI coding agents, fake help desks on Teams and workflows that steal CI secrets. Every attempt is a different version.11 steps
- Identity and emailSign-in logs, MFA, stolen session tokens, inbox rules and app consent: how accounts get taken over, and how you prove it.5 steps
- Windows and Sysmon loggingEvent IDs, logon types, process trees and scheduled tasks: read an endpoint the way an analyst does.5 steps
- Network, proxy and DNSVPN, proxy and firewall logs: spot the outside getting in, and the inside reaching out.3 steps
- Incident responseScope, contain and report: what you do after the alert turns out to be real.5 steps
- Windows endpoint, hands-onA simulated Windows box in your browser: run real commands, open Event Viewer and Task Manager, and investigate like an analyst. First look, process trees, event logs, PowerShell, ClickFix and persistence.7 steps
- AI securityPrompt injection, AI agents with tools and MCP servers, data leaking through assistants, the AI supply chain, and how a SOC monitors all of it. Built on the OWASP Top 10 for LLM Applications 2025, MITRE ATLAS and ATT&CK v20.11 steps
- Email and phishing analysisRead a header like a mail server does, know what SPF, DKIM and DMARC prove, take a lure apart safely, and recognise the phishing that passes MFA.9 steps
- Cloud and SaaS identitySign-in records, stolen sessions, OAuth apps with too much access, help desk takeovers and cloud audit logs: the attacks that need no malware at all.11 steps
- Linux monitoringauth.log and the journal, cron and systemd persistence, authorized_keys, reverse shells and cryptominers: the servers behind most of the internet.7 steps
- Threat intelligenceFrom indicator to behaviour: enrich hashes, IPs and domains honestly, share under TLP, and turn a vendor report into sweeps and hunts mapped to ATT&CK.8 steps
- Detection engineeringWrite the rules the next analyst gets alerts from: query in KQL and SPL, read and write Sigma, tune without blind spots, and prove coverage with tests.9 steps
- Ransomware responseCatch it before encryption: the precursors, the first hour, evidence before eradication, and who has to be told by when.10 steps

