Framework overlap

Does ISO 27001:2022 cover Peru DPL?

You hold ISO 27001:2022 and have been told to do Peru DPL. Here is how much overlaps, control by control.

38% of Peru DPL you already have

ISO 27001:2022 already covers about 38% of Peru DPL, leaving 5 of 8 controls as genuinely new work.

Already covered 0 Likely covered 3 New work 5

No control in ISO 27001:2022 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 ISO 27001:2022 reaches these. This is the list to scope.

PERU-1
Scope, Lawful Basis, Purpose Limitation, Quality
PERU-3
Data Subject Rights (ARCO), Habeas Data, Automated Decisions
PERU-4
Children's Data, Privacy Impact, Sensitive Categories
PERU-6
Cross-Border Transfer and Personal Data Bank Registration
PERU-8
Breach Notification, ANPD Cooperation, Sanctions, Compliance
Show the 3 you already have
PERU-2
Consent, Privacy Notice, Sensitive Data
PERU-5
Security of Personal Data and Processor Agreements
PERU-7
DPO, Records, Retention, Marketing, Training

How this is calculated

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