Framework overlap

Does API 1164 cover US NRC 10 CFR 73.54?

You hold API 1164 and have been told to do US NRC 10 CFR 73.54. Here is how much overlaps, control by control.

20% of US NRC 10 CFR 73.54 you already have

API 1164 already covers about 20% of US NRC 10 CFR 73.54, leaving 4 of 5 controls as genuinely new work.

Already covered 0 Likely covered 1 New work 4

No control in API 1164 maps directly to one in US NRC 10 CFR 73.54. 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 API 1164 reaches these. This is the list to scope.

USNRCCYBER-1
High Assurance Standard and Scope
USNRCCYBER-2
Critical Digital Asset (CDA) Identification and Protection
USNRCCYBER-3
Cyber Security Plan and Programme
USNRCCYBER-5
Incident Response, Reporting, NRC Cooperation
Show the 1 you already have
USNRCCYBER-4
Defense-in-Depth and Technical Controls

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