75% of Peru DPL you already have
AICPA Privacy Management Framework (PMF) already covers about 75% of Peru DPL, leaving
2 of 8 controls as genuinely new work.
Already covered 0
Likely covered 6
New work 2
No control in AICPA Privacy Management Framework (PMF)
maps directly to one in Peru DPL. 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 AICPA Privacy Management Framework (PMF) reaches these. This is the list to scope.
PERU-1Scope, Lawful Basis, Purpose Limitation, Quality
PERU-6Cross-Border Transfer and Personal Data Bank Registration
Show the 6 you already have
PERU-2Consent, Privacy Notice, Sensitive Data
PERU-3Data Subject Rights (ARCO), Habeas Data, Automated Decisions
PERU-4Children's Data, Privacy Impact, Sensitive Categories
PERU-5Security of Personal Data and Processor Agreements
PERU-7DPO, Records, Retention, Marketing, Training
PERU-8Breach Notification, ANPD Cooperation, Sanctions, Compliance
How this is calculated
Already covered means a mapping runs from a control in AICPA Privacy Management Framework (PMF) 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