56% of Colombia Data Protection Law (Law 1581 of 2012) you already have
Egypt Personal Data Protection Law (Law No. 151 of 2020) already covers about 56% of Colombia Data Protection Law (Law 1581 of 2012), leaving
12 of 27 controls as genuinely new work.
Already covered 0
Likely covered 15
New work 12
No control in Egypt Personal Data Protection Law (Law No. 151 of 2020)
maps directly to one in Colombia Data Protection Law (Law 1581 of 2012). 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 Egypt Personal Data Protection Law (Law No. 151 of 2020) reaches these. This is the list to scope.
CO-L1581-A12Duty to Inform the Data Subject (Privacy Notice)
CO-L1581-A14Consultations (Access Requests)
CO-L1581-A15Complaints (Reclamos)
CO-L1581-A17Duties of Controllers (Responsables)
CO-L1581-A18Duties of Processors (Encargados)
CO-L1581-A19Data Protection Authority (SIC)
CO-L1581-A2Scope of Application
CO-L1581-A21Functions of the SIC
CO-L1581-A25National Database Registry (RNBD)
CO-L1581-A27Binding Corporate Rules
CO-L1581-A8Data Subject Rights (Habeas Data)
Show the 15 you already have
CO-L1581-A10Cases Not Requiring Authorization
CO-L1581-A13Persons to Whom Information May Be Disclosed
CO-L1581-A26Prohibition on International Transfers
CO-L1581-A4-ACCESOPrinciple of Restricted Access and Circulation
CO-L1581-A4-CONFIDPrinciple of Confidentiality
CO-L1581-A4-FINALIDADPrinciple of Purpose
CO-L1581-A4-LEGALIDADPrinciple of Legality
CO-L1581-A4-LIBERTADPrinciple of Freedom (Consent)
CO-L1581-A4-SEGURIDADPrinciple of Security
CO-L1581-A4-TRANSPARENCIAPrinciple of Transparency
CO-L1581-A4-VERACIDADPrinciple of Veracity and Quality
CO-L1581-A5Sensitive Data Definition
CO-L1581-A6Processing of Sensitive Data
CO-L1581-A7Children's and Adolescents' Data
CO-L1581-A9Authorization of the Data Subject
How this is calculated
Already covered means a mapping runs from a control in Egypt Personal Data Protection Law (Law No. 151 of 2020) 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