Home lab
A VMware lab that simulates a small enterprise network, built to break things on purpose and then fix them.
The problem
Reading about Active Directory doesn't teach you what breaks when DNS is wrong. I wanted a place where breaking things was the point, and where I could see an attack from both sides.
What I built
Windows Server 2019 running AD DS, DNS and DHCP for hamanlab.local.
Windows 10 and 11, domain-joined and managed with Group Policy.
A second Server 2019 instance for shares, permissions and audit policy.
Kali Linux on its own segment for recon and attack practice.
Isolated LAN and DMZ-style segments. Internet only for updates.
Sysmon on the domain machines, forwarding logs to one collector.
How it works
- BuildPromoted the domain controller and set up DNS zones and DHCP scopes.
- ManageJoined the clients, built OUs, and wrote GPOs for passwords, lockdown and software.
- BreakPlanted real mistakes: weak password policy, over-permissioned users, open shares, AS-REP roastable accounts.
- AttackRan nmap, password spraying and BloodHound from Kali to find the paths through AD.
- FixClosed each hole, then re-tested to prove it stayed closed.
- ReviewRebuilt each attack from Sysmon and Security logs, event IDs 4624, 4625, 4768, 4769 and 7045.
Every destructive test starts from a snapshot, so a bad run is one rollback away.
What I learned
- Seeing the attack path from the attacker's side changed how I think about defense.
- A misconfigured DNS zone was my first real lesson in what takes a domain down.
- Snapshots make aggressive testing safe, and a clean rollback is a skill of its own.