Teachers and school staff are the people attackers actually reach, so a school's cyber resilience depends on what staff do with an email, a password, a laptop and a spreadsheet on an ordinary working day. This guide is written for classroom teachers, teaching assistants, office staff, site staff, supply and agency staff and anyone else in a school who has a login. It covers the workplace security habits that matter most: spotting and reporting phishing, protecting school accounts, looking after devices, handling school data and reporting incidents quickly.
It is deliberately narrow and covers workplace cyber security for staff only. For the leadership and IT view of school security, including the full Department for Education (DfE) standards and how to implement them, see the Cybersecurity for Schools Guide and the DfE Cyber Security Standards for Schools and Colleges Guide. This page translates those expectations into what a member of staff needs to know and do.
Key takeaways
- The DfE cyber security standards expect cyber training for staff at least annually, and that includes anyone else with a login, such as supply or agency staff.
- The National Cyber Security Centre (NCSC) provides a free training package for school staff, available as a scripted presentation for staff meetings or INSET days and as a self-learn video, with a completion certificate.
- Schools that use the Risk Protection Arrangement (RPA) must be able to evidence that relevant users have completed the free NCSC training, so your certificate matters to the school, not just to you.
- Use a unique password for school services, accept multi-factor authentication (MFA) when it is offered, and never share your login with colleagues or visitors.
- Do not plug in unknown USB storage. DfE expects IT support to prohibit USB storage by default unless there is a specific need.
- Report anything suspicious straight away to IT support and the senior leadership team (SLT) digital lead. DfE states that everyone is responsible for reporting a cyber incident, and staff should feel safe doing so.
- Reporting a click quickly is far more useful than hiding it. The NCSC is clear that staff should feel supported to come forward even when they have clicked.
Why staff security matters in a school
Schools run on shared systems: a management information system, cloud email and file storage, finance software, learning platforms and a mix of school-owned and personal devices. Most staff have access to at least one system that holds personal or sensitive information about colleagues, families or the school's finances. That access is exactly what an attacker wants, and the simplest way in is usually through a person rather than a technical flaw.
A school day is also unusually busy and interrupted. Staff check email between lessons, on a phone in a corridor, or at the end of a long day. Messages arrive from parents, suppliers, the local authority, the trust central team, exam boards and dozens of education platforms. That volume and variety make it harder to notice when one message is fake. Good security habits for school staff are therefore less about technical knowledge and more about having a few fixed rules that work even when you are tired and in a hurry.
The DfE standards put this into policy terms. Standard 2 asks schools to create and implement a cyber awareness plan for staff, and the guidance lists the topics that training should cover, including phishing, password security, social engineering, physical device security, removable media risks, multi-factor authentication, reporting cyber incidents and reporting personal data breaches. The sections below follow that list from a staff point of view.
Training: what you will be asked to complete
Most schools meet the awareness requirement through the NCSC's free cyber security training for school staff. The NCSC describes it as a training package to help school staff improve their school's cyber resilience. It comes in two forms with the same content: a scripted presentation pack that a member of staff can deliver at a staff meeting or INSET day, in person or virtually, and a self-learn video that you can complete on your own at a time that suits you. When you finish, you can obtain a certificate to show that you have completed the training.
Keep that certificate, or make sure the person running the session records your attendance. DfE guidance says that if a school has RPA cover it must evidence that the relevant users have undertaken the free NCSC training, taken annually. A school that cannot show completion may find it harder to rely on its cover after an incident. If you join mid-year, are on a supply contract or work across several schools, ask the school business manager or office team how they want you to record it.
DfE also expects acceptable use to be in place: anyone with access to the school network or data should be made aware of the acceptable use policy and sign up to it, including guests and supply teachers. Read it rather than ticking the box. It usually sets the rules that matter in this guide, such as whether personal devices can access school email, where files may be stored and how to report a problem.
Some roles need more. DfE notes that staff who handle higher-risk data, such as administrative, management and agency staff with logins, should receive data protection training more frequently. If you work in the office, in exams administration or with finance or HR records, expect additional sessions.
Phishing and social engineering in a school setting
Phishing is a message designed to make you click a link, open an attachment, give away a password or do something you would not normally do. It arrives by email most often, but also by text, phone call, messaging app or a collaboration platform. Social engineering is the wider set of tricks that rely on persuasion rather than technology, such as a caller who claims to be from IT support and asks you to read out a code.
The NCSC advises organisations to help users identify the common features of phishing messages and to make sure staff are familiar with the normal ways of working for key tasks. That second point is the most useful one for school staff. If you know how things normally happen, a fake request stands out. For example:
- Password and login messages. Your school or trust will have a normal way of telling you to reset a password or reconnect an account. A message that does it differently, or asks you to sign in from a link to "keep your mailbox", is suspicious.
- Shared documents. A "document shared with you" notice from a name you do not recognise, or for a file you were not expecting, is a common lure. Open shared files from inside the platform you normally use rather than from the email link.
- Urgent requests from senior staff. Messages that appear to come from the headteacher or a trust leader asking you to buy gift cards, change bank details or send a list of staff details urgently are a known pattern. Check by phone or in person using details you already have.
- Parent and supplier messages. Attackers can impersonate a parent or a supplier. A message that tries to move a conversation to a new email address, or contains an unexpected attachment, deserves a second look.
- Calls claiming to be IT support. Genuine IT support should never ask for your password. Treat any request for a password or an MFA code over the phone as a red flag.
The NCSC also makes a point that matters for how staff feel about this: training cannot teach everyone to spot every phishing email, so it should not be the only defence. Schools should also filter email, use MFA and have a quick reporting route. Your job is not to be perfect. It is to pause on anything unusual and to report what you see. For a general checklist of warning signs, see the How to Spot a Phishing Email Guide.
Passwords, MFA and your school accounts
Your school account is a key. It may open email, cloud storage, the management information system and other platforms through single sign-on. If someone else gets it, they can read and send messages as you and reach whatever you can reach.
DfE Standard 4 sets out what schools should do with accounts, and several parts apply directly to staff:
- Unique credentials. Users need unique credentials for devices, the network and services. Do not reuse your school password on personal sites, and do not share a login with a colleague, even to help during a busy day.
- Strong passwords. DfE refers to machine-generated passwords or the three-random-words approach. If your school offers a password manager, use it.
- Change compromised passwords immediately. DfE says schools should immediately change any passwords that have been compromised or are suspected of compromise. If you think you typed your password into a fake page, tell IT support and change it straight away.
- MFA. DfE states that MFA must be enabled for all staff with cloud or remote access and for IT administrative accounts. When you are asked to set it up, do so promptly, and register a method you will always have with you.
- Least access. Accounts should give only the access each role requires. If you notice you can see folders or records you do not need, tell IT support rather than using them.
MFA has one weak point that staff control: approving a sign-in you did not start. If your phone asks you to approve a login and you are not signing in at that moment, do not approve it. Report it, because it probably means someone has your password. The MFA Fatigue and Bypass Guide explains this pattern in more detail. If you think your account has already been taken over, the NCSC's guidance on recovering a hacked account describes the steps, but in a school your first step should always be to contact IT support.
Devices, classroom technology and removable media
School staff use laptops, desktops in classrooms, interactive displays, tablets, visualisers and sometimes their own phones. Each one can expose school accounts and data if it is left unlocked, lost or loaded with untrusted software.
Lock and log out
Classroom and staffroom computers are shared spaces. Lock your screen whenever you step away, and log out of email and the management information system before you leave a room. Be careful when a classroom display is mirroring your screen: close email and record systems before you project, so that notifications and personal data are not shown to the room.
Updates and software
DfE expects all network-connected devices to be securely configured and kept up to date, and expects IT support to approve applications before installation and to maintain an approved application list. For staff, that means accepting updates when prompted, restarting devices regularly so updates apply, and asking IT support before installing a new app, browser extension or classroom tool, even a free one.
USB sticks and removable media
DfE says IT support should prohibit the use of USB storage devices by default unless there is a specific need, and that any permitted drive should be scanned before use. Do not plug in a USB stick you have found or been handed by someone you do not know. If you need to move files, use the school's approved cloud storage instead.
Working away from school
DfE asks schools to enable a software firewall on devices used off-site and to consider a VPN. Follow your school's rules on taking devices home, keep school laptops with you when travelling, and do not let family members use a school device. If a device is lost or stolen, report it to IT support immediately so access can be revoked.
Handling school data safely
Staff handle personal data every day: contact details, assessment records, staff information, attendance data and more. The aim is simple: keep data in approved school systems, share it only with people who need it, and know what to do if it goes to the wrong place.
- Store files in approved locations. Use the school's cloud storage or network drives rather than personal email, personal cloud accounts or a home computer.
- Check recipients before sending. Autocomplete is a common cause of data going to the wrong person. Check the address, especially when sending to external contacts or groups.
- Share links, not attachments, where possible. A link to a file in school storage can be restricted and revoked. An attachment cannot be recalled once sent.
- Be careful with printing. Collect printouts promptly and use secure print if your school has it.
- Do not paste school data into unapproved tools. That includes online converters, personal note apps and AI chat tools that your school has not approved.
- Follow retention rules. Delete local copies once they are no longer needed and follow the school's data retention policy.
Backups are not usually a staff task, but staff habits affect them. DfE expects schools to keep at least three backup copies of important data on at least two separate devices, with one off-site, and states that backups should never be taken to anyone's home. If you keep important work only on a local drive or a personal device, it is outside those backups and may be lost.
Reporting incidents and mistakes
DfE Standard 7 is direct: everyone is responsible for and should report a cyber incident or attack to IT support and the SLT digital lead, and staff should know how to do this and feel safe doing it. Find out now how your school wants reports made, such as a helpdesk address, a phone number or a report button in your email client, and save it somewhere you can reach if your account is not working.
Report straight away if you:
- clicked a link or opened an attachment that now looks suspicious;
- entered your password on a page you are not sure about;
- approved an MFA prompt you did not start;
- notice emails in your sent folder that you did not send, or new mailbox rules you did not create;
- lose a device, USB stick or paper records containing personal data;
- sent personal data to the wrong person;
- see a ransom note, files you cannot open, or a screen that tells you files have been encrypted.
Time matters. DfE guidance notes that a school must report to the Information Commissioner's Office within 72 hours where a high-risk data breach has or may have occurred, so the school needs to hear from you quickly to make that decision. The NCSC's advice to organisations is that users should feel supported to come forward even when they have clicked, because employees who are afraid for their jobs will not report mistakes. A prompt report is the most useful thing you can do after a mistake.
For suspicious emails that you have not interacted with, use the school's report button or forward them as your school instructs. The NCSC also runs a public report a scam email service, which is useful for personal email but should not replace your school's internal process.
Where identity fits
Most school attacks are identity attacks: a stolen password, an approved MFA prompt, a shared account or an account that was never disabled when someone left. DfE asks schools to disable accounts as soon as someone leaves their role and to review accounts every term with business professionals or the finance team. Staff can help by telling the office or IT support when they change role, stop using a system, or know a colleague or supply teacher has left. Shared generic logins for classroom devices or platforms should be the exception, approved by IT support, and never used for systems that hold personal data.
Common failure patterns
- Training done once and forgotten. The NCSC course is completed at induction but not repeated each year, so the school cannot evidence annual completion.
- Supply and agency staff left out. Temporary staff are given logins without training or acceptable use sign-off, even though DfE includes them.
- Shared logins on busy days. A colleague's account is used "just for this lesson", which breaks accountability and spreads the password.
- Approving unexpected MFA prompts. Staff approve a prompt to make it stop, handing an attacker access.
- Projecting email. A display mirrors a screen with email or records open.
- Personal storage for school files. Work saved to personal cloud or home computers sits outside school backups and controls.
- Silence after a click. Staff delay reporting out of embarrassment, giving an attacker hours or days.
- No known reporting route. Staff are unsure who to tell, especially when their own account is locked.
Practitioner checklist
- Complete the NCSC cyber security training for school staff each year and keep or submit your certificate.
- Read and sign the school's acceptable use policy.
- Use a unique, strong school password and a password manager if offered.
- Set up MFA when asked and never approve a prompt you did not start.
- Never share your login, and never give a password or MFA code to a caller.
- Lock your screen every time you step away and close email before projecting.
- Accept updates and ask IT support before installing new apps or extensions.
- Do not use unknown USB storage; use approved cloud storage instead.
- Keep school data in approved systems and check recipients before sending.
- Save the IT support and SLT digital lead contact details somewhere you can reach offline.
- Report clicks, lost devices and misdirected data immediately.
- Tell the office or IT support when your role changes or you stop needing access.
Standards and references
- DfE: Cyber security standards for schools and colleges
- NCSC: Cyber security training for school staff
- NCSC: Phishing attacks, defending your organisation
- NCSC: Recovering a hacked account
- NCSC: Report a scam email
- DfE Cyber Security Hub: Risk protection arrangement
Related NHI Mgmt Group resources: Cybersecurity for Schools Guide · DfE Cyber Security Standards for Schools and Colleges Guide · How to Spot a Phishing Email Guide · Security for School Governors and Trustees Guide