14% of China Cybersecurity Law (CSL) you already have
Canadian PIPEDA already covers about 14% of China Cybersecurity Law (CSL), leaving
19 of 22 controls as genuinely new work.
Already covered 0
Likely covered 3
New work 19
No control in Canadian PIPEDA
maps directly to one in China Cybersecurity Law (CSL). 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 Canadian PIPEDA reaches these. This is the list to scope.
CSL-Art1Scope, Cyberspace Sovereignty and Definitions (Art. 1-2, 76)
CSL-Art2025AI2025 Amendment - AI Governance and Development
CSL-Art21Multi-Level Protection Scheme (MLPS) - Art. 21
CSL-Art22Security of Network Products and Services - Art. 22
CSL-Art23Critical Network Equipment Certification - Art. 23
CSL-Art24Real-Name Registration - Art. 24
CSL-Art27Prohibition on Illegal Network Intrusion - Art. 27
CSL-Art31Critical Information Infrastructure Designation - Art. 31
CSL-Art34CII Operator Security Obligations - Art. 34
CSL-Art35CII Procurement Security Review - Art. 35
CSL-Art37CII Data Localization and Cross-Border Assessment - Art. 37
CSL-Art38CII Annual Security Inspection - Art. 38
CSL-Art43Right to Correction and Deletion - Art. 43
CSL-Art47Content Management Obligations - Art. 47
CSL-Art49Complaints and Reporting Mechanism - Art. 49
CSL-Art51Cybersecurity Monitoring and Early Warning - Art. 51
CSL-Art56Cybersecurity Risk Talks (Regulatory Interview) - Art. 56
CSL-Art59Penalties for Network Operators - Art. 59-68
CSL-Art66Penalties for Cross-Border / Localization Violations - Art. 66
Show the 3 you already have
CSL-Art40Confidentiality of User Information - Art. 40
CSL-Art41Lawful Collection of Personal Information - Art. 41
CSL-Art42Personal Information Protection and Breach Handling - Art. 42
How this is calculated
Already covered means a mapping runs from a control in Canadian PIPEDA 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