HANDS-ON LAB GUIDE — STUDENT EDITION
Lesson 1 — The Cyber World and the CIA Triad
Your complete map of the labs: what you’ll do, why it matters, what to expect, and where to look it up.
How to use this guide
This guide is your complete companion to the five hands-on items in Lesson 1. For each lab you get:
- Why you need this as a cyber professional — the real-world job this skill enables
- What topic from today this lab covers — so you know where it sits in the lesson
- What you should expect — what the lab will look and feel like before you click
- Prerequisites — what you must understand to start (often: none, since this is L1)
- Step-by-step actions with: what to do, why it matters, what you should see
- Common mistakes and how to recover from them
- References — authoritative sources, textbook chapter — so you can dig deeper
- What you covered at the end — restated in defender-skill language
Print this guide or keep it open in a second window while you work. Reading the “why” matters as much as completing the click steps — that’s what lets you solve the Challenge, where no steps are given.
Lesson 1 — the big picture
Welcome to CSRP. This is the first session — there is no prior lesson. You arrive with general computer literacy and the curiosity that brought you to the bootcamp. That’s all you need.
Topics you’ll learn today
| # | Topic | Where it’s taught | Where you practice it |
| 1 | The defender’s role and the threat landscape | Deck Ch.1, Textbook Ch.1 | Practice 1-Quick (concrete grounding) |
| 2 | The CIA triad — Confidentiality, Integrity, Availability | Deck Ch.2/3/4, Textbook Ch.2–4 | All three Practice labs |
| 3 | Confidentiality — access control and least privilege | Deck Ch.2, Textbook §2 | Practice 1A |
| 4 | Integrity — hashing and File Integrity Monitoring | Deck Ch.3, Textbook §3 | Practice 1C + Challenge |
| 5 | Availability — durability, redundancy, backups, DR | Deck Ch.4, Textbook §4 | Practice 1B |
| 6 | Risk = likelihood × impact and defense in depth | Deck Ch.5, Textbook §5 | Implicit in the Challenge reflection |
The tool you’ll use today
The Meridian Records Console — a browser-based simulator with three panels:
- Files & Access — view and edit who can see which files (for Confidentiality work)
- Services — start/stop services, set start-on-boot, simulate reboot (for Availability work)
- Integrity Monitor — baseline hashes, run checks, see what changed (for Integrity work)
There is no command line in this lesson. CLI work begins in Lesson 7.
Knowledge you do NOT yet have (and that’s perfectly OK)
You haven’t yet learned: networking, the OSI model, IP addresses, operating systems, command line, firewalls, encryption details, hashing implementation, or anything beyond the most basic “what is a computer” framing. None of today’s labs need any of that. Everything is point-and-click.
Before you start — the five-lab arc
You have five hands-on items today, in this order:
| # | Lab | Difficulty | Time | Earns |
| 0 | Practice 1-Quick — “Meet the Console” | Quick-win | ~2 min | First progress point |
| 1 | Practice 1A — “Who Can See This?” | Intro | ~12 min | Progress points |
| 2 | Practice 1C — “Catching Tampering” | Core | ~15 min | Progress points |
| 3 | Practice 1B — “Keeping the Lights On” | Intro | ~10 min | Progress points |
| 4 | Challenge — “The Broken Ledger” | Challenge | ~20–30 min | [CIA-Triad-Mastery] badge + skill |
You don’t have to finish all of them during class. They stay on onyxium — finish whatever you don’t get to as homework. The Challenge is best attempted in class for the live-coaching dynamic.
How to succeed
- Read the “why this matters” column on each step. Those notes are what let you solve the Challenge, where no steps are given.
- Reset any lab and try again as many times as you like. No penalty for resets.
- The Challenge has tiered hints (concept → tool → near-spoiler). Use them only after ~10 minutes stuck. They’re meant to teach, not to short-circuit your thinking.
Lab 0 — Practice 1-Quick — “Meet the Console”
Why you need this as a cyber professional
Every defender starts every investigation by opening a tool and looking at the state of a system. The single most important first habit is: look, don’t touch. This lab is a 2-minute “look” — you open the Meridian Records Console, observe a misconfiguration that’s hurting the company, and confirm what’s wrong before fixing anything. That habit of careful observation is what separates good defenders from rash ones.
What this covers from today’s lesson
Topic 1 — the defender’s role. You’re stepping into the defender’s seat for the first time. Topic 3 (Confidentiality) gets a sneak preview, since the misconfiguration you’ll observe is a confidentiality leak.
What you should expect
A pre-loaded simulator with three panels. You’ll click into the Files & Access panel, click payroll.csv, and read who can see it. You don’t fix anything yet. You confirm: “this file is shared with Everyone.” That’s the problem. ~2 minutes.
Goal
Open the Meridian Records Console, navigate to the Files & Access panel, click payroll.csv, and confirm the file is shared with “Everyone.”
Prerequisites
None. This is the first hands-on of the bootcamp.
The situation
Meridian Corp’s IT team has just opened the Records Console for you. Three panels are visible. You’ve been told there’s a problem with the payroll.csv file — your first job is just to look at it and confirm what’s wrong.
Step-by-step
| Step | Do this | Why it matters | What you should see |
| 1 | Confirm the Meridian Records Console has loaded — you should see three panels labeled Files & Access, Services, Integrity Monitor. | This is the workspace you’ll use all lesson. Knowing the layout is step zero. | Three labeled panels, none of them selected yet. |
| 2 | Click the Files & Access panel. | Files & Access is where Confidentiality controls live. | Panel expands; you see a list including payroll.csv and ledger/transactions.db. |
| 3 | Click payroll.csv to inspect it. | Inspecting a file before changing anything is the defender’s first instinct. | Detail view opens showing the file’s current sharing settings. |
| 4 | Read who the file is shared with. | This is the misconfiguration the Meridian team is going to ask you to fix in Practice 1A. | “Shared with: Everyone” (or similar — the whole company can read this file). |
| 5 | Click “Mark complete”. | You’re done — first progress point logged. | Green checkmark; lab passes. |
Common mistakes
- Nothing happens when I click. Make sure the simulator tab is active. Reload if needed.
- I see ledger/transactions.db instead. That’s a different file. Make sure you clicked payroll.csv.
Reset
Click Reset Lab in the top-right corner. State returns to “no panel selected.”
What you covered
You proved you can open the defender’s workspace, navigate to the right panel, inspect a file’s sharing settings, and recognise a confidentiality misconfiguration. That’s the first observation skill of a security analyst. In Practice 1A you’ll fix what you just observed.
References
- Textbook §1.2 — The defender’s role
- Textbook §2.1 — What confidentiality means
- NIST SP 800-12 §3 — Information security overview: https://csrc.nist.gov/pubs/sp/800/12/rev-1/final
Lab 1 — Practice 1A — “Who Can See This?” (Confidentiality)
Why you need this as a cyber professional
Over-shared files are one of the most common findings in real-world security audits. A shared drive that “anyone in the company can read” might contain salary data, customer PII, M&A drafts, or credentials. Fixing this kind of leak is daily work for security engineers and IT admins. The principle of least privilege — give people the minimum access they need and nothing more — is one of the foundational rules of access control. You’ll apply it in every defender role you’ll ever hold.
What this covers from today’s lesson
Topic 3 — Confidentiality, access control, and least privilege.
What you should expect
You’ll continue from where the quick-win left off — the over-shared payroll.csv file. This time you fix it. You’ll remove the over-broad sharing, grant access to only the HR group, save the change, and verify the fix from the perspective of a Sales user. The lab validates that all four steps are done correctly. ~12 minutes.
Goal
Restrict payroll.csv to the HR group only, and verify that a Sales user is denied.
Prerequisites
- You completed Practice 1-Quick (you’ve already seen the over-sharing problem).
- You’ve watched Chapter 2 of the deck (CIA triad introduction, confidentiality, access control, least privilege).
- You understand that “least privilege” means giving each user the minimum access for their role.
The situation
In the Files & Access panel, payroll.csv is shared with Everyone — anyone in the company can open it and read salaries. Your job is to make sure only the HR group can see it.
Step-by-step
| Step | Do this | Why it matters | What you should see |
| 1 | Open Files & Access and click payroll.csv to see who can read it. | Protecting data starts with knowing who has access to it. | Detail view shows “Shared with: Everyone” (and possibly “All-Staff”). |
| 2 | Click Edit sharing and remove Everyone and All-Staff. | The leak is the over-broad access — remove it first, before anything else. | Both groups disappear from the access list. |
| 3 | Add the HR group with Can view, then click Save. | Least privilege: give access to the right people, and no one else. | HR appears in the access list; Save confirmation shown. |
| 4 | Use Test as → a Sales user to preview their access. | Always verify your fix from the outside — can the wrong person still get in? | A simulated Sales user attempts to open the file and sees “Access denied.” |
Expected result
File shared with HR only; Sales user denied; lab passes. Progress point logged.
Common mistakes
- Added HR but forgot to remove Everyone. The file is still leaking — the lab flags this with an inline note: “the file is still open to others.”
- Removed all groups including HR. Now no one can see it — that’s not least privilege, that’s a denial of service to the people who need it.
- Forgot to test as Sales. The lab tracks whether you verified your fix; this is a soft-skill signal of being a thorough defender.
Reset
Click Reset Lab. The file returns to “Shared with: Everyone.”
What you covered
You can now look at any file’s sharing list and apply the principle of least privilege — remove the over-broad access, add only the people who genuinely need it, and verify the fix from an outside perspective. This is the daily work of an access-control engineer and the first defensive habit of every blue-teamer.
References
- Textbook §2.2 — How defenders protect confidentiality
- NIST SP 800-53 (AC-3, AC-6) — Access control / Least Privilege: https://csrc.nist.gov/pubs/sp/800/53/r5/final
- ISC2 CC — Domain 1 (Security Principles) and Domain 3 (Access Controls)
Lab 2 — Practice 1C — “Catching Tampering” (Integrity)
Why you need this as a cyber professional
Integrity attacks — silent modification of data — are some of the most dangerous because they can go unnoticed for months. A modified bank balance, a swapped software update, a deleted log entry: these don’t trigger error messages. The defender’s tool for catching them is the hash — a one-way fingerprint of a file’s content. A File Integrity Monitor (FIM) stores a baseline of hashes and alerts when any file’s hash no longer matches. FIM technology underpins compliance frameworks (PCI-DSS, HIPAA, SOX), forensics investigations, and modern endpoint detection. Your future SOC or IR job will use FIM constantly.
What this covers from today’s lesson
Topic 4 — Integrity, hashing, and File Integrity Monitoring.
What you should expect
You’ll work in the Integrity Monitor panel. You’ll capture a baseline of hashes, run a check (everything matches), make a demo change to a file, run a check again (one file flags as CHANGED), and inspect the old-vs-new fingerprints. The lab validates each step. ~15 minutes. This view is the exact view you’ll use in the Challenge — pay attention.
Goal
Capture a baseline, run a check, induce a demo change, detect the change via the old-vs-new fingerprint view, and correctly identify the changed file.
Prerequisites
- You completed Practice 1-Quick (you know how the simulator panels work).
- You’ve watched Chapter 3 of the deck (integrity, hashing, FIM).
- You understand that a hash is a one-way fingerprint and that any change to a file flips its hash.
The situation
The Integrity Monitor panel says “No baseline captured.” Nothing is currently watching the files for tampering. Your job is to set it up and prove it works.
Step-by-step
| Step | Do this | Why it matters | What you should see |
| 1 | Click Capture baseline. | A baseline records each file’s current fingerprint — the trusted “before” state. | “Baseline captured” — all files now have a stored hash. |
| 2 | Click Run check right away. | Nothing changed yet, so every fingerprint still matches. This proves the system reports correctly. | “No changes detected — all files match baseline.” |
| 3 | Click Make a change (demo), then Run check again. | Any change flips a file’s fingerprint — that’s how tampering is detected. | One file marked CHANGED with both the old and new fingerprints displayed. |
| 4 | Open the file the report marks as Changed. | Reading the change is the first step of an investigation — the FIM tells you THAT something changed; you investigate WHAT. | File contents shown; you can see the demo modification. |
Expected result
Baseline captured, run check after the demo change, correctly identify the changed file with its old-vs-new fingerprint view. Lab passes. Progress point logged.
Common mistakes
- Ran the check before capturing a baseline. There’s nothing to compare against. The lab tells you to capture first.
- Captured a baseline AFTER the demo change. Now the change is “baseline” — the system thinks the tampered state is normal. The lab catches this.
- Identified the wrong file as changed. Look at the report — only one file should be marked CHANGED.
Reset
Click Reset Lab. Baseline cleared, demo change reverted.
What you covered
You can now baseline a file system’s integrity, run periodic checks, detect when something has changed, and inspect old-vs-new fingerprints to start an investigation. This is the foundation of File Integrity Monitoring, used by virtually every SOC and compliance program in the world. In the Challenge you’ll use this exact view to find a real (synthetic) intrusion.
References
- Textbook §3.2 — The hash: a fingerprint for data
- Textbook §3.3 — File Integrity Monitoring (FIM)
- NIST SP 800-92 — Computer Security Log Management (FIM context): https://csrc.nist.gov/pubs/sp/800/92/final
- NIST FIPS 180-4 — Secure Hash Standard (the SHA family): https://csrc.nist.gov/pubs/fips/180/4/final
- PCI-DSS v4 §11.5 — FIM as a compliance requirement
Lab 3 — Practice 1B — “Keeping the Lights On” (Availability)
Why you need this as a cyber professional
Availability is the pillar beginners forget — but it’s the one a business feels most. If customers can’t reach your site, you lose money every second. Availability engineering is a major sub-discipline of security and operations, covering redundancy, failover, backups, disaster recovery, and capacity planning. The single mistake most often made is assuming “I started the service” equals “it’s available.” Real availability means the service stays up — through restarts, traffic spikes, hardware failures, and human error. You’ll meet redundancy patterns again in Module 2 (load balancing, HA architectures) and Module 5 (incident-response runbooks).
What this covers from today’s lesson
Topic 5 — Availability, durability, redundancy, and disaster recovery.
What you should expect
You’ll work in the Services panel. The Meridian Portal is currently stopped, and start-on-boot is off. You’ll bring it online AND make sure it survives a simulated reboot. If you only click Start, the reboot test fails — that’s the lesson. ~10 minutes.
Goal
Bring the Meridian Portal online AND configure it to survive a reboot.
Prerequisites
- You completed Practice 1-Quick.
- You’ve watched Chapter 4 of the deck (availability, durability, redundancy, backups, DR).
- You understand that availability is a property over time — not a single moment of “running.”
The situation
In the Services panel, the Meridian Portal shows Stopped, and Start-on-boot is Off. Customers can’t reach it. Worse, even if you start it now, if the server reboots tonight it’ll come back to the same broken state.
Step-by-step
| Step | Do this | Why it matters | What you should see |
| 1 | Open Services and read the Meridian Portal status. | Availability means the service is running and reachable — check this before acting. | “meridian-portal — Stopped — Start-on-boot: Off.” |
| 2 | Click Start. | This restores the service right now. | Status changes to “Running.” |
| 3 | Toggle Start-on-boot to On. | Availability must survive a restart — not just this moment. | “Start-on-boot: On” displayed. |
| 4 | Click Simulate reboot, then re-check the status. | This proves your fix is durable, not a one-off. | After the simulated reboot, the portal comes back to “Running” automatically. |
Expected result
After the simulated reboot, the portal is “Running” on its own. Lab passes. Progress point logged.
Common mistakes
- Only clicked Start. The reboot check fails — the portal goes down again after the reboot. This is the intended teaching moment. Add the Start-on-boot toggle and re-run.
- Toggled Start-on-boot but didn’t click Start first. Then the reboot test passes but the service was never running in the first place. Both steps required.
- Clicked Simulate reboot before configuring. Reset and start over.
Reset
Click Reset Lab. Service stops; Start-on-boot reverts to Off.
What you covered
You can now distinguish between “I started it once” and “it stays up” — and configure persistent availability. This is the foundational mental model behind every load balancer, every HA cluster, every disaster-recovery plan. Availability isn’t a moment; it’s a property.
References
- Textbook §4.1 — What availability means
- Textbook §4.2 — Threats and controls
- NIST SP 800-34 — Contingency Planning Guide for Federal Information Systems: https://csrc.nist.gov/pubs/sp/800/34/r1/final
- ISO 22301 — Business continuity management (DR alignment)
Challenge — “The Broken Ledger”
Why you need this as a cyber professional
This is the moment you put on the SOC analyst hat. An alert has fired — something changed that shouldn’t have. You have to find what, understand it, and report it. That sequence — alert → investigate → recover evidence → report — is the heartbeat of every Security Operations Center and every Incident Response team on the planet. Doing it once, with no walkthrough, on your very first day, is the badge you earn today.
What this covers from today’s lesson
Everything: Topic 1 (defender’s role), Topic 2 (CIA — specifically integrity as the failed pillar), Topic 4 (FIM in action), Topic 6 (risk thinking — what control would have prevented this?).
What you should expect
A different state than the Practice labs — the Integrity Monitor already has an alert showing. A file changed overnight, and there’s no change ticket explaining it. You have: – The objective (find the tampered file and recover a marker) – A flag-submit box – Three tiers of opt-in hints – ~20–30 minutes
You earn a badge on success.
The brief
Overnight, the Integrity Monitor on the Meridian records system fired an alert: a protected ledger changed, and there is no change ticket explaining it. You’re on call. The attacker who made the change left a hidden marker behind. Find which file was tampered with and what was written into it, recover the marker, and submit it as your flag.
What you know
- A baseline already exists and the alert is already waiting for you in the Integrity Monitor.
- The tampered file is somewhere in the records area — the alert points the way.
- The marker (your flag) looks like ULC{…} and is per-instance — won’t work from another learner’s account.
Strategy hints (you can read these before starting — they’re not spoilers)
- The skills you’ll use are exactly the ones from Practice 1C: open the Integrity Monitor, see what’s flagged, open the flagged file, read what changed.
- The marker is inside the file content — somewhere in the rows of the ledger.
- Looking for an out-of-place row is the fastest path.
Rules
- Investigate using the console panels only. Don’t reset the instance to clear the alert.
- Stuck for more than ~10 minutes? Open the in-platform hints:
- Tier 1 (Concept): “The integrity monitor already told you a file changed — which one?”
- Tier 2 (Tool): “Open the flagged file and read it carefully.”
- Tier 3 (Near-spoiler): “Search the ledger for the word UNAUTHORIZED.”
How to submit
- Find the ULC{…} marker inside the tampered file.
- Paste it (including the braces) into the Submit Flag box and click Submit.
- On success, your profile updates with the [CIA-Triad-Mastery] badge.
After you pass — reflection
The monitor detected the effect of an intrusion without knowing who did it or how. Ask yourself in your workbook:
- Which CIA pillar was violated, and which controls (from any of the three pillars) might have prevented it?
You’ll build exactly those preventive controls in later lessons.
References
- Textbook §3.3 — File Integrity Monitoring (the tool that detected this)
- Textbook §5.4 — Defense in depth (the strategy that would have prevented it)
- MITRE ATT&CK T1565 — Data Manipulation (the technique the simulated attacker used): https://attack.mitre.org/techniques/T1565/
- NIST SP 800-61 — Computer Security Incident Handling Guide: https://csrc.nist.gov/pubs/sp/800/61/r2/final
What to do if you didn’t finish in class
That’s fine. All five hands-on items stay open on onyxium after class. Recommended sequence:
- Finish any incomplete Practice (1-Quick / 1A / 1B / 1C) first — they unlock the Challenge.
- Attempt the Challenge solo. Use the tiered hints if stuck > 10 minutes.
- Take the Lesson 1 Mastery Check quiz in LearnDash (10 questions, ≥ 80% to complete the lesson).
- Then you’re cleared to start Lesson 2.
If you get stuck on the Challenge for more than an hour with all hints used, post in the cohort channel — your instructor or a peer will help.