The chain in this composite story runs six branches in three cities, teaches around two thousand students a year, and employs a mix of full-time teachers and hourly tutors who come in for a term and move on. Like most schools of its size, it kept everything on a shared drive that every branch could reach.
A newly hired academic manager opened that drive on her first morning and found two folders side by side. One held class registers, placement test results, attendance sheets, and scanned enrolment forms with passport numbers. The other held a scanned copy of a commercial coursebook, page by page, and a folder of audio files labelled by unit, and both were open to everyone, including the receptionist at a branch four hundred kilometres away.
Two Kinds of Record With Opposite Lifecycles
Student records and teaching materials look similar on a shared drive and behave nothing alike. Student files must be kept, sometimes for years, and access to them is restricted by data protection rules that most school administrators know in outline and few enjoy reading in full.
Teaching material is the reverse. A coursebook is licensed rather than owned, the licence usually covers classroom use by enrolled students, and it rarely extends to a scanned copy on a network drive. The material has a shelf life measured in editions, while the student record has one measured in years.
The two get mixed because they are produced by the same people in the same rooms. A teacher who writes a worksheet on Monday may photocopy a page on Tuesday and photograph the whiteboard on Wednesday, and all three land in a folder called resources. Nobody is being careless in a dramatic way; the filing simply has no categories, so everything becomes one category.
The Technology, in Ordinary Terms
The useful ideas here are modest. The first is classification, which means marking a file as belonging to a type with its own rules: student record, licensed material, internal lesson plan, marketing photograph. Once a file carries a type, a system can apply a policy without anyone remembering to.
The second is separate retention clocks. A placement test result might need to be held for a defined period after a student leaves, while a licensed audio file should be removed when the edition changes. Two clocks on one drive is a recipe for keeping both too long.
The third is access scoped to role and branch. A receptionist needs enrolment details for their own campus but not the academic director’s lesson observations, and certainly not a publisher’s audio masters. Data loss prevention, in plain terms, is the practice of watching for files of a given type leaving through channels they should not use.
A Composite Chain Tries One Library
In this composite account, the chain spends a term separating the two shelves. Student records move into a governed space with branch-level access and a retention rule. Licensed audio and scanned pages are replaced with properly purchased digital copies where the publisher offers them, and the rest is removed.
Many organizations explore unified office security platforms like Ping64 as one option to streamline sensitive file protection workflows. The measure the chain uses is deliberately unexciting: whether a new teacher can find the term’s materials without asking a colleague, and whether the branch administrator can answer a parent’s question about attendance without opening a folder of passport scans.
What Changes for the Team
Teachers feel the change as a shorter search. A shared drive with six years of accumulated folders rewards the people who remember where things were, and a labelled library rewards everyone else, which is most of the staff in any given September.
Administrators feel it as a narrower surface. When enrolment scans sit behind a branch-level rule, the question of who might have opened them stops being a monthly worry and becomes a report somebody can read.
There may also be an effect on how the chain buys materials. Once licensed content has a place of its own, the conversation with a publisher shifts from apology to procurement, which is a better conversation for both sides.
Where This Stops
No policy stops a teacher photographing a page with a phone in a classroom. The image leaves the building in a pocket, and the file never touches the system that was supposed to govern it.
The rules also cannot interpret a licence. Whether a school may print one chapter for a class of twelve is a legal question, not a technical one, and software that pretends otherwise creates false confidence. Judgement still sits with the academic manager, who has to read the agreement.
Closing Thoughts
The academic manager in that first story did not report anyone. She made a list of what was in the two folders, took it to the director, and asked a question that turned out to be the whole project: which of these things are we allowed to keep, and for how long.
A language school sells hours of instruction, but what it holds is a long paper trail of people learning. Keeping that trail tidy is not the interesting part of the work. It is the part that lets the interesting part continue.
References
https://csrc.nist.gov/pubs/sp/800/53/a/r5/final
https://attack.mitre.org/tactics/TA0009/
https://www.cisa.gov/stopransomware/ransomware-guide
https://www.enisa.europa.eu/publications/enisa-threat-landscape-2024
Top comments (0)