Warm up
Try the Thinking Gym for a quick logic puzzle before you recap.
Summary and games
Cybersecurity summary and games
Well done for reaching the end of the core track. This page is your recap and a playful assessment hub. The goal is not perfect recall. The goal is a calmer, faster "what matters here" instinct.
Drop in after each level or months later to reconnect the dots between data, systems, attackers, defenders and everyday decisions. When time and budget are limited, the winning move is usually clarity: what you are protecting, who owns it, and which few controls buy you the most risk reduction.
Course map in one glance
Four stops that build the same habits
Use this as a quick reminder of how the levels connect.
Shared language, habits, and everyday defences.
Threat models, attack surfaces, and identity flows.
Architecture, detection, and governance in context.
Recap, games, and confidence checks.
Quick recap of the journey
Here is a one paragraph recap of each level. Notice how the thinking evolves from "what is this thing" to "what decision do I make next". Click through if you want to revisit details.
Foundations
You built the shared language: how data moves, how people get tricked, where accounts fail, and what basic controls actually do. The surprise for many people is that most incidents start as normal work, not movie hacking.
Revisit this levelIntermediate
You moved from facts to judgement: threat modelling, identity flows, common vulnerabilities, and how logs turn into a story you can act on. What gets misunderstood in real teams is that scanning is not security. It is just a list until you make trade offs and fix things.
Revisit this levelAdvanced
You connected the system view: architecture choices, crypto in practice, detection and response, and governance that makes improvements stick. The most useful shift here is this: security becomes a set of decisions you can explain, not a pile of tools you can buy.
Revisit this levelYour progress across the three levels
I am not tracking your personal data or building a profile. This view is a gentle reminder of the path, not a strict tracker. Use it with a team or class by agreeing what done means, such as finishing labs or being able to explain the ideas aloud.
Cross level revision challenges
Friendly prompts that stitch the three levels together. Use them solo, or as warm ups with a team.
Games that build judgement
These games are here to help you revisit key ideas in a low pressure way. None record scores or personal details. Just play, notice what feels fuzzy, and jump back to the notes if needed.
The point is purposeful repetition. Each game reinforces a decision you will make in the real world: what control to choose, where trust changes, what to log, and how to limit privilege.
Choose a game. Make the call. See the consequences.
More practice games
Explore all practice games including cybersecurity, digitalisation, and cross-topic drills.
Quick nudge: when a game result surprises you, that is not failure. It is a signal. Go find the assumption you were using, then decide what control, log, or process would protect you when that assumption is wrong.
Try the tools with real inputs
Use safe examples to see signals show up for real.
Cross topic games
Broader prompts that mix cybersecurity with other domains.
Skill focus: spotting when a problem is not purely technical. These prompts reinforce decision making under uncertainty, where you balance safety, speed, user impact, and evidence.
Reflection: what did you prioritise, and why. If you were advising a team, what would you write down as the rule of thumb so others can make the same call.
Capstone journeys
Progress insights
These insights are private to this device. No account. No tracking.
CPD reflection prompt
If you had one hour next week to make a real organisation safer, what would you change first, and what would you deliberately not do yet.
- Which two controls would you prioritise because they reduce real risk quickly.
- Which risk would you now notice immediately in a meeting or design review.
- What evidence or logs would you insist on so incidents become manageable, not mysterious.
Bonus: write the decision in one sentence, then write the trade off you are accepting. That is the skill that scales.
