Framework overlap

Does ENISA Data Protection Engineering cover Costa Rica Personal Data Protection Law (Law No. 8968) as amended by Executive Decree No. 42089-MGP?

You hold ENISA Data Protection Engineering and have been told to do Costa Rica Personal Data Protection Law (Law No. 8968) as amended by Executive Decree No. 42089-MGP. Here is how much overlaps, control by control.

13% of Costa Rica Personal Data Protection Law (Law No. 8968) as amended by Executive Decree No. 42089-MGP you already have

ENISA Data Protection Engineering already covers about 13% of Costa Rica Personal Data Protection Law (Law No. 8968) as amended by Executive Decree No. 42089-MGP, leaving 21 of 24 controls as genuinely new work.

Already covered 0 Likely covered 3 New work 21

No control in ENISA Data Protection Engineering maps directly to one in Costa Rica Personal Data Protection Law (Law No. 8968) as amended by Executive Decree No. 42089-MGP. 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.

CR-8968-Art.1
Objetivo y fin (autodeterminacion informativa)
CR-8968-Art.11
Deber de confidencialidad
CR-8968-Art.12
Protocolos de actuacion
CR-8968-Art.13
Garantias efectivas
CR-8968-Art.14
Transferencia de datos personales (regla general)
CR-8968-Art.15
Agencia de Proteccion de Datos de los Habitantes (Prodhab)
CR-8968-Art.16
Atribuciones de la Prodhab
CR-8968-Art.2
Ambito de aplicacion
CR-8968-Art.21
Registro de archivos y bases de datos
CR-8968-Art.22
Divulgacion del registro
CR-8968-Art.24
Denuncia
CR-8968-Art.25
Tramite de las denuncias
CR-8968-Art.27
Procedimiento sancionatorio
CR-8968-Art.28
Sanciones (multas)
CR-8968-Art.29-31
Tipificacion de faltas (leves, graves, gravisimas)
CR-8968-Art.3
Definiciones
CR-8968-Art.33
Canon por regulacion y administracion de bases de datos
CR-8968-Art.4
Principio de autodeterminacion informativa
CR-8968-Art.7
Derechos de acceso, rectificacion, supresion y cesion (ARCO)
CR-8968-Art.8
Excepciones a la autodeterminacion informativa
CR-8968-Art.9
Categorias particulares de los datos (datos sensibles)
Show the 3 you already have
CR-8968-Art.10
Seguridad de los datos
CR-8968-Art.5
Principio de consentimiento informado
CR-8968-Art.6
Principio de calidad de la informacion

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