Cybersecurity: the course for complete beginners
Contents
Chapter 1: The foundations
Chapter 2: Computers and networks, the basics
Chapter 3: Linux and the command line
Chapter 4: Web and application security
Chapter 5: The most common threats (field version)
Chapter 6: Basic computer security tools
Chapter 7: The basics of ethical hacking
Chapter 8: Your everyday personal security
Chapter 9: Projects to get started
Chapter 10: The basics of incident response
Chapter 11: The final project
This IT and security course starts from zero and assumes you know nothing. Every complicated word is explained in everyday language, and when a real technical term exists, we give it to you, with this marker:
The pros’ word: example. Here, we explain the word in plain language. You learn the real vocabulary without getting lost.
This edition is adapted to our reality: in Benin, Côte d’Ivoire and across the sub-region, most people’s first computer is their phone. And today, money mostly moves through mobile money (MTN MoMo, Moov Money, Orange Money, Wave, Celtiis Cash depending on your country). So the examples in this course start from there.
Rule number one, before anything else. Everything you learn here is for protecting yourself and practising on your own machines. You never test someone else’s phone, computer, website or network without their written consent. Doing it, even “just to see”, is illegal.
How to read this IT course for beginners
Each chapter is a series of short “How to” articles. Read them in order and take your time. There is nothing to learn by heart: the goal is to understand.
Three words come up everywhere, so you might as well learn them right away.
The threat: someone who could harm you.
The flaw: a weakness, like a door that doesn’t close properly. The pros’ word: a vulnerability.
The risk: the chance that things go wrong, and the damage it would cause.
Chapter 1: The foundations
Understanding what cybersecurity (computer security) is, and why it matters
Think of your home, or your shop. You lock the door, you don’t leave your money on the counter, you’re wary of a stranger hanging around. That is security.
Well, cybersecurity is the same thing, but for everything digital: your phone, your mobile money account, your WhatsApp, your Facebook page, your photos, your contacts.
It has become so important because almost your whole life is on your phone. Someone who gets in without permission can empty your MoMo account, pretend to be you to your contacts to get money out of them, or destroy what you care about.
How a cyberattack works, roughly
A cyberattack is someone (or a program) trying to get in where they have no right to be, or to break or steal something.
Almost all attacks follow the same, very human path:
Observe. The attacker studies their target, like a thief spotting the easiest shop.
Find a weakness. A MoMo code that is too simple, a phone that is never updated, a person who is too trusting.
Get in. They use the weakness.
Act. Steal money, scam your contacts, take over your account.
The good news is that most attacks work because of really silly weaknesses. So by learning the basics, you already protect yourself enormously.
Understanding threat, flaw and risk
The shop image works perfectly.
The threat is the scammer hanging around. They exist, and there’s nothing you can do about it.
The flaw is your secret code that anyone can guess (like 1234).
The risk is both together: “there are scammers AND my code is easy, so I’m at serious risk”.
You can’t make scammers disappear, but you can fix your flaws, and by fixing your flaws you lower the risk. That is all of cybersecurity in a nutshell.
Recognising the types of attackers
Not all attackers are the same.
The curious one. They try things found on the internet, with no real plan. Not very dangerous, but there are a lot of them.
The everyday scammer. The most common one around here. Fake MoMo deposit, fake MTN or Orange lottery win, fake agent, fake buyer. They want your money.
The manipulator. They don’t break anything: they sweet-talk you so that you hand over your code or your OTP yourself (chapter 5).
The highly organised attacker. Very skilled, they target banks, companies or governments. You will probably never come across one, but know that they exist.
Understanding the cybersecurity cycle
Protecting yourself is not a one-off action, it’s a loop that keeps turning. It is summed up in five steps.
Identify. Know what is precious to you (my MoMo account, my WhatsApp, my photos).
Protect. Put up barriers (strong codes, updates, backups).
Detect. Notice when something is wrong (a withdrawal SMS for a withdrawal you didn’t make).
Respond. React fast (call the operator, block, change your codes).
Recover. Repair and get back to normal.
The pros’ word: the NIST framework. These five steps have a name. It’s a very well-known model, created in the United States, called the NIST framework. You’ll come across it again.
Chapter 2: Computers and networks, the basics
How computers talk to each other on a network
A network is several connected devices exchanging messages. When your phone loads a video, it asks a distant computer for it, and that computer sends it back.
The closest image is the postal service. To send a letter, you need an address, an envelope and a sorting system. A network is the same.
The pros’ word: the packet. A message doesn’t travel in one piece. It is cut into small pieces, and each piece is called a packet. The packets travel, then are put back together on arrival. That’s also why your data bundle runs out: you pay for those packets.
How IP addresses, ports and protocols work
Three words, explained with the postal service.
The IP address is the machine’s postal address. It says where it is. Example: 192.168.1.10.
The port is the door number. A machine can do several things at once (a website, a messaging service…), and each service has its own door. A port is just a number.
The protocol is the language used to talk to each other. Two machines must speak the same language to understand each other.
Summary: the IP says where, the port says which door, the protocol says how they talk.
The pros’ word: TCP/IP. The set of rules that makes all this work is called TCP/IP. It’s the “basic language” of the internet.
How DNS and HTTP/HTTPS work
The DNS is the internet’s phone book. You type an easy name, like exemple.com, but machines only understand numbers (IP addresses). DNS does the translation: it turns the name into a number, just as a contact list turns a contact’s name into a phone number.
The HTTP is the language of websites, in other words the way your browser asks for a page and the way the site sends it back.
The HTTPS is HTTP in a sealed envelope. The little “S” stands for “secure”.
The pros’ word: encryption. Making a message unreadable to anyone who might intercept it on the way is called encrypting. With HTTPS, your code travels encrypted. That’s why you never type a password or a code on a site without the little padlock.
How routers, firewalls and VPNs work
The router is the sorting centre of your connection. At home, it’s your box: the MTN box, Orange’s Livebox, the Moov box, or the CanalBox (fibre). It receives messages and sends them to the right device, your phone, the TV or the computer. When you turn on hotspot sharing to help out a friend, your phone becomes a small router too.
The firewall is a guard at the entrance. It watches who comes in and who goes out, and blocks whatever is not allowed. The pros’ word: “pare-feu” is simply the French for firewall.
A VPN is a private, opaque tunnel. Normally, some intermediaries can see where you go on the internet. A VPN hides all that in an encrypted tunnel, and nobody around you can see what you’re doing. Very useful on shared Wi-Fi (maquis, hotel, cybercafé).
A word about your box. Your MTN, Orange, Moov or CanalBox box often comes with a Wi-Fi password written on the back, something like admin or a simple sequence. Change it. Otherwise, your neighbours can use your connection, drain your bundle, and sometimes see your traffic. We explain how to make a good password in chapter 8.
How to use basic network commands
A command is an instruction you type on the keyboard instead of clicking. The next two are harmless, you can try them on a computer.
ping is used to check whether a machine responds, like shouting “are you there?” and waiting for the echo.
ping google.com
If you get replies, the machine is reachable.
To see your own address on the network:
ipconfig (on Windows)
ip a (on Linux or Mac)
These commands don’t break anything. They just look, that’s all.
Chapter 3: Linux and the command line
How to install and use Linux
Linux is an operating system, in other words the core software that runs the computer, like Windows or macOS. It’s free, it’s used everywhere in security, and you can look at everything inside it.
You don’t need to remove Windows. To learn, the simplest option is to install Linux in a virtual machine, a “computer in a window” (we cover this in chapter 7). In cybercafés, PCs often run Windows: to practise seriously, your own machine is better, even a modest one.
The pros’ word: a distribution. There are lots of versions of Linux. Each version is called a distribution (or “distro”). To start, the easiest one is called Ubuntu.
How to move around in the command line
The command line is a window where you type orders instead of clicking. It’s intimidating at first, but it’s simply another way of talking to the computer.
The pros’ word: the terminal. This window is called a terminal (or “shell”). Remember the word, it’s used all the time.
A few basic orders:
pwd shows where you are (the current folder)
ls lists what’s in the folder
cd changes folder (like walking into a room)
cd .. goes up to the folder above
Example: cd Documents takes you into Documents, then ls shows you what’s inside.
How to manage files and permissions
Create, copy and delete files:
touch note.txt creates an empty file
mkdir dossier creates a folder
cp a.txt b.txt copies a.txt to b.txt
mv a.txt Documents/ moves a.txt into Documents
rm note.txt deletes the file (careful, there’s no recycle bin!)
A very important point for security now: permissions.
Every file has rules that say who is allowed to read it, modify it or run it. It’s like keys you give to certain people only.
ls -l shows the permissions of each file
You’ll see sequences like rwxr-xr--. In simple terms: r = read, w = write, x = execute (run).
The pros’ word: least privilege. The idea to remember: you give each person only the rights they need, no more. This principle is called least privilege, and it’s a golden rule of security.
How to run commands and install software
To install software on Ubuntu, you use a “command-line store”:
sudo apt update updates the list of software
sudo apt install nom_du_logiciel installs a piece of software
The pros’ word: sudo. The word sudo means “do this as administrator”. It’s the master key ring: powerful, so use it carefully. The administrator is also called root.
Understanding basic security on Linux
Three simple habits already go a long way.
Update often. An up-to-date machine has fewer known flaws.
Don’t be administrator all the time. Use a normal account, and switch to sudo only when you need to.
Apply least privilege. Each person and each program has only the rights it needs.
Chapter 4: Web and application security
How websites and web applications work
Picture a maquis. You (your browser) are the customer. The website is the kitchen. You place your order, the kitchen prepares it, and you get served. You never go into the kitchen yourself.
The pros’ word: client and server. Your browser (or your app) is the client. The distant computer that hosts the site is the server. This client / server pair is the basis of the whole web and of all your apps.
How the browser talks to the server
When you open a page or an app:
Your phone asks DNS for the service’s IP address (the phone book, remember).
It sends a request to the server: “give me the page”.
The server sends back a response: the content.
Your phone displays it nicely.
The pros’ word: request and response. The ask is called a request, and what comes back is called a response. The web is a request / response exchange, over and over again.
How authentication and authorisation work
These two words look alike but mean different things.
First, authentication means proving who you are, like showing your ID card. Your password or your MoMo code is used for that.
Then, authorisation is what you are allowed to do once you’re in. In your mobile money app, you prove who you are with your code (authentication), then you can only touch your own account, not other people’s (authorisation).
Mixing the two up creates classic flaws, for example a service that properly checks who you are, but then lets you see someone else’s data.
How passwords and sessions work
Your password proves your identity once. Since the service isn’t going to ask you for it again at every click, it gives you a session after you log in.
It’s the little ticket you’re handed at the entrance: as long as you have it, you can move around without showing your ID again.
The pros’ word: the cookie. This “ticket” is stored in a small file on your device, called a session cookie. If someone steals your cookie, they can pretend to be you. That’s why sessions expire, and why HTTPS matters: it stops anyone from stealing your ticket on the way.
Another important point: a good service never stores your password in plain text.
The pros’ word: hashing. The service turns your password into a fingerprint that cannot be reversed. This transformation is called hashing (a “hash”). So even if the database is stolen, the passwords cannot be read directly.
Understanding common web flaws
The main families, in simple terms, to understand and defend, not to attack.
Injection. The site trusts what you type too much. Instead of writing your name, someone can slip in a disguised order, and the site blindly executes it. The best-known case targets databases: the pros’ word is SQL injection. Defence: never trust what the user types, always check it.
Session theft. Someone grabs another person’s “ticket” (the cookie). Defence: HTTPS everywhere, sessions that expire.
Weak passwords. Nothing technical, just guessable codes. Defence: long, unique passwords, and two-factor authentication.
Outdated software. A flaw already known and fixed elsewhere, but still there. Defence: update.
The pros’ word: the OWASP Top 10. A team of specialists publishes the list of the ten most common web flaws. It’s called the OWASP Top 10, and it’s the reference for beginners and experts alike.
How to secure a small web application
Five habits already solve the vast majority of problems.
Always use HTTPS.
Never trust the data sent by the user. Always check it.
Store passwords hashed, never in plain text.
Update the components you use.
Give as few rights as possible to each part (least privilege, once again).
Chapter 5: The most common threats (field version)
This is the most important chapter for your daily life. Around here, most attacks don’t target machines but people, and they often revolve around mobile money. Read it slowly.
How phishing works
Put simply, phishing is fishing for information. The scammer sends you a message (SMS, WhatsApp) that looks like a real one: your operator, your bank, a delivery service. The message puts pressure on you (“your MoMo account will be blocked today”) and pushes you to click a link, which leads to a fake site, a copy of the real one. If you type your code there, you hand it straight to the scammer.
Around here, it mostly takes these forms:
“You have won 2,000,000 FCFA in the MTN / Orange lottery, click here.”
“Moov Money: your account is suspended, confirm your details at this link.”
A fake link that imitates an operator’s name, with a small typo (mtn-momo-gain.xyz instead of the real site).
It’s the most widely used method, because it targets not the machine but the human, who is easier to fool.
The pros’ word: phishing. In French, phishing is called “hameçonnage”. Sent by SMS, it’s called smishing; by phone call, vishing. You’ll see these words everywhere.
The mobile money scam (a must-know)
Mobile money is target number one. The big scams:
The fake deposit. You get an SMS that looks like “you have received 50,000 FCFA”, then someone calls: “sorry, I sent it to the wrong number, send the money back to me”. In reality, you received nothing: the SMS was fake. Never send anything back without checking your real balance yourself.
The fake agent. Someone calls you claiming to be an MTN, Orange or Moov agent, and asks for your code or a code received by SMS “to unblock your account”. A real operator never asks for your secret code or your OTP.
The withdrawal in your name. The scammer got your code out of you, then withdraws your money at an agent.
The golden rule of mobile money. Your secret code and the code received by SMS (the OTP) are given to nobody. Not to an “agent”, not to “customer service”, not to a friend, not to your family on the phone. Never.
The pros’ word: the OTP. The single-use code received by SMS to confirm a transaction is called an OTP (“One-Time Password”). Giving it to someone means opening your account to them.
How fraudulent SIM swapping works
This scam is serious and very real around here. The scammer goes to the operator (or an accomplice agent) and pretends to be you to get a new SIM card with your number. As soon as it works, your SIM loses signal, and they are the one receiving your SMS messages, and therefore your OTP codes. They can then empty your MoMo and take over your accounts (WhatsApp, email…).
The pros’ word: the SIM swap. This fraudulent SIM card exchange is called a SIM swap. Two signs should alert you immediately: your SIM loses network for no reason in the middle of the day, or you receive a “SIM change” message you didn’t ask for. If so, call your operator quickly to block it.
How malicious software works
A malicious program is software made to do harm. On a phone, it can read your SMS messages (and so your OTPs), spy on what you type, or display fake pages on top of your apps. It often arrives through an app downloaded outside the official store (an .apk received on WhatsApp), pirated software, or a booby-trapped link.
The pros’ word: malware. The official word is malware (a blend of “malicious” and “software”). Basic defence: only install apps from the official store (Play Store), don’t open .apk files received by message, and stay up to date.
How ransomware works
So-called ransomware is a particularly nasty kind of malware. It locks all your files by making them unreadable, then displays a message demanding money to give you back access. It’s a digital hostage-taking.
The pros’ word: ransomware. In French it’s called “rançongiciel” (“ransom” means “rançon”).
The only real protection is backup. If you have a recent copy of your files somewhere else (a USB stick put away safely, a cloud like Google Photos), the blackmail no longer works: you restore and ignore the demand.
How social engineering works
In short, social engineering means manipulating people instead of machines. The scammer doesn’t crack any code. They play on fear, trust, pity or greed.
You’ll mostly recognise it in these forms:
A loved one’s hacked WhatsApp account: “it’s me, I have a problem, quickly send me airtime or MoMo money”. Always call the person back to check.
The fake “you’ve won”, the fake job or the fake scholarship that asks for “processing fees” upfront.
The fake buyer on Jiji or in sales groups, who “has already paid” and sends you fake proof.
The best defence is doubt. Always check the identity of the person you’re dealing with through another channel before giving anything.
How attacks on passwords and codes work
Three methods come up again and again.
Guessing: trying the classics. For a 4-digit MoMo code, that’s 0000, 1234, 1111, or your year of birth. Avoid these at all costs.
Brute force: a program automatically tries thousands of combinations, very fast. The pros’ word: brute force.
Reuse: if your password leaks on one site, the scammer tries it on all your other accounts.
Hence the rules: a code that isn’t linked to your life (no date of birth, no simple sequence), a long and unique password for each account, and two-factor authentication whenever possible.
How to spot a suspicious link, file or message
A few simple warning signs.
A sense of urgency or a threat (“act right now”, “your account will be blocked”).
A prize that’s too good to be true (“you have won”).
A strange sender or website address that doesn’t exactly match the real name.
Language mistakes, clumsy French.
An unexpected attachment, especially an .apk file to install.
A request for your secret code or your OTP. It is always a scam.
The right reflex: when in doubt, don’t click and don’t call back the number in the message. Contact the service through its known official channel.
Chapter 6: Basic computer security tools
Reminder: these tools are used on your own hardware or in a training lab. Pointing them at a machine that isn’t yours, without permission, is illegal.
How to use Wireshark to observe network traffic
Wireshark is a pair of glasses that makes the mail visible. Remember: data travels in small packets. Wireshark catches those packets and shows them to you one by one, with where they come from, where they’re going and what they contain.
The pros’ word: packet capture. Catching traffic to examine it is called doing a packet capture (or “sniffing”).
For beginners, it’s mainly used to see for real what you’ve learned: IP addresses, ports, the difference between HTTP (readable) and HTTPS (encrypted, so unreadable). It also shows you, very concretely, why an unprotected maquis Wi-Fi is risky.
How to use Nmap in a safe lab
Nmap knocks on a machine’s doors to see which ones are open. Remember ports, those doors behind an IP address. Nmap tests them and tells you which ones answer, and therefore which services are running.
The pros’ word: the port scan. This action is called a port scan.
Example, on your own test machine:
nmap 192.168.56.101
It will tell you, for example, “port 80 is open” (so a website is running there). Once again: only on targets that are yours, or designed for training.
How to use a basic vulnerability scanner
A vulnerability scanner inspects a machine and compares it with a list of known weaknesses, then tells you: “careful, this software has such-and-such known flaw”. It’s like a vehicle roadworthiness test, which ticks off a checklist.
The pros’ word: the CVE. Every known flaw gets an official number, something like CVE-2024-1234. This number is called a CVE. It’s a flaw’s worldwide ID card.
How to inspect logs
The logs are your machines’ logbook. Every important event is written there: a login, an error, a refused access. Knowing how to read them means knowing how to tell what happened.
The pros’ word: logs. In French these records are called “journaux”, but everyone says logs. You’ll hear the word every day in security.
On Linux, to look at a log:
cat /var/log/auth.log shows the login log
tail -f /var/log/auth.log displays it live, line by line
As a beginner, you look for repeated failed logins, a login at an odd hour, an error that keeps coming back.
How to use testing tools in a controlled environment
There are ready-made systems that bundle security tools together.
The pros’ word: Kali Linux. The best-known distribution for training is called Kali Linux. It comes with hundreds of tools already installed.
At your level, the goal is not to pile up tools, but to understand what each one does, and to use them only in your lab. A tool you don’t understand is useless, and dangerous if it’s pointed the wrong way.
Chapter 7: The basics of ethical hacking
How ethical hacking works
Doing ethical hacking means using the same techniques as an attacker, but with permission, and to protect.
Think of a locksmith. They know how to pick a lock. If they do it at the owner’s request, to test their door, it’s a respected profession. If they do it on the neighbour’s door, it’s a crime. The only difference is authorisation, so remember that word well.
The pros’ word: the pentest. An authorised security test is called an intrusion test, or pentest (from “penetration testing”). The person who does it is a pentester. It’s a real job, including in our banks and telecom companies.
How to set up a legal cybersecurity lab
A lab is your closed playground: a place of your own where you can break everything, with no consequences and nothing illegal.
The idea is to run several “computers in windows” (virtual machines) on your computer, in an isolated network that touches neither the internet nor the rest of your home.
What you need:
Software to create virtual machines. VirtualBox is free and perfect to start with.
An “attacker” machine: for example Kali Linux.
One or more deliberately weak “target” machines, made for training.
Local tip: these images weigh several GB. Download them on a good connection (CanalBox fibre, the Wi-Fi of a school or a coworking space) rather than on your data bundle, so you don’t drain it.
How to create virtual machines to practise
A virtual machine is a complete computer, but simulated by software. It lives in a window on your real computer. You can switch it on, switch it off, break it and start again from scratch, without ever touching your real machine.
The pros’ word: the VM. A virtual machine is called a VM. The software that runs them is called a hypervisor.
The steps, in simple terms:
Install VirtualBox.
Download the system you want (Ubuntu or Kali, for example).
In VirtualBox, create a new machine and give it that system.
Set its network to isolated mode, so that it stays in your lab. The pros’ word: a “host-only” or “internal network”.
Take a picture of the VM’s state, so you can go back to it in one click if you break everything. The pros’ word: a snapshot.
How to spot vulnerabilities in your own systems
On your lab VMs, practise the full approach. List the running services (with Nmap). Check whether they are up to date. Look at the passwords being used. Examine the file permissions.
At this stage, it’s not yet about attacking, but about learning to see weaknesses, like an inspector spotting the defects in a house.
The pros’ word: the attack surface. All the points through which someone could get in (open ports, services, accounts…) are called the attack surface. The smaller it is, the better.
How to do basic reconnaissance in a lab
The reconnaissance stage is about observing, before anything else. You gather information about the target.
In your lab, on your training target, that means answering simple questions. What is its IP address? Which ports are open? Which services are running behind them? Which versions?
The pros’ word: recon and enumeration. Pros say recon (for reconnaissance). When you list in detail everything a machine exposes, it’s called enumeration.
How to document and report your findings
In security, taking notes is as important as finding. For each finding, write down:
What you found (the weakness).
Where and how you found it (the machine, the command).
Why it’s a problem (the risk).
How to fix it (the recommendation).
The pros’ word: the pentest report. This final document is called the pentest report. A good, clear report is worth more than a brilliant find that is poorly explained.
Chapter 8: Your everyday personal security
Around here, protecting yourself first means protecting your phone and your mobile money.
How to secure your phone
Your phone is your bank, your address book and your photo album. Protect it:
Set a strong screen lock (6-digit code, hard pattern, or fingerprint). Not 0000.
Update Android and your apps as soon as it’s offered.
Install only from the Play Store. Never install an .apk received on WhatsApp or found on some random website.
Clean up the permissions. A torch app doesn’t need to read your SMS messages. Remove unnecessary access in the settings.
Turn on remote location (“Find My Device”) so you can lock or wipe your phone if it’s stolen.
How to secure your mobile money
This is the most important part of the whole course.
Your secret code and your OTP are never shared. With anyone. We said it in chapter 5, and we repeat it because 9 scams out of 10 go through there.
Choose a code that’s impossible to guess. Not your date of birth, not 1234, not 1111.
Always check the recipient’s name before confirming a transfer. One wrong digit, and the money goes to a stranger, with no way back.
Check your real balance yourself before “refunding” a deposit received by SMS. The SMS may be fake.
Keep the customer service contact of your operator (MTN, Orange, Moov, Celtiis) to block quickly if there’s a problem.
How to protect your SIM card
Your SIM receives your OTP codes: it’s a precious key.
Turn on the SIM PIN code (the one requested when the phone starts up). That way, a stolen SIM can’t be used as is.
Stay alert to SIM swap (chapter 5): if your SIM loses network for no reason in the middle of the day, call your operator quickly.
How to create and manage strong passwords
A good password is long (a whole sentence is better than a complicated word), unique for each account, and not guessable from your life.
Nobody can remember fifty sentences, so you use a digital safe that remembers them for you.
The pros’ word: the password manager. This tool is called a password manager. You only remember one password: the one for the safe.
How to use two-factor authentication
Using two-factor authentication means adding a second proof on top of the password.
Like a withdrawal at the counter: you need your ID (something you have) and sometimes a code (something you know). Even if someone steals your password, they’re missing the second key.
The pros’ word: MFA or 2FA. It’s called 2FA (“two factors”) or MFA (“multiple factors”). Turn it on wherever you can, starting with your email and WhatsApp. On WhatsApp, it’s called “two-step verification”: turn it on, it’s the best protection against your account being hacked.
How to secure your accounts
Your email is the key to everything else: it’s through your email that the passwords of other services are reset. Protect it first, with a unique, strong password and two-factor authentication.
Then apply the same logic to WhatsApp, Facebook and your sensitive accounts.
How to use a cybercafé or shared Wi-Fi safely
On a cybercafé PC, you’re not at home: other people use it after you.
Don’t do mobile money or banking on a shared PC.
Never save your password in the cybercafé’s browser.
Use private browsing mode, and above all log out of all your accounts before you leave.
On shared Wi-Fi (maquis, hotel, airport), you don’t know the other people connected. Avoid sensitive operations, check that you’re on HTTPS, and if you can, use a VPN (the opaque tunnel from chapter 2).
How to protect your personal data
Two ideas to keep in mind. First, the less you share, the less exposed you are, so think before posting your number, your photos or your location. Second, back up what matters: the best way never to lose your memories is to always have a copy somewhere else (a USB stick put away safely, or a cloud like Google Photos).
Chapter 9: Projects to get started
These small projects are done entirely at home, on your own hardware. They turn theory into practice.
How to build a home cybersecurity lab
This is the starter project, already described in chapter 7. In short: install VirtualBox, create an attacker VM (Kali) and a deliberately weak target VM, put them in an isolated network, and take a snapshot of each. You have a safe, unlimited playground.
How to analyse your own computer’s traffic
Install Wireshark on your machine. Start a capture, then open a web page, and an HTTPS site.
Watch the difference. With HTTP, you can read what goes through; with HTTPS, everything is scrambled. You’ll see with your own eyes why the little padlock matters. The goal is to put a concrete picture on the words from chapter 2.
How to assess the security of a test application
There are deliberately weak applications, made for learning.
The pros’ word: deliberately vulnerable apps. The best known are called DVWA (“Damn Vulnerable Web Application”) and OWASP Juice Shop. They are made on purpose for practising on, completely legally.
Install one in your target VM, then practise the approach: reconnaissance, spotting weaknesses, taking notes. You learn on ground designed for it, without ever touching a real site.
How to build a password strength checker
A first real coding project, very simple, in Python. It looks at a password and says whether it’s strong. Copy this code into a file called verif_mdp.py, then run it.
import re
def verifier(mot_de_passe):
score = 0
conseils = []
# 1. Length: the most important criterion
if len(mot_de_passe) >= 12:
score += 2
elif len(mot_de_passe) >= 8:
score += 1
else:
conseils.append("Too short: aim for at least 12 characters.")
# 2. A mix of character types
if re.search(r"[a-z]", mot_de_passe): score += 1
else: conseils.append("Add lowercase letters.")
if re.search(r"[A-Z]", mot_de_passe): score += 1
else: conseils.append("Add uppercase letters.")
if re.search(r"[0-9]", mot_de_passe): score += 1
else: conseils.append("Add digits.")
if re.search(r"[^a-zA-Z0-9]", mot_de_passe): score += 1
else: conseils.append("Add a special character (!, ?, #...).")
# 3. The verdict
if score >= 5:
niveau = "STRONG"
elif score >= 3:
niveau = "MEDIUM"
else:
niveau = "WEAK"
return niveau, conseils
mdp = input("Enter a password to test: ")
niveau, conseils = verifier(mdp)
print(f"\nStrength: {niveau}")
for c in conseils:
print(" - " + c)
This project teaches you two things at once: a bit of programming, and above all what makes a password strong. To go further, you can add a list of MoMo codes to ban (0000, 1234, years of birth…) and reject those values.
How to create a simple log monitoring project
Goal: write a small program that reads a log file and alerts you when a suspicious word appears, for example several failed logins. It’s a very first version of what real monitoring tools do.
# Reads a log and counts failed login attempts
mot_a_surveiller = "Failed password"
compteur = 0
with open("/var/log/auth.log") as fichier:
for ligne in fichier:
if mot_a_surveiller in ligne:
compteur += 1
print("Failed attempt detected:", ligne.strip())
print(f"\nTotal failed attempts: {compteur}")
if compteur > 10:
print("ALERT: lots of failures, someone may be trying to guess a password.")
What you have here, on a tiny scale, is the principle of detection, step 3 of the cycle from chapter 1.
The pros’ word: the SIEM. Companies use big tools that do this at scale, across thousands of machines. This type of tool is called a SIEM. Your little script has the same spirit, in miniature.
Chapter 10: The basics of incident response
An incident is when something has gone wrong: your MoMo account emptied, your WhatsApp hacked, your phone infected. Knowing how to react calmly changes everything.
The pros’ word: incident response. The whole approach in this chapter is called incident response.
How to recognise a possible security incident
A few signs should alert you. You get a MoMo withdrawal SMS for a withdrawal you didn’t make, or your contacts receive messages from you that you didn’t send. Your SIM loses network for no reason. You are forcibly logged out of WhatsApp. Your phone becomes very slow and heats up for no reason.
A single one of these signs proves nothing, but it deserves to be checked straight away.
How to react fast (the first steps)
In our context, speed matters enormously:
Call your operator (MTN, Orange, Moov, Celtiis) to block your mobile money account and your line if necessary.
Take back your accounts: change your email password, reactivate WhatsApp with two-step verification.
Warn your loved ones that your account has been hacked, so they don’t send anything to the scammer in your name.
How to collect basic evidence
Before cleaning everything up, keep traces of what happened. You don’t sweep a scene before the police have seen it.
In practice, at your level: note the time and what you saw, take screenshots of the suspicious SMS messages, messages and transactions. They will be useful for the complaint and for the operator.
The pros’ word: digital evidence. These carefully kept traces are called digital evidence. The science that studies them is called forensics.
How to isolate a compromised device
The first reflex with a possibly infected device is to isolate it, to stop it spreading. Turn off mobile data and Wi-Fi (airplane mode).
On the other hand, don’t switch it off straight away if you want to investigate, because switching off erases certain live traces. Isolate first, switch off only if necessary.
The pros’ word: compromised device. A device that an attacker has taken control of is said to be compromised.
How to investigate, then document and report
Investigating means reconstructing the story from the traces, by asking questions in order. When did it happen? What was affected? How did it get in?
Then you write everything down clearly: what happened, when, what was affected, what you did to respond, and what you will change so it doesn’t happen again. In case of lost money or identity theft, this report and your screenshots are used to file a complaint.
Where to file a complaint, depending on your country:
In Benin, with the OCRC (Office Central de Répression de la Cybercriminalité, the central office for combating cybercrime), the dedicated police unit. Contact: ocrc@dgpr.bj, tel +229 65 48 78 74 / +229 63 09 51 62, in Cotonou. Careful: don’t confuse the OCRC with the ASIN (Agence des Systèmes d’Information et du Numérique). ASIN is the national agency for digital affairs and cybersecurity (strategy, nationwide incidents); it is not the office where an individual files a complaint about a scam.
In Côte d’Ivoire, with the PLCC (Plateforme de Lutte Contre la Cybercriminalité, the anti-cybercrime platform), in Cocody Danga (Abidjan), tel +225 27 22 48 97 60. Filing a complaint there is free.
Chapter 11: The final project
To finish this course, you will bring together everything you’ve learned in a single, complete and safe project.
The goal
Build your own cybersecurity lab, then assess the security of a deliberately vulnerable application, and write a short report.
The steps
Set up your lab (chapter 7): VirtualBox, a Kali VM (attacker), a target VM with a weak app such as DVWA or Juice Shop, all in an isolated network.
Do some reconnaissance (chapters 6 and 7): with Nmap, discover your target’s address, open ports and services.
Observe the traffic (chapter 6): run Wireshark while you use the app, and watch what goes through.
Spot the weaknesses (chapter 4): identify the known flaws of the training app, drawing on the families covered in chapter 4 and on the OWASP Top 10.
Document (chapter 7): for each weakness, note what it is, where it is, why it’s a risk, and how it would be fixed.
Write your final report: one page is enough. A summary for a reader in a hurry, then the list of findings with their recommendations.
What you’ll be able to do by the end
Understand the basic concepts of cybersecurity.
Understand how a network works.
Use Linux and the command line.
Spot common vulnerabilities.
Use basic security tools.
Protect your phone, your mobile money and your accounts.
Carry out a security test within an authorised framework.
Respond properly to an incident and document your findings.
One last word
You now have the foundations of computer security. Cybersecurity is a field where you keep learning all your life, by practising. Keep three principles with you.
Curiosity, always. Legality, without exception. You practise on what belongs to you, or on what is designed for it. Never on others without authorisation.
Your code and your OTP are never shared. With nobody, under any pretext. This is the rule that will protect you most in everyday life.
The basics beat sophistication. Updates, strong codes, two-factor authentication, backups, caution with phishing: these simple habits stop the vast majority of real attacks.
Safe travels.
This course was written by Salem GNANDI, president of Epihack, Epitech’s student cybersecurity group, and only covers the basics. To go further and become a certified cybersecurity expert, join one of Epitech’s programs: