Guided course - 5 chapters

Password managers: A Practical Course with Anika Soren

Anika Soren teaches Password managers through five practical chapters that move from a clear foundation to guided work, applied decisions, and revision. You will finish with a working program, configuration, or technical walkthrough, a tutor-ready capstone, saved notes, and a repeatable way to continue practicing.

Beginners, families, students, creators, and small-business learners 2 hrs 30 min Practice and checkpoints Free curriculum

Start or resume

Your course progress

0 of 5 chapters complete

Next: chapter 1

What you will learn

Build knowledge, use it, and leave with evidence of progress.

Explain the essential Password managers vocabulary through a connected mental model.
Follow and explain a reliable technical problem solving workflow in guided practice.
Apply Password managers to a realistic scenario with visible constraints and tradeoffs.
Evaluate and revise a working program, configuration, or technical walkthrough using evidence-based success criteria.
Complete a capstone and leave with a specific next-practice plan.

Before you start

Comfort using a web browser and basic files
No previous programming experience is required unless a chapter says otherwise

Useful materials

A laptop or desktop computer
A text editor or browser-based coding environment
A notes file for test cases and debugging observations

Suggested rhythm

Complete one 30-minute chapter at a time: learn for 10 minutes, practice for 15, then use 5 minutes for the checkpoint and notes.

Course capstone

Working Password managers mini project

Build a focused Password managers solution for a clear user need and show how you tested the important behavior.

What you will submit

A working project or documented configuration
Three test cases with results
A concise README explaining decisions and next improvements

How it will be reviewed

Core behavior works as intended
The solution is understandable
Tests cover likely failures
Technical choices are explained

Course chapters

Learn, practice, check, and record what matters.

2 hrs 30 min total

Chapter 1

Password managers: Foundations and vocabulary

Build a dependable mental model for Password managers before trying to memorize isolated details. You will define the essential vocabulary, inspect a worked example, and turn the ideas into a reference you can actually use.

27 min Not complete

Learning objectives

Explain the purpose of Password managers in your own words.
Use the chapter vocabulary accurately in a short example.
Distinguish a strong example from a common misconception.
Create a compact reference for later practice.

Key terms

Start with the purpose

Place Password managers inside a small but realistic software or digital-safety task. Name the result a learner is trying to produce and the constraints that make the skill useful.

How Password managers actually works

These are the load-bearing ideas. Everything later in the course is an application of one of them, so it is worth reading slowly and returning to when something stops making sense.

Programs are state changing over time. Most confusion comes from not knowing what a variable holds at a given moment. Reading code as a sequence of state changes, rather than as instructions, is what makes unfamiliar programs understandable.
Make it work, then make it clear. Working code that nobody can read becomes unmaintainable within weeks, including for its author. Naming and structure are not decoration; they are how future changes stay cheap.
A bug is a disagreement between belief and behaviour. Debugging is the process of finding which of your beliefs about the program is false. Printing or inspecting values converts an argument with the computer into an observation.

Misconceptions worth clearing early

Each of these is common, understandable, and expensive to leave in place. Recognising them now saves rework later.

Changing several things at once when something breaks. It feels faster than testing one change at a time. Fix: Change one thing, observe, and revert it if the behaviour does not move; keep the loop small.
Reading code without running it. Code looks like it does what it was named to do. Fix: Run it with a value you can predict by hand, then compare the real output with your prediction.
Treating an error message as noise. Long stack traces look intimidating and unspecific. Fix: Read the first line and the file and line number; that pair usually names the actual problem.

Build the mental model

Connect the key terms as a process rather than a word list. Use this sequence: decompose the problem, build one testable step, inspect the result, and debug deliberately.

Catch the common miss

Compare a surface-level attempt with one that shows correct behavior, readable structure, useful tests, and an explained decision. Explain the single difference that matters most.

Equation in context

Password entropy

E = L \cdot \log_2 N

Every extra character multiplies the number of possible passwords, which is why length beats cleverness.

Entropy lab

Watch a password get expensive to guess

Add length and character variety; the crack-time estimate does the arguing for you.

The model assumes an offline attacker guessing ten billion passwords per second. Length wins because every added character multiplies the whole search space.

Compare 8 characters using everything against 16 lowercase letters.
Find the shortest setting that survives for a century.

Security pseudocode

Build the account checklist

1 2 3 4 5 6

