Stage 2 · Lesson 2 of 7

Isolated lab networks

A hypervisor can connect a to a network in several ways, called network modes. lets the machine reach the internet through your own computer, like a house sharing one front door. Host-only and internal networks let lab machines talk to each other and to nothing else.

Put deliberately vulnerable machines on a host-only or internal network. Then nobody outside can reach them, and any tool you run cannot touch your home network, your family's devices or the internet. Only switch a machine to NAT when it needs updates, then switch it back.

Draw your lab network on one page, with each machine's address. This isolation is what makes the lab safe and legal to use.

Common trapleaving a vulnerable app on a bridged network, where it joins your real home network and becomes a real target for anyone on your Wi-Fi.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with

GuideFree
Docker Docs: Get Started
Docker · Beginner
Enough Docker to run, reset and remove practice targets and tools cleanly

Practise

OWASP Juice Shop
The standard intentionally vulnerable web app: run it locally and use it throughout your path
TryHackMe
Browser-based machines if your laptop cannot run a full lab, with clear rules on what you may target

Keep handy

Kali Linux Documentation
Official guides for running Kali as a virtual machine, the usual testing workstation
Wireshark User's Guide
Capture and read your own lab traffic to see what normal and unusual look like

Also worth your time

Linux Upskill ChallengeGo deeper
A month of daily tasks on a real Linux server if you want your Linux administration to be solid