Join our Newsletter — 33% off our NHI Course
Home› Guides› Security for School Governors and Trustees Guide: The…
Guide Security Leadership & Governance

Security for School Governors and Trustees Guide: The Questions to Ask and the Evidence to Expect

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 12 min read
On this page

Governors and trustees do not run a school's IT, but they are responsible for making sure cyber risk is understood, managed and tested, and that means asking the right questions and knowing what a good answer looks like. This guide turns the NCSC and Department for Education (DfE) questions for governors into a practical oversight routine: what to ask, what evidence to expect, how often to look at it, and what to do when the answers are weak.

It is written for governors and trustees of maintained schools, academies and multi-academy trusts, chairs of audit and risk committees, clerks, and the headteachers, business managers and digital leads who report to them. It focuses on the governance role. For the technical controls a school should run, see the Cybersecurity for Schools Guide and the DfE Cyber Security Standards for Schools and Colleges Guide.

This guide is general information, not legal advice. Status as of 18 Nov 2026: the DfE cyber security standards page was last updated on 16 September 2026, and the NCSC governor questions page shows a publication and review date of 15 July 2020.

Key takeaways

  • The governing body's job is oversight and strategic risk management, not hands-on IT. The DfE standards place accountability for most technical standards with the senior leadership team (SLT) digital lead.
  • The NCSC and DfE eight questions are a conversation starter, not a checklist. Use them to open a discussion, then ask for evidence.
  • Good evidence is specific and dated: a restore test result, a training completion figure, a risk register entry, a supplier list, an incident plan that names people.
  • Governors have named roles in the DfE standards: approving the acceptable use policy, taking part in cyber training, checking licensing as part of compliance review, and being told when an incident happens.
  • For schools in the DfE risk protection arrangement (RPA), some controls, such as a cyber response plan, training and backups, are conditions of cover. Governors should confirm they are met.
  • Put cyber security on the agenda at least termly, with an annual deeper review linked to the risk assessment.

What governors and trustees are responsible for

The NCSC page on cyber security questions for governors and trustees, produced with the DfE, describes the questions as a way to start the cyber security conversation between the governing body and school leaders, with the governing body taking the lead. It is explicit that the questions are not intended as a checklist.

The DfE cyber security standards for schools and colleges set out who does what. Under the first standard, the annual cyber risk assessment, the SLT digital lead is accountable and coordinates the work, IT support carries out the actions, and governors and trustees provide oversight and strategic risk management. Risks flagged by the assessment reach the governing body through the school's normal risk management process.

That division matters. Governors are not expected to configure firewalls or read logs. They are expected to:

  • make sure someone senior is clearly accountable for cyber security;
  • see that cyber risk is in the risk register and the business continuity plan;
  • challenge whether controls are working, using evidence rather than reassurance;
  • approve the policies the standards assign to them;
  • make sure the school can respond to and recover from an incident, and that they will be told when one happens.

In a multi-academy trust, these responsibilities sit with the trust board, often delegated to an audit and risk committee. Local governing bodies may still ask the same questions about their own school.

The eight questions and the evidence to expect

The NCSC groups the eight questions into three themes: information seeking, awareness and preparedness. The table below restates each question in summary and suggests the evidence a governing body can reasonably ask for. The evidence column is NHI Mgmt Group guidance, not part of the NCSC text.