FOR each important account
  CREATE a unique generated password
  SAVE it in the password manager
  ENABLE multi-factor authentication
  VERIFY recovery details
END

1 / 5

Repeat with a changing value FOR each important account

The loop exposes a sequence of states rather than one isolated result.

This is a process model, not executable code; adapt it to the controls offered by each account.

Side-by-side comparison

Two programs that both "work"

Both attempts look plausible from a distance. Toggle the highlights and study where they part ways.

Aspect	Fragile script	Dependable program
Behavior	Right answer for the one input tried so far	Right answer for normal, empty, and extreme inputs
Readability	Single-letter names; the intent lives in the author's head	Names describe the data; the next reader needs no tour guide
Failure	Crashes or returns nonsense on an empty list	Guards the edge case and proves it with a test

The difference is invisible on the happy path and decisive everywhere else.

Practice round

Match the Password managers vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.
Say each definition aloud before tapping — then check yourself.

Practice activity - 12 min

Make a one-page field guide

Create a compact field guide that would help a new learner recognize and begin using Password managers.

Write a one-sentence definition and purpose.
Add the four key terms with a plain-language example.
Include one non-example and explain why it misses.
Finish with a three-step starter checklist.

Deliverable

One annotated page or slide that can be reused in later chapters.

Success looks like

The definition is specific.
Examples match the vocabulary.
The checklist is usable without extra explanation.

Knowledge check

Which response best shows a usable foundation in Password managers?

1 question

AIt defines the idea, shows it in context, and explains why the example fits. BIt copies a list of terms without connecting them. CIt starts the final project before identifying the purpose. DIt chooses an answer without checking the situation.

Chapter notes Not started

2
Chapter 2
Phishing practice: Guided demonstration

Follow a complete Phishing practice example from setup to result, pausing at the decisions that experts often make silently. Then repeat the process with support and check your work against visible criteria.

29 min Not complete
Learning objectives

Sequence the main steps in a reliable Phishing practice workflow.

Explain why each important decision is made.

Complete a supported example without skipping verification.

Use a checklist to identify one correction.
Key terms
1

Watch the whole process

Trace a model from the initial prompt to a working program, configuration, or technical walkthrough. Mark each point where the learner must observe, choose, or verify rather than act automatically.
2

The method, one step at a time

This is the working sequence experienced practitioners follow. Do it in order the first few times, even where a step feels unnecessary.

Decompose the problem

Build one testable step

Inspect the result

Debug deliberately

The order matters: each step produces the information the next one needs.
3

Where this usually goes wrong

Watch for these while you work through the demonstration rather than afterwards.

Changing several things at once when something breaks. It feels faster than testing one change at a time. Fix: Change one thing, observe, and revert it if the behaviour does not move; keep the loop small.

Reading code without running it. Code looks like it does what it was named to do. Fix: Run it with a value you can predict by hand, then compare the real output with your prediction.

Treating an error message as noise. Long stack traces look intimidating and unspecific. Fix: Read the first line and the file and line number; that pair usually names the actual problem.
4

Practice with scaffolding

Repeat the model with one detail changed. Keep the prompts visible and say or write the reason for each choice before continuing.

5

Check before feedback

Use correct behavior, readable structure, useful tests, and an explained decision as the quality test. Make one self-correction before asking the tutor to review the result.
Spotting drill
Catch the phish before it hooks

This email contains the classic tells. Tap everything that should raise a doubt before you would ever click.

Recognition is a trainable reflex: people who have deliberately hunted for warning signs spot them faster when it counts.

Find every flag, then use Reveal to check what you missed.

For each flag, name what a safer version would look like.
Guided flowchart
A complete Phishing practice practice run

flowchart LR N1["Read the task"] N2["Model one step"] N3["Try with support"] N4["Verify the result"] N1 --> N2 N2 --> N3 N3 --> N4

Pause at each arrow and explain the decision before moving to the next step.

Step 1 of 4: Read the task
Security pseudocode
Inspect before opening a sign-in link

Pseudocode Read-only example

CHECK the sender using a trusted channel READ the full destination domain OPEN the saved website directly when unsure REPORT suspicious messages NEVER share a password or one-time code

1 / 5

Read the statement CHECK the sender using a trusted channel
Connect this statement to the state and result around it.

This is a process model, not executable code; adapt it to the controls offered by each account.
Practice round
Rebuild the Phishing practice method

