Skip to main content

School district WiFi procurement checklist: CIPA filtering, staff 802.1X and managed devices

Use this checklist to write one WiFi specification that every school in your district can meet. You can decide how staff and district-owned devices authenticate with 802.1X certificates, and how students, visitors and building devices are separated. You can also set filtering and compliance reporting that meet CIPA and E-Rate requirements.

By Iain JewittPublished
📖 14 min read3,147 words3 worked examples11 key definitions

School district WiFi procurement checklist: CIPA filtering, staff 802.1X and managed devices

Write one WiFi specification for every school in the district. Staff and district-owned devices authenticate with certificates over IEEE 802.1X. Students and visitors sit on separate networks. Filtering runs per school, network and age group, set to meet CIPA and E-Rate filtering standards. One console runs it all on each school's existing access points.

What does a district-wide WiFi specification actually do?

Most school districts grow by expansion. Each school arrives with its own access points, its own shared staff password and its own filtering contract. School district 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 district-owned device a verified identity on the network.
  • It keeps students, visitors and building devices apart from staff systems.
  • It applies filtering suited to both a six-year-old in 1st grade and a 17-year-old high school senior.
  • It lets one central team see and change all of it from one console.

What federal guidelines and CIPA standards ask of each school network

The Children's Internet Protection Act (CIPA) is federal regulation enforced by the FCC. It requires school boards and administrators to put appropriate filtering and monitoring in place and to review how well it works. Federal guidelines point schools to E-Rate filtering and compliance standards. It also gives the designated safeguarding officer lead responsibility for understanding those systems.

Federal standards set four expectations:

  • Assign roles for filtering and monitoring across senior leaders, a named board member, the safeguarding lead 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 safety and compliance 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 align with national safety lists and 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 district must meet this, which is the strongest argument for one specification.

What do you need before you write the district WiFi request for proposal (RFP)?

A portfolio 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, student 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 districts use Entra ID for staff and Google Workspace for Education for students. Tidy your groups so each school, role and grade level exists as a group. Network policy will follow those groups.

A safeguarding owner for every rule

Agree with your safety leaders 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 safety lead and the IT provider to work together.

Device enrollment records

District-owned devices must be enrolled in a mobile device management (MDM) platform before they can receive certificates. iPads bought through Apple School Manager can enroll automatically when first turned on. Find the devices bought outside those channels now, as they will need manual enrollment.

How do you set up staff 802.1X, student and visitor networks across every school?

Standardize the design, not the access points

You do not need one hardware vendor across the district. 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 district-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 district-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 enrolls district-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.

Departing staff show the value of certificates. Sync Purple with your directory so joiners, movers, and departing staff 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 district.

Keep students and visitors on their own networks

District-owned student iPads and Chromebooks can use the same certificate approach. Only the policy differs: their group places them on a student VLAN with student filtering. One secure SSID can carry staff and student devices, because identity decides where each one lands. This is the Identity-Based Networks model.

Visitors, board members, substitute teachers, 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, meeting relevant compliance and safety standards.

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, SIS, file shares, printers
Elementary student devices Shared iPads and Chromebooks, K to 5th Grade EAP-TLS certificate, student device group Elementary: strictest categories, safe search enforced Internet and classroom displays
Secondary student devices 1:1 or shared devices, 6th to 12th Grade EAP-TLS certificate, group by grade level Secondary: age-appropriate categories, safe search enforced Internet and learning platforms
High school seniors Grades 11 and 12 EAP-TLS certificate or trust account sign-in High school seniors: broader research access, illegal and harmful content blocked Internet only
Staff personal devices Staff cell phones and tablets Trust account sign-in Staff policy Internet only
Visitors Parents, board members, contractors, substitute 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.

Federal and state guidelines warn against overblocking. A high school senior researching drug policy, or a teacher planning a lesson on extremism, needs access a 3rd grade student does not. Give each student safety lead a route to request local exceptions, logged with a reason and an expiration date.

Close the bypass routes. Encrypted DNS in browsers and VPN apps are the usual ways around a filter, so specify that filtering detects and blocks them. Route any backup connection through the same filtering.

Make reports a student safety lead can read

Raw logs help nobody. Specify reports grouped by school, network and age group, showing device, time and search term. Flag safety categories such as self-harm, extremism and adult content. Purple Shield sends safety reports per school. Schedule them to each school's safety lead, with a trust summary for your district safety 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 school district 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 CIPA and federal filtering standards met on every network, guest and backup feeds included Content filtering certifications and appropriate filtering response documentation
Reporting Device, IP, individual where possible, time, search term, alerts on safety categories Sample safety 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, CCPA/CPRA, retention you control Certificates, data processing agreement, privacy impact assessment support
Support Support during school hours with named escalation Response times by severity, in writing
Rollout Phased plan by school around semester 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 board members 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.

  1. A staff laptop joins with no password prompt, lands on the staff VLAN and reaches the MIS.
  2. A student iPad lands on the student VLAN and cannot reach staff file shares.
  3. A visitor device reaches the internet and nothing internal.
  4. A building device on iPSK reaches only its named services.
  5. Disable a test staff account and confirm network access ends.
  6. Run the filtering compliance test from each network and age group.
  7. Try a VPN app and browser encrypted DNS, and confirm both are blocked.
  8. Fail over to the backup connection and repeat the filtering test.
  9. Check every test block appears in the safety report with the right school, device and time.

