Student Portals: Access Controls That Matter
Student Portals: Access Controls That Matter explained for colleges: the rule, the exceptions, and the record an institution should keep.
- Record
- student record in the cloud in cloud systems and student portals
- Data
- Student Portals: Access Controls That Matter
- Safeguard
- access controls, logging and a contract that follows the record
- First check
- State the purpose in a sentence a student could understand.
The short answer
In short, student portals: access safeguards that matter hinges on one question: which student file in the cloud is involved, who holds it, and what purpose justifies the next step with it. Get those three answers right and most of the rest of the decision follows; miss any one of them and the rule applied will be the wrong rule for the facts in front of you.
Sensitive survey topics require the highest standard of notice and consent, since the injury of an unwanted disclosure is greatest there.
Alumni records do not lose safeguarding at graduation, and the requirements for former students deserve the same care as for current ones.
Remote work extends the site boundary to employees homes, and the safeguards must travel with the record to those homes.
Directory information is the one category where a published designation may change the answer, and solely where the designation and the opt-out were done properly.
What this covers
Studies conducted on behalf of an university need written agreements that limit use, need de-identification where possible, and need destruction on schedule.
Counselling records raise the same boundary issue, and staff should verify the exception before treating such a file as an ordinary file.
Career services retain employment and internship information, and sharing that information with employers needs consent analysis even when the sharing feels useful.
Health and counseling platforms ought to be segregated from general student platforms, with access limited to the employees who provide the care.
Survey systems retain responses that can be personal, and the survey design should settle anonymity, retention and reporting before distribution.
Name, enrollment status and field of study are commonly designated, while grades, disciplinary outcomes and financial facts are not directory information.
How to work through it
Audit vendor compliance, and do not accept a vendor's self-assessment as a substitute for evidence where the information is sensitive.
Make confidentiality notices available in the languages students really read, since an unread notice can not inform consent.
Analyse mixed-audience platforms for their younger users separately, because a policy written for adults does not cover children.
Distinguish employee files from student files for student employees, because the capacity in which a file was created matters.
Retain inventories current, and treat an inventory that is a year out of date as no inventory at all.
Test the actual data flow of an integration, rather than trusting a diagram, because integrations routinely pass more than intended.
Secure staff devices that hold student data, with encryption and remote wipe, because a lost laptop can hold a filing cabinet of records.
Own every group mailbox membership list, since an unowned list is an access control failure waiting to be discovered.
A worked illustration
Consider an university that runs a wellness survey with sensitive issues and settles anonymity, storage and reporting before a single response is collected.
In that illustration students who decline biometrics are not disadvantaged, and the biometric templates of students who leave are deleted on schedule.
Consider a student organization that collects member information in a shared spreadsheet and discovers, during a review, that the sheet is apparent to the whole site.
Consider a survey of younger users on a learning platform that collects birth dates for age screening and then retains them indefinitely.
In that illustration the project is paused, the information uses are documented in plain language, and the dashboard is rebuilt around a stated objective.
Where guides go wrong
Training employees with generic slides, rather than cases from their own department, is an error that produces attendance records instead of behaviour change.
Treating aggregates as anonymous when the underlying data remains identifiable is an error, because re-identification risk does not vanish at the dashboard.
Assuming cloud hosting moves responsibility is a mistake, since the college remains answerable for a record another company stores.
Approving a disclosure without recording it is a mistake, since a reviewer, auditor or student shall eventually ask what happened and why.
Including a diagnosis in an accommodation letter, when a lecturer solely needs to know the accommodation, is a mistake that discloses more than the objective needs.
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: 34 CFR Part 99 and Department of Education guidance Applies when: When a college holds, uses or discloses a student record in the cloud in the context of cloud systems and student portals