Explore cybersecurity through hypotheses and evidence. Five projects work on paper or in a teacher-prepared local environment without testing real systems.
A good cyber project tests an idea, not someone else’s accounts
Did a file change? Who needs editing permission? Can a backup actually restore the required work? These questions make useful small science projects with a hypothesis, experiment, observation and explanation. Pupils do not need to attempt account access or inspect a real network to understand cybersecurity.
Here are 5 STEM projects with defined outputs. Most work on paper or in a local training folder prepared by a teacher. All information is fictional and tools are approved beforehand. The goal is explaining findings and limits rather than merely producing a “success” screenshot.
A lab card before every project
Specify the objective, exact folder or paper materials, permitted tools, supervisor and stop signal. Do not use actual school records, pupil photographs or real passwords. Accounts, networks and websites not listed in the activity are outside scope.
If unexpected information, an installation prompt or an unreviewed external connection appears, stop and ask. Do not disable protection or grant administration privileges to finish. A paper alternative remains available when a suitable environment is unavailable.
Choose by the learning objective
Project | Scientific question | Output |
|---|---|---|
File fingerprint | Does changing content change the result? | A comparison table with limitations |
Access matrix | Does every role need identical rights? | Rules checked against fictional cases |
Recovery test | Does the copy restore the required work? | A recovery and verification record |
Threat map | What are we protecting and from what? | Assets, risks and decisions diagram |
Minimal-data form | Which information is actually necessary? | A revised form with field justifications |
Project 1: did the file change?
Idea: a hash function produces a value representing its input, as described in the NIST glossary. Compare fictional files with the same tool. A hash is not reversible encryption and does not alone establish that a file is safe or its publisher trustworthy.
Preparation: the teacher creates a short fictional text file, an identical copy and a copy with one character changed. Use an approved local hashing tool, such as one calculating SHA-256, without uploading files to a website.
Predict whether the identical copies will have matching values.
Calculate and record values without guessing from filenames.
Change one character in a training copy and recalculate.
Rename a file without changing its content and compare.
Explain why comparison against a published value needs a trustworthy reference.
Assessment: can pupils distinguish a filename from content bytes? An editor may add a line ending or alter encoding. Investigating that difference is learning, not something to hide. Do not generalise that different files can never share a hash value.
Project 2: who can read or edit?
Idea: design a logical access model for a fictional project file. Roles are owner, reviewer and visitor; actions are read, edit and share. Pupils do not change a real system’s permissions. They examine decisions in a table.
Describe the work each role must perform.
Assign only the actions needed within the model.
Test 6 fictional requests, including a visitor asking to edit and a reviewer asking to read.
Add a temporary role and specify when its permission ends.
Consider someone with no assigned role and justify the outcome.
Optional coding: use a simple condition in an approved local environment to return “allowed” or “not allowed” from invented inputs. Collect no passwords and create no login page. Compare program output with the table and correct one inconsistency.
Limit: a table expresses a policy; it does not prove that a real platform enforces it. Designing a rule differs from authorised testing of an implementation.
Project 3: a copy exists, but can it restore?
Idea: a folder named “backup” is not enough. Establish what it restores and how to check it. DfE guidance includes recovery in school security. Use it as background rather than Moroccan legal requirements.
Preparation: a training folder with 3 fictional files, an independent copy prepared by the supervisor and an empty destination. Do not delete the originals or disconnect a school drive to simulate a failure.
List what should be restored.
Restore the prepared copy to the training destination under supervision.
Check file count, successful opening and required contents.
Compare the copy’s date: does it include the latest revision?
Record what was not covered, such as application settings outside the copy.
Finding: “We restored 3 files and checked their contents, but the latest edit is missing” is more accurate than “everything is protected”. Do not test with actual pupil records or institutional settings.
Project 4: a threat map for a fictional exhibition
Imagine a school exhibition on paper with visitor registration, project images and a display screen. Draw where information enters, who uses it and what must remain available. Identify 3 assets, such as registration, team work and uninterrupted presentation.
For each asset, describe a possible mistake or threat, its effect, a protection and that protection’s limit. For example, displaying a name list publicly is a sharing error; a reviewed display copy without names reduces that risk. No real website vulnerability search is needed.
Design challenge: choose 2 actions with limited resources and explain their priority. Context may support different answers, but the choice should follow assumptions and impact rather than tool popularity.
Project 5: accomplish the task with less information
Provide a fictional reading-club form requesting name, age, address, identity-document image and other unnecessary details. The objective is attendance at an internal school session. Pupils justify fields and propose removal or substitution within the fictional example.
Compare versions: can the organiser still identify attendance and communicate through the school channel? Did the task become harder or did information decrease without losing the purpose? Pupils do not redesign official forms or remove legally required fields without appropriate review.
Output: a revised fictional form and “field, purpose, decision, reason” list. It can remain an interactive paper prototype that collects no real responses.
A report sheet for all 5 projects
Question: … Hypothesis: … Scope: … What changed: … What stayed constant: … Observation: … Explanation: … What this does not establish: … Improvement: …
This prevents a limited observation becoming an excessive claim. A permission table or file hash does not justify “I built an unbreakable system”. State precisely what was examined and how the result was established.
Assessment and adaptation
Assess hypothesis clarity, scope, accurate recording, explanation and limits. Younger pupils can sort cards or explain orally. Older learners can add simple local coding or more comparisons without moving to real systems.
Change one factor when investigating its effect and discuss unintended changes. Rotate experimentation, recording and presentation so learning is not restricted to the fastest person at the keyboard.
Frequently asked questions
Is continuous internet access required?
No. Once materials and approved tools are ready, the proposed work can run locally or on paper.
Does hashing prove a file contains no malware?
No. It represents content for appropriate comparisons, not a safety scan or publisher guarantee.
Should real passwords make the exercise realistic?
No. Use entirely fictional information and never ask pupils to disclose secrets.
Sources and editorial notes
Checked on 29 October 2026: NIST: Hash function and DfE: school security reference. Projects, steps and sheets are original teaching proposals, not penetration testing or an audit. Cyber Sqool connects scientific curiosity with responsible decisions and explanations open to discussion.
