63% of NIST SP 800-61 you already have
PCI PIN Security already covers about 63% of NIST SP 800-61, leaving
3 of 8 controls as genuinely new work.
Already covered 0
Likely covered 5
New work 3
No control in PCI PIN Security
maps directly to one in NIST SP 800-61. 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 PIN Security reaches these. This is the list to scope.
NISTSP61-6Post-Incident Activity: Lessons Learned, Evidence Retention, Metrics
NISTSP61-7Coordination, Information Sharing, Privacy and Breach Response
NISTSP61-8Cloud, Third-Party, and Supply-Chain Incident Handling and Threat Intelligence Integration
Show the 5 you already have
NISTSP61-1Incident Response Policy, Plan, and Procedures
NISTSP61-2Computer Security Incident Response Team (CSIRT) Structure and Staffing
NISTSP61-3Preparation: Communications, Toolkits, Training, Exercises, Threat Intelligence
NISTSP61-4Detection and Analysis: Sources, Triage, Categorisation, Prioritisation
NISTSP61-5Containment, Eradication, and Recovery
How this is calculated
Already covered means a mapping runs from a control in PCI PIN Security 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