Thirty schools, one managed network: CIPA-filtered, segmented and readable by a three-person IT team
A public school district in the Southeast, a leader in its segment.
- Scale
- 30 schools, ~22,000 students, ~3,000 staff, 10 Gb/s fiber to each school, 1:1 Chromebooks, Wi-Fi 6
- Engagement
- Design, a two-summer rollout and ongoing operation
The challenge
The district needed to meet the Children's Internet Protection Act (47 U.S.C. 254(h)) to keep its E-rate discounts, protect student records under FERPA, and give every classroom dependable Wi-Fi, with a small central IT team. Each school had grown its own network. Security cameras, door controllers, bells and thermostats sat on the same flat network as student laptops.
A school district has two audiences for its network: children, whom the law says it must protect, and a small IT team that has to run thirty buildings. This district had grown a network at each school. Cameras, door controllers, bells and thermostats shared a flat network with student laptops, filtering differed by building, and Wi-Fi quality depended on which summer a school was last upgraded. The Children's Internet Protection Act, 47 U.S.C. 254(h), ties E-rate discounts to filtering and monitoring, so the stakes were real.
The design is a routed network with two district hubs and 10 Gb/s fiber to every school. Each school gets the same set of VRFs and VLANs: students, staff, administration (student information, finance, payroll), building systems and guests, with a default-deny firewall between them. A compromised student device can reach the internet through the filter and nothing else. The student information system, which holds education records protected by FERPA (20 U.S.C. 1232g), sits in the administration segment, reachable only by staff with MFA. BGP to two providers and DDoS-aware edge filtering keep the district online when one provider or one school fails.
The statute asks for a technology protection measure that blocks obscene material, child sexual abuse material and material harmful to minors, and for schools it also asks for monitoring of minors' online activity. We built filtering with DNS and TLS SNI inspection at the district hubs and a management-console policy for school-owned Chromebooks, so the same rules follow the child home. The statute lets an authorized person turn the measure off for an adult's lawful research, so staff run a lighter policy. The district writes and adopts the Internet safety policy after public notice and hearing; we supply the technical description of what the controls do.
Identity does the rest. Managed laptops and staff devices use IEEE 802.1X with EAP-TLS and certificates pushed by device management. Printers, projectors and building systems that cannot do 802.1X use MAC authentication bypass and land in a restricted VLAN, and guests get an isolated, rate-limited portal. Wi-Fi 6 access points were placed from a measured survey with real classroom client counts, not from a brochure ratio. Switch configurations are templates, backed up automatically, and changed through a reviewed process.
The rollout took two summers, school by school, with a rollback ready for each night. Because every school is a copy of the same template, the three-person central team can see and fix all thirty from one dashboard, and a new school or a rebuilt wing is a configuration exercise. When a reviewer asks how filtering, monitoring and segmentation work, the answer is a diagram and a test report. Our zero trust article applies the same identity-first thinking to a mid-size organization.
What our team delivered
- A routed design with a pair of district hubs and 10 Gb/s fiber to each school, BGP to two internet providers and a DDoS-aware edge, so one school or one provider can fail without an outage
- Per-school VRFs and shared VLAN numbering: students, staff, administration (student information, finance, payroll), building systems and guests, each with a default-deny firewall policy between them
- Internet filtering on the district side so it follows the student: a technology protection measure that blocks obscene content, child sexual abuse material and material harmful to minors, built on DNS and TLS SNI filtering plus managed-device inspection, with a lighter policy for staff as the statute allows for adults
- The same filter on school-owned Chromebooks at home, through the device management console, so protection does not end at the front door
- IEEE 802.1X with EAP-TLS and device certificates for managed laptops and staff, MAC authentication bypass for printers and building systems that cannot do 802.1X, and a captive guest network that is isolated and rate limited
- Monitoring of minors' online activity as the statute requires for schools, with alerting rules reviewed by the district and written into its Internet safety policy; the public notice and hearing the law requires were the district's own, and we supplied the technical documentation
- A central log, one dashboard per school and automated configuration backups
Result
The district can show a reviewer how filtering, monitoring and segmentation work, every school runs on the same templates, a compromised student device cannot reach the student information system, and the three-person team manages all thirty buildings from one place.
Defense in depth, on a loop
Every device on your network sits behind a monitored firewall with two internet circuits, so attacks are stopped at the door and a provider outage does not stop the business.
Separate by region and by business unit
Each business unit lives in its own VRF and VLAN in every region, so a problem in retail cannot reach finance. Traffic between units has to pass a firewall that denies by default and allows only what is written down.
Every sign-in, verified
Staff sign in once, but behind the scenes the device, the identity, a phone approval and your access policy are all checked before any app opens, and strangers are turned away.
Roaming without dropping the call
Time from leaving one access point to the first data frame on the next, split by phase. A full WPA2/WPA3‑Enterprise re-authentication repeats the 802.1X exchange; 802.11r (Fast BSS Transition) reuses cached keys, 802.11k (neighbour reports) removes the blind scan, and 802.11v (BSS transition management) lets the network steer the client. Illustrative figures.
Facing something similar?
Tell us about your environment. We will tell you plainly what we would do and what it would take.