3.3 Installation Options Overview

Kali Linux Certified Professional KLCP

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 How to Use This Guide & Study Strategy 1.3 PEN-103 Syllabus & Study Path

2 About Kali Linux

2.1 A Bit of History: From BackTrack to Kali 2.2 Kali's Relationship with Debian 2.3 Purpose and Use Cases 2.4 Main Features and Design Policies

3 Getting Started with Kali Linux

3.1 Downloading and Verifying a Kali ISO 3.2 Booting Kali in Live Mode 3.3 Installation Options Overview 3.4 Troubleshooting Installations

4 Linux Fundamentals

4.1 What Linux Is and What It Does 4.2 The Command Line 4.3 The Filesystem Hierarchy Standard 4.4 Useful Commands: Files, Search, Environment

5 Permissions and Process Management

5.1 File Permissions and Ownership 5.2 Managing Processes 5.3 Shells, Variables, and the Environment

6 Installing Kali Linux

6.1 Minimal Installation Requirements 6.2 Step-by-Step Installation on a Hard Drive 6.3 Unattended Installations with Preseeding 6.4 ARM Installations

7 Configuring the Network, Users, and SSH

7.1 Configuring the Network 7.2 Managing Unix Users and Groups 7.3 Configuring SSH

8 Configuring Services

8.1 Apache Web Server 8.2 PostgreSQL Database 8.3 Managing Services with systemd

9 Helping Yourself and Getting Help

9.1 Documentation Sources 9.2 Kali Linux Communities 9.3 Filing Good Bug Reports

10 Security Policy and Network Services

10.1 Defining a Security Policy 10.2 Possible Security Measures 10.3 Securing Network Services

11 Firewalling and Monitoring

11.1 Netfilter and iptables Behavior 11.2 Writing iptables Rules and NAT 11.3 Monitoring and Logging

12 Debian Package Management: APT

12.1 Introduction to APT 12.2 The sources.list File 12.3 Kali Repositories 12.4 Basic Package Interaction with apt

13 dpkg and Advanced Package Management

13.1 dpkg Fundamentals 13.2 Inspecting .deb Files and Package State 13.3 Maintainer Scripts and Conffiles 13.4 APT Pinning and Package Authenticity

14 Advanced Usage

14.1 Modifying and Rebuilding Kali Packages 14.2 Recompiling the Kernel 14.3 Building Custom Kali Live ISO Images 14.4 USB Persistence with LUKS Encryption

15 Kali Linux in the Enterprise

15.1 Network Installation with PXE Boot 15.2 Configuration Management with SaltStack 15.3 Metapackages and Custom Repositories 15.4 Configuration Packages and Forking

16 Introduction to Security Assessments

16.1 Kali Linux in an Assessment 16.2 Types of Assessments 16.3 Types of Attacks 16.4 Formalization and the Road Ahead

3.3 Installation Options Overview

Key Takeaways Explain This Topic AI

Bare-metal installs give full hardware access and the best performance; a live USB boot also drives the internal Wi-Fi card directly, whereas a VM never does

Prebuilt VMware, VirtualBox, and Hyper-V images from kali.org are the fastest VM path; VMs add snapshots and isolation but virtualize the network card, so wireless injection needs a USB adapter passed through to the guest

Kali publishes official cloud images in the AWS and Azure marketplaces — headless by default, reached over SSH

The Docker image kalilinux/kali-rolling shares the host kernel, so containers cannot do wireless injection or load custom kernel modules

WSL (wsl --install kali-linux) puts the Kali command line on Windows quickly, with Win-KeX available for a GUI, but hardware access is limited

Last updated: July 2026

Installation Options Overview

Kali runs almost anywhere, and the exam wants you to match each deployment method to its use case and its limitations. The main options:

• Method Effort GUI Raw hardware access Best for
• Bare metal Full install Full Xfce desktop Complete Daily-driver hacking workstation, Wi-Fi injection

Virtual machine Import prebuilt image or install from ISO Full desktop Partial (USB passthrough) Safe lab work, snapshots, course study

