Framework overlap

Does GDPR cover Colombia Data Protection Law (Law 1581 of 2012)?

You hold GDPR and have been told to do Colombia Data Protection Law (Law 1581 of 2012). Here is how much overlaps, control by control.

70% of Colombia Data Protection Law (Law 1581 of 2012) you already have

GDPR already covers about 70% of Colombia Data Protection Law (Law 1581 of 2012), leaving 8 of 27 controls as genuinely new work.

Already covered 19 Likely covered 0 New work 8

What is genuinely new work

Nothing in GDPR reaches these. This is the list to scope.

CO-L1581-A12
Duty to Inform the Data Subject (Privacy Notice)
CO-L1581-A14
Consultations (Access Requests)
CO-L1581-A15
Complaints (Reclamos)
CO-L1581-A19
Data Protection Authority (SIC)
CO-L1581-A2
Scope of Application
CO-L1581-A21
Functions of the SIC
CO-L1581-A23
Sanctions
CO-L1581-A8
Data Subject Rights (Habeas Data)
Show the 19 you already have
CO-L1581-A10
Cases Not Requiring Authorization
CO-L1581-A13
Persons to Whom Information May Be Disclosed
CO-L1581-A17
Duties of Controllers (Responsables)
CO-L1581-A18
Duties of Processors (Encargados)
CO-L1581-A25
National Database Registry (RNBD)
CO-L1581-A26
Prohibition on International Transfers
CO-L1581-A27
Binding Corporate Rules
CO-L1581-A4-ACCESO
Principle of Restricted Access and Circulation
CO-L1581-A4-CONFID
Principle of Confidentiality
CO-L1581-A4-FINALIDAD
Principle of Purpose
CO-L1581-A4-LEGALIDAD
Principle of Legality
CO-L1581-A4-LIBERTAD
Principle of Freedom (Consent)
CO-L1581-A4-SEGURIDAD
Principle of Security
CO-L1581-A4-TRANSPARENCIA
Principle of Transparency
CO-L1581-A4-VERACIDAD
Principle of Veracity and Quality
CO-L1581-A5
Sensitive Data Definition
CO-L1581-A6
Processing of Sensitive Data
CO-L1581-A7
Children's and Adolescents' Data
CO-L1581-A9
Authorization of the Data Subject

How this is calculated

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