Framework overlap

Does API 1164 cover Tennessee Information Protection Act (TIPA)?

You hold API 1164 and have been told to do Tennessee Information Protection Act (TIPA). Here is how much overlaps, control by control.

57% of Tennessee Information Protection Act (TIPA) you already have

API 1164 already covers about 57% of Tennessee Information Protection Act (TIPA), leaving 3 of 7 controls as genuinely new work.

Already covered 0 Likely covered 4 New work 3

No control in API 1164 maps directly to one in Tennessee Information Protection Act (TIPA). 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 API 1164 reaches these. This is the list to scope.

TENNTIPA-5
Processor Agreements and Vendor Management
TENNTIPA-6
DPIA and NIST Privacy Framework
TENNTIPA-7
Enforcement and Right to Cure
Show the 4 you already have
TENNTIPA-1
Scope, Applicability, Definitions
TENNTIPA-2
Consumer Rights
TENNTIPA-3
Sensitive Data and Consent
TENNTIPA-4
Privacy Notice and Transparency

How this is calculated

Already covered means a mapping runs from a control in API 1164 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