53% of Family Educational Rights and Privacy Act (FERPA) you already have
NIST SP 800-190 already covers about 53% of Family Educational Rights and Privacy Act (FERPA), leaving
7 of 15 controls as genuinely new work.
Already covered 0
Likely covered 8
New work 7
No control in NIST SP 800-190
maps directly to one in Family Educational Rights and Privacy Act (FERPA). Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in NIST SP 800-190 reaches these. This is the list to scope.
FERPA-99.31a3-Audit-99.31a6-StudiesAudit and Evaluation Exception + Studies Exception (34 CFR 99.31(a)(3), 99.31(a)(6), 99.35)
FERPA-99.31a9-Judicial-99.31a10-Emergency-99.31a13-14Judicial Disclosure + Health and Safety Emergency + Sex Offense Disclosures (34 CFR 99.31(a)(9), (10), (13), (14), 99.36)
FERPA-Part99.1_3Applicability and Definitions (34 CFR 99.1, 99.3)
FERPA-Part99.32-Recordkeeping-99.33-RedisclosureRecordkeeping of Disclosures + Limitations on Redisclosure (34 CFR 99.32, 99.33)
FERPA-Part99.37-DirectoryDirectory Information (34 CFR 99.31(a)(11), 99.37)
FERPA-Part99.4_5Rights Transfer (34 CFR 99.4, 99.5)
FERPA-StatusFERPA Implementation Status, 2024-2025 Guidance and AI/Cloud Trends
Show the 8 you already have
FERPA-99.31a1-School-OfficialsSchool Officials with Legitimate Educational Interest (34 CFR 99.31(a)(1))
FERPA-99.60-99.67-EnforcementEnforcement and Complaint Procedures (34 CFR 99.60 to 99.67)
FERPA-Coord-COPPA-PPRA-StateCoordination with COPPA, PPRA, State Student Privacy Laws and Sectoral Laws
FERPA-Part99.10_11_12Right to Inspect and Review (34 CFR 99.10, 99.11, 99.12)
FERPA-Part99.20_21_22Right to Request Amendment + Hearing (34 CFR 99.20, 99.21, 99.22)
FERPA-Part99.30_31Prior Consent Required for Disclosure + Exceptions (34 CFR 99.30, 99.31)
FERPA-Part99.7Annual Notification of Rights (34 CFR 99.7)
FERPA-Safeguards-PTACData Security Safeguards for PII in Education Records (PTAC Best Practices, SPPO Guidance)
How this is calculated
Already covered means a mapping runs from a control in NIST SP 800-190 to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition