Your contract · Scoliom Cybersecurity

IT security for a private school: protecting student data

A school cannot close for three days waiting for a server to come back, and it answers to families for the data it holds on their children. Yet its IT has almost always grown layer upon layer, with no one keeping a map of it. Scoliom puts three simple questions back in order: who has access to what, what is genuinely being backed up, and what happens on the day something breaks.

  • Supervised backups — daily encrypted copies, kept off site and checked
  • Named accounts — one account per person, permissions by role, closed on the day someone leaves
  • Student data within a clear framework — hosting in the European Union, GDPR and local regulations
What an assessment brings to light

Three blind spots found in almost every school

A backup nobody has ever opened

A copy goes off somewhere: a disk left on a shelf, an online space paid for three years ago, an old server at the back of a cupboard. As long as nobody opens it, no one knows whether it still holds this year's report cards and accounts.

Access nobody keeps track of

One “management” account shared by four people, a contractor's access left open after a forgotten redesign, a teacher who left in June still looking up marks in October. With no register of accounts, the school no longer knows who can open a student's record.

An IT estate ageing unnoticed

Expired antivirus, systems past their vendor's support date, a front-office machine that doubles as the file server. One attachment opened on a Monday morning is enough for the whole school record system to be encrypted — and no document says what to do in the hour that follows.

What we put in place

Six areas of work maintained over time, rather than a call-out on the day it breaks

Supervised backups

Copies that are checked, not merely scheduled.

Daily encrypted backups kept off site, with a check that each run completed: a failure is reported the same day, not discovered six months later.

Getting back up and running

A written procedure instead of improvisation.

An overwritten file, a machine out of action or a server locked up: the steps to follow, the order of priorities and the people to call are written down in advance.

Accounts & permissions

One person, one account, one scope.

A register of accounts kept up to date, permissions aligned with the role actually held, and access closed on the day someone leaves — contractors included.

Workstations kept up to date

Known flaws closed in time.

Operating systems, browsers and business software tracked, antivirus supervised on every machine: patches are applied before the flaw starts circulating.

Protecting student data

A written framework for children's records.

The data entrusted to Scoliom solutions and the backups we manage stay within the scope of the contract: hosting in the European Union, encryption, and processing under the GDPR and the regulations that apply in the school's country.

Continuity plan

Who does what, and in what order.

A short procedure, known to the leadership team and the front office: what restarts first, what can wait, and how the school keeps welcoming students in the meantime.

How to activate it

Security built into the contract, never invoiced after the incident

Scoliom Cybersecurity is not an emergency call-out placed once everything has already stopped: the setup exists, we configure it for your school as part of the Scoliom IT management contract, and then we maintain it over time. Remote supervision of your IT estate by our managed service, backups and security are included from the Scoliom Sérénité plan onwards — “the connected school”. The amount is quoted on request, settled in writing after the remote assessment, and then stays fixed for the whole school year — never billed per student.

What your quote covers: day-to-day security — backups, accounts and permissions, patches, supervision of the IT estate — is included from Sérénité onwards, while the Essentiel school management foundation that comes before it falls under the same written quote. Heavier pieces of work — an in-depth audit, a formalised continuity plan, documented compliance work — are priced as projects. The scope is confirmed in writing after the remote assessment, and does not move during the school year.

Included in the foundation
  • Antivirus and patches tracked on every workstation
  • Encrypted backups, scheduled and monitored
  • A register of accounts, permissions and departures
  • Software firewall on the workstations
As an option, quoted on request
  • In-depth security audit of the IT estate
  • Hardening of sensitive workstations: encryption, two-factor authentication
  • A written continuity plan and a documented restoration procedure
  • Documented compliance work (GDPR and local regulations)
Frequently asked questions

Your questions about IT security at school

Let's get started

Start by finding out where your school really stands

A remote exchange to go through your backups, your accounts, your workstations and the data you hold on students. You come away with a written review, risks ranked by priority and a first budget estimate, with no commitment — see how the IT assessment for schools works.

Request an assessment

No commitment · Reply within 48 working hours