Framework overlap

Does Angola Personal Data Protection Law (Law No. 22/11) cover Argentina Law 25.326 (Personal Data Protection Law)?

You hold Angola Personal Data Protection Law (Law No. 22/11) and have been told to do Argentina Law 25.326 (Personal Data Protection Law). Here is how much overlaps, control by control.

38% of Argentina Law 25.326 (Personal Data Protection Law) you already have

Angola Personal Data Protection Law (Law No. 22/11) already covers about 38% of Argentina Law 25.326 (Personal Data Protection Law), leaving 21 of 34 controls as genuinely new work.

Already covered 0 Likely covered 13 New work 21

No control in Angola Personal Data Protection Law (Law No. 22/11) maps directly to one in Argentina Law 25.326 (Personal Data Protection Law). 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 Angola Personal Data Protection Law (Law No. 22/11) reaches these. This is the list to scope.

AR-25326-AAIP-DPIA
Data Protection Impact Assessment Recommendation
AR-25326-AAIP-DPO
Data Protection Officer (DPO) Recommendation
AR-25326-ART14-ACCESS
Right of Access
AR-25326-ART15-CONTENT
Content of Access Response
AR-25326-ART16-RECTIFICATION
Right of Rectification, Update, Suppression and Confidentiality
AR-25326-ART17-OPPOSITION
Right of Opposition and Refusal Exceptions
AR-25326-ART2
Scope and Definitions
AR-25326-ART20-ADM
Automated Decisions
AR-25326-ART21-REGISTRATION
Database Registration with AAIP
AR-25326-ART22-PUBLIC-DB
Public Database Operation
AR-25326-ART26-CREDIT
Credit Information Database Rules
AR-25326-ART27-MARKETING
Direct Marketing and Opt-Out
AR-25326-ART29-AAIP
AAIP Authority and Powers
AR-25326-ART31-ADM-SANCTIONS
Administrative Sanctions
AR-25326-ART32-CRIMINAL
Criminal Penalties
AR-25326-ART5-EXCEPTIONS
Consent Exceptions
AR-25326-ART6-NOTICE
Information Duty at Collection
AR-25326-ART7-CRIMINAL
Criminal Records Restrictions
AR-25326-EU-ADEQUACY
EU Adequacy Status Maintenance
AR-25326-HABEAS-DATA
Habeas Data Judicial Remedy
AR-25326-MODERNIZATION
Pending Modernization Bill 2023
Show the 13 you already have
AR-25326-AAIP-BREACH
Personal Data Breach Notification
AR-25326-ART11-DISCLOSURE
Disclosure to Third Parties
AR-25326-ART12-ADEQUACY
AAIP Adequacy List Reliance
AR-25326-ART12-XBORDER
Cross-Border Transfer Restrictions
AR-25326-ART4-PURPOSE
Lawful Purpose and Purpose Limitation
AR-25326-ART4-QUALITY
Data Quality Principle
AR-25326-ART4-RETENTION
Retention Limitation
AR-25326-ART5-CONSENT
Consent as Default Lawful Basis
AR-25326-ART7-SENSITIVE
Sensitive Data Restrictions
AR-25326-ART8-HEALTH
Health Data Special Rules
AR-25326-ART9-CONFIDENTIALITY
Confidentiality Duty
AR-25326-ART9-SECURITY
Security Measures Obligation
AR-25326-PROCESSOR
Processor Agreements (Art 25)

How this is calculated

Already covered means a mapping runs from a control in Angola Personal Data Protection Law (Law No. 22/11) 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