What Kali is, and the law

What the distro is and is not, who it is for, and why permission comes first

By the end of this lesson you can

  • Describe what Kali Linux is, who maintains it, and who it is built for.
  • List three reasons Kali is not a general-purpose desktop or a shortcut past Linux skills.
  • State the rule that unauthorized access is a crime and name the matching law in Switzerland, the UK, and the US.
  • Explain scope, rules of engagement, and responsible disclosure in a sentence each.
  • Describe how this course keeps every lab inside your own isolated network.

01What Kali is

Kali Linux is a free, open-source Linux distribution built for security testing. A distribution (or "distro") is a complete operating system: a Linux kernel, a set of programs, a package manager, and a desktop, all assembled and maintained by one team. What makes Kali different is the toolbox it ships with: several hundred security tools for scanning networks, testing web applications, analyzing traffic, checking password strength, and much more, already packaged and ready to install.

Kali is maintained by OffSec, a security training company. It is based on Debian, one of the oldest community Linux distributions, so most of what you learned in Linux Fundamentals works unchanged: apt installs software, files live in the usual places, and the shell behaves the way you expect.

A few technical choices set Kali apart from a normal Debian install:

  • Rolling release. Kali updates continuously instead of in big, separate versions. You get new tool versions as they are packaged. Lesson 5 shows what that means for updating.
  • A customized kernel. The kernel carries patches for wireless injection, so a compatible Wi-Fi adapter can send crafted frames during a wireless test. You will meet this, legally, in lesson 18.
  • Signed packages. Packages are signed with GPG, so your system can check that each one really came from the Kali project. Lesson 2 applies the same idea to the download itself.

Where it came from

Kali grew out of an older security distro called BackTrack, which began in 2006. The first Kali release, version 1, nicknamed "Moto", came out on March 13, 2013, and was based on Debian 7. Kali 2.0 followed in August 2015, and from January 2016 Kali moved to the rolling model it uses today. At the time of writing the current release is Kali 2026.2, published on June 29, 2026. You do not need to remember these dates. They explain why you will still see the name BackTrack in old tutorials.

Who is Kali for? The project says it plainly: it is tailored to experienced penetration testers and security auditors, and it assumes you are already comfortable with Linux. A penetration test is an authorized, scoped attempt to find and safely demonstrate weaknesses so the owner can fix them. That word "authorized" is the hinge of this whole lesson.

02What Kali is not

Many people install Kali because it looks exciting in videos. The Kali documentation is unusually honest about why that is often a mistake. It says Kali is not a general-purpose desktop distribution and is "probably not what you are looking for" if you lack Linux fundamentals.

Not this

A daily desktop

Kali deliberately keeps its software repositories small and trusted. Adding outside repositories, personal package archives (PPAs), or large consumer apps can break the system. For email, gaming, and browsing, a general distro is a better home.

Not this

A shortcut past Linux

Every tool here assumes you can read error messages, edit files, manage permissions, and understand networking. Without those skills, the tools produce output you cannot interpret.

Not this

A license to attack

Having the tools installed gives you no right to use them on anyone else's systems. The operating system does not check permission. You do.

Kali also behaves more cautiously than a typical desktop. Network services such as an SSH server or a web server are disabled by default, so a fresh Kali machine does not expose listening services to the network. You switch them on only when a task needs them, and you switch them off again afterwards. You will practice that in lesson 5.

Myth

"Installing Kali makes you a hacker." It does not. Kali is a collection of tools, most of which also run on other Linux distros. What makes someone a competent tester is understanding networks, operating systems, and applications, plus the discipline to work only within permission. This course builds the second half on top of the Linux Fundamentals and Networking Basics tracks, which cover the first.

03The one rule: permission

Here is the rule that separates a security professional from a criminal: you test only systems you own or have written permission to test. The actions are the same. A port scan, a login attempt, or a proxy session looks identical whether a contracted tester or an intruder runs it. What changes is authorization: written permission from the owner of the system.

Two panels side by side. Left, an authorized test: a shield, a signed scope letter, and your own lab, marked allowed. Right, unauthorized access to someone else's system, crossed out. Beneath both, the three laws: Swiss Criminal Code Art. 143bis, UK Computer Misuse Act 1990, US CFAA 18 U.S.C. 1030. Authorized test LAB SCOPE SIGNED OWN LAB · ALLOWED Unauthorized access YOU THEIRS NO PERMISSION A CRIME CH ART. 143BIS STGB UK CMA 1990 US CFAA 18 USC 1030
The same tools, two very different situations. Permission, written down, is the only thing that moves an action from the right panel to the left.

Most countries have a law that makes unauthorized access to computer systems a criminal offense. This course names three, because many learners live or work under them. You do not need to be a lawyer, but you should know the name of the law that applies to you and what it forbids in plain words.

