01 / STARTER
Synthetic authentication-log analysis
Find a suspicious pattern, explain your rule and test normal events as well as suspicious ones.
PATHWAY / CYBERSECURITY
Explain your method, not just a badge.
Defensive cybersecurity portfolio projects with safe lab scope, validation and useful reports.
Three mission briefs
A suggested progression, not a certification track. The briefs are prompts; reference builds are not included.
02 / NEXT
Defensive incident-triage report
Create a fictional timeline, explain affected assets and separate confirmed facts from assumptions.
03 / NEXT
Secure configuration and recovery checklist
Document a team-owned lab, a small hardening change, a validation check and rollback steps.
What useful evidence looks like
Show the method and leave room for uncertainty.
The short version
I wrote a rule for repeated failures followed by a success in a fictional dataset. I tested a normal forgotten-password case and a missing-timestamp case. The rule flags a pattern for review; it does not prove account compromise.
Illustrative summary. No completed result or learner identity is claimed.
Bring these checks
- The lab/data scope is authorized and contains no real credentials or personal identifiers.
- The event fields, time window and data-generation method are described.
- The detection rule is explicit and can be reproduced.
- Expected results include normal, suspicious and incomplete-data cases.
Keep going
Write down the result before you package it.
GUIDE
Cybersecurity project documentation template
A practical structure for explaining your project and its limits.
TOOL
Evidence checklist
Review the requirements for your pathway without an overall skill score.
TOOL
Evidence-pack builder
Turn your notes into a locally downloadable project summary.