Framework overlap

Does NIST SP 800-171A Rev 3 cover NRC 10 CFR 73.54?

You hold NIST SP 800-171A Rev 3 and have been told to do NRC 10 CFR 73.54. Here is how much overlaps, control by control.

25% of NRC 10 CFR 73.54 you already have

NIST SP 800-171A Rev 3 already covers about 25% of NRC 10 CFR 73.54, leaving 6 of 8 controls as genuinely new work.

Already covered 2 Likely covered 0 New work 6

What is genuinely new work

Nothing in NIST SP 800-171A Rev 3 reaches these. This is the list to scope.

NRC7354-1
Cybersecurity Plan, Programme Establishment, and NRC Submission
NRC7354-3
Defensive Architecture, Multi-Layer Defense, and Network Segregation
NRC7354-5
Access Control, Authentication, Removable Media, and Portable Devices
NRC7354-6
Vulnerability Management, Configuration Management, Baseline Control, and Patching
NRC7354-7
Monitoring, Assessment, Incident Response, Reporting, and Contingency
NRC7354-8
Programme Oversight, Independent Review, Documentation, Training, Supply Chain
Show the 2 you already have
NRC7354-2
Critical Digital Asset (CDA) Identification, Scope, and Boundary
NRC7354-4
Security Controls Implementation per NRC RG 5.71 Appendix B/C

How this is calculated

Already covered means a mapping runs from a control in NIST SP 800-171A Rev 3 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