CSRP TEXTBOOK
Lesson 1 — The Cyber World and the CIA Triad
Module 1 — Infrastructure, Networks & Operating Systems
Cyber Security Responder & Practitioner (CSRP) · In partnership with BDO Ziv Haft · ISC2 CC
How to use this book
This chapter follows the same order as your classroom presentation, so you can read ahead, revise afterwards, or study on your own. Watch for these recurring markers:
- ▶ TIP — a practical pointer that makes the idea stick or saves you time.
- ✎ TRY IT YOURSELF — a small exercise to do yourself — the best way to learn.
- ◆ KEY TERM — a definition worth memorising; the words professionals use daily.
- ✶ REAL-WORLD — a real-world scenario showing why the idea matters.
- ⚑ WATCH OUT — a common misconception or mistake to avoid.
Lesson objectives
By the end of this lesson you will be able to: – Explain the three pillars of the CIA triad and classify which one a security incident violates. – Restore Confidentiality by fixing an over-shared file using the principle of least privilege. – Restore Availability by bringing a service back online and keeping it durably available. – Arm Integrity monitoring and detect an unauthorized change to a file. – Investigate an integrity alert and recover an attacker-planted marker (the Challenge).
What to expect, and what you’ll achieve
The lesson runs about four hours across six chapters, with roughly half the time spent hands-on in the onyxium.io lab. You’ll finish with a working mental model you’ll reuse in every later lesson, practical experience hardening a system across all three pillars, and — once you pass the Challenge — your first verified skill badge, [CIA-Triad-Mastery], on your profile.
Chapter 1 — The Cyber World
Before we can defend, we need to understand the world we are defending and the people we are defending against.
1.1 Why cybersecurity, why now
Every modern organization runs on information and on the computer systems that store, move, and process it. A hospital depends on patient records being accurate and available; a bank depends on account balances that no one can secretly change; a law firm depends on client documents staying private. Cybersecurity is the discipline of protecting these qualities of information — and the systems that hold it — from people and events that would damage them.
Attacks today are constant, largely automated, and profitable, which is why security has become everyone’s concern rather than a niche IT task. There is also a well-known paradox in the field: the world has millions of unfilled cybersecurity roles, yet newcomers struggle to get hired because employers want evidence of practical ability. The CSRP program is designed to close exactly that gap by combining theory with hands-on practice you can prove.
✶ REAL-WORLD In its annual Data Breach Investigations Report, Verizon consistently finds that the large majority of breaches involve a human element — stolen credentials, errors, or social engineering — not exotic ‘movie hacking’. Strong fundamentals stop most real attacks.
1.2 Your role: the organizational defender
Security professionals often speak of two mindsets. The red team thinks like an attacker, probing systems for weaknesses (ethically, to test defenses). The blue team is the defender — the people who design, configure, monitor, and protect an organization’s systems. CSRP trains you primarily as a defender, a practitioner and responder, though you will study offensive techniques later because you cannot defend against an attack you do not understand.
◆ KEY TERM Blue team / defender — the people responsible for protecting an organization’s systems and data: hardening configurations, monitoring for problems, and responding to incidents.
A defender’s goal is not a perfectly impenetrable system — that is impossible. It is to reduce risk to an acceptable level, to detect problems quickly when they happen, and to respond effectively to limit the damage. Good defense is mostly judgment and process, not memorizing every possible attack.
▶ TIP Whenever you meet a new security control in this course, ask: which risk does this reduce, and to which pillar of the CIA triad? That single habit will organize everything you learn.
1.3 The threat landscape
Threats come from people (threat actors) and from circumstances such as hardware failure or human error. Threat actors differ in skill, motivation, and resources:
|
Threat actor |
Motivation |
What it means for a defender |
|
Opportunistic attackers |
Curiosity, bragging |
Use ready-made tools on easy targets; basic hygiene stops most. |
|
Cybercriminals |
Money |
Ransomware and fraud at scale — the biggest day-to-day threat. |
|
Insiders |
Grievance, money, error |
Already trusted and inside; least privilege limits damage. |
|
Hacktivists |
Ideology, publicity |
Defacement and denial-of-service to disrupt or embarrass. |
|
Nation-state (APT) |
Espionage |
Skilled, patient, well-funded; persistent over long periods. |
◆ KEY TERM APT (Advanced Persistent Threat) — a skilled, well-resourced adversary that gains access and stays hidden for a long time to pursue a specific objective. The key word is persistent: they do not give up after one failed attempt.
Two patterns dominate the modern landscape. Ransomware encrypts an organization’s files and demands payment for the key, and increasingly the attackers steal a copy of the data first to threaten a leak — so it harms more than one security property at once. Phishing tricks a person into revealing credentials or running malicious code and is the most common way attackers gain their first foothold. Both receive full lessons later in the course.
✎ TRY IT YOURSELF Think of an organization you know. List two assets worth protecting, one plausible threat actor, and what that actor would want. Keep your notes — you’ll refine them in Chapter 5.
Chapter 1 in one line: you are a defender; your job is to reduce risk, detect fast, and respond — against adversaries ranging from opportunists to patient APTs.
Chapter 2 — Confidentiality
Almost every control you will ever configure protects one or more of three properties: Confidentiality, Integrity, and Availability — the CIA triad.
◆ KEY TERM CIA Triad — the three properties of information that security controls protect: Confidentiality (only the right people can see it), Integrity (it is accurate and unaltered), and Availability (it is usable when needed).
The triad is the most important model in this field because it gives defenders a shared, precise way to answer one question about any incident: what exactly was harmed? A leaked file harms confidentiality; a tampered record harms integrity; a system knocked offline harms availability. One event can harm more than one. We take the pillars one chapter at a time, starting with confidentiality.
2.1 What confidentiality means
◆ KEY TERM Confidentiality — the property that information is available only to those authorized to see it. When it fails, data is disclosed to someone who should not have it.
Confidentiality failures include a salary file readable by the whole company, a database exposed to the public internet, or a stolen laptop whose disk was never encrypted. It is the pillar most people first associate with ‘security’, but it is only one of three.
2.2 How defenders protect confidentiality
- Access control — deciding who can do what to which resource. This is the everyday tool of confidentiality: you grant access to the people who need it and to no one else.
- Least privilege — the principle that each person and program should have the minimum access required for their role, and nothing more. If a salesperson does not need payroll data, they should not be able to open it. Least privilege limits both honest mistakes and the damage an attacker can do with a stolen account.
- Encryption — scrambling data so that, even if intercepted or stolen, it is unreadable without the key. Data can be encrypted at rest (on disk) and in transit (moving across a network).
✶ REAL-WORLD The over-shared payroll file at ‘Meridian Corp’ — the scenario you’ll fix in Practice 1A — is a classic confidentiality failure. No system was ‘hacked’; sensitive data was simply left open to everyone. Most real data exposure looks exactly this mundane.
⚑ WATCH OUT ‘Secure’ is not the same as ‘confidential.’ Encryption protects confidentiality but does nothing to keep a system online (availability) or to prove a file was not altered (integrity). Each pillar needs its own controls.
✎ TRY IT YOURSELF Open Practice 1A — “Who Can See This?” on onyxium.io. Restrict the payroll file to the HR group, then use ‘Test as a Sales user’ to confirm they’re denied. Note which step removes the leak and which step grants the right access.
Chapter 2 in one line: confidentiality keeps data from the wrong eyes, mainly through access control and least privilege; encryption adds protection even when data is stolen.
Chapter 3 — Integrity
If confidentiality is about who can see data, integrity is about whether you can trust that the data has not been secretly changed.
3.1 What integrity means
◆ KEY TERM Integrity — the property that information is accurate, complete, and has not been altered in an unauthorized way.
Integrity failures include a bank balance someone secretly edits, a software update swapped for a malicious version, or a log file quietly deleted to hide an intrusion. These are dangerous precisely because they can go unnoticed — which is why we need a tool that makes change visible.
3.2 The hash: a fingerprint for data
The central tool for detecting change is the hash. A hash function takes any data — a file, a message, a password — and produces a short, fixed-length string called a digest or fingerprint, with two important properties:
- Deterministic — the same input always produces the same digest.
- Sensitive to change — changing even a single character of the input produces a completely different digest.
So if you record a file’s hash today and the file is altered tomorrow, re-hashing it yields a different value and you know it changed. Common hash algorithms you’ll hear named include SHA-256.
◆ KEY TERM Hash (digest / fingerprint) — a one-way, fixed-length representation of data used to detect change. It cannot be reversed to recover the original data.
✎ TRY IT YOURSELF If you have a terminal at home, run a hash of a short text file, change one character, and hash it again — notice the digest changes entirely. (We do this for you in the lab if you don’t.)
3.3 File Integrity Monitoring (FIM)
A File Integrity Monitor puts hashing to work: it stores a baseline of fingerprints for important files, then periodically re-hashes them and alerts you to any file whose fingerprint no longer matches. A FIM detects the effect of a compromise even when the cause is unknown — which is exactly the situation in this lesson’s Challenge.
⚑ WATCH OUT A hash is not a password and not encryption. It is a one-way fingerprint used to detect change; it hides nothing and cannot be reversed.
▶ TIP Integrity controls also include digital signatures (which prove both integrity and who created the data) and input validation (which stops malicious data from corrupting a system). We return to both later in the course.
✎ TRY IT YOURSELF Open Practice 1C — “Catching Tampering”. Capture a baseline, run a check, make the demo change, and run the check again. Study the old-vs-new fingerprint view; you’ll rely on it in the Challenge.
Chapter 3 in one line: integrity means data is unaltered; a hash is a one-way fingerprint, and a File Integrity Monitor uses it to detect tampering.
Chapter 4 — Availability
The pillar beginners forget is often the one a business feels most: if people can’t use the system, it doesn’t matter how private or accurate the data is.
4.1 What availability means
◆ KEY TERM Availability — the property that systems and data are usable by authorized users when they need them.
An online store that is down loses money every minute, regardless of whether any data was stolen. Availability is a genuine security property, not merely an ‘IT uptime’ concern, because attackers deliberately target it.
4.2 Threats and controls
Availability is threatened both by deliberate attacks and by ordinary failures:
- Denial-of-Service (DoS/DDoS) — flooding a system with traffic until it can no longer serve legitimate users.
- Ransomware — destroying availability by encrypting the data an organization needs to operate.
- Hardware failure, power loss, human error — taking systems offline with no attacker at all.
Defenders protect availability with redundancy (more than one of everything critical), backups (clean copies that can be restored after loss or ransomware), and disaster recovery planning (a tested way to bring systems back).
✶ REAL-WORLD When ransomware hits, the organizations that recover fastest are usually those with good, tested backups — they restore rather than pay. Backups protect availability and blunt the leverage of the attack.
⚑ WATCH OUT Bringing a service back once is not enough. True availability means it stays up — surviving a restart, a traffic spike, or a failed component. In Practice 1B, simply pressing ‘Start’ will not complete the task; you must make the service durable.
✎ TRY IT YOURSELF Open Practice 1B — “Keeping the Lights On”. Start the portal AND enable start-on-boot, then run the simulated reboot to prove it returns on its own.
Chapter 4 in one line: availability keeps systems usable; protect it with redundancy, backups, and disaster recovery — and make sure it stays up.
Chapter 5 — Risk & Defense in Depth
Because perfect security is impossible, professionals prioritize using the language of risk — and they never rely on a single control.
5.1 The building blocks of risk
- Asset — something of value worth protecting (data, a server, a service, a reputation).
- Threat — something that could harm an asset (an attacker, malware, a flood).
- Vulnerability — a weakness a threat can exploit (an unpatched system, a weak password, an over-shared file).
Risk emerges when a threat can act on a vulnerability to harm an asset. A simple, widely used way to express it:
Risk = Likelihood × Impact
Likelihood is how probable the harmful event is; impact is how badly it would hurt. A weakness that is easy to exploit and would cause severe damage is high risk and is fixed first; one that is hard to exploit and would cause little harm can wait. This is how real teams decide what to do each week — they cannot fix everything at once.
◆ KEY TERM Risk — the combination of how likely a harmful event is and how severe its impact would be. Managing risk, not eliminating it, is the defender’s job.
5.2 Treating risk
Once you identify a risk you choose among four responses: mitigate it (add a control to reduce likelihood or impact), transfer it (e.g., insurance), accept it (decide it’s small enough to live with), or avoid it (stop the risky activity). Every control in this course exists to reduce some risk to one or more CIA pillars.
5.3 One incident, many pillars
✶ REAL-WORLD Ransomware that steals data, encrypts the originals, and demands payment harms all three pillars at once: confidentiality (stolen data), integrity (files altered without authorization), and availability (the business can’t use its data). The CIA triad lets you describe even a messy incident precisely.
5.4 Defense in depth
◆ KEY TERM Defense in depth — layering multiple, independent controls so that no single failure is catastrophic.
If a file is protected by access control AND encrypted AND watched by an integrity monitor AND backed up, an attacker must defeat several independent controls to cause real harm, and the defender has several chances to detect and recover. This lesson installs the first three layers — one per pillar — and the course keeps adding more.
Chapter 5 in one line: prioritize with risk = likelihood × impact, treat each risk deliberately, and never trust a single control — layer them.
Chapter 6 — Hands-On: Practice & the Challenge
Everything you read connects to hands-on work on onyxium.io inside the Meridian Records Console — a browser-based simulator with three panels (Files & Access, Services, Integrity Monitor) and no command line. The Practice labs rehearse one pillar each (plus a quick-win confidence builder) and award progress points; the single Challenge tests you with only an objective and awards a badge and skill.
The lab arc
- Practice 1-Quick — “Meet the Console” — a 2-minute look at the over-shared payroll file (no fix yet). Confidence anchor.
- Practice 1A — “Who Can See This?” — Confidentiality: apply least privilege to fix what you just observed.
- Practice 1C — “Catching Tampering” — Integrity: baseline file hashes, induce a change, watch the FIM catch it.
- Practice 1B — “Keeping the Lights On” — Availability: start a stopped service AND make it survive a reboot.
- Challenge — “The Broken Ledger” — an integrity alert fired overnight; investigate and recover the attacker’s marker.
The Challenge — “The Broken Ledger”
An integrity monitor has fired an alert overnight: a protected ledger changed with no change ticket. With no step-by-step help, you must identify the tampered file, recover the attacker’s hidden marker (a string of the form ULC{…}), and submit it. Succeeding awards the [CIA-Triad-Mastery] badge and writes the skill to your profile.
▶ TIP Stuck on the Challenge? The platform offers tiered hints — a gentle concept nudge first, a tool hint next, and a near-answer last. Using a hint is fine; it’s how you learn.
✎ TRY IT YOURSELF After you pass, write one sentence: which control would have prevented the tampering (not just detected it)? You’ll build exactly those controls in later lessons.
Further reading & references
These are authoritative, free resources to deepen any topic in this lesson. They are optional but recommended.
- ISC2 — Certified in Cybersecurity (CC), the certification this course targets — https://www.isc2.org/certifications/cc
- NIST Computer Security Resource Center — Glossary (authoritative definitions of CIA, risk, etc.) — https://csrc.nist.gov/glossary
- NIST FIPS 199 — standards for categorizing systems by confidentiality, integrity, availability impact — https://csrc.nist.gov/pubs/fips/199/final
- NIST FIPS 180-4 — Secure Hash Standard (the SHA family) — https://csrc.nist.gov/pubs/fips/180/4/final
- NIST SP 800-53 — Security and Privacy Controls (access control, least privilege references) — https://csrc.nist.gov/pubs/sp/800/53/r5/final
- NIST SP 800-34 — Contingency Planning Guide (DR alignment) — https://csrc.nist.gov/pubs/sp/800/34/r1/final
- CISA — Cybersecurity best practices and beginner guidance — https://www.cisa.gov/topics/cybersecurity-best-practices
- Verizon Data Breach Investigations Report (DBIR) — annual real-world breach data — https://www.verizon.com/business/resources/reports/dbir/
- OWASP Foundation — open application-security knowledge (used later in the course) — https://owasp.org/
Bibliography
- ISC2. Certified in Cybersecurity (CC) — Official study materials. International Information System Security Certification Consortium.
- National Institute of Standards and Technology (NIST). FIPS Publication 199: Standards for Security Categorization of Federal Information and Information Systems. U.S. Department of Commerce.
- National Institute of Standards and Technology (NIST). FIPS 180-4: Secure Hash Standard (SHS).
- National Institute of Standards and Technology (NIST). SP 800-12 Rev. 1: An Introduction to Information Security.
- National Institute of Standards and Technology (NIST). SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations.
- National Institute of Standards and Technology (NIST). SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems.
- Verizon. Data Breach Investigations Report (DBIR), annual editions. Verizon Business.
- Cybersecurity and Infrastructure Security Agency (CISA). Cybersecurity Best Practices. U.S. Department of Homeland Security.