Cybersecurity and Ethical Hacking: Fundamentals

Every security choice is a trade between three goals. If you cannot say which goal a rule protects, you cannot judge whether the rule is worth its cost. This lesson gives you those three words. It also shows you the road ahead, so nothing later comes as a surprise.

Security is the work of keeping information and systems safe from harm. Experts sort that harm into three goals. Together they are called the CIA triad. (The letters here have nothing to do with any government agency.)

1. Confidentiality means only the right people can see the data. Your medical record should not be readable by your neighbor.
2. Integrity means the data is correct and only the right people can change it. A bank balance that anyone can edit has no integrity.
3. Availability means the data and systems work when you need them. A shop website that is down on a busy day fails this goal.

An attacker usually aims at one goal. A data thief attacks confidentiality. Someone who quietly changes a payment list attacks integrity. Ransomware attacks availability. Ransomware is software that locks your files until you pay.

A hacker is a person who explores how systems work and makes them do things their makers did not plan. The word covers good and bad people. An ethical hacker, also called a penetration tester, tests a system with the owner's permission, reports the weak spots and helps fix them. A criminal makes the same moves without permission and to cause harm. Permission is the only difference that matters. The next lesson is all about it.

Here is how this course works. It has six modules and 24 lessons. Every lesson has the same six parts: what you will be able to do, why it matters, the teaching, a worked example, common mistakes and a check that tells you when you are done. Every module ends with a project piece. The pieces add up to one document: a written security assessment of a practice lab. You will build that lab on your own computer. You will test only that lab, then fix it, then write the report.

Plan for about 20 to 40 minutes a lesson. Do the hands-on task each time. Reading alone will not make the ideas stick.

Example (illustrative): Maria runs a small dental office. She lists what matters most.

• Patient records. Confidentiality matters most. A leak harms patients and breaks trust.
• The appointment calendar. Integrity and availability both matter. A wrong time or a dead calendar means missed patients.
• The front-desk computer. Availability matters most. If it fails, the whole office slows down.

Then she asks one question about each item: which goal would hurt most if it failed? That question shapes her plan. She locks down the records first. She sets up backups for the calendar second. She does not spend money on the front-desk computer until the first two are safe.

Notice that Maria did not start with tools. She started with what she must protect and why.

• Thinking security means secrecy. Secrecy is only one goal. A system nobody can use fails on availability. Fix: check all three goals every time.
• Thinking every hacker is a criminal. This makes people afraid to learn. Fix: use the word attacker for the person who causes harm and ethical hacker for the person who has permission.
• Skipping the notes. Every later module builds on what you write now. Fix: make the folder and the file below before you move on.

You can write the three goals from memory with one example each. Your folder named secure-lab holds a file named assessment.md with your five items and your one-sentence answer.