Framework overlap

Does NIST Cybersecurity Framework 2.0 cover CISA Industrial Control Systems (ICS) Security Guidance?

You hold NIST Cybersecurity Framework 2.0 and have been told to do CISA Industrial Control Systems (ICS) Security Guidance. Here is how much overlaps, control by control.

100% of CISA Industrial Control Systems (ICS) Security Guidance you already have

NIST Cybersecurity Framework 2.0 already covers about 100% of CISA Industrial Control Systems (ICS) Security Guidance, leaving 0 of 16 controls as genuinely new work.

Already covered 16 Likely covered 0 New work 0

What is genuinely new work

Nothing in NIST Cybersecurity Framework 2.0 reaches these. This is the list to scope.

Nothing. Every control is reached.

Show the 16 you already have
CISA-ICS-7S-1
Implement Application Allowlisting (Whitelisting)
CISA-ICS-7S-2
Ensure Proper Configuration and Patch Management
CISA-ICS-7S-3
Reduce Your Attack Surface Area
CISA-ICS-7S-4
Build a Defendable Environment
CISA-ICS-7S-5
Manage Authentication
CISA-ICS-7S-6
Implement Secure Remote Access
CISA-ICS-7S-7
Monitor and Respond
CISA-ICS-DID-21
Risk Management for ICS
CISA-ICS-DID-22
Asset Inventory and Risk Characterization
CISA-ICS-DID-23
Physical Security
CISA-ICS-DID-24
ICS Network Architecture
CISA-ICS-DID-25
Security Architecture (Perimeter, Firewalls, Diodes, Access)
CISA-ICS-DID-26
Host Security (Patch, Field Devices, Virtual Machines)
CISA-ICS-DID-27
Security Monitoring (IDS/IPS, Logging, SIEM)
CISA-ICS-DID-28
Vendor Management and Supply Chain Security
CISA-ICS-DID-29
The Human Element (Awareness and Training)

How this is calculated

Already covered means a mapping runs from a control in NIST Cybersecurity Framework 2.0 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