The steps of this chapter's method, shuffled. Arrange them so they would actually work.

A method is a sequence, not a bag of tips — if the order surprises you, that is exactly the gap worth closing now.

Order the steps, then explain to yourself why step 2 cannot go last.

Shuffle again and solve it in fewer moves.
Practice activity - 15 min
Complete the guided run

Use the chapter workflow to produce a working program, configuration, or technical walkthrough for a slightly changed Phishing practice example.
1. Restate the task and constraints.
2. Follow the model one decision at a time.
3. Record the reason for two key choices.
4. Check the result and revise one issue.
Deliverable
A completed guided example with two decision notes and one correction.
Success looks like

The workflow is complete.

Decisions have reasons.

The final check produces a visible correction.
Knowledge check
During guided Phishing practice practice, when is the best time to explain a choice?

1 question

During guided Phishing practice practice, when is the best time to explain a choice? AAt the decision point, before seeing whether the final result works. BOnly after the tutor supplies the correct answer. COnly when the result is wrong. DAfter deleting the draft and starting over.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Submit the guided example with decision notes, one self-correction, and the checkpoint response.
3
Chapter 3
Privacy settings: Applied scenario

Transfer Privacy settings into a realistic scenario where the prompt is less tidy and more than one option may be reasonable. You will define the constraints, choose an approach, and defend the tradeoff.

32 min Not complete
Learning objectives

Extract the relevant facts and constraints from a realistic scenario.

Generate at least two plausible approaches to Privacy settings.

Choose an approach using explicit criteria.

Explain the likely consequence of the choice.
Key terms
1

Read the situation

Translate the scenario into a clear task. Separate facts, assumptions, constraints, and information that is interesting but not relevant to Privacy settings.
2

Choosing well under real constraints

Applied work is mostly judgement under limits: less time, less information, and more competing goals than a textbook example allows. These are the decision rules that hold up in practice.

Two approaches both look workable: Choose the one you can test more easily; testability compounds faster than elegance.

The task feels too large to start: Cut it until one piece can be finished and verified in under an hour, then build outward.

You are unsure whether something is a real bug: Write the smallest input that reproduces it; if you cannot reproduce it, you cannot claim to have fixed it.
3

Reading the situation before acting

Before choosing an approach, state three things explicitly: what result the situation actually requires, which constraints are fixed rather than preferences, and what evidence would tell you the approach is working. Skipping this step is the most common reason competent work solves the wrong problem.

Programs are state changing over time. Most confusion comes from not knowing what a variable holds at a given moment. Reading code as a sequence of state changes, rather than as instructions, is what makes unfamiliar programs understandable.
4

Compare real options

Generate two workable approaches and test both against the purpose. Do not hide the tradeoff; name what each option improves and what it gives up.

5

Make the reasoning visible

Produce a working program, configuration, or technical walkthrough and attach a short decision note. The note should make the result auditable, not merely confident.
Entropy lab
Watch a password get expensive to guess

Add length and character variety; the crack-time estimate does the arguing for you.

The model assumes an offline attacker guessing ten billion passwords per second. Length wins because every added character multiplies the whole search space.

Compare 8 characters using everything against 16 lowercase letters.

Find the shortest setting that survives for a century.
Practice round
Match the Privacy settings vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.

Say each definition aloud before tapping — then check yourself.
Practice activity - 18 min
Solve the scenario

Apply Privacy settings to a scenario from school, work, home, or community life that includes at least two constraints.
1. Write the task, audience, and constraints.
2. Sketch two possible approaches.
3. Choose using three criteria from the chapter.
4. Produce the result and explain one tradeoff.
Deliverable
A scenario response with an option comparison and a short decision note.
Success looks like

Constraints are visible.

Both options are plausible.

The final choice follows the stated criteria.
Knowledge check
What makes an applied Privacy settings decision defensible?

1 question

What makes an applied Privacy settings decision defensible? AThe chosen approach follows stated constraints and criteria, with the tradeoff acknowledged. BIt is the first idea that came to mind. CIt avoids mentioning uncertainty. DIt copies the guided example without adapting it.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Finish the scenario response, compare two options, and explain the selected tradeoff.

Chapter 4

Home network basics: Review and improve

Learn to diagnose and improve Home network basics work with a focused rubric instead of vague judgment. You will separate symptoms from causes, revise the highest-value issue, and document the before-and-after difference.

