Build a Small Home Security Lab
a safe place to break things, watch the logs and learn for real
Reading about security helps; doing it makes it stick. A home lab is a set of virtual machines on your own computer where you can attack, defend and investigate without risking anything real. It is also great evidence of your skills when you apply for jobs.
What you need
- A computer with 16 GB of RAM if possible (8 GB works for a small lab), some free disk space and a processor with virtualization support enabled in the BIOS.
- A hypervisor to run virtual machines: VirtualBox is free, and other options include VMware Workstation and Proxmox.
- Time and curiosity.
Safety first
- Put lab machines on an isolated virtual network (host-only or an internal network). Deliberately vulnerable machines must never be reachable from the internet or your home network.
- Only attack machines you built and own.
- Use snapshots so you can roll back after experiments.
- Keep the host patched, and do not reuse real passwords inside the lab.
A starter design
- An attacker machine: Kali Linux, a Linux distribution packed with security tools.[2]
- A target or two: a deliberately vulnerable web app such as OWASP Juice Shop,[1] DVWA, or an intentionally weak virtual machine, plus a Windows evaluation machine from Microsoft and an ordinary Linux server.
- A defender view: install Wazuh or Security Onion (free security monitoring platforms), and add Sysmon on the Windows machine so you can see detailed activity.
- Optional: a virtual firewall such as pfSense or OPNsense to practice segmentation and rules.
First exercises
- Scan your target with Nmap, then see the traffic in the monitoring tool.
- Run a harmless "attack" such as a failed-login burst and write a detection for it.
- Practice Linux commands, permissions and log reading on the server.
- Find an injection or access-control flaw in Juice Shop, then read how it is fixed.
- Simulate a phishing-style payload in the lab and trace the process tree in the logs.
- Take a snapshot, break something, and restore it.
Learn alongside
Structured platforms such as TryHackMe, Hack The Box and PortSwigger's Web Security Academy provide guided exercises. Free blue-team resources include Security Onion training and public detection rule libraries.
Keep notes and share them
Write short write-ups: what you tried, what you saw, what you learned and what you would do differently. Publishing them (without sensitive data) builds your portfolio and your understanding. Employers value clear thinking and curiosity as much as tools.
Ethical reminder
Skills you practice here are for learning and defense. Never test systems without written permission.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.