Framework overlap

Does ENISA Data Protection Engineering cover African Union Malabo Convention?

You hold ENISA Data Protection Engineering and have been told to do African Union Malabo Convention. Here is how much overlaps, control by control.

21% of African Union Malabo Convention you already have

ENISA Data Protection Engineering already covers about 21% of African Union Malabo Convention, leaving 22 of 28 controls as genuinely new work.

Already covered 0 Likely covered 6 New work 22

No control in ENISA Data Protection Engineering maps directly to one in African Union Malabo Convention. 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 ENISA Data Protection Engineering reaches these. This is the list to scope.

MALABO-Art11
Preconditions for Personal Data Processing
MALABO-Art12
National Personal Data Protection Authority
MALABO-Art13-P5
Principle of Transparency
MALABO-Art14
Sensitive Data and Specific Processing
MALABO-Art16
Data Subject Right to Information
MALABO-Art17
Data Subject Right of Access
MALABO-Art18
Data Subject Right to Object
MALABO-Art19
Data Subject Right of Rectification and Erasure
MALABO-Art2
Scope of Electronic Commerce
MALABO-Art23
Transborder Flows of Personal Data
MALABO-Art24
National Cyber Security Framework
MALABO-Art25
National Cyber Security Policy and Strategy
MALABO-Art26
Cyber Security Governance and Leadership
MALABO-Art27
Protection of Critical Information Infrastructure
MALABO-Art28
International Cooperation and Culture of Cyber Security
MALABO-Art29
Offences Against Computer Systems and Data
MALABO-Art3
Electronic Advertising Obligations
MALABO-Art30
Computer Content and Property Offences
MALABO-Art31
Criminal Sanctions and Corporate Liability
MALABO-Art5
Contractual Obligations in Electronic Form
MALABO-Art7
Security of Electronic Transactions and Electronic Signatures
MALABO-Art9
Scope of Personal Data Protection
Show the 6 you already have
MALABO-Art13-P1
Principle of Consent and Legitimacy
MALABO-Art13-P2
Principle of Lawfulness and Fairness
MALABO-Art13-P3
Principle of Purpose, Relevance and Storage Limitation
MALABO-Art13-P4
Principle of Accuracy
MALABO-Art13-P6
Principle of Confidentiality and Security
MALABO-Art20
Confidentiality and Security Obligations of the Controller

How this is calculated

Already covered means a mapping runs from a control in ENISA Data Protection Engineering 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