Framework overlap

Does API 1164 cover NIST SP 800-61?

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

63% of NIST SP 800-61 you already have

API 1164 already covers about 63% of NIST SP 800-61, leaving 3 of 8 controls as genuinely new work.

Already covered 2 Likely covered 3 New work 3

What is genuinely new work

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

NISTSP61-6
Post-Incident Activity: Lessons Learned, Evidence Retention, Metrics
NISTSP61-7
Coordination, Information Sharing, Privacy and Breach Response
NISTSP61-8
Cloud, Third-Party, and Supply-Chain Incident Handling and Threat Intelligence Integration
Show the 5 you already have
NISTSP61-4
Detection and Analysis: Sources, Triage, Categorisation, Prioritisation
NISTSP61-5
Containment, Eradication, and Recovery
NISTSP61-1
Incident Response Policy, Plan, and Procedures
NISTSP61-2
Computer Security Incident Response Team (CSIRT) Structure and Staffing
NISTSP61-3
Preparation: Communications, Toolkits, Training, Exercises, Threat Intelligence

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