Cambridge: 01223 209920        London: 020 3519 0124        Ireland: +353 1697 2287        Sheffield: 0114 349 8054        Suffolk: 0144 059 2163         Email: Lucy@breathetechnology.com
How to Prepare a School for Cyber Accreditation

How to Prepare a School for Cyber Accreditation

A cyber accreditation assessment rarely fails because a school does not care about security. More often, good practice is happening in pockets: an IT manager has tightened Microsoft 365 settings, the business team keeps records, and staff receive occasional phishing reminders. The gap is proving that these measures work together. To prepare a school for cyber accreditation, turn those separate efforts into a clear, repeatable and evidenced security programme.

For many UK schools and trusts, Cyber Essentials is the logical starting point. It provides a recognised baseline for protecting devices, accounts and data, while Cyber Essentials Plus adds independent technical testing. The right route depends on your procurement requirements, risk profile and existing controls. Either way, preparation should improve day-to-day resilience, not become a last-minute paperwork exercise.

Start with the accreditation scope

Before changing a setting or collecting evidence, agree what the assessment covers. A single maintained school may have a relatively straightforward scope. A multi-academy trust may need to account for central teams, several sites, shared systems, cloud platforms and locally managed devices.

Document the legal entity, sites, staff groups, networks and systems in scope. Include laptops taken home, tablets used in classrooms, staff mobile phones where they access school email, servers, Wi-Fi, firewalls and cloud services. Do not overlook devices managed by a third party, such as print systems, catering terminals, CCTV platforms or classroom technology.

This exercise can expose uncomfortable grey areas. For example, a school may believe every device is managed, yet have an old laptop in a department cupboard or a former staff member’s personal tablet still linked to email. Accreditation assessors are looking for accurate answers, not perfection. Identifying an issue early gives you time to fix it properly.

Assign ownership beyond the IT office

Cyber security is a leadership responsibility, even where IT teams carry out the technical work. Name an executive owner, usually within the senior leadership team or trust leadership, who can remove obstacles and approve investment. The IT lead or managed service provider should own the technical plan. School business leaders, HR, safeguarding and data protection colleagues also have a role because security touches onboarding, leavers, procurement and incident response.

A short weekly check-in is often enough during preparation. Track decisions, outstanding risks, evidence required and completion dates. Clear accountability prevents the familiar problem of everyone assuming someone else has cancelled an old account or renewed a security licence.

Build an honest picture of your current controls

Do not begin with a policy template. Begin with what is actually in place. Create an asset register that records devices, operating systems, owners, locations and whether they are centrally managed. Review your administrator accounts, user accounts, network equipment, backup arrangements and key cloud applications.

Then compare reality against the controls required by the accreditation scheme. For Cyber Essentials, the core areas are boundary firewalls and internet gateways, secure configuration, access control, malware protection and security update management. They sound simple, but each area raises practical questions.

Can you identify every administrator account and explain why it has elevated access? Are staff prevented from installing unapproved software? Does multi-factor authentication protect email and cloud services, including administrator accounts? Are critical security updates applied within the required timeframe? Is endpoint protection active and reporting from every supported device?

Schools often have valid reasons for exceptions. A specialist curriculum application may require local administrator permissions, or a legacy device may support essential equipment. Treat these as managed risks, not invisible exceptions. Record why the exception exists, who approved it, how it is protected and when it will be reviewed. Isolation, restricted access and a replacement plan may be appropriate, but the answer depends on the device and its impact on teaching.

Prepare your school for cyber accreditation with evidence

Evidence is where a well-run environment can still lose momentum. An assessor cannot rely on verbal assurance that patching happens or leavers are removed promptly. They need evidence that demonstrates the control is configured and operating.

Gather screenshots, configuration exports, system reports, policies and process records as you work. Label each item clearly with the control it supports and the date it was captured. A shared evidence folder with restricted access makes review far easier than chasing screenshots across email inboxes a week before submission.

Useful evidence might show firewall configuration, device-management compliance, operating system versions, endpoint security status, multi-factor authentication policies and the latest account review. Keep sensitive details protected. A screenshot can show that a control exists without displaying passwords, pupil information or full network addresses.

Policies matter, but only when they match practice. Your acceptable use, password, mobile-device, backup and incident response policies should be current, approved and understandable to the people expected to follow them. A thirty-page document that nobody has read will not help a receptionist report a suspicious email or a teacher respond to a lost laptop.

Check the people processes

Technical settings do not remove the risk created by hurried onboarding or incomplete offboarding. Review how new starters receive accounts and equipment, how role changes are authorised, and how leavers lose access. This includes supply staff, contractors, governors and temporary staff who may have access to shared systems.

Phishing awareness deserves particular attention. Schools are attractive targets because busy staff handle payment requests, personal data and urgent parent communications. Training should be short, relevant and repeated, with an easy route for reporting suspicious messages. A culture where staff report rather than hide mistakes is far more useful than one built on blame.

Also test your incident response process. If a member of staff clicks a malicious link at 3.30pm on a Friday, who do they contact? Who can disable an account, assess affected devices and communicate with leadership? Your plan should include IT, senior leadership, data protection and safeguarding considerations. Practise the process with a short tabletop scenario rather than waiting for a real incident.

Fix the common technical blockers early

Unsupported operating systems, unpatched software and unmanaged devices are frequent accreditation obstacles. Start remediation early because some fixes require budget approval, procurement lead times or disruption to lessons. Replacing a device is not always the only option, but continuing to use unsupported software without compensating controls is rarely defensible.

Pay close attention to cloud identity. Microsoft 365 and Google Workspace can be well protected, but only if the configuration supports the way staff work. Multi-factor authentication, conditional access, secure administrator roles, external sharing controls and audit logging should be reviewed together. A rushed blanket restriction may prevent legitimate collaboration, while loose settings can expose sensitive files. Pilot significant changes with a representative group before rolling them out school-wide.

Backups are another area that deserves more than a tick-box answer. Confirm what is backed up, how often, where copies are held and who can restore them. More importantly, test a restore. A backup that has never been restored is an assumption, not a recovery plan. Protect backup accounts with strong access controls so an attacker cannot simply delete the copies they find.

Choose the right support and timeline

A school with a capable internal IT team may only need an independent gap assessment and extra hands to resolve the harder issues. A smaller school may benefit from a managed partner that can coordinate the asset review, technical remediation, evidence gathering and submission process. The key is to retain clear ownership within the school while drawing on specialist support where it removes risk or pressure.

Avoid setting an arbitrary deadline that forces shortcuts. Allow time for remediation, policy approval, staff communications and rechecking. For Cyber Essentials Plus, build in time for the independent tests and for resolving any findings. If a grant, tender or insurance requirement creates a fixed date, work backwards and prioritise issues that would prevent certification.

Accreditation should leave your school in a better position on the Monday after assessment, not merely with a certificate on the wall. When device ownership is clear, accounts are controlled, staff know how to raise concerns and leaders can see the remaining risks, technology becomes less of a source of stress and more dependable support for learning.


Download the Outsourced IT Support Checklist

Every Manager responsible for IT (Finance, Office Manager, Ops etc), that's not an IT Manager by profession should review their IT Support experience. How do you know if your expectations are realistic, is the team performing, are you at risk and didn't realise? Do you have doubts? Or are they simply great,

This Check Outsourced IT Support Checklist has been created, after performing hundreds of IT Audits over more than 20 years, revealing the most commonly found problems caused by IT Support Providers.

How does yours compare? Download for free today!

(PS. Your details remain confidential and will never be shared with anyone else)