29% of Bermuda Personal Information Protection Act 2016 (PIPA) you already have
China Personal Information Protection Law (PIPL) already covers about 29% of Bermuda Personal Information Protection Act 2016 (PIPA), leaving
17 of 24 controls as genuinely new work.
Already covered 0
Likely covered 7
New work 17
No control in China Personal Information Protection Law (PIPL)
maps directly to one in Bermuda Personal Information Protection Act 2016 (PIPA). 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 China Personal Information Protection Law (PIPL) reaches these. This is the list to scope.
BM-PIPA-12Integrity of personal information
BM-PIPA-13Security safeguards
BM-PIPA-17Access to personal information
BM-PIPA-18Access to medical records
BM-PIPA-19Rectification, blocking, erasure and destruction
BM-PIPA-20Procedure for making a request
BM-PIPA-21Compensation for financial loss or distress
BM-PIPA-26The Privacy Commissioner: establishment and powers
BM-PIPA-32Codes of practice
BM-PIPA-38Reviews and complaints
BM-PIPA-44Commissioner's orders and judicial review
BM-PIPA-5Responsibility and compliance
Show the 7 you already have
BM-PIPA-10Purpose limitation
BM-PIPA-11Proportionality
BM-PIPA-14Breach of security
BM-PIPA-15Transfer of personal information to an overseas third party
BM-PIPA-16Personal information about children in the information society
BM-PIPA-6Conditions for using personal information
BM-PIPA-7Sensitive personal information
How this is calculated
Already covered means a mapping runs from a control in China Personal Information Protection Law (PIPL) 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