75% of NIST SP 800-122 you already have
PCI P2PE already covers about 75% of NIST SP 800-122, leaving
2 of 8 controls as genuinely new work.
Already covered 0
Likely covered 6
New work 2
No control in PCI P2PE
maps directly to one in NIST SP 800-122. 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 PCI P2PE reaches these. This is the list to scope.
NISTSP122-1Scope, PII Definition, and PII Confidentiality Impact Analysis
NISTSP122-2PII Privacy Notice, Consent, and Lawful Processing
Show the 6 you already have
NISTSP122-3PII Data Subject Rights and Automated Decision-Making
NISTSP122-4PII Minimisation, Purpose Limitation, and Pseudonymisation
NISTSP122-5PII Security Controls - Encryption, Access Control, Storage, Audit
NISTSP122-6PII Breach Response and Incident Handling
NISTSP122-7PII Sharing, Cross-Border Transfers, and Third-Party Agreements
NISTSP122-8Continuous Monitoring, Training, and Privacy Programme Governance
How this is calculated
Already covered means a mapping runs from a control in PCI P2PE 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