Cross-Framework Mapping

CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0vsNRC 10 CFR 73.54 - Nuclear Facility Cybersecurity

See exactly how CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 controls map to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity. Pre-computed mappings, identified gaps, and coverage analysis.

2
Controls Mapped
33
Gaps Found
3%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 maps to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity with 3% coverage across 1 directly mapped controls. Analysis of 35 CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 controls identifies 38 compliance gaps — primarily concentrated in Device Security.

Source: TheArtOfService Knowledge Graph | 35 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 2 of 2 mapped controls across 1 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Supply Chain and Third Party(2 mappings)

CPG-6.BSupply Chain Incident Reporting2 targets
NRC7354-2Critical Digital Asset (CDA) Identification, Scope, and Boundary
NRC7354-4Security Controls Implementation per NRC RG 5.71 Appendix B/C

Related Comparisons

Other CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 comparisons

Other NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?

CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 has 35 controls across its framework, while NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity covers 8 controls. Direct mapping analysis identifies 1 overlapping controls (3% coverage). The frameworks diverge most significantly in Device Security, where 8 CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 controls have no direct NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity equivalent.

How many controls map between CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?

Of 35 total CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 controls, 1 map directly to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls — representing 3% coverage. The remaining 38 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?

38 CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 controls have no direct equivalent in NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity. The highest concentration of gaps is in Device Security with 8 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 CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?

The domain with the highest gap count is Device Security (8 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

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.