41% of Botswana Data Protection Act (2024) you already have
Bermuda Personal Information Protection Act 2016 (PIPA) already covers about 41% of Botswana Data Protection Act (2024), leaving
19 of 32 controls as genuinely new work.
Already covered 0
Likely covered 13
New work 19
No control in Bermuda Personal Information Protection Act 2016 (PIPA)
maps directly to one in Botswana Data Protection Act (2024). 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 Bermuda Personal Information Protection Act 2016 (PIPA) reaches these. This is the list to scope.
BW-DPA-s10Right of access to information by Commissioner
BW-DPA-s11Commission to seek rectification
BW-DPA-s12Order to delete personal data
BW-DPA-s18Processing for direct marketing
BW-DPA-s19Revocation of consent
BW-DPA-s28Information for data subject
BW-DPA-s30Rights of data subject
BW-DPA-s36Data protection representative
BW-DPA-s38Mandatory notification and registration
BW-DPA-s4Establishment of the Information and Data Protection Commission
BW-DPA-s41Investigation by Commissioner
BW-DPA-s43Enforcement notice
BW-DPA-s45Appeals Tribunal
BW-DPA-s5Functions and powers of Commission
BW-DPA-s51Offences and penalties
BW-DPA-s52Compensation for damages
BW-DPA-s7Powers of the Commissioner
Show the 13 you already have
BW-DPA-s14Requirements for processing
BW-DPA-s15Limitation to processing
BW-DPA-s16Criteria for processing
BW-DPA-s17Processing for other purposes
BW-DPA-s20Prohibition for processing of sensitive personal data
BW-DPA-s21Safeguards for processing sensitive personal data
BW-DPA-s25Processing of genetic and biometric data
BW-DPA-s32Safeguards for processing of personal data
BW-DPA-s33Notification of breach to safeguards
BW-DPA-s34Obligation to notify Commissioner
BW-DPA-s48Transborder flow of personal data
BW-DPA-s49Transfer of personal data to a third country
How this is calculated
Already covered means a mapping runs from a control in Bermuda Personal Information Protection Act 2016 (PIPA) 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