01. Map digital risks
Professional objective : Six-asset register and three-risk matrix.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: List the fictional accounts, devices, data and owners; rank three risks by likelihood and impact.
- Check the result against this criterion: Document the reasoning behind each risk rating.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. List the fictional accounts, devices, data and owners; rank three risks by likelihood and impact.
Reference answer and verification
Six-asset register and three-risk matrix. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Document the reasoning behind each risk rating.
Expected output : Six-asset register and three-risk matrix.
Next chapter: reuse this output as the starting point for the next activity.
02. Passwords, managers and multifactor authentication
Professional objective : Account procedure and offline recovery sheet.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Design an MFA deployment plan for three demonstration accounts; include recovery and revocation.
- Check the result against this criterion: Do not include real secrets or recovery codes in shared submissions.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Design an MFA deployment plan for three demonstration accounts; include recovery and revocation.
Reference answer and verification
Account procedure and offline recovery sheet. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not include real secrets or recovery codes in shared submissions.
Expected output : Account procedure and offline recovery sheet.
Next chapter: reuse this output as the starting point for the next activity.
03. Recognize phishing and social engineering
Professional objective : Message assessment sheet and reasoned decision.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Compare two fictional messages; mark warning signs, reporting channel and independent verification.
- Check the result against this criterion: Do not open suspicious attachments or follow their links.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Compare two fictional messages; mark warning signs, reporting channel and independent verification.
Reference answer and verification
Message assessment sheet and reasoned decision. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not open suspicious attachments or follow their links.
Expected output : Message assessment sheet and reasoned decision.
Next chapter: reuse this output as the starting point for the next activity.
04. Patch and harden endpoints
Professional objective : Patch plan and verification checklist.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Create a patch calendar, disable unused accounts and track fictional software versions.
- Check the result against this criterion: Test changes on a non-production device before rollout.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Create a patch calendar, disable unused accounts and track fictional software versions.
Reference answer and verification
Patch plan and verification checklist. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Test changes on a non-production device before rollout.
Expected output : Patch plan and verification checklist.
Next chapter: reuse this output as the starting point for the next activity.
05. Secure sharing and access
Professional objective : Access-control matrix and decision log.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Assign read, edit and admin permissions to six fictional roles; remove excess permissions.
- Check the result against this criterion: Each role must justify its least-privilege access.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Assign read, edit and admin permissions to six fictional roles; remove excess permissions.
Reference answer and verification
Access-control matrix and decision log. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Each role must justify its least-privilege access.
Expected output : Access-control matrix and decision log.
Next chapter: reuse this output as the starting point for the next activity.
06. Back up and restore documents
Professional objective : Backup schedule and restore-test record.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Plan three copies on two media with one isolated; simulate restoring a fictional document.
- Check the result against this criterion: A backup is not verified until a restore test succeeds.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Plan three copies on two media with one isolated; simulate restoring a fictional document.
Reference answer and verification
Backup schedule and restore-test record. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
A backup is not verified until a restore test succeeds.
Expected output : Backup schedule and restore-test record.
Next chapter: reuse this output as the starting point for the next activity.
07. Understand logs and alerts
Professional objective : Event table and three cautious hypotheses.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Analyze synthetic logs; classify normal events, anomalies and unknowns.
- Check the result against this criterion: An alert alone does not prove a breach; preserve context.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Analyze synthetic logs; classify normal events, anomalies and unknowns.
Reference answer and verification
Event table and three cautious hypotheses. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
An alert alone does not prove a breach; preserve context.
Expected output : Event table and three cautious hypotheses.
Next chapter: reuse this output as the starting point for the next activity.
08. Respond to incidents without losing evidence
Professional objective : Triage card and fictional incident timeline.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Write an incident card for a suspected device; specify supervised isolation, contacts and trace preservation.
- Check the result against this criterion: Do not wipe or reset the device before authorized guidance.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Write an incident card for a suspected device; specify supervised isolation, contacts and trace preservation.
Reference answer and verification
Triage card and fictional incident timeline. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Do not wipe or reset the device before authorized guidance.
Expected output : Triage card and fictional incident timeline.
Next chapter: reuse this output as the starting point for the next activity.
09. Small-organization network safety
Professional objective : Annotated network diagram and separation rationale.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Draw a fictional network with separate guest Wi-Fi, work devices and backups.
- Check the result against this criterion: Never scan or test systems without authorization.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Draw a fictional network with separate guest Wi-Fi, work devices and backups.
Reference answer and verification
Annotated network diagram and separation rationale. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Never scan or test systems without authorization.
Expected output : Annotated network diagram and separation rationale.
Next chapter: reuse this output as the starting point for the next activity.
10. Supplier and remote-work risk
Professional objective : Ten-criterion supplier questionnaire.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Review a fictional SaaS contract for access, backups, incident notice and exit process.
- Check the result against this criterion: Flag missing clauses as unknown, not guaranteed.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Review a fictional SaaS contract for access, backups, incident notice and exit process.
Reference answer and verification
Ten-criterion supplier questionnaire. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Flag missing clauses as unknown, not guaranteed.
Expected output : Ten-criterion supplier questionnaire.
Next chapter: reuse this output as the starting point for the next activity.
11. Measure and explain security posture
Professional objective : Four-indicator dashboard with limitations.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Build a simple dashboard of MFA coverage, patching, restore tests and fictional incidents.
- Check the result against this criterion: Record the period and source of every indicator.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Build a simple dashboard of MFA coverage, patching, restore tests and fictional incidents.
Reference answer and verification
Four-indicator dashboard with limitations. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Record the period and source of every indicator.
Expected output : Four-indicator dashboard with limitations.
Next chapter: reuse this output as the starting point for the next activity.
12. Final project: realistic security plan
Professional objective : Security dossier with 30/60/90-day priorities.
Fictional case study
A fictional small non-profit uses three accounts, six computers and shared documents. It needs to reduce risks without offensive testing.
Method to understand
This lesson turns a workplace decision into observable evidence. All data is fictional, and no live service change is required. First separate known facts from assumptions. Work offline or in a dedicated sandbox; then record the rationale and non-sensitive evidence for review.
Guided demonstration
- Prepare the case: read the scenario, identify the output, record assumptions.
- Perform the chapter task: Combine asset register, risk matrix, prioritized controls, incident response and tested restoration for the fictional non-profit.
- Check the result against this criterion: Require human review of high-impact decisions.
- Archive output, date and limitations; request human approval for sensitive choices.
Independent practice
Repeat the task with a changed fictional constraint (smaller team or shorter deadline) without using live systems. Combine asset register, risk matrix, prioritized controls, incident response and tested restoration for the fictional non-profit.
Reference answer and verification
Security dossier with 30/60/90-day priorities. An acceptable submission includes the deliverable, reasons for choices, and evidence of checking. An inadequate submission only claims success without evidence or discussion of limits.
Limits and safety
Require human review of high-impact decisions.
Expected output : Security dossier with 30/60/90-day priorities.
Next chapter: reuse this output as the starting point for the next activity.