ThemeQuestion (summary)Evidence to expect
Information seeking1. Is there a record of every organisation that supplies the school's IT?A supplier list with service, contract end date, contact and what data or systems each supplier can reach
Information seeking2. Does the school leader know who oversees IT, whether staff, network manager or outside provider?A named SLT digital lead and a named technical contact, with deputies
Information seeking3. Has the school identified its most critical digital systems and sought assurance about their security?A short list of critical systems, such as the management information system, finance, safeguarding records and email, with the assurance obtained for each
Information seeking4. Is there a sound backup and restoration plan, with restores practised regularly?The backup plan and the date and result of the most recent restore test
Awareness5. Do governance and IT policies reflect the importance of good cyber security?Current acceptable use policy, data protection policy and IT policy, with review dates and approval records
Awareness6. Are staff trained on common threats and incidents, such as phishing?Training completion figures for staff and governors in the last 12 months
Preparedness7. Could the school keep operating if it temporarily lost access to its data or internet connection?A business continuity plan covering loss of systems, with the date it was last exercised
Preparedness8. Does the school know who to contact if it suffers a cyber incident?A cyber response plan with internal and external contacts, including the insurer or RPA

Governor duties in the DfE standards

Most of the DfE standards are actioned by IT support and owned by the SLT digital lead, but several give governors and trustees a direct role. The points below summarise the DfE page as fetched in November 2026.

Risk assessment (standard 1)

The cyber risk assessment should be completed as soon as possible, repeated annually or after significant technology or process change or an incident, and revisited every term. Risks go into the risk register and into a tested business continuity plan. Governors provide oversight and strategic risk management. For RPA members, the DfE page states that a cyber response plan is a condition of cover.

Awareness and acceptable use (standard 2)

The headteacher or principal is accountable for the cyber awareness plan. Governors or trustees approve the acceptable use policy, and the DfE page states that training must include at least one current governor or trustee. Training should take place at least annually, and the page states that RPA members must evidence annual completion of the free NCSC training by relevant users.

Licensing and updates (standard 5)

The DfE page states that governors should check that digital technology is fully licensed as part of their normal compliance review. The same standard expects vulnerability fixes for operating systems, applications and firmware to be completed within 14 days of release, and DfE security instructions to be applied within 5 working days of notification. Governors can ask how often these targets are met.

Backups (standard 6)

Backups should be tested termly and the plan reviewed annually. The DfE page notes that backing up to the level described is currently a condition of RPA cover.

Reporting (standard 7)

The DfE page expects a potential incident or attack to be reported to the governing body or trustees. It also lists external reporting routes: the RPA or cyber insurer, Report Fraud, the DfE sector cyber team, the NCSC in serious cases, and Jisc for further education. Where a high-risk personal data breach has or may have occurred, the page notes that the Information Commissioner's Office must be informed within 72 hours.

Reading the answers: weak and strong responses

Governors often receive reassurance rather than evidence. The contrasts below help a governing body judge the quality of a report.

TopicWeak answerStrong answer
Backups"Our IT company does backups.""Backups are kept off site and offline. A full restore of the management information system was tested on a named date and took a stated number of hours."
Training"Staff were reminded about phishing.""A stated percentage of staff and two governors completed NCSC training this year; the remainder are booked for a named date."
Suppliers"We use a few providers.""Here is the supplier list, with which ones can access pupil data, and when each contract ends."
Accounts"Leavers are removed.""Accounts are disabled on the leaving date. The termly review found a stated number of stale accounts, now removed."
Incidents"Nothing has happened.""There were a stated number of reported phishing emails and one account compromise this term; here is what we changed."
Continuity"We would manage.""We exercised a loss of internet scenario on a named date; registers and safeguarding reporting continued on paper."

A strong answer is dated, measurable and tied to a named owner. If the school cannot produce evidence, the action is to ask for it by a set date, not to accept the reassurance.

Building cyber security into the governance cycle

Cyber security works best as a standing item rather than a one-off presentation. A simple cycle for a school or trust:

  • Every term: a short report from the SLT digital lead covering incidents, training completion, the result of the termly backup test, account reviews and any risks raised. The DfE standards already expect several of these checks termly.
  • Annually: a deeper review of the cyber risk assessment, the business continuity plan, the cyber response plan and the supplier list, alongside approval of the acceptable use policy.
  • After an incident or major change: a review of what happened, what was learned and whether the risk assessment needs updating.
  • When procuring: confirmation that new systems and suppliers were assessed for security and data protection before contracts were signed.

