Govern · GV.OC
When ransomware or an outage hits, the first question is which systems come back first. A district that has already ranked its student information system (SIS), identity platform, payroll and transportation routing can restore in a sensible order instead of debating it while buses, lunch lines and attendance wait.
5 quick wins · 4 at no cost
Govern · GV.RM
A small technology team will always have more open issues than time. A written, scored risk register lets the superintendent and technology director agree on what gets fixed first, so untested backups or staff accounts without multi-factor authentication (MFA) are not pushed aside by the newest urgent ticket.
5 quick wins · 5 at no cost
Govern · GV.RR
In a small district, cybersecurity often rests on one person. If that person is out when an account is compromised, a written list of duties with named backups is what lets someone else disable accounts, call the insurer and reach vendors without guessing.
5 quick wins · 4 at no cost
Govern · GV.PO
Written, board-adopted policy lets the technology director require multi-factor authentication (MFA), restrict personal devices or remove an unapproved app without it becoming a personal argument with a principal or teacher. Enforcement points to the policy, not to IT.
5 quick wins · 4 at no cost
Govern · GV.OV
Security programs drift quietly: multi-factor authentication (MFA) exceptions pile up, a backup job fails without anyone noticing, and training lapses for new hires. Regular review of a few measures catches that drift before an incident, audit or insurance claim exposes it.
5 quick wins · 5 at no cost
Govern · GV.SC
Student information systems, learning platforms, transportation, nutrition and special education software keep district data on vendor servers. When one of those vendors is breached, families and reporters call the district, and the district carries the notification work and the loss of trust.
5 quick wins · 2 at no cost