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