← Back to the blog School cybersecurity management

School network safety: assign decisions, manage suppliers and verify recovery

📅 30/10/2026⏱ 11 min🏷️ school network safety, IT suppliers, school leadership, recovery, continuity

Contracts can cover every service while leaving responsibilities unclear. Turn network safety into named decisions, evidence and workable continuity.

A maintenance contract does not tell you who decides during an incident

The parent portal fails before an important deadline. The internet provider says the connection works; the platform supplier says the server is available. Staff do not know who coordinates, or how to communicate if email is also unavailable. Every service may have a contract while the gaps between responsibilities remain the school’s problem.

This guide helps school leaders assign work and request meaningful evidence. It does not provide firewall settings or a network-testing plan. Leadership should know its dependencies, who implements, who approves and how readiness is verified without collecting passwords in one document.

Start with the school service, not the device

Ask what the school needs to operate safely: attendance, essential communication, appropriate information access and learning. Connect each service to its platform, accounts, devices, connectivity and supplier. One unavailable account can interrupt important work even when network hardware is functioning.

NCSC’s school leadership questions encourage discussion of risk and preparedness. DfE supplier resources emphasise ongoing review. These provide organisational context, not British requirements transplanted into Morocco.

A one-page service map

For each service, record name, purpose, internal owner, supplier, support route and dependencies. Use an appropriate management description, not a publicly circulated diagram with internal addresses and secrets. Authorised personnel retain technical detail securely.

A fictional entry might read: “Communication portal — family alerts — administrative coordinator — platform supplier — approved support — relies on internet and staff accounts.” Then identify an outage alternative, the information it needs and who may access it.

A responsibility table requiring named local owners

Decision or task

Who approves?

Who implements?

Evidence to request

Add a device or service

Leadership through the approved route

Authorised support and service owner

Request, review and handover

Grant or end access

The institution’s authorised approver

Account administrator

Task, duration and completion confirmation

Updates and maintenance

Named service owner

Support or supplier

Suitable report and justified exceptions

Backup and restoration

Owner of continuity needs

Contracted technical team

Test result and verified restored content

Incident management

Named lead and deputy

Authorised response team

Decision, communication and follow-up record

Family communication

Message approver

Identified spokesperson

Verified information and update time

Supplier transition

Leadership and contract authority

Coordinated authorised handover

Data return, access and transition plan

This is a proposed model, not a fixed legal allocation for every school. Put names and deputies in a restricted version, with contact methods not wholly dependent on a system that might fail. “The supplier is responsible” leaves a gap unless someone inside the school accepts and checks the outcome.

Different uses need qualified access review

Ask technical staff how they distinguish guest access, school devices and administrative services, and how access is limited to the task. Do not ask a teacher to change router settings during a meeting. Different wireless network names are not sufficient evidence of effective separation.

Request an explanation and appropriate test evidence without publishing sensitive details. Monitoring and filtering also require a purpose, permissions, someone handling alerts and protection of user information. An alert does not establish that anyone responds, and blocking a site alone does not resolve communication or behavioural risks.

Agree what “restored” means

Leadership and specialists identify which service returns first, tolerable work loss and acceptable downtime according to actual needs. “Daily backup” says little without knowing coverage, recovery ownership and what happens if the administrative account is unavailable.

Request a safe test report: what was restored, where, when, how it was checked and what remained incomplete. Do not require an operational shutdown as proof or create a public copy of pupil records. Continuity arrangements also need privacy safeguards.

A 30-minute supplier meeting with a written outcome

  • 5 minutes: one service and its operational requirement.

  • 10 minutes: responsibilities and gaps between parties.

  • 10 minutes: one piece of evidence for recovery, maintenance or access closure.

  • 5 minutes: 3 actions with owner, date and completion criterion.

The discussion may reveal that the connectivity provider does not manage access points or that the platform supplier does not back up laptop files. These are boundaries to document, not automatic accusations. Compare the contract with actual provision rather than assuming “full support” covers everything.

Slowness or failure is not automatically an attack

Capacity, settings, faults or security incidents can cause disruption. Staff describe observations, time and affected services, then refer appropriately. They should not publish an unverified diagnosis or recruit pupils to “test” the network.

The incident lead approves containment under the plan and specialist direction while the team records decisions. Child risk or possible information exposure activates the appropriate protection or legal-assessment route alongside technical work. Foreign notification deadlines and reporting bodies are not automatic Moroccan procedures.

An outage message template

“Service […] has been unavailable since […]. We are checking with the responsible specialists. The approved temporary process is […]. Please do not send information through unapproved channels or use support links from unfamiliar senders. Our next update is planned for [… realistic time] through […].”

Do not claim information is safe or exposed before verification, or include details that enable misuse. The spokesperson distinguishes established facts from matters under review. Clear communication can maintain trust even without a guaranteed repair time.

Continuity with privacy

Identify what needs an alternative during an outage, who uses it and how records return to the normal process afterwards. An alternative should not be an unrestricted file for every employee. Keep it limited, current and protected according to need and applicable rules.

Run a paper scenario: “Email is unavailable this morning.” Can the coordinator reach support another way? Do staff know whom to tell? Do not actually disable email or circulate family contact lists outside the institution to test readiness.

The first 30 days

  1. Map 3 essential services and their component owners.

  2. Name the decision owner and deputy for each.

  3. Review one access or contractual gap.

  4. Request suitable evidence of recovery or handover.

  5. Run a paper communication exercise and examine failures.

  6. Schedule follow-up on what changed and who accepted it.

A month does not make a school invulnerable. Progress can mean removing an unclear responsibility, establishing a known alternative or correcting unsuitable access. Review after service, staff or supplier changes, not only when buying equipment.

Frequently asked questions

Is a new firewall enough?

A tool needs appropriate configuration, management, monitoring and response. Purchasing does not allocate decisions.

Can pupils test the network as coursework?

A learning activity grants no permission. Use a dedicated environment with approved boundaries; the operational network is not an automatic exercise.

Should we collect supplier passwords to document responsibility?

No. Keep secrets out of management reports. Agree secure access, recovery and handover arrangements with authorised people.

Sources and editorial notes

Checked on 29 October 2026: NCSC: leadership questions and DfE: third-party suppliers. Table, meeting, template and monthly plan are original organisational proposals, not a technical audit or legal advice. At Cyber Sqool, school security becomes practical when each party knows its decision and evidence of completion.