60% of Protective Security Policy Framework (PSPF) Release 2024 you already have
PCI P2PE already covers about 60% of Protective Security Policy Framework (PSPF) Release 2024, leaving
2 of 5 controls as genuinely new work.
Already covered 0
Likely covered 3
New work 2
No control in PCI P2PE
maps directly to one in Protective Security Policy Framework (PSPF) Release 2024. 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.
PSPF24-3Personnel Security and Vetting
PSPF24-5Information and Cyber Incidents
Show the 3 you already have
PSPF24-1Security Culture, Governance, Risk Management
PSPF24-2Information Security, Cybersecurity Maturity, Essential Eight
PSPF24-4Physical Security
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