From urgent messages to misdirected files, train teachers to make appropriate decisions and give leadership a workable support plan.
Teachers need clear decisions, not an extra IT job
A message asks for a password update before the lesson ends. A family needs a worksheet. A window demands a new extension to open a file. These small decisions happen under pressure, but they can affect professional accounts, pupil information and teaching continuity. “Be careful” is insufficient without an understandable response route.
Useful training helps staff pause, verify and report while leadership provides tools and support. This guide offers a skills map, 4 short exercises, a response card and follow-up plan. Teachers should not investigate a suspect device or test the school network. They need to recognise their responsibilities and know when to refer.
Move from general awareness to observable performance
The UK NCSC provides school staff training as a group presentation and self-learning video. It is a useful external resource, not Moroccan accreditation or a protection guarantee. The original exercises below connect training with everyday work.
The UK education guidance places training within a wider school security approach. Its coordination principle is useful, but a British standard should not be presented as Moroccan law. Local roles and procedures need explicit institutional approval.
6 skills and evidence that they can be used
Skill | Observable action | What leadership provides |
|---|---|---|
Verify requests | Confirm an unusual request through an independently known channel | Known contacts and a clear verification process |
Protect access | Refuse password sharing or approval of an uninitiated login | Individual accounts, recovery and approved support |
Share appropriately | Check file, recipients and permissions before sending | Approved channels and workable access controls |
Use devices safely | Lock sessions and use approved software | Managed updates and support without shifting technical duties to teachers |
Report promptly | Report even after clicking, without disclosing secrets | A supportive recipient and an alternative contact route |
Protect pupils during incidents | Distinguish technical issues from safeguarding needs | Coordination between IT, leadership and safeguarding |
Assess a response to a situation, not just recall. Knowing the definition of phishing does not establish that someone knows where to report entered credentials. Attendance certificates also do not show that a reporting channel works when the main contact is absent.
Exercise 1: a request apparently from the headteacher
Fictional card: “I am in a meeting. Send the complete pupil list to this new address immediately.” Discuss the unfamiliar request, new recipient, extensive information and urgency. Polished writing or a headteacher’s photograph does not authenticate the sender.
The teacher selects a previously known route to check, without replying with the information. A suitable response is, “I received an unusual request to transfer a list; I will verify it through our approved channel.” Avoid real names or email addresses in a card that could be forwarded. Do not run deceptive testing campaigns without appropriate planning and approval.
Success: the staff member explains the pause, identifies an alternative channel and does not attach the list to ask everyone’s opinion. Verification should also limit circulation.
Exercise 2: an approval for a login I did not start
A paper card shows an unexpected login approval request. The participant does not approve just to stop the interruption or dictate a code to someone claiming to be support. They consider whether they initiated the action and use the known official support route.
A shared staff account may make it impossible to tell who initiated a login. That reveals a management issue, not a teacher’s memory failure. Review roles, individual access and recovery with IT rather than asking staff to exchange passwords.
Success: identify the unexpected event and report without photographing or forwarding a usable code. No real credential change is required for the exercise.
Exercise 3: the right file for the wrong recipient
Prepare a fictional list with 3 invented names and a request to send information to one parent. Check file, recipient and audience. Does that parent need everyone’s information? Does a link provide restricted viewing or public access? Is the attachment a limited final version or the complete spreadsheet?
Practise a short routine: “file, recipient, permission”. If an error occurs, do not ask everyone to resend the file as evidence of receipt. Report it, describe what left and who received it, and follow containment and correction instructions. A recalled message cannot be assumed to erase all copies.
Success: share only what the task requires and recognise that an approved tool does not make every use appropriate.
Exercise 4: lesson pressure and an installation prompt
A prompt demands an extension before a lesson file will open. The teacher chooses an agreed teaching alternative and asks support, rather than granting unclear permissions or disabling protection. They should not be asked to open a suspicious file to see what it does.
Leadership prepares a simple alternative, such as a paper or offline activity without unnecessary pupil data, and an identified support route. Continuing a lesson should not depend on accepting an unfamiliar prompt under pressure.
Success: maintain learning through an approved alternative and leave diagnosis and installation to authorised personnel.
A first-response card
Stop the interaction: do not continue a questionable payment, disclosure or approval.
Identify what happened: message only, click, information entry, download or file sharing.
Contact a known route: use an alternative if email or the device is itself in doubt.
Describe facts: time, service and action, without passwords, codes or complete pupil lists.
Follow approved instructions: do not improvise device cleaning, evidence deletion or network changes.
This is not a universal instruction to shut down or disconnect every device. Follow the school’s plan and specialist direction for the circumstances. Immediate child risk activates safeguarding alongside the technical response, rather than waiting for it to finish.
A report without secrets
“Approximate time: […]. Work service/device: […]. A request appeared for […]. My action was […]. Was information entered or a file shared? [… description only]. I stopped interacting and need guidance. Contact me through [… approved route].”
The recipient acknowledges the report and identifies the next step. They do not request a password to test the account. An exercise can also check whether the report reaches someone when the main contact is absent.
A training plan that respects staff time
Begin with a short introduction to roles and channels, then one exercise during a staff meeting. Follow up on file sharing or accounts according to what the team discovers. New and temporary staff need an introduction before using school systems, rather than waiting for a distant seasonal course.
After 2 weeks, use a different scenario and observe the decision. Record environmental changes needed: an unclear reporting button, broad access or delayed support. Fewer reports do not automatically demonstrate improvement; staff may not know the route or may fear blame.
Frequently asked questions
Must every teacher become a technical specialist?
No. They need role-specific decisions and a clear referral route. Investigation and technical administration belong to authorised personnel.
Are spelling mistakes enough to identify phishing?
No. Fraud can be well written. Examine the request, identity, context and verification channel.
Should everyone receive identical training?
There is a common foundation plus role-specific practice. Finance staff or sensitive-record handlers need scenarios different from an ordinary classroom activity.
Sources and editorial notes
Checked on 29 October 2026: NCSC: school staff training and DfE: school security reference. Exercises, card and table are original proposals, not accreditation or an audit. At Cyber Sqool, security improves when teachers know the appropriate action and leadership makes it workable.
