Join our Newsletter — 33% off our NHI Course
Home› Guides› DfE Cyber Security Standards for Schools and Colleges…
Guide Regulations & Frameworks

DfE Cyber Security Standards for Schools and Colleges Guide: Meeting Each Core Standard Step by Step

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, under the editorial direction of Lalit Choda Updated 18 November 2026 14 min read
On this page

The Department for Education's cyber security standards set out seven concrete things every school and college in England should do, and this guide walks through each one: what it asks for, who is responsible, the specific numbers to hit and the evidence to keep. It is written for senior leadership digital leads, school business managers, trust IT teams and the IT support providers who do the work.

For the wider picture of school cyber risk, safeguarding, filtering and monitoring and lessons from incidents, read our Cybersecurity for Schools Guide. This page stays narrowly on meeting the DfE cyber security standard, item by item.

Status as of 18 Nov 2026. This page summarises DfE guidance last updated on 16 September 2026. It is not legal advice; always check the current DfE text before relying on it.

Key takeaways

  • Cyber security is one of six core digital and technology standards that, according to the DfE, all schools and colleges should be working towards meeting by 2030. The others are broadband, wireless, network switching, digital leadership and governance, and filtering and monitoring.
  • The standards are framed as DfE's recommended approach rather than statute, but they are increasingly the benchmark used by trusts, governors, insurers and the Risk Protection Arrangement (RPA).
  • Seven items make up the cyber security standard: annual risk assessment, an awareness plan, anti-malware and firewall, account and access control, licensing and updates, backups, and reporting attacks.
  • Several items carry hard numbers: lockout after no more than 10 failed attempts, critical and high vulnerability fixes within 14 days, DfE security instructions within 5 working days, and at least 3 backup copies on 2 devices with one off-site.
  • Multi-factor authentication is expected for staff with cloud or remote access and for administrator accounts.
  • The senior leadership team (SLT) digital lead is accountable for most items, with IT support doing the work. Governors have a role in approving policy and checking compliance.

The DfE cyber security standards at a glance

StandardHeadline requirementsReview cycle
1. Conduct a cyber risk assessment annually and review every termAsset and access review, risk register, cyber response planAnnual, termly review
2. Create and implement a cyber awareness plan for students and staffAcceptable use policy, training at least annuallyPolicy updated each year
3. Secure digital technology and data with anti-malware and a firewallBoundary firewall with MFA on admin, managed anti-malware, USB blocked by default, email anti-spoofingTermly
4. Control and secure user accounts and access privilegesUnique credentials, MFA, lockout after 10 attempts, separate admin accounts, leaver processTermly account review
5. License digital technology and keep it up to dateSupported software, high and critical fixes in 14 days, DfE instructions in 5 working daysTermly contracts register
6. Develop and implement a plan to back up your data and review this every year3 copies, 2 devices, 1 off-site, immutable, termly restore testsTermly tests, annual review
7. Report cyber attacksResponse plan, report to RPA or insurer, Report Fraud, DfE, NCSC and ICO as relevantIn place now

Standard titles are quoted from the DfE cyber security standards for schools and colleges page.

Scope and status

The DfE's digital and technology standards describe the infrastructure and technology that schools and colleges in England should have. Alongside the six core standards, DfE publishes further standards on cloud solutions, digital accessibility, IT support, laptops, desktops and tablets, network cabling, and servers and storage.

The cyber security and filtering and monitoring standards are described as the DfE's recommended approach. They sit alongside, and support, the statutory responsibility to keep children and young people safe online that schools have under Keeping children safe in education. In practice:

  • Maintained schools, academies, free schools, multi-academy trusts and further education colleges should all treat the standard as the baseline.
  • Where IT is outsourced, the DfE says that provision that does not meet the risk assessment standard must be reviewed by the next contract renewal date. Use renewals to write the standards into contracts.
  • RPA members should note that a cyber response plan is a condition of RPA cyber cover, and that annual NCSC training must be evidenced.
  • Academy trusts must also follow part 6 of the Academy Trust Handbook when reporting incidents.

Standard 1: Conduct a cyber risk assessment annually and review every term

What it asks. Review digital assets, check licensing and access, document the network, identify the greatest risks and any past incidents, and build a risk register and cyber response plan. Keep a record of processing activities with your data protection officer (DPO).

Who. The SLT digital lead is accountable and IT support carries out the actions, with input from the DPO, headteacher, business and finance, estates and governors.

When. As soon as possible, then annually, after major technology or process changes, and after any incident, with a review every term.

How to meet it in practice.

  • Start with an inventory: devices, cloud services, management information system (MIS), finance system, safeguarding tools, network kit and every supplier with remote access.
  • Score risks on likelihood and impact, and record an owner and next action for each. Ransomware, account takeover, invoice fraud and supplier compromise should be on every school's register.
  • Use the NCSC Exercise in a Box tool, which the DfE points to, to test the response plan with SLT.
  • Bring the register to governors at least annually so they can see the risks and the progress.

