Security training catalogue
Hands-on courses for SOC analysts, incident responders, cloud and security engineers, identity and GRC professionals: each one worked in a simulated environment and marked on what you actually did.
Scripting and automation
The three languages an analyst or administrator automates in, each marked on what the code returns and the state it leaves.
- PowerShell — A prompt against a Windows host with something wrong on it — marked on the objects your pipeline returns.
- Bash — A taught course in the shell, from first command to production script — read here, typed in your own terminal.
- Python — Python for security and operations jobs: real Python 3.14 in the browser, marked on what your functions return and the state they leave.
Security operations
From getting logs in to writing the rule, hunting, working the alert and automating the response.
- Log Management — A hands-on course on log files you import: onboard, parse, time and search them in a Splunk-style platform.
- Professional Detection Engineering — From a threat profile to a validated detection programme: telemetry, rules in six languages, hunting, replay, detection as code and metrics.
- Hunting with KQL and SPL — Hunt through each CTF case's constructed telemetry in KQL, with SPL twins: a guide to writing the queries, then graded exercises marked in the case's SIEM view.
- Endpoint Detection & Response — An EDR console, simulated: triage alerts, read the process tree, hunt, isolate, run live response and scope indicators on a fictional estate, with graded labs.
- Playbooks — Response automation to build elsewhere — checked for structure, never executed here.
- Vulnerability Management — A four-tier practitioner course — scan, triage, prioritise, ticket, verify and report in an enterprise-style VM console, graded against a hidden truth table.
Investigation and reference
The corpus as something to study and be tested against: artifacts, techniques, drills, worked cases, timed CTF investigations and interview preparation.
- Windows OS Atlas — Every Windows artifact an analyst reads, across 18 domains — baseline, attack, analysis, limits.
- Attack Atlas — Microsoft ecosystem techniques mapped to ATT&CK and D3FEND.
- FlagRush — Spot-the-delta drills, solo or as a live cohort arena.
- Case Library — Worked investigations — the decisions, not just the artifacts.
- Commands — What to run, indexed by the question — and the commands that answer a different one.
- CTF — Timed investigations against telemetry constructed for each case. Answers stay server-side.
- Interview — Panel prep — scenarios by level, hunts, ladders and a mock.
Application security
What the detections and the atlas are defending: web application weaknesses found, fixed and proved fixed.
- AppSec — A four-tier application-security course — OWASP Top 10:2025 on Juice Shop and WebGoat, checkpoints, auto-scored labs and a gated capstone.
Cloud (AWS) and IT operations
AWS with the real CLI against simulated accounts: a core course, four role tracks, and the service desk the operations work arrives through.
- Amazon Web Services (AWS) — Cloud security on AWS, hands on — real aws CLI commands against simulated accounts: IAM, roles, S3 and KMS, CloudTrail investigations and organization guardrails.
- AWS SysOps Administrator -- operating workloads in production — An AWS SysOps professional keeps workloads on AWS available, performant, secure, recoverable and cost-effective after they have been deployed. Where a Solutions Architect decides how a system should be built, you answer whether it is working and how to keep it working: you carry the pager, investigate what alarms, run the changes and the patches, prove the backups restore, watch the capacity and the bill, and turn every repeated chore into automation so the next one costs less.
- AWS Cloud Solutions Architect — An AWS Cloud Solutions Architect designs solutions on AWS that meet business and technical requirements for security, availability, performance, scalability, resilience and cost. You turn what the business needs into a design, choose services and trade-offs on purpose, write the decisions down with their reasons, and explain them to engineers, security teams and the people paying for it. The track covers the major AWS services, how they work together, when to use each, and the trade-offs an architect must weigh.
- AWS Security Operations -- from foundations to enterprise practitioner — Security operations in AWS: understanding the cloud control plane, identities and permissions, workloads, networks and data well enough to detect threats, investigate what happened, respond without destroying the evidence, and prevent it recurring -- in one account or many. The track teaches not just what AWS's security services do, but why they exist, how they work, what evidence they produce, how attackers abuse cloud configurations, and how defenders detect, investigate, contain and prevent.
- Cloud Security Engineering -- from foundations to enterprise practitioner — A cloud security engineer designs, implements, validates and keeps improving the controls that protect cloud infrastructure, identities, networks, workloads, applications, data, delivery pipelines and enterprise architectures. Where SecOps notices what went wrong, you make it hard to go wrong in the first place -- and prove the controls work. The emphasis throughout is why a control is needed, how it should be designed, how it interacts with other controls, and how its effectiveness is validated. AWS is the only cloud you practise here: every lab and every mark is on simulated AWS accounts. Microsoft Azure and Google Cloud are in the reading only: each module names their equivalent services and where they behave differently, and a few module-check questions ask for an equivalent's name, but no lab configures, practises or marks either.
- Service Desk — Service desk work in a simulated ITSM instance at a fictional company: the ITSM processes, then incident tickets and service requests worked to resolution.
Governance, risk, compliance and privacy
The people who decide about all of the above, and the evidence they decide on, at fictional organisations.
- GRC: Analyst to Professional — A four-tier, 16-module GRC (Governance, Risk and Compliance) course of about 170 hours that takes a security or IT analyst from zero GRC knowledge to running a program. The previous edition, at a fictional Canadian health provider or a fictional U.S. federal contractor, stays available beside it.
- Privacy Analyst — Privacy law and operations for working analysts at a fictional health provider, with a Canada and a United States track.
Windows Atlas
The Windows artifact index: 297 artifacts, each with what it records and, as importantly, what it does not prove.
Create a free account