Student Data Inventories: The First Audit Step
A plain-language guide to student data inventories: the first audit step: the record, the purpose, the authority and the safeguard.
- Record
- privacy audit record in audits, documentation and readiness
- Data
- Student Data Inventories: The First Audit Step
- Safeguard
- an inventory, a trail of disclosures and findings tracked to closure
- First check
- Limit the sharing to the minimum the purpose requires.
The short answer
Put simply, student information inventories: the first audit step is regarding control over a privacy audit file that belongs, in a practical sense, to a student and is held in trust by an university. The university may use it for the objective it was collected for, share it where the law or a valid consent permits, and must safeguard it everywhere else. Everything in this guide is a way of making that sentence workable at a desk, stage by stage.
A school authoritative exception covers employees who genuinely need the record for their work, and it does not extend to curiosity, convenience or broad awareness.
Device security for employees laptops matters since a stolen laptop may retain more student files than a filing cabinet ever did.
Vendor selection is a privacy determination before it is a purchasing determination, because the vendor's data practices become the institution's risk.
Group mailboxes and disclosed drives are where access control most often fails, because nobody owns the membership list.
What this covers
Publishing a directory notification in a handbook nobody reads is weaker than publishing it where students really encounter it at enrolment.
Bluetooth beacons in classrooms can file attendance quietly, and silent collection deserves explicit notice to the students affected.
Email can be an education record when it is maintained about a student, and the fact that it lives in a mailbox does not remove it from the category.
Employment files for student employees sit in a distinct category, and the distinction matters when a file is requested.
Parents of independent students do not acquire access by asking, however strongly they feel the request is justified.
Attendance information, participation logs and advising notes can all be education files when they are maintained regarding an identifiable student.
How to work through it
Assess new platforms before purchase, with privacy review as a gate, not as a comment added following the contract is signed.
Analyse mixed-audience platforms for their younger users separately, since a policy written for adults does not cover children.
Design age screening to collect as little as possible, because screening that collects more than it needs becomes the problem it was meant to solve.
Run internal audits on a stated cycle, and track findings to closure with owners and dates.
Log access to personal records, and review those logs, since unreviewed logs protect nobody.
Review a determination following it is made: was the information used for the stated objective, does the receiver still need it, has retention expired?
Apply the highest notice and permission standard to sensitive survey topics, because the harm of unwanted disclosure is greatest there.
Contain students in oversight, because students notification privacy problems that employees have normalised.
A worked illustration
In that illustration the sharing is limited to the disciplinary purpose, and the file is not treated as a routine student file afterwards.
Consider a learning app for younger students that tracks behavior across sessions and shares aggregates with a third party, without a privacy review.
Consider an employer who requests a college to confirm a graduate's degree and is given only the directory facts the college has designated, not the transcript.
In that illustration the audit finding becomes a remediation task with an owner and a date, and the subprocessor's copy is deleted on a verified timetable.
Consider a counselling service that retains notes in a personal file and is asked whether those notes are education records, and that checks the exception before answering.
Where guides go wrong
Retaining audit evidence too long is an error of its own, because evidence kept beyond its schedule becomes a file that itself needs safeguarding.
Treating silence as informed agreement is an error, especially for students who are less familiar with confidentiality notices and opt-outs.
Redisclosing a record received under an exemption, without verifying whether the second sharing is covered, is an error that spreads the original sharing.
Sending an accrediting body more than the accreditation objective needs is an error, because the exemption bounds what might be sent.
Accepting a vendor's consumer privacy policy as a substitute for a contract is a mistake, since consumer policies describe the vendor's own practices, not the institution's objectives.
Sources and evidence on the record
- Family Educational Rights and Privacy Act regulations, 34 CFR Part 99, text on eCFR.
- US Department of Education, Student Privacy Policy Office, studentprivacy.ed.gov - FERPA guidance, FAQs and model notices.
- National Institute of Standards and Technology, Computer Security Resource Center - control guidance used here as method, not as law.
Evidence basis: Department of Education guidance and audit practice Applies when: When a college holds, uses or discloses a privacy audit record in the context of audits, documentation and readiness