Keep the results. They become evidence for the annual review compliance standards require.

What goes wrong in school district WiFi rollouts, and how do you fix it?

Certificates expire mid-semester

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 enrollment before cutover, then enrolling the gaps.

Overblocking floods the helpdesk

Teachers lose a lesson resource and start routing around the filter. Publish the exception route, set a response target and review blocked educational sites each grading period.

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 student safety test. Name the designated safety officer as recipient in every school, and add report review to their quarterly 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 school district?

These two worked scenarios are illustrative. They describe typical public sector district estates, not named results.

Scenario 1: a 12-school district with four access point vendors

Situation. Eight elementary schools and four high schools 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 district 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 student devices, and Purple Shield applied elementary, high school 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 designated safeguarding lead.

Scenario 2: a high school with a senior class joining mid-year

Situation. The school ran PEAP-MSCHAPv2 with staff directory passwords. Filtering reports went to the IT technician as spreadsheets, and the designated safeguarding lead had never seen one.

What was done. The district 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 6th to 11th grade and the senior class, with a weekly safeguarding report.

Outcome. Staff passwords sent over WiFi from managed devices fell to zero. The designated safeguarding lead received 39 weekly reports across the school year, ready for the annual review.

What does district-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 enrollment. 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 district. Leavers lose access when their account or device is retired, not at the next password change. Designated safeguarding leads 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 district 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 standardize 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. Enroll 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 school district structure WiFi pricing in the tender?

Ask for a per-school price, broken down by network access, filtering and device management, plus a district-wide total. Schools join and leave districts, 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 cell 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 district 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 SIS and file shares without banning cell 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 enrollment 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 CCPA/CPRA 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

CIPA

The Children's Internet Protection Act (CIPA), enacted by Congress to address concerns about children's access to obscene or harmful content over the internet. It requires school districts to enforce an internet safety policy that includes technology protection measures (filtering) to qualify for E-Rate discounts.

CIPA is the legal driver behind your procurement. Every school in the district must meet it, which is the strongest argument for one district-wide specification.

CIPA filtering and monitoring standards

Federal Communications Commission (FCC) standards that set key expectations: internet safety policies, annual review, blocking harmful content without unreasonably affecting education, and monitoring digital communications of minors. The filtering standard covers guest accounts, all internet connections including backup feeds, and circumvention tools.

You meet these requirements when you write filtering, bypass blocking and reporting clauses. Ask every provider for evidence against them, including compliance validation.

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 RFP. 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, board members, contractors and substitute staff join through Purple Guest WiFi on an internet-only network that is still filtered under CIPA compliance standards.

Mobile device management (MDM)

A platform that enrolls district-owned devices and pushes configuration to them, including certificates and WiFi profiles. iPads bought through Apple School Manager can enroll 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 enrollment takes longer than network configuration.

CIPA and NCMEC filtering

The Children's Internet Protection Act (CIPA) requires schools to block harmful content. The National Center for Missing & Exploited Children (NCMEC) provides data to block child sexual abuse material.

Ask for CIPA compliance and NCMEC database integration as RFP evidence, and include restricted content in the district filtering baseline.

Worked Examples

A 12-school district of eight elementary schools and four high schools 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 standardize without replacing hardware?

The district 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 student devices, and identity placed each device on its VLAN. Purple Shield applied elementary, 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 compliance officer the same report format for the annual review.

A high school joins the district mid-year. It runs PEAP-MSCHAPv2 with staff directory passwords, and filtering reports go to the IT technician as spreadsheets the administrator has never seen. How do you migrate without disrupting teaching?

The district enrolled 140 staff laptops in Purple MDM and ran the old and new networks side by side for four weeks. Once each device joined with EAP-TLS, it switched PEAP-MSCHAPv2 off, removing the offline cracking risk. Purple Shield applied separate policies for grades 9 to 10 and grades 11 to 12, so older students kept broader research access. A weekly report went straight to the administrator. Staff passwords sent over WiFi from managed devices fell to zero, and the administrator received 39 weekly reports across the year, ready for the annual audit.

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?

CIPA standards expect 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 content filtering test from each network and age group. Then confirm each test block appears in the administration report with the right school, device and time. Keep the results as evidence for the annual compliance 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 standardize 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. Enroll 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 cell 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 cell 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 enrollment 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 CCPA/CPRA compliant, and your contract should set a retention period you control. Filtering logs about students 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.

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.