Framework overlap

Does API 1164 cover NIST SP 800-122?

You hold API 1164 and have been told to do NIST SP 800-122. Here is how much overlaps, control by control.

75% of NIST SP 800-122 you already have

API 1164 already covers about 75% of NIST SP 800-122, leaving 2 of 8 controls as genuinely new work.

Already covered 3 Likely covered 3 New work 2

What is genuinely new work

Nothing in API 1164 reaches these. This is the list to scope.

NISTSP122-1
Scope, PII Definition, and PII Confidentiality Impact Analysis
NISTSP122-2
PII Privacy Notice, Consent, and Lawful Processing
Show the 6 you already have
NISTSP122-5
PII Security Controls - Encryption, Access Control, Storage, Audit
NISTSP122-6
PII Breach Response and Incident Handling
NISTSP122-8
Continuous Monitoring, Training, and Privacy Programme Governance
NISTSP122-3
PII Data Subject Rights and Automated Decision-Making
NISTSP122-4
PII Minimisation, Purpose Limitation, and Pseudonymisation
NISTSP122-7
PII Sharing, Cross-Border Transfers, and Third-Party Agreements

How this is calculated

Already covered means a mapping runs from a control in API 1164 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