NRC 10 CFR 73.54 - Nuclear Facility CybersecurityvsNIST Cybersecurity Framework 2.0
See exactly how NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls map to NIST Cybersecurity Framework 2.0. Pre-computed mappings, identified gaps, and coverage analysis.
Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.
According to the TheArtOfService Compliance Knowledge Graph:
NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity maps to NIST Cybersecurity Framework 2.0 with 21% coverage across 7 directly mapped controls. Analysis of 33 NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls identifies 26 compliance gaps, primarily concentrated in 10 CFR 73.54 Programme Requirements.
Source: TheArtOfService Knowledge Graph | 33 controls analysed | 686 frameworks | 309K+ cross-framework mappings
Control Mappings
Showing 18 of 18 mapped controls across 3 domains. Sign up to explore all 309K+ mappings across 686 frameworks.
Critical Digital Asset Identification(2 mappings)
Security Controls Implementation(2 mappings)
Regulatory Guide 5.71 Appendix C Security Controls(14 mappings)
A NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity to NIST Cybersecurity Framework 2.0 crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which NIST Cybersecurity Framework 2.0 controls your existing NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 21% in the header counts how many NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many NIST Cybersecurity Framework 2.0 controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity comparisons
Other NIST Cybersecurity Framework 2.0 comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 686 frameworks, at a fraction of consulting costs.
Free
- ✓ 686 framework browser
- ✓ Cross-framework mappings (309K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity and NIST Cybersecurity Framework 2.0?
NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity has 33 controls across its framework, while NIST Cybersecurity Framework 2.0 covers 106 controls. Direct mapping analysis identifies 7 overlapping controls (21% coverage). The frameworks diverge most significantly in 10 CFR 73.54 Programme Requirements, where 6 NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls have no direct NIST Cybersecurity Framework 2.0 equivalent.
How many controls map between NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity and NIST Cybersecurity Framework 2.0?
Of 33 total NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls, 7 map directly to NIST Cybersecurity Framework 2.0 controls, representing 21% coverage. The remaining 26 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity to NIST Cybersecurity Framework 2.0?
26 NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls have no direct equivalent in NIST Cybersecurity Framework 2.0. The highest concentration of gaps is in 10 CFR 73.54 Programme Requirements with 6 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity and NIST Cybersecurity Framework 2.0?
The domain with the highest gap count is 10 CFR 73.54 Programme Requirements (6 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.