• Live USB Flash an image Full desktop Complete Portable toolkit, try-before-install
• Live USB + persistence Flash + partition setup Full desktop Complete Portable toolkit that remembers changes
• ARM device Flash device image Varies Complete (device hardware) Raspberry Pi drop boxes, cheap field kits
• Cloud (AWS/Azure) Launch marketplace image None by default None Internet-facing scanners, remote labs
• Docker docker pull None (CLI) None, shares host kernel Scripted tooling, CI pipelines
• WSL One command on Windows Via Win-KeX Limited Kali CLI alongside Windows tools
• Bare metal

Installing Kali directly onto a machine's disk — solo or dual-booted — gives you full performance and unrestricted hardware access. This matters most for wireless work: packet injection and monitor mode require direct control of a Wi-Fi card, and Kali's kernel is custom-patched for wireless injection. Bare metal and a live USB boot are the two options where the laptop's internal card is directly usable for that, because both run Kali's own kernel on the real hardware; a VM never does. The trade-offs are commitment (repartitioning disks, managing dual boot) and the lack of a hypervisor's safety net between your attack tools and your everyday data.

Virtual machines

The most common lab setup. You can install from the standard ISO into VMware Workstation/Fusion, VirtualBox, or Hyper-V, but the faster path is importing the prebuilt VM images published on kali.org — download, import, log in as kali/kali. VMs give you snapshots (roll back a broken tool install or a rootkitted guest in seconds), isolation from your host, and easy networking choices: NAT for simple outbound access, bridged when the guest must be a first-class citizen on the LAN, host-only for closed attack-lab networks.

The critical limitation is the virtualized NIC . The guest sees a virtual Ethernet adapter created by the hypervisor, not your physical wireless card, so 802.11 monitor mode and injection are impossible through it. The standard workaround — heavily emphasized in the Kali Linux Revealed material — is a USB Wi-Fi adapter passed through to the guest : the hypervisor hands the whole USB device to the VM, and Kali drives it directly. If an exam question describes injection failing inside a VM, this is almost always the answer.

USB: with and without persistence

Covered in detail in Section 3.2: a plain live USB is disposable and forgets everything at shutdown, while a persistence partition (optionally LUKS-encrypted) preserves your files, settings, and installed packages. Both boot the full desktop with real hardware access; neither requires touching the host's disks.

ARM devices

OffSec maintains images for ARM boards such as the Raspberry Pi. An ARM Kali box is small, silent, and cheap — ideal as a physical drop box on a penetration test or as a dedicated wireless-attacking appliance. You flash the image to an SD card exactly as you would a USB stick.

Cloud

Kali is published in the AWS Marketplace and Azure Marketplace as official images maintained by OffSec. Launch an instance and you reach it over SSH — there is no desktop by default, and (consistent with Kali's policy of network services being disabled by default) you must explicitly start or enable any services you need. Cloud Kalis shine for internet-facing reconnaissance, scanning, and command-and-control infrastructure that must live outside your home IP. Check your cloud provider's acceptable-use policy before scanning; many providers require you to request authorization for penetration-testing traffic.

Docker

docker pull kalilinux/kali-rolling gives you a minimal Kali userland in seconds, and metapackages such as kali-linux-headless layer on tool collections. Containers are superb for scripted, reproducible tooling — a disposable nmap or recon environment in CI. But a container shares the host kernel , so anything requiring kernel-level control is off the table: no wireless injection, no custom kernel modules, no low-level network interface manipulation beyond what the host permits.

WSL

On Windows 10/11, wsl --install kali-linux (or the Microsoft Store package) installs Kali as a Windows Subsystem for Linux distribution. You get the Kali command line and apt tooling integrated with Windows — great for quickly running Linux-native scripts on a Windows work machine. The Win-KeX package adds a graphical Kali desktop experience inside a window. Hardware access is limited (no straightforward PCI/USB wireless control), so WSL is a convenience option, not an attack platform for radio work.

Choosing

Rule of thumb for the exam: need wireless injection or maximum performance? Bare metal, or a VM with a USB adapter. Need safety, snapshots, and a course companion? VM. Need portability? Live USB, with persistence if it is a daily tool. Need an internet-facing presence? Cloud. Need disposable automation? Docker. Need Linux tools on a Windows desktop? WSL.