ced4568andClaude Sonnet 5
15b616274b
Adds all 6 ROOT 01 modules (how computers run software, the shell, filesystem navigation, files & text, processes, users & permissions foundations), each with a real lesson, demonstration/guided exercise, knowledge check where warranted, a hands-on Lab, and a reflection — 35 activities, 29 new content files. Adds 6 new hands-on Linux scenarios (linux-inspect-hardware, linux-shell-basics, linux-filesystem-navigation, linux-files-and-text, linux-process-management, linux-permissions-foundations) plus 2 MCQ scenarios, using the existing generic scenario/ validation engine (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §1) — every one tested end-to-end via the real scenario setup/validate API, including negative tests confirming they correctly FAIL when not actually solved (e.g. the process-management scenario fails while the target process is still running; the permissions scenario is tested against a real `su - labuser` denial). Wires rootnode-linux-foundations-assessment (2 required + 4 random-draw scenarios) using the existing Phase 3B assessment engine. Adds a real, server-side ROOT 01->02->03->04->05 course prerequisite chain (courses.prerequisites) — verified live on two students: one who completed ROOT 01 sees ROOT 02 unlock; a fresh student sees ROOT 02 correctly locked while 03/04/05 stay vacuously satisfied (their own prerequisite courses are still empty). ROOT 06+ and the Capstone are unaffected. Co-Authored-By: Claude Sonnet 5 <[email protected]>
34 lines
1.7 KiB
Markdown
34 lines
1.7 KiB
Markdown
# Reflection: Least Privilege Is a Habit, Not a One-Time Fix
|
|
|
|
## Reflection questions
|
|
|
|
1. Before this module, what would you have done the first time you hit a "permission denied"
|
|
error? How does that compare to what you'd do now?
|
|
2. Name one place outside of file permissions where you'd expect "grant only what's needed" to
|
|
matter (a user account, an API key, a service's network access — anything).
|
|
|
|
## Real Ops takeaway
|
|
|
|
**Least privilege is the single idea from this entire module that reappears the most across
|
|
the rest of ROOT_.** File permissions are just the first, most concrete place you'll apply it —
|
|
ROOT 09 applies the exact same principle to Kubernetes RBAC (what can a user or workload
|
|
actually DO) and SecurityContext (what can a container actually access). Getting comfortable
|
|
asking "what's the minimum this actually needs" now, on a file you can see and touch, makes that
|
|
same question much easier to ask later about something more abstract, like a ServiceAccount's
|
|
permissions.
|
|
|
|
This module is complete. This is the end of ROOT 01 — continue to ROOT 02: Linux
|
|
Administration & Networking.
|
|
|
|
## Instructor Notes
|
|
|
|
**Discussion questions for a live classroom:** question 2 works well as a round-robin — the
|
|
variety of answers (API keys, database credentials, network firewall rules) is itself useful
|
|
evidence of how far this one principle travels.
|
|
|
|
**Approximate timing:** 5-8 minutes live discussion; 5 minutes self-paced writing.
|
|
|
|
**Milestone note:** this is the last module of ROOT 01 — consider a short recap of the whole
|
|
course's arc (hardware → shell → filesystem → files/text → processes → permissions) before
|
|
moving on, so students see it as one coherent foundation rather than six separate topics.
|