Courses / Cybersecurity and digital literacy / Protect, verify and recover / Secure a fictional club service Build and defend your work Secure a fictional club service Deliver an access and response plan for a club inventory service. Use captured experiments to justify permissions, message verification, input boundaries, recovery objectives and maintenance priorities. Include a tested sandbox contract or equivalent decision table; never use real credentials.
Choose an audience, investigate alternatives, copy evidence from your experiments, and produce an artifact. You can open this project at any time. Reports, numerical transfer checks and human review are separate outcomes.
Your project workspace Choose the kind of work you want to produce School investigation College investigation Workplace application Submit a role/file permission table, message verification checklist and incident timeline for a school club. Test three legitimate and three rejected requests.
1. Collect and compare evidence Required experiment sources:
Include every source above and at least one pair with different inputs from the same experiment. Explain confounding changes yourself; the presence check does not judge your interpretation.
Open an experiment and change an input or capture a trial to make evidence available here.
2. Write and revise your report Service, users and task contract Name fictional assets, legitimate operations, sensitive data and which actors need which permissions.
Protection and request tests Attach a permission matrix and whole-input validation cases. Explain safe output rendering separately from input acceptance.
Incident timeline and recovery Use a capture to show detection/action timing, affected devices, downtime units, last backup and lost records.
Maintenance and recovery trade-offs Compare at least two plans under equal resources. Distinguish exposure inventory from likelihood of attack.
Retest and accountable follow-up Name a fresh failure case, owner, rollback or recovery step and evidence needed before deployment.
Your artifact: code, analysis, prototype or decision brief This field stores up to 12,000 characters of inert text. Code runs only through the explicit bounded editor in the relevant lessons; project attachments never execute.
Load a text artifact Review your work against the rubric Permissions preserve legitimate tasks and remove unjustified grants. Boundary tests reject malformed requests without executing arbitrary text. Timing, data loss and interrupted device-hours are calculated with explicit assumptions. Maintenance decisions cite capacity and missing risk evidence. A fresh case and follow-up plan are supplied; real security assurance requires further review. 11 evidence requirements remain Capture evidence from permission repair. Capture evidence from validate a sandbox request. Capture evidence from contain an incident. Capture evidence from backup recovery. Include two different input configurations from the same experiment to compare. Write your service, users and task contract. Write your protection and request tests. Write your incident timeline and recovery. Write your maintenance and recovery trade-offs. Write your retest and accountable follow-up. Add your project artifact: code, analysis, prototype or decision brief. Record my report Download report and evidence Editing the report or evidence returns it to draft. Recording verifies field presence and input comparisons, not correctness of your reasoning or code.
3. Check transfer to unfamiliar cases These authored cases use different numbers or conditions from the lesson practice. They are public local checks, not secure certification. Each case permits three submissions. Opening, first responses and attempt counts survive imports; no reset creates fresh evidence.
Case excess-access Open case excess-access Case recovery-loss Open case recovery-loss Case parallel-outage Open case parallel-outage
Return to the course · My Work and backups
