Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 31 ยท Ethics, Law and Lab Setup

What Kali Linux Is and Who It Is For

Learn what Kali Linux is, why it is built on Debian, how its security tools are grouped, and how red, blue and purple teams use it.

Kali Linux is a Linux distribution made for security work. It is maintained by Offensive Security and built on top of Debian, so everything you know about Debian-style Linux (apt, systemd, the filesystem layout, the shell) applies. What makes Kali different is not a secret kernel or special powers. It is a curated collection: hundreds of security tools, already installed, already configured to work together, and updated from one trusted repository.

This tutorial treats Kali as a learning platform for defense and authorized testing. You will learn how scanners see a network, how passwords are stored and attacked in theory, how web flaws appear in logs, and how to write a report that gets problems fixed. You will not be pointed at real targets. Every lesson that cannot run on this site gives you read-only commands plus a Python stand-in that models the idea on fake data.

Security tools are dual-use. The same scanner that helps an administrator find an exposed database helps an intruder find it too. Only use these tools on systems you own or have written permission to test. The next lesson covers this in detail: Law, Ethics and Authorization.

Why a special distribution at all?

You could install every tool on Ubuntu or Fedora by hand. People do. A dedicated distribution saves time in three ways.

Why people use Kali

Pre-packaged Hundreds of tools installed from one repository.
Rolling updates New tool versions arrive without a new install.
Consistent Everyone on a team has the same setup.
Lab friendly Runs as a VM, live USB or inside WSL.

A shared, predictable toolbox is the main benefit.

1 / 2

Kali is a poor choice as a general-purpose desktop. Many tools expect elevated privileges, some network services are tuned for testing rather than comfort, and the default setup trades some hardening for convenience. Treat it as a workbench: start it for a task, keep it in a virtual machine, and use a normal OS for banking and email.

The Debian foundation

Because Kali is Debian-based, package management is familiar. Kali follows a rolling model: a branch called kali-rolling that is refreshed continuously. You update it with the same tools you would use on Debian.

Terminal
# Read-only on this site: these need a real Kali system
cat /etc/os-release          # shows NAME="Kali GNU/Linux" and the rolling version
sudo apt update              # refresh the package index
sudo apt full-upgrade        # upgrade, allowing packages to be added or removed
apt list --installed | wc -l # roughly how many packages you have

If you are new to the command line, work through the Linux tutorial introduction and Packages and services first. Installing and updating Kali itself is covered in Installing and Updating Kali.

Tool categories

Kali groups its tools by what they help you do. The grouping mirrors the stages of a security assessment, which is also how this tutorial is organized.

Category Typical question it answers Examples (names only)
Information gathering What does this organization expose? whois, dig, theHarvester
Vulnerability analysis Which known weaknesses might apply? OpenVAS, Nikto
Web application analysis How does this site handle input and sessions? Burp Suite, OWASP ZAP
Password attacks How resistant are stored credentials? hashcat, John the Ripper
Wireless How is this Wi-Fi network configured? aircrack-ng suite
Sniffing and spoofing What is crossing the wire? Wireshark, tcpdump
Exploitation frameworks Can a finding be proven safely? Metasploit Framework
Forensics What happened on this system? Autopsy, binwalk
Reporting How do we record and share findings? CherryTree, Dradis

You do not need to memorize these. Notice the pattern instead: each category is a question, and a professional asks the question for a reason (reduce risk), not for the thrill of the tool.

Defensive and offensive roles

Security work is usually described in colors.

  • Red team: plays the attacker, with permission. Goal: show how a determined intruder could reach important assets.
  • Blue team: defends. Builds monitoring, patches systems, responds to incidents, and tunes detection.
  • Purple team: red and blue working together in the open. The red side runs a technique, the blue side checks whether it was detected, and both improve the result.
  • White team (sometimes): referees and coordinates an exercise.

