Framework overlap

Does SOC 2 cover New Jersey Data Privacy Act?

You hold SOC 2 and have been told to do New Jersey Data Privacy Act. Here is how much overlaps, control by control.

63% of New Jersey Data Privacy Act you already have

SOC 2 already covers about 63% of New Jersey Data Privacy Act, leaving 3 of 8 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 3

No control in SOC 2 maps directly to one in New Jersey Data Privacy Act. 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 SOC 2 reaches these. This is the list to scope.

NJDPA-1
Applicability, Thresholds, and Scope
NJDPA-3
Opt-Out Rights and Universal Opt-Out Mechanism (UOOM)
NJDPA-5
Privacy Notice, Data Minimisation, and Purpose Limitation
Show the 5 you already have
NJDPA-2
Consumer Rights - Access, Correct, Delete, Portability, Appeal
NJDPA-4
Sensitive Data, Children, and Adolescents 13-17 Opt-In
NJDPA-6
Reasonable Data Security and Incident Response
NJDPA-7
Data Protection Assessments and Processor Contracts
NJDPA-8
AG Platkin Enforcement, 18-Month Cure Sunset, and Division of Consumer Affairs

How this is calculated

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