JurisdictionLaw and articleWhat it forbids, in plain words
SwitzerlandSwiss Criminal Code (SR 311.0), Art. 143bis "Unauthorized access to a data processing system"Getting into another person's specially secured system over a network without authorization. Prosecuted on complaint. The maximum is a custodial sentence of up to three years or a monetary penalty. Paragraph 2 also covers passing on passwords or programs meant for such an offense.
United KingdomComputer Misuse Act 1990, section 1 "Unauthorized access to computer material"Getting access to programs or data on a computer when you know you are not authorized to. Later sections cover access with intent to commit further offenses (s.2), impairing a system (s.3 and s.3ZA) and making or supplying tools for an offense (s.3A).
United StatesComputer Fraud and Abuse Act, 18 U.S.C. 1030, subsection (a)(2)Accessing a computer without authorization, or going beyond the access you were given, to obtain information from a protected computer. Subsection (a)(5) covers knowingly causing damage, and (e)(6) defines "exceeds authorized access".

Two details are worth noticing. First, none of these laws requires you to break, steal, or change anything. Getting in without permission can be enough. Second, the US law explicitly covers going beyond the access you were given. A tester who has permission for one server and drifts onto the next one is outside their authorization. This course does not quote penalties for the UK and US laws. If you need them, read the official text or ask a lawyer.

Law and ethics

No permission, no test. That includes "just looking," "just one scan," "just checking whether a login page is weak," and "I was going to report it anyway." Good intentions are not authorization. If you are not sure whether something is in scope, the answer is no until the owner says yes in writing.

Myth

"A disclaimer or a VPN makes it legal." Neither does. A line saying "for educational purposes" changes nothing about who owns the system you touched. A VPN hides your address from the target. It does not grant you permission, and the act is just as unlawful. The only thing that makes testing legal is the owner's written consent, or a target you own.

04Scope, rules of engagement and disclosure

In professional work, permission is not a vague "go ahead." It is a document that answers precise questions. Three ideas carry most of the weight.

Scope is the exact list of what you may touch: which addresses, which hostnames, which applications, and which kinds of test. Anything not listed is out of scope, even if it sits next door on the same network.

Rules of engagement are the agreed terms around that scope: the dates and hours of testing, what is off-limits (for example, no testing of the payroll system during month-end), who to call if something breaks, and how findings will be handled and stored. NIST Special Publication 800-115, a public guide to security testing published in September 2008, describes testing in four phases: planning, discovery, attack, and reporting. The rules of engagement are written in the first phase, before a single packet is sent. The Ethical Hacking track (Track 12) builds its methodology on that model.

Responsible disclosure, also called coordinated disclosure, is how you handle a weakness you find: you report it privately to the owner and give them time to fix it before anything becomes public. Many organizations publish a small file at /.well-known/security.txt on their website, defined in RFC 9116, which says where to send such reports. It must contain a Contact field and an Expires field. Lesson 20 covers disclosure in detail.

Here is how this looks for the recurring example in this course. Sam is a one-person IT contractor building a home lab to learn (a fictional example). Later in the course, a small fictional client called Northwind Supplies signs a short scope letter so Sam can practice reporting. Until that letter exists, the only systems Sam may test are the ones he built himself.

05How this course keeps you safe

Every hands-on lab in this course follows the same pattern, so the habit becomes automatic:

  • Your own isolated lab only. In lessons 2 and 3 you build a Kali virtual machine and a deliberately vulnerable target on a host-only network, 192.168.56.0/24, which cannot reach the internet or your home network. The web practice apps run on your own Kali machine. No lab ever points a tool at a real third-party address or domain.
  • A scope reminder first. Each lab opens with a "Scope reminder" box that names exactly what you may touch.
  • The defender's view last. Each lab closes with a "Defender's view" box that explains how the activity you just performed can be detected and prevented. Knowing both sides is what makes the skill useful to an employer.
  • Minimal, harmless demos. No malware, no evading security products, no denial of service, no stealing real credentials, and no phishing of real people. Deeper exploitation methodology lives in Track 12.

You may read online about scanme.nmap.org. It is a host the Nmap project runs and gives everyone permission to scan for testing, within a limit of about a dozen scans per day. It is the rare public example of standing written permission. This course does not need it: your own lab gives you unlimited, private practice with nobody else's server involved.

Defender's view

For defenders, the same rule has a mirror image: anything that touches your systems without an agreed scope is unauthorized and worth investigating. Keep logs from firewalls and servers, watch for bursts of connection attempts to many ports or many hosts, and agree in advance how your own authorized testers will announce themselves, so you can tell a planned test from a real intrusion.

Practical exercise: what Kali is, and your first scope

A browser and a text editor (or paper). No tools are run in this exercise. Check off each step as you finish it. Your checkmarks are saved in this browser.

Scope reminder

This exercise only reads public documentation. Do not run any tool against any system. From lesson 3 on, the only targets in scope are the machines on your own host-only lab network.

Defender's view

The scope statement you just wrote is also a defender's tool. When an organization knows exactly what an authorized test covers and when, its monitoring team can treat anything outside that window or those addresses as a possible real attack.

Key takeaways

  • Kali Linux is a free, open-source, Debian-based rolling distro from OffSec with several hundred security tools.
  • It is built for experienced testers who already know Linux. It is not a daily desktop or a shortcut.
  • Unauthorized access is a crime: Art. 143bis in Switzerland, the Computer Misuse Act 1990 in the UK, and the CFAA in the US.
  • Written permission, with a clear scope and rules of engagement, is the only thing that makes testing legal.
  • Found a weakness? Report it privately and give the owner time to fix it: responsible disclosure.
  • Every lab in this course runs only in your own isolated lab, opens with a scope reminder, and closes with the defender's view.