Framework overlap

Does ENISA Data Protection Engineering cover Egypt Personal Data Protection Law (Law No. 151 of 2020)?

You hold ENISA Data Protection Engineering and have been told to do Egypt Personal Data Protection Law (Law No. 151 of 2020). Here is how much overlaps, control by control.

8% of Egypt Personal Data Protection Law (Law No. 151 of 2020) you already have

ENISA Data Protection Engineering already covers about 8% of Egypt Personal Data Protection Law (Law No. 151 of 2020), leaving 44 of 48 controls as genuinely new work.

Already covered 0 Likely covered 4 New work 44

No control in ENISA Data Protection Engineering maps directly to one in Egypt Personal Data Protection Law (Law No. 151 of 2020). 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.

EGY-PDPL-Art.10
Procedures for disclosure of personal data
EGY-PDPL-Art.11
Determinative effect of digital evidence
EGY-PDPL-Art.12
Processing of sensitive personal data and children's data
EGY-PDPL-Art.13
DPO security duties for sensitive personal data
EGY-PDPL-Art.14
Cross-border transfer adequacy and licensing
EGY-PDPL-Art.15
Derogations from the cross-border protection level
EGY-PDPL-Art.16
Disclosure to controllers/processors abroad under licence
EGY-PDPL-Art.17
Conditions for direct electronic marketing
EGY-PDPL-Art.18
Obligations of the direct-marketing sender
EGY-PDPL-Art.19
Establishment and mandate of the Personal Data Protection Centre
EGY-PDPL-Art.20
Board of Directors of the Centre
EGY-PDPL-Art.21
Competencies of the Centre's Board
EGY-PDPL-Art.22
Board meetings and resolutions
EGY-PDPL-Art.23
Chief Executive Officer of the Centre
EGY-PDPL-Art.24
Confidentiality obligation of Board members and Centre staff
EGY-PDPL-Art.25
International cooperation by the Centre
EGY-PDPL-Art.26
Types of licenses, permits and certifications
EGY-PDPL-Art.27
Procedures for issuing licenses, permits and certifications
EGY-PDPL-Art.28
Amendment of license and permit conditions
EGY-PDPL-Art.29
Cancellation of licenses, permits and certifications
EGY-PDPL-Art.30
Administrative sanctions
EGY-PDPL-Art.31
Budget and financial resources of the Centre
EGY-PDPL-Art.32
Requests by data subjects
EGY-PDPL-Art.33
Complaints to the Centre
EGY-PDPL-Art.34
Judicial control powers
EGY-PDPL-Art.35
General penalty provision
EGY-PDPL-Art.36
Penalty for unauthorised processing
EGY-PDPL-Art.37
Penalty for denying rights and unlawful collection
EGY-PDPL-Art.38
Penalty for breach of controller/processor obligations
EGY-PDPL-Art.39
Penalty for failure to appoint a DPO
EGY-PDPL-Art.40
Penalty for DPO failure of duties
EGY-PDPL-Art.41
Penalty for unlawful sensitive-data processing
EGY-PDPL-Art.42
Penalty for unlawful cross-border transfer
EGY-PDPL-Art.43
Penalty for marketing violations
EGY-PDPL-Art.44
Penalty for breach of Centre confidentiality
EGY-PDPL-Art.45
Penalty for license/permit/certification violations
EGY-PDPL-Art.46
Penalty for obstructing Centre officers
EGY-PDPL-Art.47
De facto manager and juristic-person liability
EGY-PDPL-Art.48
Publication of sentences and recidivism
EGY-PDPL-Art.49
Settlement and reconciliation
EGY-PDPL-Art.6
Lawful bases for processing
EGY-PDPL-Art.7
Personal data infringement (breach) notification
EGY-PDPL-Art.8
Appointment of the Data Protection Officer
EGY-PDPL-Art.9
Data Protection Officer obligations
Show the 4 you already have
EGY-PDPL-Art.2
Data subject rights and consent requirement
EGY-PDPL-Art.3
Conditions for lawful collection and processing
EGY-PDPL-Art.4
Controller obligations
EGY-PDPL-Art.5
Processor obligations

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