88% of NIST SP 800-92 you already have
PCI P2PE already covers about 88% of NIST SP 800-92, leaving
1 of 8 controls as genuinely new work.
Already covered 0
Likely covered 7
New work 1
No control in PCI P2PE
maps directly to one in NIST SP 800-92. 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.
NISTSP92-8Integration with NIST SP 800-53 AU Family, SP 800-137 ConMon, SP 800-61 IR, and Maturity
Show the 7 you already have
NISTSP92-1Log Management Programme, Policy, Roles, and Operational Runbooks
NISTSP92-2Log Generation: OS, Application, Security Tools, Network, Cloud, Required Event Content
NISTSP92-3Log Infrastructure: Architecture, Centralisation, Transport Security, SIEM Governance
NISTSP92-4Log Management: Time Synchronisation, Parsing, Storage, Integrity, Access Control
NISTSP92-5Log Analysis: Correlation, Baselining, Anomaly Detection, Alerting, Manual Review
NISTSP92-6Log Retention: Policy, Tiered Storage, Backup, Secure Disposal, Legal Hold
NISTSP92-7Privacy in Logs, Sensitive Content Handling, Cloud and SaaS Log Considerations
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