30 min Not complete

Learning objectives

Evaluate a draft using explicit Home network basics criteria.
Identify the cause behind the most important weakness.
Choose a revision with high impact and reasonable effort.
Explain how the revision changes the result.

Key terms

Use the rubric, not a feeling

Review the work for correct behavior, readable structure, useful tests, and an explained decision. Record evidence for each judgment so feedback points to something observable.

Diagnostic checklist

Run this before you revise anything. Diagnosing first prevents the common failure of polishing the parts that were already fine.

Check: Changing several things at once when something breaks — is this present in your work?
Check: Reading code without running it — is this present in your work?
Check: Treating an error message as noise — is this present in your work?

The quality bar

This is what finished work looks like in this field. Use it as the standard for your revision rather than a general sense of improvement.

The behaviour is correct on ordinary input and on at least one awkward edge case
Names describe intent, so the code can be read without the author present
There is a concrete way to demonstrate that it works, not just an assurance

Diagnose before editing

Name the symptom, then ask what decision or missing step produced it. Choose the cause you can address rather than changing everything at once.

Revise and compare

Make one purposeful revision and compare the two versions. Keep the change only if it improves the intended result without creating a larger problem.

Revision flowchart

Evidence-led improvement loop

flowchart LR
    N1["Inspect evidence"]
    N2["Find the likely cause"]
    N3["Revise one issue"]
    N4["Compare versions"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Revise the cause of the highest-value issue, then compare the new result with the original criteria.

Step 1 of 4: Inspect evidence

Security pseudocode

Run a quarterly security review

UPDATE the password manager and browser
CHECK important accounts for alerts
REPLACE exposed passwords
VERIFY multi-factor methods
EXPORT an encrypted recovery backup

1 / 5

Read the statement UPDATE the password manager and browser

Connect this statement to the state and result around it.

This is a process model, not executable code; adapt it to the controls offered by each account.

Side-by-side comparison

Two programs that both "work"

Use this pair as your revision rubric: find which column your current draft sits in, one row at a time.

Aspect	Fragile script	Dependable program
Behavior	Right answer for the one input tried so far	Right answer for normal, empty, and extreme inputs
Readability	Single-letter names; the intent lives in the author's head	Names describe the data; the next reader needs no tour guide
Failure	Crashes or returns nonsense on an empty list	Guards the edge case and proves it with a test

The difference is invisible on the happy path and decisive everywhere else.

Practice round

Rebuild the Home network basics method

The steps of this chapter's method, shuffled. Arrange them so they would actually work.

A method is a sequence, not a bag of tips — if the order surprises you, that is exactly the gap worth closing now.

Order the steps, then explain to yourself why step 2 cannot go last.
Shuffle again and solve it in fewer moves.

Practice activity - 16 min

Run a focused revision cycle

Review a previous Home network basics artifact or the supplied flawed example, then improve the most consequential issue.

Score the draft against three criteria.
Quote or point to evidence for the weakest score.
Name the likely cause and revise it.
Write a before-and-after comparison.

Deliverable

A marked-up draft, revised version, and four-sentence change note.

Success looks like

Feedback cites evidence.
The revision addresses a cause.
The comparison explains a measurable or observable improvement.

Knowledge check

Which feedback is most useful for improving Home network basics?

1 question

AA specific observation linked to a criterion and a realistic next action. BA general statement that the work is good or bad. CA complete replacement made by someone else. DA list of unrelated preferences.

Chapter notes Not started

5
Chapter 5
Ethical security labs: Capstone integration

Integrate the course methods in a compact Ethical security labs capstone. You will define the brief, plan milestones, produce a complete result, gather tutor feedback, and leave with a repeatable next-practice plan.

36 min Not complete
Learning objectives

Translate the capstone brief into milestones and checks.

Combine the course methods without losing the central purpose.

Present evidence for the quality of the final result.

Choose the next skill to practice from the final review.
Key terms
1

Define a finishable brief

Choose a specific audience, result, and boundary for the Ethical security labs capstone. Reduce scope until the project can be finished and reviewed in one focused cycle.
2

Bringing the parts together

A capstone is judged on coherence, not on the number of techniques it includes. Return to the core ideas and make sure the work demonstrates them rather than decorating them.

Programs are state changing over time. Most confusion comes from not knowing what a variable holds at a given moment. Reading code as a sequence of state changes, rather than as instructions, is what makes unfamiliar programs understandable.

Make it work, then make it clear. Working code that nobody can read becomes unmaintainable within weeks, including for its author. Naming and structure are not decoration; they are how future changes stay cheap.

A bug is a disagreement between belief and behaviour. Debugging is the process of finding which of your beliefs about the program is false. Printing or inspecting values converts an argument with the computer into an observation.
3

Standards that make the work credible

These are the marks of work that would be taken seriously by someone who does this professionally.

The behaviour is correct on ordinary input and on at least one awkward edge case

Names describe intent, so the code can be read without the author present

There is a concrete way to demonstrate that it works, not just an assurance
4

Build with checkpoints

Plan foundation, first draft, verification, and revision milestones. At each checkpoint, save evidence instead of relying on memory.

5

Present and continue

Present a working program, configuration, or technical walkthrough with a concise rationale. Use the final rubric to choose one strength to retain and one next practice target.
Entropy lab
Watch a password get expensive to guess

Add length and character variety; the crack-time estimate does the arguing for you.

The model assumes an offline attacker guessing ten billion passwords per second. Length wins because every added character multiplies the whole search space.

Compare 8 characters using everything against 16 lowercase letters.

Find the shortest setting that survives for a century.
Visual model
Capstone learning loop

The capstone is a complete cycle: define a finishable brief, build, review evidence, then choose the next practice target.
Practice round
Match the Ethical security labs vocabulary

Tap a term, then the definition it belongs to. Wrong guesses cost nothing but honesty.

Retrieval beats rereading: pulling a definition from memory strengthens it far more than recognizing it on the page.

Clear the board once, shuffle, and beat your attempt count.

Say each definition aloud before tapping — then check yourself.
Practice activity - 22 min
Complete the capstone sprint

Create a complete Ethical security labs artifact for a defined audience and purpose, using the course rubric to review it.
1. Write a brief with scope and success criteria.
2. Create the first complete version.
3. Run a self-check and request focused tutor feedback.
4. Revise, present, and set one next-practice target.
Deliverable
A finished capstone, evidence of one revision, and a next-practice note.
Success looks like

The result answers the brief.

Course methods are visible.

Revision follows feedback or evidence.

The next step is specific and achievable.
Knowledge check
When is the Ethical security labs capstone ready to finish?

1 question

When is the Ethical security labs capstone ready to finish? AIt meets the written brief and criteria, includes a reviewed revision, and has a clear next-practice target. BIt contains every possible feature or idea. CThe learner can no longer think of any improvement. DIt looks exactly like the tutor example.

Chapter notes Not started

Sign in to save chapter notes to your account.

Ready to complete this chapter? Submit the completed capstone, revision evidence, rubric review, and one concrete next-practice target.

Make it personal

Turn the public curriculum into your own learning path.

Ask Anika Soren to adapt the sequence to your level, available time, and goal. The personalized path can then be saved in your workspace.

0 of 5 chapters complete

Build knowledge, use it, and leave with evidence of progress.

Before you start

Useful materials

Suggested rhythm

Working Password managers mini project

What you will submit

How it will be reviewed

Learn, practice, check, and record what matters.

Password managers: Foundations and vocabulary

Learning objectives

Key terms

Start with the purpose

How Password managers actually works

Misconceptions worth clearing early

Build the mental model

Catch the common miss

Which response best shows a usable foundation in Password managers?

Phishing practice: Guided demonstration

Learning objectives

Key terms

Watch the whole process

The method, one step at a time

Where this usually goes wrong

Practice with scaffolding

Check before feedback

During guided Phishing practice practice, when is the best time to explain a choice?

Privacy settings: Applied scenario

Learning objectives

Key terms

Read the situation

Choosing well under real constraints

Reading the situation before acting

Compare real options

Make the reasoning visible

What makes an applied Privacy settings decision defensible?

Home network basics: Review and improve

Learning objectives

Key terms

Use the rubric, not a feeling

Diagnostic checklist

The quality bar

Diagnose before editing

Revise and compare

Which feedback is most useful for improving Home network basics?

Ethical security labs: Capstone integration

Learning objectives

Key terms

Define a finishable brief

Bringing the parts together

Standards that make the work credible

Build with checkpoints

Present and continue

When is the Ethical security labs capstone ready to finish?

Turn the public curriculum into your own learning path.