- Purple
- Enterprise WiFi security and authentication: a complete guide
- Multi-academy trust WiFi procurement checklist: KCSIE filtering, staff 802.1X and managed devices
Multi-academy trust WiFi procurement checklist: KCSIE filtering, staff 802.1X and managed devices
Use this checklist to write one WiFi specification that every school in your trust can meet. You can decide how staff and trust-owned devices authenticate with 802.1X certificates, and how pupils, visitors and building devices are separated. You can also set filtering and DSL reporting that meet KCSIE and the DfE filtering and monitoring standards.
By Iain JewittPublished
📖 14 min read3,137 words3 worked examples11 key definitions
Part of our core series: Enterprise WiFi security and authentication: the complete guide →
- What does a trust-wide WiFi specification actually do?
- What KCSIE and the DfE standards ask of each school network
- What do you need before you write the MAT WiFi tender?
- An estate audit, school by school
- One identity source
- A safeguarding owner for every rule
- Device enrolment records
- How do you set up staff 802.1X, pupil and visitor networks across every school?
- Standardise the design, not the access points
- Authenticate staff and trust-owned devices with certificates
- Keep pupils and visitors on their own networks
- Set filtering per school, per network and per age group
- Make reports a DSL can read
- What should the MAT WiFi tender ask for on reporting, support and rollout?
- How do you check filtering and access work in every school?
- What goes wrong in trust WiFi rollouts, and how do you fix it?
- Certificates expire mid-term
- An older school cannot assign VLANs dynamically
- Devices sit outside the MDM
- Overblocking floods the helpdesk
- The backup connection bypasses filtering
- Reports nobody reads
- What does this look like in a real trust?
- Scenario 1: a 12-school trust with four access point vendors
- Scenario 2: a secondary with a sixth form joining mid-year
- What does trust-wide WiFi cost, and what do you get back?
- Frequently asked questions
- Can Purple run on the access points our schools already have?
- Does Purple Shield meet the DfE filtering and monitoring standards?
- Do we have to move off PEAP-MSCHAPv2 before we switch?
- How should a trust structure WiFi pricing in the tender?
- Can staff use their personal phones on the school network?
- Does visitor WiFi in a school need filtering?
- How long does a trust-wide rollout take?
- Where is filtering log data held, and how long is it kept?

