Secure by Design: A Guide for Manufacturers (CISA)vsNRC 10 CFR 73.54 - Nuclear Facility Cybersecurity
See exactly how Secure by Design: A Guide for Manufacturers (CISA) controls map to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity. 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:
Secure by Design: A Guide for Manufacturers (CISA) maps to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity with 12% coverage across 3 directly mapped controls. Analysis of 26 Secure by Design: A Guide for Manufacturers (CISA) controls identifies 23 compliance gaps, primarily concentrated in Secure by Design Pledge Goals.
Source: TheArtOfService Knowledge Graph | 26 controls analysed | 686 frameworks | 310K+ cross-framework mappings
Control Mappings
Showing 4 of 4 mapped controls across 3 domains. Sign up to explore all 310K+ mappings across 686 frameworks.
Ownership(2 mappings)
Organization(1 mappings)
Secure Development Practices(1 mappings)
A Secure by Design: A Guide for Manufacturers (CISA) to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls your existing Secure by Design: A Guide for Manufacturers (CISA) 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 12% in the header counts how many Secure by Design: A Guide for Manufacturers (CISA) controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity 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 Secure by Design: A Guide for Manufacturers (CISA) comparisons
Other NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity 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 (310K+)
- ✓ 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 Secure by Design: A Guide for Manufacturers (CISA) and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?
Secure by Design: A Guide for Manufacturers (CISA) has 26 controls across its framework, while NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity covers 8 controls. Direct mapping analysis identifies 3 overlapping controls (12% coverage). The frameworks diverge most significantly in Secure by Design Pledge Goals, where 16 Secure by Design: A Guide for Manufacturers (CISA) controls have no direct NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity equivalent.
How many controls map between Secure by Design: A Guide for Manufacturers (CISA) and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?
Of 26 total Secure by Design: A Guide for Manufacturers (CISA) controls, 3 map directly to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity controls, representing 12% coverage. The remaining 23 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping Secure by Design: A Guide for Manufacturers (CISA) to NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?
23 Secure by Design: A Guide for Manufacturers (CISA) controls have no direct equivalent in NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity. The highest concentration of gaps is in Secure by Design Pledge Goals with 16 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 Secure by Design: A Guide for Manufacturers (CISA) and NRC 10 CFR 73.54 - Nuclear Facility Cybersecurity?
The domain with the highest gap count is Secure by Design Pledge Goals (16 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.