Framework overlap

Does ISO 27018 cover Ley Orgánica de Protección de Datos Personales (LOPDP)?

You hold ISO 27018 and have been told to do Ley Orgánica de Protección de Datos Personales (LOPDP). Here is how much overlaps, control by control.

63% of Ley Orgánica de Protección de Datos Personales (LOPDP) you already have

ISO 27018 already covers about 63% of Ley Orgánica de Protección de Datos Personales (LOPDP), leaving 3 of 8 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 3

No control in ISO 27018 maps directly to one in Ley Orgánica de Protección de Datos Personales (LOPDP). 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 27018 reaches these. This is the list to scope.

LOPDP-EC-Lawful-Basis-Consent-Notice-Information-Duty-Principles-Article-7-15-Purpose-Limitation-Minimisation
Ecuador LOPDP Lawful Basis + Consent + Notice + Principles + Articles 7-15
LOPDP-EC-Scope-Application-Asamblea-Nacional-10-May-2021-Effective-26-May-2023-SPDP-Constitution-Article-66-Habeas-Data
Ecuador LOPDP Scope + Asamblea Nacional + 10 May 2021 + Effective 26 May 2023 + SPDP
LOPDP-EC-Sensitive-Personal-Data-Children-Adolescents-Healthcare-Articles-28-32-Codigo-Ninez-Adolescencia
Ecuador LOPDP Sensitive Data + Children + Adolescents + Articles 28-32
Show the 5 you already have
LOPDP-EC-Cross-Border-Transfers-Articles-59-65-Adequacy-SCC-BCR-EU-Schrems-LatAm-CBPR-Andean-Community
Ecuador LOPDP Cross-Border + Articles 59-65 + Adequacy + Andean Community + LatAm
LOPDP-EC-Data-Subject-Rights-Access-Rectification-Erasure-Object-Portability-Automated-Decisions-Articles-16-27
Ecuador LOPDP Data Subject Rights + Access + Rectification + Erasure + Articles 16-27
LOPDP-EC-Enforcement-Sanctions-Articles-66-76-SPDP-Investigation-Administrative-Fines-Tiered-Penalty-Habeas-Data
Ecuador LOPDP Enforcement + Sanctions + Articles 66-76 + SPDP + Habeas Data
LOPDP-EC-Governance-DPO-ROPA-DPIA-Privacy-by-Design-Training-Articles-46-58-Compliance-Monitoring
Ecuador LOPDP Governance + DPO + ROPA + DPIA + Privacy by Design + Training
LOPDP-EC-Security-Processor-Breach-Notification-Articles-37-45-Encryption-72-Hour-SPDP-Notification-CSIRT
Ecuador LOPDP Security + Processor + Breach Notification + Articles 37-45 + 72-Hour

How this is calculated

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