72% of Armenia Law on Protection of Personal Data (2015) you already have
GDPR already covers about 72% of Armenia Law on Protection of Personal Data (2015), leaving
5 of 18 controls as genuinely new work.
Already covered 13
Likely covered 0
New work 5
What is genuinely new work
Nothing in GDPR reaches these. This is the list to scope.
AM-DPA-04Data Subject Rights Fulfilment
AM-DPA-05Notification to Personal Data Protection Agency
AM-DPA-08Information to Data Subjects at Collection
AM-DPA-14Automated Decision-Making Safeguards
AM-DPA-18Direct Marketing Restrictions
Show the 13 you already have
AM-DPA-01Lawful Basis for Processing
AM-DPA-02Data Subject Consent
AM-DPA-03Special Category Data Restrictions
AM-DPA-06Cross-Border Transfer Conditions
AM-DPA-07Processor and Sub-Processor Oversight
AM-DPA-09Data Minimisation and Purpose Limitation
AM-DPA-10Retention and Deletion
AM-DPA-11Security of Processing
AM-DPA-12Records of Processing Activities
AM-DPA-13Children and Minors
AM-DPA-15Breach Response and Notification
AM-DPA-16Staff Training and Confidentiality
AM-DPA-17PDPA Inspections and Cooperation
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