Larger trusts may use the NCSC Cyber Security Toolkit for Boards, which the NCSC governor questions page recommends for governing bodies of large schools or trusts. The Board Cyber Risk Reporting Guide covers how to shape a cyber report for a board.

Where identity and access fit

Many school incidents start with a stolen password or an account that should have been closed. Governors do not need technical detail, but they can ask:

  • Is multi-factor authentication switched on for staff email, the management information system and finance systems, and for anyone with administrator rights?
  • Are accounts disabled as soon as someone leaves, as the DfE standards expect, including supply staff, contractors and former governors?
  • Who has administrator access, and is it reviewed every term?
  • Do suppliers have standing remote access, and is it monitored?

Governors' own accounts matter too. Governors often handle confidential papers about staff, pupils and finances through school email or governance portals. Use school-provided accounts rather than personal email, protect them with multi-factor authentication, and remove access promptly when a governor's term ends.

When an incident happens

Governors should know their role before an incident, not during one. The DfE standards expect the governing body to be informed of a potential incident. A practical approach:

  • Agree in advance who on the governing body is contacted first, usually the chair and the chair of the relevant committee.
  • Let the response team lead the technical work. The governing body's role is to support decisions, approve emergency spending where needed, and oversee communication with parents, staff and the trust or local authority.
  • Make sure external reporting happens: insurer or RPA, Report Fraud, the DfE sector cyber team, and the Information Commissioner's Office where personal data is at risk.
  • Do not pay or promise a ransom without advice from the insurer or RPA and law enforcement.
  • After the incident, ask for a short lessons learned report and track the actions to completion.

The Briefing the Board During a Cyber Incident guide covers what a governing body should expect to hear during a live incident.

Decision guidance: single school, trust or federation

SettingWho leads oversightPractical focus
Single maintained schoolFull governing body or a resources committeeMake sure a named SLT digital lead exists and that the local authority or IT provider supplies evidence
Standalone academyTrust board, usually through audit and riskConfirm RPA or insurance conditions are met and that the IT supplier contract includes security and support terms
Multi-academy trustTrust board and audit and risk committee; local governing bodies for local assuranceConsistent standards across schools, a central supplier list, trust-wide incident plan and reporting by school
FederationFederated governing bodyShared systems and suppliers mean one weakness can affect every school in the federation

Common failure patterns

  • Cyber security reported once a year as a slide, with no termly evidence.
  • Reliance on an IT supplier's assurance without asking for restore test results or account reviews.
  • No governor or trustee taking part in cyber training, despite the DfE expectation that at least one does.
  • An acceptable use policy that has not been reviewed or approved for several years.
  • No supplier list, so nobody knows which providers hold pupil data.
  • A cyber response plan that names people who have left the school.
  • Governors using personal email accounts for confidential governance papers.
  • RPA or insurance conditions assumed to be met but never checked.

Practitioner checklist

  • Confirm a named SLT digital lead and a named technical contact, with deputies.
  • Put cyber security on the governing body or committee agenda every term.
  • Ask for evidence against each of the eight NCSC and DfE questions.
  • Confirm cyber risks are in the risk register and the business continuity plan.
  • Review and approve the acceptable use policy each year.
  • Make sure at least one current governor or trustee completes cyber training each year.
  • Ask for the date and result of the most recent backup restore test.
  • Check licensing as part of the normal compliance review.
  • Confirm RPA or insurance conditions for cyber cover are met.
  • Agree who on the governing body is contacted first in an incident.
  • Use school accounts with multi-factor authentication for governance papers, and remove access when terms end.

Standards and references

Related NHI Mgmt Group resources: Cybersecurity for Schools Guide · DfE Cyber Security Standards for Schools and Colleges Guide · Board Cyber Risk Reporting Guide · Board Cyber Security Training 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.