Connect assets, access control and recovery evidence in a basic security workflow.
Free · No sign-in required3 lessonsWorked examples & practiceBeginner
0 of 3 lessons checked · Progress is saved in this browser.
01 / SYSTEM VIEWAssets
02 / SYSTEM VIEWProtective controls
03 / SYSTEM VIEWDetection and recovery
This map connects the course ideas; it is not a detailed engineering schematic.
LESSON 1 / 3 · FREE
Assets, threats and exposure
Your goal: Start security reasoning with a specific asset and consequence.
Understand the idea
Identify what must be protected, who can reach it and what failure would matter. A threat is not the same as a confirmed incident. Inventory, configuration and monitoring provide evidence; a geography label or unusual visit alone does not prove compromise.
Worked example
A fictional inventory contains 50 systems, with 5 missing an owner. Ownership coverage is 45/50 = 90 percent. This measures inventory completeness, not security effectiveness.
Try it yourself
Of 80 assets, 8 lack an owner. Calculate the percentage with owners.
Your goal: Separate proving identity from granting permissions.
Understand the idea
Authentication checks an identity; authorization decides what that identity may do. Multifactor authentication improves resistance to some attacks but does not fix excessive permissions or every phishing technique. Grant only necessary access, review it and remove stale accounts through approved procedures.
Worked example
Of 40 fictional accounts requiring MFA, 32 are enrolled. Coverage is 80 percent; enrollment alone does not establish phishing resistance.
Try it yourself
Out of 60 required accounts, 54 use MFA. Calculate coverage.
Your goal: Use recovery tests as evidence rather than assuming copies are enough.
Understand the idea
A backup is useful only if it can support recovery when needed. Recovery objectives describe acceptable loss and interruption for a defined service. Exercise restoration in an authorized isolated environment, verify integrity and document the outcome; a successful copy job is not a successful service restore.
Worked example
A fictional restore test uses 40 minutes for data retrieval and 20 for application checks: 60 minutes total for those stages, excluding any unmeasured incident work.
Try it yourself
A supplied restore takes 35 minutes and verification takes 25 minutes. Find total tested time.
Explain each worked example in your own words, check the units and identify one assumption that could change the result. Then use the linked labs or roadmap to apply the ideas to a broader task.
Practice progress is a study aid, not a professional qualification or proof of field competence.
Continue in Cybersecurity
Apply these foundations in an available course, lab or roadmap. The linked resource’s access rules still apply.
These original lessons use simplified models and explicitly supplied practice values. Calculations teach concepts; they do not select real equipment, establish code compliance or authorize field work. Follow the linked references and advanced resources for deeper study.
Updated · Study progress stays in this browser. There is no certificate or paid gate for these lessons.