Build your own DFIR lab, step by step. The manual route: from bare metal to GOAD, historical noise and forensic imaging.
The lab is the workbench: this is where things get built, broken and investigated. Every entry is a reproducible, documented, version-controlled step — no loose screenshots without context.
This first series is the manual route: standing up an Active Directory lab by hand, from bare metal to GOAD, with two years of historical noise and a forensic-imaging pipeline. The groundwork on which, later, each case is walked in three acts: the crime, the defense and the investigation.
This is Part 1 of the AD DFIR Lab series. We start from a freshly provisioned Hetzner dedicated server and end with Proxmox VE installed and ready to create virtual machines.
This is Part 3 of the AD DFIR Lab series. We configure pfSense to separate the attack network from the corporate network, forcing Kali to pivot like an external attacker.
This is Part 5 of the AD DFIR Lab series. We catalog everything GOAD creates inside the domains: users, groups, vulnerabilities, and how they fit together to form realistic attack chains.
This is Part 6 of the AD DFIR Lab series. We configure all the auditing before running the attacks — if we don’t do it now, the attacks won’t leave a trace.
This is Part 8 of the AD DFIR Lab series. We turn a sterile clean-ad snapshot into noisy-ad-2years — a dataset that looks like a real company has been using the domain for two years.
This is Part 9 of the AD DFIR Lab series. Part 8 gave us a noisy-ad-current snapshot packed with 2 years of realistic narrative. Part 9 pulls that snapshot out as a forensic image, intact and ready...