Write one WiFi specification for every school in the trust. Staff and trust-owned devices authenticate with certificates over IEEE 802.1X. Pupils and visitors sit on separate networks. Filtering runs per school, network and age group, set to meet KCSIE and the DfE filtering and monitoring standards. One console runs it all on each school's existing access points.
What does a trust-wide WiFi specification actually do?
Most trusts grow by conversion. Each school arrives with its own access points, its own shared staff password and its own filtering contract. Multi-academy trust WiFi procurement is your chance to replace that patchwork with one standard every school meets.
A good specification does four things:
- It gives every member of staff and every trust-owned device a verified identity on the network.
- It keeps pupils, visitors and building devices apart from staff systems.
- It applies filtering suited to both a six-year-old in Year 2 and a 17-year-old in the sixth form.
- It lets one central team see and change all of it from one console.
What KCSIE and the DfE standards ask of each school network
Keeping Children Safe in Education (KCSIE) is statutory guidance from the Department for Education. It requires governing boards and proprietors to put appropriate filtering and monitoring in place and to review how well it works. Since the 2023 edition, KCSIE points schools to the DfE filtering and monitoring standards. It also gives the designated safeguarding lead (DSL) lead responsibility for understanding those systems.
The DfE standards set four expectations:
- Assign roles for filtering and monitoring across senior leaders, a named governor, the DSL and the IT service provider.
- Review filtering and monitoring provision at least once a year.
- Block harmful and inappropriate content without unreasonably affecting teaching and learning.
- Run monitoring strategies that meet the school's safeguarding needs.
The filtering standard is specific about the network itself. Filtering should apply to everyone, including guest accounts, school-owned devices and any device on the school's connection. It should cover every internet feed, backup connections included. It should block circumvention tools such as VPNs and proxies, and suit the age and ability of the people using it. The provider should belong to the Internet Watch Foundation (IWF) and use the Counter-Terrorism Internet Referral Unit (CTIRU) list. It should also block illegal content, including child sexual abuse material.
Reports matter as much as blocks. The standard expects records of the device name or ID, IP address and, where possible, the individual. It also expects the time and date, plus the search term or content blocked. Every school in your trust must meet this, which is the strongest argument for one specification.
What do you need before you write the MAT WiFi tender?
An estate audit, school by school
Record the following for each school:
- Access point vendor, model, firmware and controller, cloud or on-premises.
- Whether the access points support WPA2-Enterprise or WPA3-Enterprise and dynamic VLAN assignment.
- Whether the switches carry VLANs. A VLAN (virtual LAN) separates traffic into isolated groups on one physical network.
- Broadband and any 4G or 5G backup connection, and who filters each.
- Current network names (SSIDs) and how staff join them today.
- Device counts: staff laptops, iPads, Chromebooks, pupil devices, interactive displays and printers.
- The current filtering provider, contract end date and report format.
One identity source
Decide which directory defines who counts as staff: Microsoft Entra ID, Google Workspace or Okta. Many trusts use Entra ID for staff and Google Workspace for Education for pupils. Tidy your groups so each school, role and year group exists as a group. Network policy will follow those groups.
A safeguarding owner for every rule
Agree with your DSLs which content categories each age group can reach. Agree who approves an exception and how quickly. Write that sign-off route into the specification, because the standards expect the DSL and the IT provider to work together.
Device enrolment records
Trust-owned devices must be enrolled in a mobile device management (MDM) platform before they can receive certificates. iPads bought through Apple School Manager can enrol automatically when first switched on. Find the devices bought outside those channels now, as they will need manual enrolment.
How do you set up staff 802.1X, pupil and visitor networks across every school?
Standardise the design, not the access points
You do not need one hardware vendor across the trust. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Replace hardware on its normal lifecycle, not because a new school joined. Why your next WiFi upgrade doesn't need new hardware sets out the reasoning.
Write the same SSIDs, VLAN roles and policies into every school. A trust-wide school network should look identical from a staff laptop in any building. A teacher covering at another site then connects without a call to IT.
Authenticate staff and trust-owned devices with certificates
IEEE 802.1X is the standard for network access control: a device proves who it is before it joins. A RADIUS server checks that proof and tells the access point which network the device belongs on.
Specify EAP-TLS, the 802.1X method that uses a certificate instead of a password. Purple MDM enrols trust-owned laptops, iPads and Chromebooks, then installs the certificate and WiFi profile. Staff never type a password, and no shared key exists to leak. Purple Access checks the certificate and places each device on the right VLAN by its group.
Many schools still run PEAP-MSCHAPv2, which sends a username and password inside an encrypted tunnel. It persists because it is easy, but captured exchanges can be cracked offline. PEAP-MSCHAPv2: Why It Is Still Common, Why It Is Risky, and How to Move On covers the risk and the migration route.
Leavers show the value of certificates. Sync Purple with your directory so joiners, movers and leavers are handled once, for every school. For user certificates, disabling the account removes access. For device certificates, retiring the device and revoking its certificate stops it joining anywhere in the trust.
Keep pupils and visitors on their own networks
Trust-owned pupil iPads and Chromebooks can use the same certificate approach. Only the policy differs: their group places them on a pupil VLAN with pupil filtering. One secure SSID can carry staff and pupil devices, because identity decides where each one lands. This is the Identity-Based Networks model.
Visitors, governors, supply staff and contractors join a separate network through a captive portal, the sign-in page shown before access is granted. Purple Guest WiFi handles that sign-in. The visitor network reaches the internet only, and it is filtered, because the DfE standard covers guest accounts.
Interactive displays, printers and door controllers often cannot do 802.1X. Put them on iPSK (identity pre-shared key), which gives each device group its own key and VLAN. One leaked key then opens one small segment, not the network.
| Network | Who joins | How they authenticate | Filtering policy | What they can reach |
|---|---|---|---|---|
| Staff managed devices | Teachers, support staff, central team | EAP-TLS certificate via Purple MDM | Staff: illegal content and bypass tools blocked, wide research access | Internet, MIS, file shares, printers |
| Primary pupil devices | Shared iPads and Chromebooks, Reception to Year 6 | EAP-TLS certificate, pupil device group | Primary: strictest categories, safe search enforced | Internet and classroom displays |
| Secondary pupil devices | 1:1 or shared devices, Years 7 to 11 | EAP-TLS certificate, group by key stage | Secondary: age-appropriate categories, safe search enforced | Internet and learning platforms |
| Sixth form devices | Years 12 and 13 | EAP-TLS certificate or trust account sign-in | Sixth form: broader research access, illegal and harmful content blocked | Internet only |
| Staff personal devices | Staff phones and tablets | Trust account sign-in | Staff policy | Internet only |
| Visitors | Parents, governors, contractors, supply staff | Captive portal | Visitor: illegal, adult and bypass content blocked | Internet only |
| Building devices | Displays, printers, door controllers | iPSK per device group | Restricted to required services | Named internal services only |
Set filtering per school, per network and per age group
Purple Shield applies filtering per school, per network and per age group. Set a trust baseline once: illegal content, CTIRU-listed terrorist content and circumvention tools. Then add age policies on top.
The DfE standard warns against overblocking. A sixth former researching drug policy, or a teacher planning a lesson on extremism, needs access a Year 3 pupil does not. Give each DSL a route to request local exceptions, logged with a reason and an expiry date.
Close the bypass routes. Encrypted DNS in browsers and VPN apps are the usual ways round a filter, so specify that filtering detects and blocks them. Route any backup connection through the same filtering.
Make reports a DSL can read
Raw logs help nobody. Specify reports grouped by school, network and age group, showing device, time and search term. Flag safeguarding categories such as self-harm, extremism and adult content. Purple Shield sends safeguarding reports per school. Schedule them to each school's DSL, with a trust summary for your trust safeguarding lead.
Got questions about your specific setup?
Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.
What should the MAT WiFi tender ask for on reporting, support and rollout?
A tender that asks for "a filtered network" gets one quote per vendor that cannot be compared. Ask for specific capabilities and the evidence behind each.
| Requirement | What to write into the specification | Evidence to ask for |
|---|---|---|
| Hardware | Runs on every access point vendor in your audit | Supported vendor list matched to your estate |
| Staff authentication | IEEE 802.1X with EAP-TLS, no shared staff passwords | Certificate issue, renewal and revocation process |
| Identity | Sync with Microsoft Entra ID or Google Workspace for joiners, movers and leavers | Live demonstration of a leaver losing access |
| Filtering compliance | DfE filtering standard met on every network, guest and backup feeds included | IWF membership, CTIRU list use, UK Safer Internet Centre appropriate filtering response |
| Reporting | Device, IP, individual where possible, time, search term, alerts on safeguarding categories | Sample DSL report from a live school |
| Management | One console across all schools, with delegated access per school | Demonstration of role-based access |
| Security and data | ISO 27001, UK GDPR, retention you control | Certificates, data processing agreement, DPIA support |
| Support | Support during school hours with named escalation | Response times by severity, in writing |
| Rollout | Phased plan by school around term dates | Pilot plan, cutover checklist, rollback plan |
Ask too how the provider will support your annual review. The output you want is a report pack your governors can sign off.
How do you check filtering and access work in every school?
Run the same acceptance test in each school before you sign it off. Write the test into the contract so the supplier runs it with you.
- A staff laptop joins with no password prompt, lands on the staff VLAN and reaches the MIS.
- A pupil iPad lands on the pupil VLAN and cannot reach staff file shares.
- A visitor device reaches the internet and nothing internal.
- A building device on iPSK reaches only its named services.
- Disable a test staff account and confirm network access ends.
- Run the SWGfL filtering test, published with the UK Safer Internet Centre, from each network and age group.
- Try a VPN app and browser encrypted DNS, and confirm both are blocked.
- Fail over to the backup connection and repeat the filtering test.
- Check every test block appears in the DSL report with the right school, device and time.
Keep the results. They become evidence for the annual review the DfE standards require.
What goes wrong in trust WiFi rollouts, and how do you fix it?
Certificates expire mid-term
Staff arrive on a Monday and nothing connects. Fix it by setting automatic renewal well before expiry, and by alerting on certificates due within 30 days.
An older school cannot assign VLANs dynamically
Some older controllers or firmware do not support dynamic VLAN assignment. Update the firmware first. If that fails, run a separate SSID per role at that school until the hardware reaches end of life.
Devices sit outside the MDM
Staff laptops bought locally before conversion never get a certificate. Fix it by reconciling your device register against MDM enrolment before cutover, then enrolling the gaps.
Overblocking floods the helpdesk
Teachers lose a lesson resource and start routing round the filter. Publish the exception route, set a response target and review blocked educational sites each half-term.
The backup connection bypasses filtering
A 4G failover router plugged in years ago often has no filtering. Include every connection in your audit and filter each one.
Reports nobody reads
A report sent to IT alone fails the safeguarding test. Name the DSL as recipient in every school, and add report review to their termly checklist. Securing a business network: A practical guide for 2026 covers the wider segmentation principles behind these fixes.
What does this look like in a real trust?
These two worked scenarios are illustrative. They describe typical trust estates in the public sector, not named results.
Scenario 1: a 12-school trust with four access point vendors
Situation. Eight primaries and four secondaries ran Cisco Meraki, HPE Aruba, Ubiquiti UniFi and Ruckus. Each school had a shared staff password, and three filtering providers sent reports in three formats.
What was done. The trust wrote one specification with three SSIDs: secure, visitor and building devices. Purple ran as a cloud overlay on all four vendors. Purple MDM issued certificates to staff and pupil devices, and Purple Shield applied primary, secondary and staff policies.
Outcome. Shared staff passwords fell from 12 to zero. Management consoles fell from four to one. Filtering providers fell from three to one, with one report format for every DSL.
Scenario 2: a secondary with a sixth form joining mid-year
Situation. The school ran PEAP-MSCHAPv2 with staff directory passwords. Filtering reports went to the IT technician as spreadsheets, and the DSL had never seen one.
What was done. The trust enrolled 140 staff laptops in Purple MDM and ran both networks side by side for one half-term. It then switched PEAP-MSCHAPv2 off. Purple Shield applied separate policies for Years 7 to 11 and the sixth form, with a weekly DSL report.
Outcome. Staff passwords sent over WiFi from managed devices fell to zero. The DSL received 39 weekly reports across the school year, ready for the annual review.
What does trust-wide WiFi cost, and what do you get back?
Your costs fall into three groups. There is a subscription per school for network access, filtering and device management. There is internal time for the audit, the pilot and device enrolment. And there are access point replacements, limited to hardware that has genuinely reached end of life.
| Approach | New hardware | Consoles to run | Staff authentication | Filtering and reports | Disruption to schools |
|---|---|---|---|---|---|
| Keep per-school arrangements | None | One per school | Shared passwords or PEAP-MSCHAPv2 in most schools | Different provider and format per school | Repeated at every contract renewal |
| Replace every school with one access point vendor | New access points in every school on another vendor | One | 802.1X if specified | Separate filtering contract still needed | Physical installation in every school |
| Purple cloud overlay on existing access points | End-of-life replacements only | One | EAP-TLS certificates via Purple MDM | Purple Shield, one policy set and one report format | Configuration changes scheduled around term dates |
What you get back is one place to evidence compliance across the trust. Leavers lose access when their account or device is retired, not at the next password change. DSLs read one report format, wherever they work.
Purple has run since 2012 across 80,000+ live venues in over 90 countries, at 99.999% uptime. We are ISO 27001, Cyber Essentials, GDPR and B Corp certified. Our education work includes University of Sheffield, University of Leeds, University of the Arts London, Eastern Michigan University and VCCS.
Frequently asked questions
Can Purple run on the access points our schools already have?
Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. A trust with a different vendor in each school can still run one design and one console. Check each school's model and firmware in your audit. Replace hardware only when it reaches end of life, not to standardise the estate.
Does Purple Shield meet the DfE filtering and monitoring standards?
Purple Shield gives you the network filtering and safeguarding reports the standards describe, with policy per school, network and age group. Compliance itself sits with your governing board, which must assign roles and review provision every year. Ask every filtering provider in your tender for its IWF membership, CTIRU list use and UK Safer Internet Centre appropriate filtering response. File those with your annual review.
Do we have to move off PEAP-MSCHAPv2 before we switch?
No. You can run your existing PEAP-MSCHAPv2 network alongside the new certificate-based network while devices migrate. Enrol devices in Purple MDM school by school, confirm each joins with EAP-TLS, then switch PEAP off. Set a firm end date in the plan. PEAP-MSCHAPv2 exchanges can be captured and cracked offline, so leaving it running keeps the risk you are paying to remove.
How should a trust structure WiFi pricing in the tender?
Ask for a per-school price, broken down by network access, filtering and device management, plus a trust-wide total. Schools join and leave trusts, so the contract should add or remove a school at the same unit price. Require hardware costs to be listed separately. Tie each item to an end-of-life access point from your audit, so nothing is replaced without reason.
Can staff use their personal phones on the school network?
Yes, if your specification allows it, but not on the managed-device network. Put staff personal devices on a separate staff network where they sign in with their trust account. There they receive staff filtering and reach the internet only. Managed laptops and iPads keep their certificates and their access to internal systems. That separation protects your MIS and file shares without banning phones.
Does visitor WiFi in a school need filtering?
Yes. The DfE filtering standard applies to guest accounts and to any device using the school's connection. Parents, governors, contractors and supply staff are therefore filtered too. Give visitors their own network through a captive portal, with internet-only access and a visitor filtering policy. Blocked attempts on that network should appear in the same DSL report as every other network in the school.
How long does a trust-wide rollout take?
Plan it in waves around the school calendar, not as one cutover. Pilot one primary and one secondary for a half-term, and fix what the pilot finds. Then move the remaining schools in groups, saving larger changes for holidays. Device enrolment takes longer than network configuration, so your MDM audit is the best predictor of your timeline.
Where is filtering log data held, and how long is it kept?
Purple is ISO 27001 certified and GDPR compliant, and your contract should set a retention period you control. Filtering logs about pupils are personal data, so record them in your DPIA. Agree retention with your data protection officer, long enough to support safeguarding concerns and the annual review. Ask every provider in the tender to state where logs are stored.
Key Definitions
KCSIE
Keeping Children Safe in Education, statutory guidance from the Department for Education. It requires governing boards and proprietors to put appropriate filtering and monitoring in place and review it. Since the 2023 edition it points schools to the DfE filtering and monitoring standards and gives the DSL lead responsibility for understanding those systems.
KCSIE is the legal driver behind your tender. Every school in the trust must meet it, which is the strongest argument for one trust-wide specification.
DfE filtering and monitoring standards
Department for Education standards that set four expectations: assigned roles, at least an annual review, blocking harmful content without unreasonably affecting teaching, and monitoring that meets safeguarding needs. The filtering standard covers guest accounts, all internet feeds including backup, circumvention tools, IWF membership and the CTIRU list.
You meet these requirements when you write filtering, bypass blocking and reporting clauses. Ask every provider for evidence against them, including a UK Safer Internet Centre appropriate filtering response.
IEEE 802.1X
The IEEE standard for port-based network access control. It carries the Extensible Authentication Protocol (EAP, RFC 3748) between the device, the access point and an authentication server, so a device proves its identity before it joins the network.
Specifying 802.1X removes shared staff passwords across every school and lets identity decide which VLAN each device lands on.
EAP-TLS
The EAP method defined in RFC 5216 that authenticates with mutual TLS certificates rather than passwords. The device presents a certificate and the server validates it, so no reusable secret crosses the air.
This is the staff authentication method to write into the tender. Purple MDM installs the certificate and WiFi profile, so staff never type a password.
PEAP-MSCHAPv2
An 802.1X method that sends a username and password, checked with MSCHAPv2, inside an encrypted TLS tunnel. Captured exchanges can be cracked offline.
Many schools still run it because it is easy. Run it alongside EAP-TLS while devices migrate, then switch it off on a fixed date.
RADIUS
Remote Authentication Dial-In User Service, defined in RFC 2865. The server checks the credential an access point forwards and returns an accept or reject decision, with attributes that tell the access point how to treat the device.
Purple Access performs this role, checking each certificate and placing each device on the right VLAN by its directory group.
Dynamic VLAN assignment
A VLAN separates traffic into isolated groups on one physical network. With 802.1X, RFC 3580 describes how RADIUS tunnel attributes tell the access point which VLAN to assign each authenticated device.
Your audit must confirm each school's access points and switches support it. Where older firmware cannot, run a separate SSID per role until end of life.
iPSK
Identity pre-shared key: each device group gets its own key and VLAN on the same SSID, rather than one shared WPA2 passphrase for everything.
Use it for interactive displays, printers and door controllers that cannot do 802.1X. A leaked key then opens one small segment, not the network.
Captive portal
The sign-in page shown to a device before network access is granted, used here to register visitors on a separate network.
Parents, governors, contractors and supply staff join through Purple Guest WiFi on an internet-only network that is still filtered under the DfE standard.
Mobile device management (MDM)
A platform that enrols trust-owned devices and pushes configuration to them, including certificates and WiFi profiles. iPads bought through Apple School Manager can enrol automatically when first switched on.
Devices must be enrolled before they can receive certificates. Your MDM audit is the best predictor of rollout timeline, as enrolment takes longer than network configuration.
IWF and CTIRU list
The Internet Watch Foundation (IWF) supplies data to block child sexual abuse material. The Counter-Terrorism Internet Referral Unit (CTIRU) list identifies terrorist content. The DfE filtering standard expects providers to be IWF members and use the CTIRU list.
Ask for IWF membership and CTIRU list use as tender evidence, and include CTIRU-listed content in the trust filtering baseline.
Worked Examples
A 12-school trust of eight primaries and four secondaries runs Cisco Meraki, HPE Aruba, Ubiquiti UniFi and Ruckus. Each school has a shared staff password, and three filtering providers send reports in three formats. How do you standardise without replacing hardware?
The trust wrote one specification with three SSIDs: secure, visitor and building devices. Purple ran as a cloud overlay on all four vendors, so no school needed new access points to join the standard. Purple MDM issued certificates to staff and pupil devices, and identity placed each device on its VLAN. Purple Shield applied primary, secondary and staff policies from one console. Shared staff passwords fell from 12 to zero. Management consoles fell from four to one. Filtering providers fell from three to one, giving every DSL the same report format for the annual review.
A secondary school with a sixth form joins the trust mid-year. It runs PEAP-MSCHAPv2 with staff directory passwords, and filtering reports go to the IT technician as spreadsheets the DSL has never seen. How do you migrate without disrupting teaching?
The trust enrolled 140 staff laptops in Purple MDM and ran the old and new networks side by side for one half-term. Once each device joined with EAP-TLS, it switched PEAP-MSCHAPv2 off, removing the offline cracking risk. Purple Shield applied separate policies for Years 7 to 11 and the sixth form, so sixth formers kept broader research access. A weekly report went straight to the DSL. Staff passwords sent over WiFi from managed devices fell to zero, and the DSL received 39 weekly reports across the year, ready for the annual review.
During the audit, an older school turns out to have a 4G failover router plugged in years ago with no filtering on it. What should the specification require?
The DfE filtering standard expects filtering on every internet feed, backup connections included. Record every connection and who filters it during the audit, then route the backup through the same filtering as the primary line. Write it into the acceptance test: fail over to the backup connection and repeat the SWGfL filtering test from each network and age group. Then confirm each test block appears in the DSL report with the right school, device and time. Keep the results as evidence for the annual review.
Frequently asked questions
Can Purple run on the access points our schools already have?
Yes. Purple is hardware-agnostic and runs as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. A trust with a different vendor in each school can still run one design and one console. Check each school's model and firmware in your audit. Replace hardware only when it reaches end of life, not to standardise the estate.
Does Purple Shield meet the DfE filtering and monitoring standards?
Purple Shield gives you the network filtering and safeguarding reports the standards describe, with policy per school, network and age group. Compliance itself sits with your governing board, which must assign roles and review provision every year. Ask every filtering provider in your tender for its IWF membership, CTIRU list use and UK Safer Internet Centre appropriate filtering response. File those with your annual review.
Do we have to move off PEAP-MSCHAPv2 before we switch?
No. You can run your existing PEAP-MSCHAPv2 network alongside the new certificate-based network while devices migrate. Enrol devices in Purple MDM school by school, confirm each joins with EAP-TLS, then switch PEAP off. Set a firm end date in the plan. PEAP-MSCHAPv2 exchanges can be captured and cracked offline, so leaving it running keeps the risk you are paying to remove.
How should a trust structure WiFi pricing in the tender?
Ask for a per-school price, broken down by network access, filtering and device management, plus a trust-wide total. Schools join and leave trusts, so the contract should add or remove a school at the same unit price. Require hardware costs to be listed separately. Tie each item to an end-of-life access point from your audit, so nothing is replaced without reason.
Can staff use their personal phones on the school network?
Yes, if your specification allows it, but not on the managed-device network. Put staff personal devices on a separate staff network where they sign in with their trust account. There they receive staff filtering and reach the internet only. Managed laptops and iPads keep their certificates and their access to internal systems. That separation protects your MIS and file shares without banning phones.
Does visitor WiFi in a school need filtering?
Yes. The DfE filtering standard applies to guest accounts and to any device using the school's connection. Parents, governors, contractors and supply staff are therefore filtered too. Give visitors their own network through a captive portal, with internet-only access and a visitor filtering policy. Blocked attempts on that network should appear in the same DSL report as every other network in the school.
How long does a trust-wide rollout take?
Plan it in waves around the school calendar, not as one cutover. Pilot one primary and one secondary for a half-term, and fix what the pilot finds. Then move the remaining schools in groups, saving larger changes for holidays. Device enrolment takes longer than network configuration, so your MDM audit is the best predictor of your timeline.
Where is filtering log data held, and how long is it kept?
Purple is ISO 27001 certified and GDPR compliant, and your contract should set a retention period you control. Filtering logs about pupils are personal data, so record them in your DPIA. Agree retention with your data protection officer, long enough to support safeguarding concerns and the annual review. Ask every provider in the tender to state where logs are stored.
Sources
- Keeping children safe in education (DfE statutory guidance)
- DfE: Meeting digital and technology standards in schools and colleges
- IETF RFC 3748: Extensible Authentication Protocol (EAP)
- IETF RFC 5216: The EAP-TLS Authentication Protocol
- IETF RFC 2865: Remote Authentication Dial In User Service (RADIUS)
- IETF RFC 3580: IEEE 802.1X RADIUS Usage Guidelines
- UK Safer Internet Centre
- Internet Watch Foundation
Continue reading in this series
Council WiFi procurement checklist: public WiFi, staff 802.1X and filtering across council buildings
Use this checklist to write a council WiFi tender that you can score: four separated networks, staff access tied to your identity provider, certificates on council-owned devices, filtering on every public site and plain-English ward reports. You will also know which evidence to request from bidders and which eight tests to run before go-live.
GP surgery WiFi providers checklist: patient access, clinical networks and DSPT evidence
Use this checklist to choose a GP surgery WiFi provider that keeps patient WiFi away from clinical systems, gives every salaried GP, locum and visiting clinician an individual, revocable credential, and runs on your existing access points. You will also know which six tests to run and which records to keep for your annual DSPT submission.
Further education college WiFi procurement: student BYOD, staff 802.1X and KCSIE filtering
You will be able to specify how learners, staff and college-owned devices authenticate in an FE college WiFi tender, and how filtering meets the DfE filtering and monitoring standards. The guide sets out per-learner iPSK, staff EAP-TLS, visitor captive portals, age-based filtering profiles and the bid evidence to request, so you can score tenders on safeguarding and five-year cost.
Got questions about your specific setup?
Our team works with venue operators, IT managers, and network engineers across 80,000 venues. Book a 20-minute call and we will show you how others like you solved it.