✳ Learning path / 8 lessons
Cybersecurity foundations
Eight lessons that teach a beginner to name assets and losses, judge risk under uncertainty, trace a request, handle identity, write scoped policies, plan recovery, read evidence, and connect those skills to frameworks and product categories.
Work through the lessons in sequence, or choose the question you want to answer today.
01What we protect: assets, confidentiality, integrity, and availability
Learn to name the things worth protecting and describe a concrete loss as a confidentiality, integrity, or availability failure before talking about products.
Threat, vulnerability, likelihood, impact, and uncertainty
Learn why two similar weaknesses can receive different priorities by separating threat, vulnerability, exploitation evidence, impact, and what you still do not know.
How systems communicate: network, DNS, HTTP, and TLS
Trace a browser request to a tracking portal and identify what the network, DNS, HTTP, and TLS each do and do not protect.
Identity, authentication, authorization, and recovery
Distinguish proving who someone is from granting access, and treat account recovery as part of the same control system.
Least privilege, secure defaults, trust boundaries, and layered controls
Choose a scoped access policy by naming trust boundaries and stacking independent controls instead of one powerful exception.
Data protection, updates, backups, and resilience
Build a small organization's prevention and recovery plan that covers classification, updates, backups, and what must still work when a warehouse is down.
Logs, alerts, and evidence
Separate observed facts, hypotheses, and missing information when reading logs and alerts so a later decision can be defended.
From principles to frameworks and product categories
Relate a named risk to an outcome, a control, the evidence you would collect, and the product category that might help—without treating a purchase as the outcome.
Turn knowledge into a decision.
Once you have the ideas, try a short scenario. You’ll see why the tempting answer isn’t always the most useful one.
Open the practice range ↗