Framework overlap

Does ISO 27019 cover Nebraska Data Privacy Act?

You hold ISO 27019 and have been told to do Nebraska Data Privacy Act. Here is how much overlaps, control by control.

100% of Nebraska Data Privacy Act you already have

ISO 27019 already covers about 100% of Nebraska Data Privacy Act, leaving 0 of 8 controls as genuinely new work.

Already covered 5 Likely covered 3 New work 0

What is genuinely new work

Nothing in ISO 27019 reaches these. This is the list to scope.

Nothing. Every control is reached.

Show the 8 you already have
NDPA-1
Applicability, Scope, and Carve-Outs
NDPA-2
Consumer Rights - Access, Correct, Delete, Portability, Appeal
NDPA-5
Privacy Notice, Data Minimisation, and Purpose Limitation
NDPA-6
Reasonable Security Practices and Incident Response
NDPA-7
Data Protection Assessments and Processor Contracts
NDPA-3
Opt-Out Rights for Targeted Advertising, Sale, and Profiling
NDPA-4
Sensitive Data Processing Consent and Childrens Protections
NDPA-8
Nebraska Attorney General Enforcement, Permanent 30-Day Cure, and Penalties

How this is calculated

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