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.How the engagement ran
- DiscoverReviewed the school's technical documentation with the IT team: users, devices, network, servers, systems and hosting.
- AssessRan a 48-question control questionnaire across 10 domains. Every answer got a red, yellow or green rating.
- CalibrateReviewed the IT team's corrective actions and re-rated findings against a scale written for a school.
- PlanWrote the diagnosis, the technical proposal and the action plan with owners, priorities and time frames.
- 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
Result: 48 controls across 10 domains
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.
| Domain | What was tested |
|---|---|
| Network and perimeter | Internet exposure of services, public address inventory, remote-management paths, rules between segments, admission of devices to wired and wireless networks. |
| Access and MFA | Multi-factor authentication for staff and administrators, password policy, privileged access paths, offboarding. |
| Endpoints | User privileges, removable media, management of malware protection, mobile device management, disk encryption. |
| Patching and vulnerabilities | Patch cadence, vulnerability scanning, updates of self-hosted applications, end-of-life components. |
| Data protection | Encryption at rest, external file sharing, classification and access tiers, review of custom applications, API authentication. |
| Backup and recovery | Separation of backups from redundancy, immutability, isolation of backup storage, restore testing, recovery objectives. |
| Incident response | Response plan, exercises, central logging, log retention and alerting, breach-notification duties. |
| Physical security | Server room and rack access, monitoring of power protection, screen locking. |
| Third parties | Vendor security review, data processing agreements, external provider access, parental consent for platforms. |
| Governance and awareness | Awareness 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.
- 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
- 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
| Initiative | Priority | Horizon | Owners |
|---|---|---|---|
| Security and data protection hardening | High | 0 to 3 months | Leadership, IT, administration |
| Gradebook usability improvements | High | 0 to 3 months | Academic leadership, IT, vendor |
| Digital staff records | Medium-high | 0 to 6 months | HR, administration, IT |
| New admissions system | High | 3 to 6 months | Leadership, admissions, administration, IT |
| Extracurricular enrolment automation | Medium | 3 to 9 months | Administration, academic areas, IT |
| Unified central database in the cloud | Strategic | 6 to 12 months | Leadership, IT, administration, user areas |
- 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
- 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 element | Where the assessment covers it |
|---|---|
| Written risk assessment | 48-control gap register with rated, calibrated risks |
| Access controls and multi-factor authentication | Access and MFA domain |
| Encryption and data inventory | Data protection domain, classification tiers |
| Monitoring and vulnerability assessment | Patching and vulnerabilities, logging in incident response |
| Security awareness training | Governance and awareness domain |
| Service provider oversight | Third parties domain |
| Incident response plan | Incident response domain |
| Regular reporting to the board | Board deck with decisions and owners |