Kali Linux on a VPS: a training lab and testing your own systems
Kali Linux is a Debian-based distribution that comes with a ready collection of security testing tools: vulnerability scanners, traffic analysers, and tools for auditing web applications and passwords. It is used by information security professionals, students on security courses and CTF competitors. On a VPS, Kali is usually set up as a remote lab: the machine is reachable from anywhere, it's easy to rebuild from scratch, and training environments don't tie up your home computer. Below is what you should know before ordering such a server.
Rules first: what you may do from such a server
The tools included in Kali are legal in themselves, but using them is not without the system owner's permission. You may test only your own servers and sites, training environments and CTF platforms, and other people's systems under a written testing agreement with clearly defined scope. In Russia, unauthorised access to computer information and creating malicious software are punishable under articles 272–274 of the Criminal Code, and claiming "educational purposes" offers no protection.
The host's rules are a separate matter. Almost every terms of service forbids scanning other people's addresses and networks from a rented server. The network owner's complaint goes to the host, who blocks the VPS, often without a refund. If you are running a test under an agreement, warn the host in advance and keep the agreement at hand; some companies explicitly ask for this in their rules.
What a Kali VPS is good for
- Training and exam preparation. Security and certification courses usually provide their own lab network that you connect to from Kali; a server in a data centre holds the connection more reliably than a home internet line.
- CTF competitions. It's convenient for a team to have a shared machine with the same toolset and a public IP address.
- Testing your own projects. Before launching a site or service, it's useful to look at it from the outside: which ports are open, which software versions are visible, whether there are typical web server misconfigurations.
- Contracted work. An external test under an agreement needs an address that the client can add to an allowlist and recognise in their logs.
If all you need is to secure your own server, a separate Kali isn't required: basic checks can be done with tools from ordinary Debian or Ubuntu.
What server you need
- Virtualisation: KVM. Many tools need their own network stack, kernel modules and raw sockets; on OpenVZ and LXC containers they work partially or not at all. Suitable plans are on the VPS on KVM page.
- Memory: from 4 GB. The system itself without a GUI gets by on 2 GB, but vulnerability databases, a browser for testing web applications and virtual training environments quickly eat up memory. If you need a desktop over VNC or RDP, choose a VPS with 4 GB RAM or more.
- Disk: from 40–60 GB. The full kali-linux-large package set takes over 20 GB, plus wordlists, reports and system snapshots.
- Hourly billing is convenient for short training tasks: spin up a lab for an evening and delete it. Such plans are collected on the VPS with hourly billing page.
How to install Kali if it isn't in the image list
Few hosts offer a ready Kali image. There are two usual routes. The first is a plan with a custom ISO: you upload the official installation image from the project's website, open the VNC console in the panel and install the system as on an ordinary computer (a list of such plans is at VPS with custom ISO). The second is to take a clean Debian and add the Kali repository to it, installing only the metapackages you need. The second route is easier to maintain, but mixing repositories needs care: Kali is a rolling distribution, and its packages are newer than in stable Debian.
How to keep such a server in good shape
Kali is updated continuously, so update the system regularly and in full rather than package by package. Take a disk snapshot before a big update: rolling back takes minutes. Disable password login and leave SSH key access only, and if you need a desktop, open it only through an SSH tunnel, not directly to the internet: a server with a set of audit tools is an attractive target. Run deliberately vulnerable training environments in an isolated network inside the server without exposing them to the outside. And store test reports separately and encrypted: they often contain client data.