Framework overlap

Does NIST SP 800-171A cover Azerbaijan Law on Personal Data (2010)?

You hold NIST SP 800-171A and have been told to do Azerbaijan Law on Personal Data (2010). Here is how much overlaps, control by control.

33% of Azerbaijan Law on Personal Data (2010) you already have

NIST SP 800-171A already covers about 33% of Azerbaijan Law on Personal Data (2010), leaving 10 of 15 controls as genuinely new work.

Already covered 0 Likely covered 5 New work 10

No control in NIST SP 800-171A maps directly to one in Azerbaijan Law on Personal Data (2010). 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 NIST SP 800-171A reaches these. This is the list to scope.

AZ-DPA-1
Article 1 - Purpose of the Law
AZ-DPA-10
Article 10 - Responsibilities of the operator
AZ-DPA-11
Article 11 - Characteristics of personal data information systems
AZ-DPA-13
Article 14 - Security requirements
AZ-DPA-3
Article 3 - Legislation in the field of personal data
AZ-DPA-4
Article 4 - Principles of collection and processing
AZ-DPA-5
Article 5 - Legal regime and categories of personal data
AZ-DPA-7
Article 7 - Rights of the data subject
AZ-DPA-8
Article 8 - Consent to collection and processing
AZ-DPA-9
Article 9 - Processing without consent
Show the 5 you already have
AZ-DPA-12
Article 13 - Cross-border transfer
AZ-DPA-14
Article 16 - Liability for violations
AZ-DPA-15
Article 17 - Dispute resolution
AZ-DPA-2
Article 2 - Basic Concepts
AZ-DPA-6
Article 6 - State regulation in personal data protection

How this is calculated

Already covered means a mapping runs from a control in NIST SP 800-171A 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