My home lab isn't impressive. The virtualization host is a five-year-old laptop. It exists for one reason: I'd rather break something at home on a Saturday than learn the same lesson on a production system at work.
What's in it
- Proxmox on an old Dell laptop with 32 GB of memory, running a handful of virtual machines, including Windows.
- Pi-hole for DNS filtering across the whole house.
- A Synology NAS for storage and backups.
- A UniFi gateway feeding a 48-port Cisco Catalyst switch that powers devices over the network cable.
Nothing here is exotic. That's the point. It's the same kind of gear small businesses run every day.
Reading about a control isn't the same as running one
Running Pi-hole for the whole house teaches DNS in a way a course can't, because when something breaks, I'm the one who has to figure out why. Snapshots in Proxmox mean I can try something risky, watch it fail, and roll back in seconds. That loop of trying, breaking, and fixing builds the kind of judgment you can't get from a slide deck.
What's next
The network today is simpler than I'd accept at work. Next up is proper segmentation, so lab machines, cameras, and guests each live on their own network and can't reach each other by default. After that comes hardening the storage and virtual machine configurations, and standing up an open-source SIEM, a security information and event management system, to see what my own logs actually say.
The point
A lab is cheap insurance on judgment. Every hour spent breaking something at home is an hour I don't have to spend guessing at work.