Does Colombia Data Protection Law (Law 1581 of 2012) cover Ethiopia Personal Data Protection Proclamation (No. 1321/2024)?

42% of Ethiopia Personal Data Protection Proclamation (No. 1321/2024) you already have

Colombia Data Protection Law (Law 1581 of 2012) already covers about 42% of Ethiopia Personal Data Protection Proclamation (No. 1321/2024), leaving 14 of 24 controls as genuinely new work.

Already covered 0 Likely covered 10 New work 14

No control in Colombia Data Protection Law (Law 1581 of 2012) maps directly to one in Ethiopia Personal Data Protection Proclamation (No. 1321/2024). 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 Colombia Data Protection Law (Law 1581 of 2012) reaches these. This is the list to scope.

ETH-PDPP-Art.1-3

Short Title, Definitions and Scope

ETH-PDPP-Art.23

Duration of personal data protection

ETH-PDPP-Art.24-28

Right to be informed, access, rectification and erasure

ETH-PDPP-Art.29-32

Right to object, restriction, automated decision-making, portability

ETH-PDPP-Art.33-39

Controller registration regime

ETH-PDPP-Art.4-5

Powers and functions of the Ministry and the Authority

ETH-PDPP-Art.40-41

Data Protection Officer

ETH-PDPP-Art.46-48

Records of processing, DPIA and prior authorisation/consultation

ETH-PDPP-Art.49-51

Data protection by design and by default; duty to destroy; joint controllers

ETH-PDPP-Art.53-54

Research and exceptions to research

ETH-PDPP-Art.55-58

Enforcement orders, monitoring and complaints

ETH-PDPP-Art.59-62

Administrative fines, sanctions and complaints

ETH-PDPP-Art.63-64

Burden of proof and criminal offences

ETH-PDPP-Art.65-70

Reference, cooperation duties, non-applicable laws, transitory and final provisions

Show the 10 you already have

ETH-PDPP-Art.11

Processing of personal data of a minor

ETH-PDPP-Art.12-15

Fairness/transparency, purpose limitation, accuracy, storage limitation

ETH-PDPP-Art.16-17

Integrity and confidentiality; Security

ETH-PDPP-Art.18-22

Cross-border transfer and data sovereignty

ETH-PDPP-Art.42-45

Security measures, breach notification and prior security check

ETH-PDPP-Art.52

Accountability of the controller

ETH-PDPP-Art.6

Principles of personal data processing

ETH-PDPP-Art.7

Lawfulness of processing

ETH-PDPP-Art.8

Conditions for consent

ETH-PDPP-Art.9-10

Processing of sensitive personal data and further categories

How this is calculated

Already covered means a mapping runs from a control in Colombia Data Protection Law (Law 1581 of 2012) 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