How to Review Student Risk After a School Data Incident

Map data before selecting safeguards

For Iris, list exact exposed fields and whether they were viewed, downloaded, changed, indexed, or merely present in an affected system. Separate names and contact details from credentials, government identifiers, financial information, disability records, health information, location, and safety plans. Record known and unknown exposure.

Prioritize immediate student safety

Address stalking, threats, extortion, bullying, medical danger, changed emergency contacts, or exposed safety locations through the appropriate urgent route. Give Iris understandable information, privacy, AAC, and choices about support. Avoid requiring public disclosure or repeated detailed retelling as a condition of help.

Protect accounts and identity with official guidance

Follow the school's confirmed credential steps. Use IdentityTheft.gov for a tailored federal identity-theft recovery plan when facts support that concern, and consult qualified financial, legal, or law-enforcement help for case-specific decisions. Preserve reports, account changes, alerts, disputes, and outcomes.

Set monitoring periods and triggers

Define which account, credit, benefit, health, school, communication, or safety indicators will be checked, by whom, and for how long. Record triggers for renewed school contact or specialized help. Monitoring is an action with limits; it does not prove that misuse will occur or that future harm is impossible.

Prepare Iris's privacy-incident review

Bring Iris's student incident-risk register, the school's current privacy and security contacts, annual FERPA notice, incident messages, minimal evidence, record and account categories, access needs, service-continuity concerns, and a short decision list. Also bring school and vendor responses, correction history, complaint questions, current deadlines, and requested outcomes. End with owners, dates, and a representative validation test.

Build Iris's source-attributed incident record

Create a restricted student incident-risk register for Iris's data type, sensitivity, exposure, recipient, misuse path, immediate safety, account, identity, financial, health, bullying, support, monitoring, and escalation. Give every field a source, version, holder, sender, recipient, time, authority, status, owner, next action, due date, correction, and closure evidence. Attribute student communication, family report, school statement, vendor notice, system evidence, clinical information, and legal conclusion separately.

Protect Iris's safety, access, and dignity

Give Iris and family participants understandable, accessible information, privacy, realistic update times, and a reliable way to ask questions, disagree, correct, accept, decline, pause, and request help. Keep AAC, interpreters, schoolwork, health and safety information, mobility, food, water, bathroom access, prescribed care, rest, and emergency help available during the response.

Ask eight incident-response questions for Iris

Use these questions in the student incident-risk register:

• Which alert, event, record, account, device, product, holder, sender, recipient, and time apply?
• What is known, unknown, disputed, contained, corrected, or still exposed?
• Which FERPA, IDEA, HIPAA, state, school, contract, security, complaint, or other source governs the step?
• Who may classify, contain, investigate, communicate, notify, correct, restore, and close each field?
• Which immediate safety, identity, health, disability, bullying, financial, or access risk needs action?
• What did Iris communicate directly, and what did family, school, vendor, or a professional report separately?
• Which evidence supports the exposure, containment, notice, correction, continuity, or recovery state?
• Which representative test will show that the repaired path works?

Classify fields as complete, failed, pending, declined, disputed, false positive, suspected, confirmed, contained, superseded, or inapplicable with a reason.

A fictional school-data incident example for Iris

In this fictional example, Iris's school reports an incident involving contact information, portal credentials, disability records, and partial financial identifiers. Reviewers freeze 40 data-type, exposure, safety, identity, account, support, monitoring, and escalation fields and complete 28 of 40 by the checkpoint. A missing event, record, holder, recipient, data, exposure, containment, account, communication, correction, continuity, or validation field remains in Iris's denominator with an owner, age, and next action.

The student incident-risk register measures evidence completion. Legal compliance, notification duty, security effectiveness, service quality, student understanding, harm, family experience, and recovery remain separate questions. Concurrent changes limit causal conclusions.

Use compatible incident denominators for Iris

For Iris's student incident-risk register, report alerts triaged divided by alerts due; confirmed incidents contained divided by confirmed incidents due; affected accounts secured divided by accounts due; required communications completed divided by communications due; affected records corrected divided by records due; and recovery tests passed divided by tests attempted.

Publish raw counts with percentages and age every open item. Keep discovery, triage, classification, containment, evidence preservation, exposure analysis, notice review, communication, correction, continuity, complaint, and recovery as distinct measures.

Apply the federal privacy and security boundaries for Iris

For Iris, current 34 CFR Part 99 governs FERPA within its stated scope, and the Education Department's FERPA hub provides public guidance. The Department's data-security page explains that FERPA does not prescribe specific security controls, while security failures can create privacy risk. Its older breach checklist is general best-practice guidance, and current scenario trainings support planning exercises.

No cited federal source creates one universal family notification rule for every school data incident. Verify current state, district, vendor, contract, insurance, law-enforcement, record-holder, and student-specific duties.

Apply complaint, health, and professional boundaries for Iris

The current SPPO complaint page describes the federal complaint route and its 180-day timeliness rule. IdentityTheft.gov offers a federal recovery-plan route when identity theft facts support it. Federal school health-record guidance and joint FERPA-HIPAA guidance explain why record holder and entity status matter. ASHA addresses AAC; the BACB Ethics Code and CASP overview remain limited to their professional and organizational scope for Iris page 7.

Close Iris's loop with an incident test

Ask Iris and the relevant family participant to review the outcome through their usual language and communication methods. Test the repaired recipient list, account, device control, public-link permission, vendor path, family communication, record correction, complaint file, service-continuity route, or recovery evidence suited to the event. The defined review question for Iris is student risk after school data incident. Preserve every mismatch with an owner, due date, and next step.

Before closure, record what the school confirmed, what remains unknown, which source governed notice, which student access or service depended on the affected system, and how the response changed the source control. For Iris's incident review, keep incident state, family communication, record correction, safety support, and technical recovery separate. Reopen the file after a failed test, new recipient, changed exposure window, recurring alert, or inaccurate notice. The tracked topic remains student risk after school data incident.