Evidence to keep. Dated risk register, network diagram, cyber response plan, exercise notes, termly review minutes. Our Incident Response Plan Template can be adapted for a school.

Standard 2: Create and implement a cyber awareness plan for students and staff

What it asks. An acceptable use policy for everyone with network access, including visitors and supply staff, plus regular training. Training should cover phishing, passwords, MFA, removable media, physical device security, and how to report incidents and personal data breaches.

Who. The headteacher is accountable, the SLT digital lead coordinates, and IT support, the DPO and the designated safeguarding lead contribute. Governors approve the policy.

When. Training at least annually for students, staff, at least one governor and anyone else with a login. Update the policy towards the end of the year and share it at the start of the next. If nobody has had cyber training in the past 12 months, act now.

How to meet it in practice.

  • Map every group that holds a login: teaching staff, support staff, supply and peripatetic staff, governors, contractors and students.
  • Record completion by name so you can show evidence to the RPA or an insurer.
  • Make reporting easy: one email address or form, and a no blame message so that a member of staff who clicked a link says so quickly.
  • Pitch student content to age; primary pupils need simple messages about passwords and telling an adult.

Our Acceptable Use Policy Template and Security Awareness Plan Template are useful starting points.

Standard 3: Secure digital technology and data with anti-malware and a firewall

What it asks. Securely configure, update and firewall all networked devices, including Internet of Things devices. Specifically:

  • A correctly configured boundary firewall, with MFA on its administration interface.
  • Unauthenticated inbound connections blocked by default.
  • Firewall firmware and permitted inbound traffic reviewed termly, with sign-off from the SLT digital lead.
  • Centrally managed anti-malware that scans web pages, files and email attachments and alerts IT support.
  • USB storage blocked by default, with any approved drives scanned.
  • All applications checked and approved, and user installed browser extensions disabled.
  • Email configured to prevent spoofing, using the NCSC Mailcheck tool.

Who. SLT digital lead accountable, IT support acting, designated safeguarding lead advising.

When. Should already be in place, with settings reviewed termly.

How to meet it in practice. Ask IT support for a short termly report listing firewall firmware version, each inbound rule with its business reason, anti-malware coverage (devices reporting versus devices owned), and email authentication status. Remove any inbound rule nobody can explain. Smart boards, cameras, door entry and heating controllers count as networked devices and need the same treatment.

Standard 4: Control and secure user accounts and access privileges

What it asks. Agree who can access what, set password policies and apply MFA where needed. The DfE lists specific controls:

  • Unique credentials for devices, networks and services; consider single sign-on.
  • Strong passwords enforced, with compromised passwords changed immediately.
  • Lockout after no more than 10 failed attempts.
  • MFA, using at least two factors, for staff with cloud or remote access and for administrator accounts.
  • Accounts created only when needed and disabled promptly when people leave.
  • Dedicated administrator accounts separate from day to day accounts, with administrator changes approved by SLT or trustees.
  • An emergency administrator account held for SLT.
  • Accounts reviewed every term.
  • Network switches protected by a PIN or password of at least 6 characters.

Who. SLT digital lead accountable, IT support acting, working with suppliers, the DPO, HR and finance.

When. Should already be met; if not, roll out through a structured plan as soon as possible.

How to meet it in practice. This is the standard where identity work pays off most.

  • Link accounts to HR. Have the MIS or HR system drive account creation and removal, so a leaver's date triggers disablement. See the Joiner-Mover-Leaver Guide.
  • Roll out MFA in waves. Administrators and SLT first, then finance and safeguarding staff, then all staff using cloud email and remote access. Prefer authenticator apps or passkeys over SMS where practical. Our Authentication and MFA Policy Template helps record the decision.
  • Separate administrator accounts. IT technicians should browse and read email with a standard account and use a separate administrator account only for administration.
  • Do not forget non-human accounts. MIS integrations, single sign-on connectors, backup service accounts, printer and scanner accounts, and supplier remote support accounts are all accounts under this standard. List them, give each an owner, and include them in the termly review.
  • Seal the emergency account. Store the emergency administrator credentials securely, test them termly, and alert on any use.

Evidence to keep. Termly account review signed by the SLT digital lead, MFA coverage figures, list of administrator and service accounts with owners, approvals for administrator changes.

Standard 5: License digital technology and keep it up to date

What it asks. Confirm all technology is licensed and supported, record end of support dates, and review the contracts register. In particular:

  • Apply vulnerability fixes within 14 days when the vendor rates them critical or high, when the CVSS v3.1 score is 7.0 or above, or when no rating is given.
  • Isolate devices where fixes for high risk vulnerabilities are not available.
  • Apply DfE security instructions within 5 working days.
  • Follow open source licence terms.
  • Cloud services can replace licensed software; ask the DPO for a data protection impact assessment if personal data is involved.

Who. SLT digital lead accountable, IT support acting, business and finance managing licence records, governors checking compliance, the DPO advising.

