Higher-Education Tabletop Exercise: A Third-Party Student-Data Breach
A generic, reusable tabletop exercise template for colleges and universities. Run it on paper in about 90 minutes. Replace bracketed details to fit your institution. No real organization names are used.
This exercise is aligned to FERPA student-privacy expectations and designed to support GLBA Safeguards obligations that apply to institutions handling student financial data. It does not by itself satisfy any regulation or ensure compliance.
Scenario summary
A software vendor that holds student records for the institution reports a vague security incident. The institution discovers a legacy data feed was quietly sending sensitive student information, including identifiers, to the vendor, and that a large share of student records may be exposed. Over the exercise the team confirms scope, manages the vendor relationship and a trivial liability cap, decides who notifies whom and how fast, faces a student who posts first, holds a town hall, and makes a mid-year decision about whether to keep the vendor.
Exercise objectives
- Confirm what data was exposed and roughly how many students, within a target time, using institutional records rather than the vendor's word alone.
- Determine notification responsibilities and timing across the institution and the vendor, and document the decision.
- Manage the vendor relationship, including contract terms and any liability cap, without letting the vendor set the institution's posture.
- Communicate accurately with students, families, faculty, and staff, and manage media and campus reaction.
- Coordinate privacy, IT security, legal, the registrar, and financial aid through single owners.
- Make and record a decision on continuing with the vendor, including the controls required to do so.
Participants and roles
- Incident lead — senior IT or administrative officer who runs the response.
- Privacy office / FERPA official — student-privacy obligations and scope.
- IT security — forensics, the data feed, and containment.
- Registrar — the system of record and affected-student identification.
- Financial aid — exposure of financial data and related obligations.
- Legal / compliance — notification, contract, and regulatory questions.
- Communications / PR — student, family, campus, and media messaging.
- Executive sponsor — approves external statements and the vendor decision.
- Facilitator — delivers injects, keeps time, captures decisions (not a participant).
Injects
T+0 — A vague email from the vendor. Delivered to: IT security → incident lead. A vendor that holds student records sends a short, vague note about a "security incident" with few specifics and no clear scope.
- How do you turn a vague vendor notice into a real picture of exposure?
- Who at the institution needs to know in the first hour, and who decides that?
- What do you ask the vendor for immediately, and what do you preserve?
T+20m — The feed that shouldn't exist. Delivered to: IT security + registrar. Investigation finds a legacy data feed that was quietly sending student records — including identifiers and some financial-aid data — to the vendor, and it may have been doing so for a long time.
- How do you determine which students and what data were exposed?
- What does a long-running, forgotten feed mean for your data inventory and controls?
- Who confirms the feed is stopped and that no others like it exist?
T+45m — A student posts first. Delivered to: communications + privacy office. Before the institution says anything, a student posts publicly that their information was leaked, and it begins to spread on campus.
- What can the institution say while scope is still unconfirmed?
- How do you reach students directly rather than letting social posts set the story?
- Who owns the single, accurate message?
T+1h15 — The vendor offers to send the notices. Delivered to: legal / compliance + privacy office. The vendor offers to send breach notifications under its own name and points to a liability cap in the contract that is small relative to the exposure.
- Who should notify affected students, and under whose name — and why?
- How does the liability cap change your stance with the vendor, if at all?
- What is the institution's own notification obligation, regardless of the vendor?
T+2h — The town hall. Delivered to: executive sponsor + communications. Pressure builds for the institution to address the campus directly. The honest position is that a full data inventory did not exist and the feed was not being monitored.
- How do you hold a town hall when some answers are "we don't know yet"?
- How much do you disclose about the control gap, and when?
- What do students and families most need to hear to act and to trust the response?
T+4h — The final count. Delivered to: incident lead + registrar + financial aid. The vendor's review confirms a large share of student records were taken, identifiers among them. The practical and reputational weight of the number lands.
- What changes now that scope is confirmed — notifications, services offered, reporting?
- What support (credit monitoring, help lines, guidance) do you provide, and how?
- What reporting obligations, if any, are triggered, and who owns them?
T+Day — Keep the vendor? Delivered to: executive sponsor + legal. Mid-term, with the vendor embedded in operations, the institution must decide whether to keep it, and the vendor's team is pushing to "move forward together."
- What would have to be true about controls to continue with this vendor?
- How do you weigh operational disruption against the risk of staying?
- Who makes and records this decision, and against what criteria?
Contingency — A fraud wave. Delivered to: incident lead. Reports arrive that exposed student data is being used — fraudulent aid applications, account-takeover attempts, or tax fraud — before notifications have fully gone out.
- How do you accelerate protection for students already being targeted?
- What does active misuse change about your messaging and reporting?
After-action checklist
- Time from vendor notice to a confirmed scope of exposure, measured against target.
- Data inventory and the forgotten feed addressed as a root cause and a recurring risk.
- Notification responsibility and timing decided and documented (institution vs. vendor).
- Vendor relationship and contract terms managed without ceding the institution's posture.
- Student, family, campus, and media communication consistent and accurate.
- Support services for affected students defined and offered.
- Vendor continuation decision made against explicit control criteria.
- Privacy, security, registrar, financial aid, and legal coordinated through clear owners.
Frequently asked questions
How long does this campus tabletop exercise take?
About 90 minutes, from a vague vendor notice through scoping, the first public posts from students, the notification decision and the decision on whether to keep the vendor.
Who should take part?
The incident lead, the privacy office or FERPA official, IT security, the registrar, financial aid, legal, communications and an executive sponsor. A facilitator runs the exercise.
Does this count as our Clery Act emergency test?
No. The Clery Act requires an annual test of your emergency response and evacuation procedures. This data-breach exercise is aligned to FERPA and designed to support GLBA Safeguards obligations. For your Clery test, use a campus emergency scenario such as Lockdown Decision.
What makes vendor breaches hard for institutions?
The vendor may control the facts, offer to send notices under its own name, and point to a small liability cap. The exercise tests whether your institution keeps control of its own response.