A security lab lives on an isolated network. This is not optional — practice environments include intentionally vulnerable systems, and you do not want them reachable from your main LAN.
The lab needs its own VLAN or physical segment:
Internet
└─ Router/Firewall (pfSense or OPNsense)
├─ Main LAN (VLAN 10)
├─ IoT (VLAN 20)
└─ Security Lab (VLAN 99) ← isolated, no access to other VLANs
Block VLAN 99 from reaching VLAN 10 at the firewall. Allow internet access for downloading tools, but firewall it off from your real machines.
Run Kali as a VM in Proxmox. It comes with the full tool suite pre-installed — Nmap, Metasploit, Burp Suite, Wireshark, Nikto, Hydra, sqlmap.
Keep a clean snapshot you can revert to. Kali VMs accumulate tool conflicts fast.
Deploy these in your lab VLAN:
Wazuh is a free, open-source SIEM that runs on-prem. Deploy the Wazuh server as a Docker stack and install agents on your lab VMs. It collects logs, detects intrusion patterns and generates alerts.
The Wazuh documentation covers Docker deployment in detail. Run it on a VM with at least 4GB RAM.
Zeek (formerly Bro) analyzes network traffic and generates structured logs — DNS queries, HTTP requests, connection summaries. Arkime (formerly Moloch) stores and indexes full packet captures with a search UI.
Both run well on a server with a spare NIC connected to a mirror port on your lab switch.
Start with Kali + Metasploitable + Wazuh. That gives you an attacker, a target and a detector — the core of any security lab.
As an Amazon Associate, IT Lad earns from qualifying purchases made through links on this page. Read the full affiliate disclosure.