When. Required now for existing technology; check every new purchase against the standard, and review the contracts register termly.

How to meet it in practice. Ask IT support to report the percentage of devices patched within 14 days and to list any device past end of support. Old servers, unsupported Windows versions and network kit with expired firmware support are common gaps. The Patch Management Guide covers process and tooling, and the CVSS v4 Guide explains scoring; note that the DfE threshold is written against CVSS v3.1.

Standard 6: Develop and implement a plan to back up your data and review this every year

What it asks. A backup plan that feeds business continuity and disaster recovery, with recovery priorities agreed. Specifically:

  • At least 3 copies of data, on at least 2 separate devices, with at least one off-site; cloud is acceptable.
  • Immutable backups.
  • Restores tested and logged every term.
  • A policy setting how often restores happen and how results are reported.
  • Backups never taken to anyone's home, and unencrypted physical backups never leaving the site.
  • An annual process to delete or archive old data.

Who. The SLT digital lead owns the plan and IT support acts, with business and finance, the designated safeguarding lead and the DPO helping to set priorities.

When. Backups must happen now; create a plan as soon as possible if none exists; test termly; review annually or after major system changes.

How to meet it in practice. Check that cloud services such as email and file storage are covered, not only on-premises servers. Make sure the accounts that manage backups are separate from normal domain administrator accounts and protected with MFA, because ransomware operators target backup consoles first. See the Backup Security and Immutable Backup Guide.

Standard 7: Report cyber attacks

What it asks. Anyone who spots an attack reports it to IT support and the SLT digital lead. The school then activates its cyber incident response plan: contain the risk, notify the right people, investigate, record the incident and inform governors.

External reporting. The DfE lists:

  • The RPA or the school's cyber insurer.
  • Report Fraud on 0300 123 2040.
  • The DfE sector cyber team at [email protected].
  • The NCSC, where an incident causes long term closure, closure of multiple schools, or serious financial damage.
  • The ICO within 72 hours for high risk personal data breaches.
  • Further education institutions may also report to Jisc, and trusts must follow part 6 of the Academy Trust Handbook.

Who. The SLT digital lead assigns who reports externally; SLT and the headteacher approve formal reports; IT support investigates; the DPO checks for data breaches; the designated safeguarding lead reviews safeguarding impact; governors are informed.

How to meet it in practice. Print a one page contact sheet with these routes, your RPA or insurer number and your IT provider's out of hours number, and keep it offline. A ransomware attack may take email and file shares with it.

What it means for security and identity teams

For trust IT teams and managed service providers, the standards translate into a small number of measurable controls:

  • MFA coverage for administrators, SLT, and all staff with cloud or remote access, tracked as a percentage.
  • A complete account inventory, including service and supplier accounts, reviewed every term.
  • Patch compliance against the 14 day and 5 working day targets.
  • Termly restore test logs.
  • Firewall rule and firmware reviews with SLT sign-off.

Trusts with many schools should centralise identity, using one directory and single sign-on, so that leaver removal, MFA enforcement and administrator separation are done once. Providers serving many schools should treat their own remote access tools and technician accounts as the highest risk accounts in the estate, because one compromised technician account can reach every customer. For the national baseline that complements the DfE standard, see the Cyber Essentials Guide.

Common failure patterns

  • The risk assessment is written once and never reviewed termly.
  • MFA is on for staff email but not for the firewall, backup console or MIS administrator accounts.
  • IT technicians use one administrator account for everything, including email.
  • Leavers, supply staff and former governors keep working logins.
  • Supplier remote access accounts are shared, permanent and missing from account reviews.
  • Backups exist but no restore has been tested, or backups sit on the same network and are encrypted with everything else.
  • Training is delivered to teachers but not to support staff, governors or contractors.
  • The response plan lives only on the file server that ransomware has just encrypted.

Practitioner checklist

  • A dated cyber risk register and response plan exist, reviewed this term.
  • Every person with a login has had cyber training in the past 12 months, including at least one governor.
  • The boundary firewall admin interface uses MFA and inbound rules were reviewed this term.
  • Anti-malware is centrally managed, USB storage is blocked by default and email anti-spoofing is checked.
  • Accounts lock after no more than 10 failed attempts and MFA covers administrators and cloud or remote access users.
  • Administrators use separate accounts and an emergency administrator account is sealed and tested.
  • Accounts, including service and supplier accounts, were reviewed this term and leavers are removed promptly.
  • Critical and high fixes are applied within 14 days and DfE instructions within 5 working days.
  • Backups follow 3 copies, 2 devices, 1 off-site, are immutable, and a restore was tested and logged this term.
  • An offline contact sheet lists the RPA or insurer, Report Fraud, DfE, NCSC and ICO routes.

Standards and references

Related NHI Mgmt Group resources: Cybersecurity for Schools Guide · Cyber Security for Nurseries and Childcare Providers Guide · Cyber Essentials Guide · Joiner-Mover-Leaver Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick both boxes to continue.