Framework overlap

Does PCI P2PE cover Virginia CDPA?

You hold PCI P2PE and have been told to do Virginia CDPA. Here is how much overlaps, control by control.

67% of Virginia CDPA you already have

PCI P2PE already covers about 67% of Virginia CDPA, leaving 2 of 6 controls as genuinely new work.

Already covered 2 Likely covered 2 New work 2

What is genuinely new work

Nothing in PCI P2PE reaches these. This is the list to scope.

VIRGINIAVCDPA-5
Processor Contracts and Vendor Management
VIRGINIAVCDPA-6
AG Enforcement, Cure, Penalties
Show the 4 you already have
VIRGINIAVCDPA-2
Consumer Rights
VIRGINIAVCDPA-3
Sensitive Data Consent and Children
VIRGINIAVCDPA-1
Scope, Applicability, Definitions
VIRGINIAVCDPA-4
Privacy Notice and DPIA

How this is calculated

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