Your project brief
Threat-model a fictional online service and test defensive controls in an isolated lab.
The aim is to connect knowledge of the protection of digital systems through risk-based controls with a concrete, reviewable output. Use open, properly licensed or synthetic materials. Do not collect sensitive personal information or conduct experiments requiring approval without the appropriate supervision.
Define the question
State the problem in one sentence and identify who would use the result. Explain how network security and secure coding shape your approach. Set clear boundaries so the project can be completed with available resources.
Build an evidence trail
Keep a source register recording authorship, dates, permissions and limitations. Separate observations from interpretations. Compare at least two possible approaches and explain why you selected one. Record failed attempts as well as successful ones.
Create and review
Produce a small first version before expanding the scope. Ask a peer to check whether the evidence supports your conclusions and whether the output is understandable. Revise the work using that feedback and preserve a short account of what changed.
Deliverables and evaluation
- A clear problem statement and scope.
- A documented method and source register.
- A prototype, analytical report or creative output suited to the brief.
- A limitations statement and a reflection on the next investigation.
Evaluate the quality of reasoning, the appropriateness of methods, responsible handling of evidence and clarity of communication. A modest conclusion supported by good evidence is more valuable than an ambitious unsupported claim.