StudentPrivacy.college
The Privacy Ledger - protect and govern student data

Encryption for Records at Rest and in Transit

Encryption for Records at Rest and in Transit: what it means for a student record system, who may use it, and the check to make before it moves.

Privacy check
Record
student record system in security controls for student data
Data
Encryption for Records at Rest and in Transit
Safeguard
least-privilege access, encryption and access logging
First check
Limit the sharing to the minimum the purpose requires.

The short answer

The direct answer to encryption for records at rest and in transit is less about memorising a statute and more about a repeatable check before information moves: confirm what the student record platform is, confirm the objective, confirm the authority, confirm that the receiver needs it, and confirm the safeguard. Five confirmations, done in writing where the stakes are high, prevent most of the errors this ledger exists to describe.

Language access for confidentiality notifications is a confidentiality control, since a notice a student can not read can not inform consent or an opt-out.

Students retain rights over their records even when they never exercise them, and an university's duty does not depend on a student asking about it.

The safest test for any proposed disclosing is to write it down in one sentence naming the file, the recipient, the purpose and the authority, and then to read that sentence back critically.

International students face additional exposure when files travel across borders, and that exposure ought to shape storage and disclosing decisions.

What this covers

Directory information is a defined subset that a college might designate and publish, and the designation must be published before it is relied on.

Event and attendance platforms hold location information about students, and that information can reveal patterns that deserve protection.

Name, enrolment status and field of study are commonly designated, while grades, disciplinary outcomes and financial facts are not directory information.

Public records requests may reach student information, and staff handling them need to know which records are safeguarded before responding.

Accrediting bodies receive data under a specific exception, and the scope of that exception ought to bound what is actually sent.

A note kept only for its author's personal use, never disclosed, sits outside the category, and the moment it is disclosed that protection may fall away.

How to work through it

State the purpose in a sentence a student could understand, and if the sentence cannot be documented plainly, the purpose is probably too broad.

Run internal audits on a specified cycle, and track findings to closure with owners and dates.

Document emergency disclosures at the time, with the facts that made the emergency real, because later reconstruction rarely convinces a reviewer.

Design age screening to collect as little as possible, since screening that collects more than it needs becomes the problem it was meant to solve.

Secure employees devices that retain student information, with encryption and remote wipe, since a lost laptop can retain a filing cabinet of files.

Review assistive technology vendors for the usage information they collect, because that information can reveal disability.

Run confidentiality impact assessments for new platforms, and retain the assessment with the procurement record, not in a separate folder nobody opens.

Apply the highest notification and permission standard to sensitive survey topics, because the injury of unwanted disclosure is greatest there.

A worked illustration

In that illustration the review, when it finally happens, finds monitoring that was never disclosed, and the college must withdraw the app mid-term.

Consider a proctoring tool adopted during a rush to online teaching, and reviewed properly only a year later, after thousands of recordings were stored.

In that illustration the disclosing is limited to the disciplinary objective, and the file is not treated as an ordinary student file afterwards.

In that illustration the older logs are deleted, the new period is published, and future logs expire automatically.

Consider a site police unit that produces a law enforcement file and is asked to disclose it with the dean's office, and that verifies the objective of the sharing first.

Where guides go wrong

Publishing a directory without checking the opt-out list is an error that is apparent to every student who opted out, and to their peers.

Screening younger users by collecting more data than the screening requires is a mistake, because the safeguarding then becomes the problem.

Treating internal sharing as unrestricted is a mistake, since internal receivers still need an objective and authorization for the record.

Accepting a vendor's self-assessment as evidence, where the data is personal, is a mistake, since self-assessment answers the issues the vendor chose to ask.

Responding to a media request from the first office that answers is a mistake, because the first office is rarely the office that knows the disclosure limits.

Sources and evidence on the record

  • Family Educational Rights and Privacy Act regulations, 34 CFR Part 99, text on eCFR.
  • National Institute of Standards and Technology, Computer Security Resource Center - control guidance used here as method, not as law.
  • US Department of Education, Student Privacy Policy Office, studentprivacy.ed.gov - FERPA guidance, FAQs and model notices.

Evidence basis: 34 CFR Part 99 and NIST control guidance used as method Applies when: When a college holds, uses or discloses a student record system in the context of security controls for student data

Next on the ledger