Setting Up a VM
Pick a hypervisor (see Tools), download an ISO, create the VM. That is the whole process.
The details differ by tool, but the steps below are universal.
Step 1 — Choose a Guest OS
For security work, start with one of these:
| OS | Why |
|---|---|
| Kali Linux | Comes with most security tools pre-installed |
| Parrot OS | Lighter than Kali, good for older hardware |
| Ubuntu | Clean slate, you install what you need |
Kali is the default choice for offensive security. Ubuntu is better if you want to learn Linux from scratch without preinstalled noise.
Download the ISO from the official site. Verify the checksum before using it.
Step 2 — Create the VM
In your hypervisor, create a new VM and point it at the ISO. Standard recommended specs:
| Resource | Minimum | Comfortable |
|---|---|---|
| RAM | 2 GB | 4 GB |
| Storage | 20 GB | 40–60 GB |
| CPUs | 1 core | 2 cores |
Do not over-allocate. Your host machine needs resources too.
Step 3 — Network Modes
Choose based on what you need:
| Mode | What it does |
|---|---|
| NAT | VM shares host’s IP. Can reach the internet. Cannot be reached from outside. |
| Bridged | VM gets its own IP on your network. Visible to other devices. |
| Host-only | VM talks only to the host. No internet. Good for isolated lab setups. |
| Internal Network | Multiple VMs talk to each other. Completely isolated from host and internet. |
Start with NAT. Switch to host-only or internal when you set up attack/defend lab environments.
The lab recipe: put the attacker VM and the target VM on the same host-only or internal network, so they see each other and nothing else. Give the attacker a second adapter on NAT when it needs to download tools. Inside a VM, ip a shows which network it landed on, and ip r shows whether it has a gateway. Two VMs that cannot see each other are almost always on different adapter types.
Step 4 — Take a Snapshot
Before you install anything or run any tools, take a snapshot. Name it something useful like clean-install.
When things break — and they will — revert and start from a known good state.
Take one more before every experiment: an unknown binary, a CTF file, a script from a writeup. Snapshot, run it, revert. A snapshot is not a backup. It lives on the same disk as the VM, so it does not survive the disk.
Recommended First Steps After Install
Guest Additions / VMware Tools
Install the guest additions for your hypervisor after setup. They improve display resolution, clipboard sharing, and file drag-and-drop. Look up the specific steps for your tool.
How the Club Uses This
TODO: Add recommended VM setup for club competitions and labs — specific OS versions, network configs, shared snapshots, etc.
References
- Why Virtual Machines
-
Setting Up a VM
- VM Tools