Cross-Framework Mapping

Tennessee IPAvsFERPA

See exactly how Tennessee IPA controls map to FERPA. Pre-computed mappings, identified gaps, and coverage analysis.

49
Controls Mapped
0
Gaps Found
41%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Tennessee IPA maps to FERPA with 41% coverage across 18 directly mapped controls. Analysis of 29 Tennessee IPA controls identifies 29 compliance gaps — primarily concentrated in Tennessee IPA: Data Subject Rights.

Source: TheArtOfService Knowledge Graph | 29 controls analysed | 726 frameworks | 463K+ cross-framework mappings

Control Mappings

Showing 20 of 49 mapped controls across 10 domains. Sign up to explore all 463K+ mappings across 726 frameworks.

Security(1 mappings)

TN-IPA-09Security Practices
FERPA-09Right to data portability

Tennessee IPA: Data Subject Rights(1 mappings)

TN-IPA-09Security Practices
FERPA-09Right to data portability

Awareness(4 mappings)

TN-IPA-13Cross Functional Training4 targets
FERPA-08Right to erasure and deletion
FERPA-10Right to restrict processing
FERPA-13Encryption of personal data
FERPA-22Privacy by design and default

Tennessee IPA: Data Security(14 mappings)

TN-IPA-13Cross Functional Training4 targets
FERPA-08Right to erasure and deletion
FERPA-10Right to restrict processing
FERPA-13Encryption of personal data
FERPA-22Privacy by design and default
TN-IPA-15Records and Audit Readiness4 targets
FERPA-08Right to erasure and deletion
FERPA-10Right to restrict processing
FERPA-15Access control for personal data
FERPA-22Privacy by design and default
TN-IPA-16Profiling Safeguards5 targets
FERPA-08Right to erasure and deletion
FERPA-10Right to restrict processing
FERPA-16Data breach notification requirements
FERPA-17Security incident response procedures
FERPA-22Privacy by design and default
TN-IPA-17Information Sharing and Selling Controls
FERPA-16Data breach notification requirements

+29 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 726 frameworks.

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 726 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 726 framework browser
  • Cross-framework mappings (463K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between Tennessee IPA and FERPA?

Tennessee IPA has 29 controls across its framework, while FERPA covers 64 controls. Direct mapping analysis identifies 18 overlapping controls (41% coverage). The frameworks diverge most significantly in Tennessee IPA: Data Subject Rights, where 6 Tennessee IPA controls have no direct FERPA equivalent.

How many controls map between Tennessee IPA and FERPA?

Of 29 total Tennessee IPA controls, 18 map directly to FERPA controls — representing 41% coverage. The remaining 29 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Tennessee IPA to FERPA?

29 Tennessee IPA controls have no direct equivalent in FERPA. The highest concentration of gaps is in Tennessee IPA: Data Subject Rights with 6 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between Tennessee IPA and FERPA?

The domain with the highest gap count is Tennessee IPA: Data Subject Rights (6 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.