Framework overlap

Does GDPR cover Botswana Data Protection Act (2024)?

You hold GDPR and have been told to do Botswana Data Protection Act (2024). Here is how much overlaps, control by control.

44% of Botswana Data Protection Act (2024) you already have

GDPR already covers about 44% of Botswana Data Protection Act (2024), leaving 18 of 32 controls as genuinely new work.

Already covered 14 Likely covered 0 New work 18

What is genuinely new work

Nothing in GDPR reaches these. This is the list to scope.

BW-DPA-s10
Right of access to information by Commissioner
BW-DPA-s11
Commission to seek rectification
BW-DPA-s12
Order to delete personal data
BW-DPA-s18
Processing for direct marketing
BW-DPA-s2
Interpretation
BW-DPA-s28
Information for data subject
BW-DPA-s3
Application
BW-DPA-s30
Rights of data subject
BW-DPA-s38
Mandatory notification and registration
BW-DPA-s4
Establishment of the Information and Data Protection Commission
BW-DPA-s41
Investigation by Commissioner
BW-DPA-s42
Complaints
BW-DPA-s43
Enforcement notice
BW-DPA-s45
Appeals Tribunal
BW-DPA-s5
Functions and powers of Commission
BW-DPA-s51
Offences and penalties
BW-DPA-s52
Compensation for damages
BW-DPA-s7
Powers of the Commissioner
Show the 14 you already have
BW-DPA-s14
Requirements for processing
BW-DPA-s15
Limitation to processing
BW-DPA-s16
Criteria for processing
BW-DPA-s17
Processing for other purposes
BW-DPA-s19
Revocation of consent
BW-DPA-s20
Prohibition for processing of sensitive personal data
BW-DPA-s21
Safeguards for processing sensitive personal data
BW-DPA-s25
Processing of genetic and biometric data
BW-DPA-s32
Safeguards for processing of personal data
BW-DPA-s33
Notification of breach to safeguards
BW-DPA-s34
Obligation to notify Commissioner
BW-DPA-s36
Data protection representative
BW-DPA-s48
Transborder flow of personal data
BW-DPA-s49
Transfer of personal data to a third country

How this is calculated

Already covered means a mapping runs from a control in GDPR 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