75% of API 1164 you already have
NIST Privacy Framework already covers about 75% of API 1164, leaving
6 of 24 controls as genuinely new work.
Already covered 12
Likely covered 6
New work 6
What is genuinely new work
Nothing in NIST Privacy Framework reaches these. This is the list to scope.
API1164-01Scope and Applicability
API1164-03Governance and Roles
API1164-04Asset Inventory
API1164-10Malware Protection
API1164-15Personnel Security
API1164-20Program Review and Continuous Improvement
Show the 18 you already have
API1164-09Patch and Vulnerability Management
API1164-13Business Continuity and Recovery
API1164-14Physical Security
API1164-17Wireless and Field Communications
API1164-18Field Device Security
API1164-19Safety Instrumented Systems Interface
API1164-21TSA Pipeline Security Directive Alignment
API1164-22Configuration management for OT systems
API1164-23Change management procedures
API1164-24Vulnerability assessment for critical systems
API1164-02Risk Management Framework
API1164-05Network Segmentation and Zones
API1164-08Configuration Management
API1164-11Logging and Monitoring
API1164-12Incident Response
API1164-16Supply Chain and Third Party
How this is calculated
Already covered means a mapping runs from a control in NIST Privacy Framework 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