The academy where analysts learn why, not just how

You can't detect, or investigate, what you can't imagine.

Tools change every year. How an intrusion works, and how it is analysed, does not. The book says one thing, the SOC/DFIR floor says another. We teach both.

Standards we never break

Ten standards behind every course we teach. We hold to them on every lesson, for every batch.

Standard 01 / 10

Designed here, from the ground up.

Every curriculum is designed here, over months, from years of casework and from watching where analysts get stuck.

Standard 02 / 10

Rock-solid fundamentals before any tool.

Networking, operating systems and Windows internals are the core of every course, not the warm-up. You learn where a tool's data is born, the process, the registry, the log, before you touch the tool. Then the dashboard stops being magic.

Standard 03 / 10

Every technology, through the problem it solved.

DNS exists because one text file stopped scaling. Firewalls exist because perimeters failed. Learn what broke, and you understand the fix down to its design.

Standard 04 / 10

Real, recent intrusions only.

Every attack you study happened: in incidents we worked ourselves, or in investigations published by trusted sources. Current, cited, and real.

Standard 05 / 10

Think like the attacker first.

Before you learn to defend, you plan the attack. You can't detect, or investigate, what you can't imagine.

Standard 06 / 10

Taught from the floor, not the book.

The book says one thing, real SOCs say another. Every lesson is written by someone who does the job, and shows you both.

Standard 07 / 10

Hard on purpose.

Reading before every session, homework after, and parts you study alone before you ask. The field needs analysts who can carry the weight.

Standard 08 / 10

Honest about the gaps.

Each course names what it does not cover and exactly where to learn it next. An analyst who knows their gaps is safer than one who thinks they are complete.

Standard 09 / 10

The thinking AI can't do for you.

AI will always know more facts than you. We train what it can't: reading context, forming a hypothesis, doubting the obvious answer. And we show where AI helps, and where it misleads.

Standard 10 / 10

We win only when you do.

Every course also teaches the market: the skills teams hire for, the gaps they cannot fill, and what the job really asks of you. Then we help you get there, with CV reviews, interview practice and introductions. A stronger analyst, a better-staffed SOC, a healthier market: everyone has to win.

I hold every course we teach to these standards. If you find one we broke, tell me directly.
Ahmed Thabit Founder

Tracks

Each course has a code, like IR-200. Courses in a track build on each other, but you do not have to take them all in order: start where you need to, as long as you already know what the earlier ones teach.

DFIR Digital Forensics, Incident Response & Threat Hunt
  • Available 0
  • Releasing 3
  • In Production 0
  • In Design 0
  • Concept 0

Next batches

Live sessions with the person who wrote the course. Reading before each one, homework after.

All live trainings
SOC Analyst Mindset cover image
DFIR-200 Live

SOC Analyst Mindset

Systems Internals, Enterprise Infrastructure, Adversary Tradecrafts, Analysis Process & Much More

To be announced soon.

Schedule coming soon

Recorded courses

The same curriculum at your own pace: lessons, labs and quizzes. Buy once, or start free, and keep it.

All courses
Investigation & Analysis Insights cover image
DFIR-201 On-Demand Arabic Free

Investigation & Analysis Insights

Standalone sessions on how analysts think: storytelling, context, the Pyramid of Pain and pivoting

A series of standalone sessions on how analysts really think: reading an intrusion as a story, building context, going after the indicators that hurt the attacker, and pivoting without getting lost.

Free Lifetime access · 3 Hours
 Chasing Rider cover image
DFIR-206 On-Demand Arabic Free

Chasing Rider

A practical incident response series: one intrusion, followed from the first alert to the domain controller

Follow Rider.exe through a real intrusion, from Tier 1 triage in Elastic to PsExec, identity, file and network telemetry, and the incident response decisions along the way. New episodes are added as the series continues.

Free Lifetime access · 5 Hours

We build what we teach

Signal came out of the same casework as the courses. It is the first minute of an investigation, done for you.

DFIR survey tool

The first minute of every investigation.

Hours of triage, distilled into one: where to look, and what you can't see. Read-only, about a minute on Windows 10, 11 and Server.

  • ~1 min to a first answer, where a manual triage takes hours
  • 50+ Windows artifacts and data sources - and the audit gaps in them
  • Read-only safe on production hosts, from one host to the whole fleet
Designed with enterprise requirements in mind Compliance-mapped, penetration-tested, self-hosted and sized for the whole fleet.
Signal Console: Signals

Field notes

Write-ups from cases and labs, and answers to the questions students asked that we couldn't answer on the spot.

All notes
Pinned English

Weaponizing Google Chrome Update Service for Execution & Persistence

A weekend Process Monitor boot log turned into a full DLL side-loading study: finding a hijackable load in Google's updater service, building and stabilizing a PoC with a DLL proxy, turning it into SYSTEM persistence, and the detection and forensic opportunities it leaves behind.

[-ACB] 11 min read 0 comments

Read Post
ShimCache Presence Is Not Proof of Execution
English

ShimCache Presence Is Not Proof of Execution

A ShimCache entry does not mean the program ran. Walking through AppCompatCacheParser's "Executed" column, a Prefetch cross-check, the last-four-bytes assumption and where it breaks down — and why you must understand how an artifact and its tools really work before you conclude.

[-ACB] 3 min read 0 comments

Read Post

Your team, trained on your incidents.

For SOC, DFIR and security teams. The same standards, built around your environment.

Tell us where your analysts are and where they need to be. We design the path from your stack and your incidents, teach it with the people who wrote it, and show you what each analyst can now do.

  1. 01Tell us your stack, your team and the gaps you see.
  2. 02We send a plan: courses, order, schedule and price.
  3. 03Your team trains together. You see who can do what.
  • Built from your stack

    We map the courses to your tools, your log sources and each analyst's level, and cut what your team won't use.

  • Private batches, around your shifts

    Your team only, on the days and hours your rota allows. Reading before, homework after, like every batch.

  • Your incidents, rebuilt as labs

    We rebuild the attacks your team has seen, or should expect, so they practise on what will actually reach them.

  • Skill you can verify

    Quiz and lab results for every analyst: what they can investigate now, not how many hours they sat.