The Family Educational Rights and Privacy Act (FERPA) is a US federal law that protects the privacy of student education records and gives students and parents specific rights over them. It applies to schools and institutions that receive certain federal education funding, and it reaches the vendors those institutions rely on. This guide explains what FERPA requires, how it is enforced, and how to build a program that holds up.
What it is
FERPA is a federal statute, codified at 20 U.S.C. § 1232g, enacted in 1974. The US Department of Education issues implementing regulations at 34 CFR Part 99 and enforces the law through its Student Privacy Policy Office (formerly the Family Policy Compliance Office). FERPA is mandatory law, not a standard or a certification scheme. There is no FERPA certification, and no version numbering as with ISO or NIST publications. The regulations have been amended over time, and the Department publishes guidance that interprets them, so check current guidance when you design your program.
The purpose is narrow and specific: control who can see and disclose personally identifiable information from education records, and give eligible students and parents the right to inspect, request correction of, and consent to disclosure of those records. FERPA is a privacy and access-rights law. It does not prescribe technical security controls.
Who it applies to
FERPA applies to educational agencies and institutions that receive funds under programs administered by the US Department of Education. In practice this covers most public K-12 schools and districts, and most colleges and universities, public and private, that participate in federal student aid. Many private and religious K-12 schools are not covered because they do not receive such funds.
Rights belong to parents until the student turns 18 or enrolls in a postsecondary institution at any age. At that point the rights transfer to the student, who is called an "eligible student." Postsecondary students therefore control their own records, with limited exceptions such as certain disclosures to parents of dependent students.
Companies are not directly regulated in most cases, but they are pulled in by contract and by the rules on disclosure. Edtech vendors, cloud providers, learning platforms, and service providers that handle education records on behalf of a school typically need to fit within a FERPA exception, and the institution remains responsible for their handling of the data.
Two boundaries are often confused. Records held by a school's law enforcement unit for law enforcement purposes, and employment records of staff who are not students, are generally outside the definition of education records. Medical or treatment records of eligible students are also treated separately, though they can become education records when disclosed beyond treatment. Where a school health clinic's records fall between FERPA and HIPAA, get legal advice.
Key requirements and control areas
Education records and PII
Education records are records directly related to a student and maintained by the institution or a party acting for it. FERPA protects personally identifiable information (PII) in those records, including direct identifiers and indirect identifiers that could let a reasonable person in the school community identify a student. The institution must know where such records live, which in modern environments includes learning management systems, cloud storage, email, and analytics tools.
Right to inspect and review
Eligible students and parents have the right to inspect and review records. The institution must respond within a reasonable period, and no more than 45 days after a request. Institutions need an intake process, identity verification, and a way to locate records across systems.
Right to request amendment
Students and parents may ask to correct records they believe are inaccurate, misleading, or in violation of privacy rights. If the school declines, the requester is entitled to a hearing and may add a statement of disagreement to the record.
Consent and disclosure
The default rule is that PII from education records may not be disclosed without written consent from the parent or eligible student. The regulations list exceptions, including:
- School officials with a legitimate educational interest. This can include contractors and vendors, provided they are under the institution's direct control regarding use and maintenance of the records, are subject to the same use and redisclosure limits, and meet the criteria the institution sets in its annual notice.
- Transfers to other schools where the student seeks or intends to enroll.
- Audit or evaluation of federal or state education programs by authorized representatives.
- Financial aid determinations.
- Studies conducted for or on behalf of the institution, under a written agreement.
- Health and safety emergencies, judicial orders and subpoenas (usually with notice to the student), and certain other defined cases.
Directory information
Institutions may disclose designated directory information, such as name or enrollment status, without consent if they give public notice of the categories and give students a reasonable chance to opt out. The institution decides which categories to designate. Be cautious with categories that could be combined to identify or target students.
Annual notification
Institutions must notify students and parents annually of their FERPA rights and explain how to exercise them, including the school official criteria and directory information policy.
Recordkeeping of disclosures
Institutions generally must keep a record of requests for and disclosures of PII from education records, with the party and the legitimate interest, subject to exceptions such as disclosures to the student, school officials, or under a directory information release.
Redisclosure and destruction
Parties receiving PII under certain exceptions face limits on redisclosure. For studies and audits, written agreements typically must address purpose, data use, and destruction of information when it is no longer needed.
Security expectations
The statute and regulations do not set a detailed security standard. The Department's guidance expects reasonable methods to protect records, and a data breach can reflect a failure to control disclosure. Treat the security program as the practical means of preventing unauthorized disclosure.
Assessment, audit and enforcement
There is no external audit or certification for FERPA. Compliance is managed internally and demonstrated through policies, notices, agreements, and records. Enforcement runs primarily through the Department of Education's Student Privacy Policy Office, which investigates complaints filed by students and parents, typically within a limited period after the violation was or should have been discovered, and can require corrective action.
The ultimate sanction in the statute is withdrawal of federal education funding, although in practice the Department emphasizes voluntary compliance and corrective steps. FERPA does not create a private right of action: the US Supreme Court has held that individuals cannot sue schools directly for damages under FERPA. Schools may still face state privacy laws, contract claims, and reputational harm. Many states have their own student privacy statutes that add obligations for vendors, so FERPA is often the floor and not the full picture.
A practical path to meeting FERPA
- Confirm applicability. Determine whether your institution receives relevant federal funding, or whether you are a vendor serving covered institutions.
- Inventory education records and systems. Map where student PII is stored, processed, and shared, including SaaS tools, backups, and exports.
- Define roles and the school official standard. Document which employees and contractors have a legitimate educational interest, and tie access to those roles.
- Publish the required notices. Prepare the annual notification and directory information policy, with an opt-out process.
- Build request workflows. Set up procedures for inspection, amendment, and consent requests, with identity verification and tracking against the 45-day limit.
- Control vendors. Review each vendor against an exception, put written agreements in place covering use limits, redisclosure, security, breach notice, and deletion, and keep them current.
- Apply access and security controls. Use least privilege, authentication, logging, and encryption appropriate to the sensitivity of the data.
- Log disclosures. Keep the required disclosure records and be able to retrieve them.
- Train staff. Cover faculty, administrators, and IT on what counts as an education record and when consent is needed, with special attention to email, shared drives, and emergency disclosures.
- Prepare for incidents and review regularly. Define how unauthorized disclosures are escalated and corrected, and revisit policies as systems and guidance change.
How it maps to other frameworks
FERPA overlaps with security and privacy frameworks but is not equivalent to any of them. It governs disclosure and rights, while those frameworks govern controls.
- ISO 27001 and SOC 2: Access control, logging, vendor management, and incident response controls support FERPA's disclosure restrictions. Neither demonstrates FERPA compliance by itself, since neither addresses consent, directory information, or access and amendment rights.
- NIST CSF: Its Identify, Protect, and Respond functions help structure the data inventory, safeguards, and incident handling that FERPA programs depend on.
- NIST SP 800-171 and similar: Useful as a control baseline for protecting sensitive data, though not required by FERPA.
- State student privacy laws and COPPA: These are related but separate regimes. COPPA applies to online services directed to children under 13, and state laws often impose extra vendor duties. Schools and edtech companies often face them together with FERPA.
- GDPR: Comparable concepts of access, rectification, and purpose limitation, but different legal bases and scope. Institutions with EU students or operations should assess both.
FAQs
Is there a FERPA certification?
No. FERPA is a law, and no body certifies compliance. Institutions and vendors demonstrate it through policies, agreements, notices, and records, and the Department of Education investigates complaints.
Does FERPA apply to software vendors?
Usually indirectly. Vendors are not typically regulated on their own, but a school may only share education records with them under an exception, such as the school official exception, which imposes direct control, use, and redisclosure conditions. Contracts and security practices carry most of the weight.
Can a school disclose student information to parents of college students?
In general, rights move to the student at the postsecondary level, so disclosure to parents usually requires the student's consent. Exceptions exist, for example for parents of students who are tax dependents and in certain health or safety situations.
Is a data breach automatically a FERPA violation?
Not automatically. FERPA does not contain a breach notification rule or a specific security standard. A breach can, however, amount to an improper disclosure if the school failed to use reasonable methods to protect records, and state breach notification laws may apply separately.
What is the difference between FERPA and HIPAA?
HIPAA protects health information held by covered entities and their business associates. FERPA protects education records. Records that are education records under FERPA are generally excluded from HIPAA's privacy rule, so a school's student health records are usually handled under FERPA.
Does FERPA require encryption or specific security controls?
The law does not name specific technical controls. Guidance expects reasonable protection, and institutions normally choose controls from frameworks such as NIST or ISO and apply them through contracts and internal policy.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. FERPA has no audit to pass, but institutions and edtech vendors still need to show that student data is controlled, access is limited, and vendors are managed. Aristiun supports that work by collecting evidence automatically and tracking whether the controls behind it stay in place across compliance frameworks.
- Automated evidence collection: Gather evidence from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets, to document access controls and data handling for systems that hold student records.
- Cross-framework mapping: Map controls across 340+ frameworks so one evidence base supports FERPA-related practices alongside ISO 27001, SOC 2 or NIST work.
- Real-time control monitoring: Monitor control effectiveness and get alerts when controls drift out of compliance, so you can remediate issues promptly.
- Vendor risk: Map vendor controls to your compliance requirements to support the review of edtech and cloud providers.