Framework overlap

Does CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 cover Armenia Law on Protection of Personal Data (2015)?

You hold CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 and have been told to do Armenia Law on Protection of Personal Data (2015). Here is how much overlaps, control by control.

22% of Armenia Law on Protection of Personal Data (2015) you already have

CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 already covers about 22% of Armenia Law on Protection of Personal Data (2015), leaving 14 of 18 controls as genuinely new work.

Already covered 1 Likely covered 3 New work 14

What is genuinely new work

Nothing in CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 reaches these. This is the list to scope.

AM-DPA-01
Lawful Basis for Processing
AM-DPA-02
Data Subject Consent
AM-DPA-03
Special Category Data Restrictions
AM-DPA-04
Data Subject Rights Fulfilment
AM-DPA-05
Notification to Personal Data Protection Agency
AM-DPA-06
Cross-Border Transfer Conditions
AM-DPA-07
Processor and Sub-Processor Oversight
AM-DPA-08
Information to Data Subjects at Collection
AM-DPA-09
Data Minimisation and Purpose Limitation
AM-DPA-11
Security of Processing
AM-DPA-12
Records of Processing Activities
AM-DPA-13
Children and Minors
AM-DPA-14
Automated Decision-Making Safeguards
AM-DPA-18
Direct Marketing Restrictions
Show the 4 you already have
AM-DPA-10
Retention and Deletion
AM-DPA-15
Breach Response and Notification
AM-DPA-16
Staff Training and Confidentiality
AM-DPA-17
PDPA Inspections and Cooperation

How this is calculated

Already covered means a mapping runs from a control in CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 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