Prerequisites

This book teaches defensive security from the ground up, but it does not teach computing from the ground up. To get the most from it, you should arrive with a handful of general technical foundations. None of them needs to be deep — a working familiarity is plenty — and this section tells you exactly what to know, gives you a quick self-check, and points you toward free refreshers for anything that feels shaky.

First, the reassurance that matters most: you do not need any prior security experience. This is a first serious security book by design. Every security concept — threats, controls, the CIA triad, firewalls, encryption, identity, detection, governance — is built up from scratch, in order, with a concrete story before every abstraction. What you do need is enough general computing background that we can talk about networks, systems, and a little code without stopping to explain what a file or an IP address is. If you have worked in IT, studied computer science, run a home lab, or are simply a technically curious person comfortable around a computer's inner workings, you are ready.

What you should know going in

1. Basic networking. You should know, roughly, that computers communicate over networks using addresses and protocols. Helpful to have met before: IP addresses (the difference between a private 192.168.x.x address and a public one), ports (that a web server "listens on port 443"), the idea of TCP versus UDP, what DNS does (turns example.com into an address), and what a router and a firewall broadly do. You do not need to subnet in your head or recite the OSI layers — Chapter 6 builds all of that carefully from the defender's point of view. You just need to not be starting from "what is an IP address?"

2. The command line (Linux/Unix). A great deal of defensive work happens at a shell prompt. You should be comfortable opening a terminal, moving between directories (cd, ls, pwd), reading files (cat, less, grep), and running a command with flags. Familiarity with Windows PowerShell helps too, since much of the world (including Meridian) runs Windows — but Linux comfort is the more important of the two. If you can navigate a filesystem and search a log file with grep, you have enough to start.

3. Basic Python. The bluekit toolkit you build is written in Python 3.10+, and several exercises involve reading or lightly modifying code. You should be able to read a function, follow a for loop and an if statement, understand a list and a dictionary, and run a .py file. You do not need to be a strong programmer, know object-oriented design, or have written anything large. Every code example is short (under ~40 lines), heavily commented, and ends with its expected output written out by hand, so you can follow the logic even if you would not have written it yourself. If you have done an introductory Python tutorial, you are set.

4. Operating-system concepts. A general sense of how an operating system works helps throughout Part III especially. Useful to have met: processes, files and file permissions, users and privileges (the idea of an administrator or root account versus a normal user), services/daemons that run in the background, and the rough idea that Windows, Linux, and macOS do these things differently. Again, breadth over depth — you need the vocabulary, not mastery.

5. A learning lab (recommended, not required). You can read this entire book without touching a keyboard, but you will learn far more if you set up a small, safe lab to try things in. That means a virtual machine or two on your own computer — free virtualization software plus a free Linux distribution is enough to start, and you can add a Windows evaluation VM later. A lab is where the "🧩 Try It in the Lab" callouts come alive, and where you can practice safely and legally on systems you own. Chapter 39 expands on building a home lab; you do not need anything elaborate on day one.

A quick self-check

Read these. If you can answer most of them without looking anything up, you are ready. If a few stump you, that is fine — just skim the matching refresher below before you reach the relevant part.

  1. Networking: What is the difference between a private and a public IP address, and what does a firewall do at the most basic level?
  2. Ports/protocols: A web browser connecting securely to a website typically uses which port, and is HTTPS carried over TCP or UDP?
  3. Command line: How would you list the files in a directory and then search one of them for the word error?
  4. Python: What does this print? python for n in [2, 4, 6]: if n > 3: print(n * 10)
  5. OS concepts: What is the practical difference between a normal user account and an administrator (or root) account, and why does it matter for security?

Answers

  1. A private IP (e.g., 192.168.1.10) is used inside a local network and is not routable on the public internet; a public IP is globally reachable. A firewall, at its simplest, allows or blocks network traffic according to rules. 2. Port 443, carried over TCP. 3. ls to list, then grep error filename (or grep error * to search all files). 4. It prints 40 and 60 (4 and 6 are greater than 3; 2 is not). 5. An administrator/root account can change the system, install software, and access anything; a normal user is limited. It matters because limiting privileges contains the damage when an account is compromised — the principle of least privilege you will meet in Chapter 3.

Where to brush up

Everything above is covered for free online, and you do not need to master any of it before starting — just close the biggest gaps:

  • Networking: any introductory "how the internet works" or "networking fundamentals" course or tutorial; look for coverage of IP addressing, ports, TCP/UDP, and DNS. The networking chapters of a CompTIA Network+ study guide are an excellent (and free-to-find) primer if you want structure.
  • Linux command line: any "Linux basics" or "command line crash course" tutorial that covers navigation, viewing files, and grep. An hour is enough to be dangerous.
  • Python: any reputable beginner Python tutorial through functions, loops, conditionals, lists, and dictionaries. You can stop well before advanced topics.
  • OS concepts: a short "operating systems basics" overview covering processes, files, permissions, and users.

If you can comfortably handle the self-check, open Chapter 1 now. If a couple of items gave you pause, spend an evening with the matching refresher and then begin — the foundation will be solid enough, and the rest you will build as you go. Security rewards the curious far more than it rewards the already-expert, and curiosity is the one prerequisite this book cannot supply. The rest you can learn here.