Case study ยท Education sector

Information security assessment for an independent K-12 school

A full review of cloud, on-premises hardware and software services, calibrated to a school's real risks, then turned into a 12-month roadmap for the board.

Facundo Montefalcone, security and technology advisor. Client name and individual findings are withheld.
~1,000Users, mostly students
~350Devices
18Systems and platforms
10Security domains
48Controls rated
12 moRoadmap horizon

How the engagement ran

  1. DiscoverReviewed the school's technical documentation with the IT team: users, devices, network, servers, systems and hosting.
  2. AssessRan a 48-question control questionnaire across 10 domains. Every answer got a red, yellow or green rating.
  3. CalibrateReviewed the IT team's corrective actions and re-rated findings against a scale written for a school.
  4. PlanWrote the diagnosis, the technical proposal and the action plan with owners, priorities and time frames.
  5. PresentTook the plan to the board with four decisions to approve.

Deliverables
Gap analysis register, corrective-action memo, diagnostic deck, technology plan report, board deck.

The environment assessed

People and devices
StudentsTeachers and staffStaff laptops and desktopsShared tabletsLab laptopsPersonal devices
Software services
Learning managementAcademic management and gradebookAdmissionsAdministration and billingFamily communicationHelp deskAlumniExtracurricular enrolmentCustom web applications
Cloud
Productivity suitesSelf-hosted cloud serversHosted websitesCloud backupCentral cloud database (planned)
On-premises
Directory and file servicesVirtualisationNAS backupManaged switchingManaged Wi-FiUPSServer room and racksCCTV
Network
Redundant internet linksSD-WAN firewallSegmented LANs and VLANsVPN for remote access

Result: 48 controls across 10 domains

Critical gapsPartial controlsEffective controls

First-pass ratings, before calibration. The school had a real security base, applied unevenly. Individual findings stay with the client; the table shows what each domain tested.

DomainWhat was tested
Network and perimeterInternet exposure of services, public address inventory, remote-management paths, rules between segments, admission of devices to wired and wireless networks.
Access and MFAMulti-factor authentication for staff and administrators, password policy, privileged access paths, offboarding.
EndpointsUser privileges, removable media, management of malware protection, mobile device management, disk encryption.
Patching and vulnerabilitiesPatch cadence, vulnerability scanning, updates of self-hosted applications, end-of-life components.
Data protectionEncryption at rest, external file sharing, classification and access tiers, review of custom applications, API authentication.
Backup and recoverySeparation of backups from redundancy, immutability, isolation of backup storage, restore testing, recovery objectives.
Incident responseResponse plan, exercises, central logging, log retention and alerting, breach-notification duties.
Physical securityServer room and rack access, monitoring of power protection, screen locking.
Third partiesVendor security review, data processing agreements, external provider access, parental consent for platforms.
Governance and awarenessAwareness training, phishing simulation, acceptable-use policy, data-protection compliance.

Calibrating risk to a school

Corporate benchmarks do not fit a school with non-technical users, mixed-ownership devices and a small IT team. I wrote a rating scale for the school, then re-rated each finding against the IT team's evidence.

Critical

Exposure of minors' data, uncontrolled remote access, or total loss of backups.

Accepted with conditions

Acceptable when documented and reviewed every year.

Controlled

Control in place and evidenced.

Proportionate by design
  • Strong authentication scoped by how sensitive a role's data is, not rolled out to everyone at once
  • Sharing restrictions tied to classification labels, not a global block that stops daily work
  • No central management of students' personal devices: operational and legal limits
  • Physical controls sized to the institution, with periodic access reviews
Govern before buying
  • Use the firewall, cloud admin console and directory policies the school already owns
  • Most priority actions fit inside existing licences
  • Lightweight evidence: a one-page incident checklist, an update register, a logged yearly restore test
  • Accepted risks written down and reviewed yearly with leadership

The 12-month roadmap

InitiativePriorityHorizonOwners
Security and data protection hardeningHigh0 to 3 monthsLeadership, IT, administration
Gradebook usability improvementsHigh0 to 3 monthsAcademic leadership, IT, vendor
Digital staff recordsMedium-high0 to 6 monthsHR, administration, IT
New admissions systemHigh3 to 6 monthsLeadership, admissions, administration, IT
Extracurricular enrolment automationMedium3 to 9 monthsAdministration, academic areas, IT
Unified central database in the cloudStrategic6 to 12 monthsLeadership, IT, administration, user areas
Prioritisation criteria
  • Cut critical security and data risk first
  • Remove high-impact friction for teachers and administration
  • Reuse infrastructure and tools already owned
  • Favour what integrates, scales and the team can sustain
What the board was asked to decide
  • Start of the security actions and the immediate usability fixes
  • Selection criteria for admissions: extend, buy or build
  • Design of the central data architecture
  • An internal owner per workstream and a preliminary budget for specialists

How it transfers to higher education

Scale differs, the method does not. The ten domains line up with what a US college or university answers to: FERPA for student records, and the GLBA Safeguards Rule for financial aid data.

Safeguards Rule elementWhere the assessment covers it
Written risk assessment48-control gap register with rated, calibrated risks
Access controls and multi-factor authenticationAccess and MFA domain
Encryption and data inventoryData protection domain, classification tiers
Monitoring and vulnerability assessmentPatching and vulnerabilities, logging in incident response
Security awareness trainingGovernance and awareness domain
Service provider oversightThird parties domain
Incident response planIncident response domain
Regular reporting to the boardBoard deck with decisions and owners
Client, staff and vendor names, addresses, system configurations and individual findings are withheld.