Kali is most visible in red-team and penetration-test work, but blue teams use it too: to check what their own network looks like from outside, to read packet captures, and to test whether an alert fires. A defender who has never run a port scanner cannot judge what a port-scan log line means.

flowchart LR
    R["Red team<br/>simulates attacks"] -->|"findings and techniques"| P["Purple team<br/>shared exercise"]
    B["Blue team<br/>detects and responds"] -->|"alerts and gaps"| P
    P -->|"fixes and better detection"| B

Purple teaming turns an attack simulation into a defensive improvement loop.

What is real here and what is a stand-in

Kali needs a real operating system, root privileges and network access. This site gives you a browser sandbox, so the commands above are shown in read-only blocks. The runnable parts are Python programs that model how the tools think. In the first stand-in, a small script groups a sample tool list by category, the same bookkeeping that Kali's menu does for you.

Python Group a sample tool list by category

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Dictionaries that map a category to a list are the same structure a package metadata tool uses. Next, a second stand-in connects tools to the roles that would reasonably use them. It shows that most tools serve both sides.

Python Which team uses which tool?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A short history of Kali

Kali grew out of earlier security-focused live systems. Several small projects (WHAX, Auditor Security Collection) merged into BackTrack, which was built on Slackware and later Ubuntu. In 2013 the team rebuilt it from scratch on Debian and called it Kali Linux 1.0.

Period What changed
2013-2015 Foundation: Debian base, a dedicated tool repository, ARM images, GNOME desktop.
2016 Rolling releases (kali-rolling) replace big versioned jumps.
2019-2021 Modernization: non-root default user, Xfce as the default desktop, Kali NetHunter on phones, Win-KeX for the Windows Subsystem for Linux.
2022 to now Cloud and enterprise readiness: images for cloud providers, Hyper-V, Docker and Vagrant, plus a growing, officially documented tool set.

Two lessons from that history still matter. First, the toolbox is large but not unlimited: you will install extra packages. Second, customization is possible (you can build your own ISO), but keeping a custom build maintained over years is real work, so most people use the official images and metapackages.

Kali Linux versus Ubuntu

Both are Debian-family systems that use apt, so the commands look alike. The goals differ:

Kali Linux Ubuntu
Purpose Security testing, forensics, research General desktop, server and cloud use
Tools Hundreds of security tools preinstalled or one metapackage away Everyday software: office, media, development
Releases Rolling, tracks current tool versions Fixed releases; LTS every two years, supported for five
Default user Ordinary user with sudo (older versions: root) Ordinary user with sudo
Hardening for daily use Not the priority Updates, sandboxed apps, wide hardware support
Typical user Testers, students, analysts Almost everyone

Ubuntu is free, friendly and customizable, and it suits gaming, programming and servers. Kali is a specialist workbench: use it in a lab for authorized testing, and keep Ubuntu (or another general distribution) for daily life.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which Linux distribution is Kali based on?

    Kali is built on Debian and uses apt and the Debian package format. Its own repository adds the security tools.
  2. 2. What does a purple team do?

    Purple teaming brings red and blue together. Each technique is checked against detection, and both sides learn from the result.
  3. 3. Why is Kali not recommended as your everyday desktop?

    Kali favors testing convenience over hardening. Keep it in a VM or on a separate drive, and use an ordinary system for daily tasks.
  4. 4. Having Kali installed means you may scan any network you can reach.

    Software does not grant permission. Testing a system without written authorization can be illegal even if the tool is freely available.

Summary

  • Kali is a Debian-based, rolling distribution packed with security tools.
  • Its value is convenience and consistency, not magic: skill and permission matter more than the toolbox.
  • Tool categories follow the stages of an assessment, and each answers a question about risk.
  • Red teams simulate attackers, blue teams defend, and purple teams combine both to improve detection.
  • On this site, real commands are read-only and Python stand-ins model the ideas safely.

Next up: Law, Ethics and Authorization.