38% of Russia Federal Law on Personal Data (152-FZ) you already have
Azure Security Benchmark already covers about 38% of Russia Federal Law on Personal Data (152-FZ), leaving
5 of 8 controls as genuinely new work.
Already covered 0
Likely covered 3
New work 5
No control in Azure Security Benchmark
maps directly to one in Russia Federal Law on Personal Data (152-FZ). 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 Azure Security Benchmark reaches these. This is the list to scope.
RUSPD-3Data Subject Rights (Access, Correction, Object, Block/Destroy)
RUSPD-5Security of Processing, Confidentiality, FSB/FSTEC Requirements
RUSPD-6Cross-Border Transfer and Data Localization (Article 18.5)
RUSPD-7Roskomnadzor Registration, Operator Notification, Governance
RUSPD-8Breach Notification, RKN Inspections, Sanctions
Show the 3 you already have
RUSPD-1Scope, Definitions, Principles under 152-FZ
RUSPD-2Lawful Basis, Consent, Notice
RUSPD-4Special Categories, Biometric Data
How this is calculated
Already covered means a mapping runs from a control in Azure Security Benchmark 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