Framework overlap

Does PCI P2PE cover Liechtenstein DPA?

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

63% of Liechtenstein DPA you already have

PCI P2PE already covers about 63% of Liechtenstein DPA, leaving 3 of 8 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 3

No control in PCI P2PE maps directly to one in Liechtenstein DPA. 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 PCI P2PE reaches these. This is the list to scope.

LIDPA-Enforcement-Sanctions-Articles-50-65-DSS-Administrative-Fines-20M-EUR-4-Percent-Cooperation-Codes-Certification
Liechtenstein DPA Enforcement + Articles 50-65 + Administrative Fines EUR 20M + 4%
LIDPA-Scope-Datenschutzgesetz-DSG-2018-Princely-Decree-EEA-Agreement-GDPR-DSS-Vaduz-Constitution-Article-32
Liechtenstein DPA Scope + DSG 2018 + Princely Decree + EEA Agreement + GDPR via EEA + DSS Vaduz
LIDPA-Special-Categories-Sensitive-Data-Children-Article-9-GDPR-Article-9-Health-Financial-Sector
Liechtenstein DPA Special Categories + Sensitive Data + Children + Article 9
Show the 5 you already have
LIDPA-Cross-Border-International-Transfer-Articles-40-49-GDPR-Chapter-V-EEA-Adequacy-SCC-BCR-Switzerland
Liechtenstein DPA Cross-Border + Articles 40-49 + EEA + Switzerland + SCC
LIDPA-Data-Subject-Rights-Access-Rectification-Erasure-Object-Portability-DSG-Articles-15-22-GDPR-Aligned
Liechtenstein DPA Data Subject Rights + Articles 15-22 + GDPR-Aligned
LIDPA-Governance-DPO-ROPA-DPIA-Privacy-by-Design-Articles-32-39-Codes-of-Conduct-Whistleblowing
Liechtenstein DPA Governance + DPO + ROPA + DPIA + Articles 32-39 + Whistleblowing
LIDPA-Lawful-Basis-Consent-Notice-Principles-DSG-Articles-4-13-GDPR-Articles-5-6-7-Liechtenstein-Specific
Liechtenstein DPA Lawful Basis + Consent + Notice + Principles + Articles 4-13
LIDPA-Security-Processor-Engagement-Breach-Notification-Articles-25-31-72-Hour-DSS-FMA-Coordination
Liechtenstein DPA Security + Processor + Breach + Articles 25-31 + 72-Hour + FMA

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