13% of Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018) you already have
Bahrain PDPL already covers about 13% of Latvia Personal Data Processing Law (Fizisko personu datu apstrades likums, 2018), leaving
7 of 8 controls as genuinely new work.
Already covered 1
Likely covered 0
New work 7
What is genuinely new work
Nothing in Bahrain PDPL reaches these. This is the list to scope.
LV-PDPL-Childrens-Consent-Age-13-Section-16-Digital-Services-Lower-Than-GDPR-Default-16Latvia PDPL Children Consent Age 13 + S.16 + Digital Services + Lower Than GDPR Default 16
LV-PDPL-Cross-Border-Transfer-S60-Cooperation-Authorities-S65-Administrative-Liability-S50-Transitional-S68-EDPB-LEDLatvia PDPL Cross-Border + S.60 + Cooperation + S.65 + Administrative Liability + Transitional
LV-PDPL-DPO-Data-Protection-Officer-Designation-Qualifications-Notification-S18-S21Latvia PDPL DPO + Designation + Qualifications + Notification + S.18 + S.21
LV-PDPL-Lawful-Basis-Public-Interest-Tasks-S5-Sensitive-Special-Categories-Genetic-Biometric-S30-Purpose-Limit-Sec20-Data-Minim-Sec21Latvia PDPL Lawful Basis + S.5 Public Interest + S.30 Special Categories + Purpose Limitation
LV-PDPL-Scope-PersonalDataProcessingLaw-Saeima-21-June-2018-Effective-5-July-2018-GDPR-Implementation-DVILatvia PDPL Scope + Saeima 21 June 2018 + Effective 5 July 2018 + GDPR Implementation + DVI
LV-PDPL-Special-Contexts-Journalistic-Academic-Artistic-Literary-S10-Personal-ID-Numbers-S9-Video-Surveillance-S25-Direct-Marketing-S28Latvia PDPL Special Contexts + Journalism + S.10 + Personal ID Numbers + Video Surveillance + Direct Marketing
LV-PDPL-Supervisory-Authority-Data-State-Inspectorate-DVI-Powers-S35-Codes-of-Conduct-S55-Certification-S45-Complaints-S40Latvia PDPL Supervisory Authority + DVI Powers + S.35 + Codes of Conduct + Certification + Complaints
Show the 1 you already have
LV-PDPL-Data-Subject-Rights-Access-Correction-Erasure-Restriction-Portability-Objection-Sec18-Sec38Latvia PDPL Data Subject Rights + Access + Correction + Erasure + Portability + Section 18 + 38
How this is calculated
Already covered means a mapping runs from a control in Bahrain PDPL 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