63% of NIST SP 800-82 Revision 3: Guide to Industrial Control Systems (ICS) Security you already have
CWE Top 25 Most Dangerous Software Weaknesses (2024) already covers about 63% of NIST SP 800-82 Revision 3: Guide to Industrial Control Systems (ICS) Security, leaving
3 of 8 controls as genuinely new work.
Already covered 0
Likely covered 5
New work 3
No control in CWE Top 25 Most Dangerous Software Weaknesses (2024)
maps directly to one in NIST SP 800-82 Revision 3: Guide to Industrial Control Systems (ICS) Security. 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 CWE Top 25 Most Dangerous Software Weaknesses (2024) reaches these. This is the list to scope.
NISTSP82-3OT Network Architecture: Zoned Architecture, Conduits, Segmentation, and Defence-in-Depth
NISTSP82-6OT Audit, Monitoring, Anomaly Detection, and OT-Specific SOC
NISTSP82-8OT Supply Chain Security, Asset Lifecycle, and Physical Security
Show the 5 you already have
NISTSP82-1OT Security Program Governance, Policy, Roles, and Safety-Security Integration
NISTSP82-2OT Risk Assessment and Threat/Vulnerability Identification
NISTSP82-4OT Access Control, Identity, Authentication, and Remote Access
NISTSP82-5OT Configuration Management, Patching, Vulnerability Management, and Malware Protection
NISTSP82-7OT Incident Response, Forensics, Recovery, and Continuity
How this is calculated
Already covered means a mapping runs from a control in CWE Top 25 Most Dangerous Software Weaknesses (2024) 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