Building Your Lab

Before attacking anything you need a place to practice legally and safely: your own lab. This card is the practical guide to building it from scratch —attack box, victims, isolated network, and practice platforms— so you can break, reset, and learn with no legal risk and no damage to others’ systems.

The attack box

A pentest-oriented distro with tools already installed:

Kali Linux — the most common; thousands of preinstalled tools.
Parrot OS Security — a light, polished alternative.
Install it as a VM (see Virtualization and Labs), not bare metal, so you can snapshot.

# after installing, first thing:
sudo apt update && sudo apt full-upgrade -y
# snapshot "kali-clean" before you start tinkering

The lab network (isolated)

The golden rule: your lab doesn’t touch the Internet or your real network when testing noisy attacks.

Host-only / internal network:  Kali + victims, no Internet access
# so you can run Responder, aggressive scans, test malware, without affecting anyone

To download tools, switch temporarily to NAT; to attack, back to host-only.

The victims

# Windows / AD
GOAD (Game Of Active Directory)   a full, vulnerable AD lab -> practice the WHOLE Windows&AD area
Windows eval VMs (Microsoft)      evaluation Windows Server/10 (90 days)
# Linux / generic
Metasploitable 2/3, VulnHub       downloadable vulnerable VMs
# Web
DVWA, OWASP Juice Shop, bWAPP      vulnerable web apps (Docker)

Guided practice platforms

TryHackMe          guided paths, ideal to start
HackTheBox         machines and Pro Labs (more realistic)
PortSwigger Web Security Academy   free web labs (the web reference)
VulnHub            VMs to download and break offline

Recommended workflow

1. Kali (VM) with a clean snapshot
2. Host-only network with the victim(s)
3. Pick a target (an HTB machine, GOAD, a vulnerable web)
4. Apply the methodology (recon -> enum -> exploitation -> post)
5. Document each step in your vault (Obsidian)
6. Restore snapshots and repeat

Hygiene and notes

Snapshots before each session; restore when you break something.
Document in a vault (see your Second Brain): commands, screenshots, lessons.
Never point attack tools at systems outside your lab or an authorized program (bug bounty with scope).

Why it matters in security

A lab is where you turn this wiki’s theory into real skill, without consequences. It’s the space to make mistakes, repeat, and truly understand each attack before seeing it in a real authorized environment. Building it well (isolated, with snapshots, with GOAD for AD) saves you scares and speeds up learning.

Mastery checklist

I have Kali/Parrot as a VM with a clean snapshot
I built an isolated host-only/internal network
I have at least one victim (GOAD, Metasploitable, vulnerable web)
I can toggle NAT (download) and host-only (attack)
I use TryHackMe/HTB/PortSwigger Academy for guided practice
I document each session in my vault
I never attack outside my lab or an authorized scope