Join our Newsletter — 33% off our NHI Course
Home› Guides› Nuclear Facility Cybersecurity Guide: NRC 10 CFR 73.54,…
Guide OT & IoT Security

Nuclear Facility Cybersecurity Guide: NRC 10 CFR 73.54, RG 5.71 and Defensive Architecture

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 14 min read
On this page

Nuclear plants are one of the few places where cyber security is a licensing condition backed by a design basis threat, and the controls that work in ordinary OT are not enough to meet it. In the United States, 10 CFR 73.54 requires power reactor licensees to provide high assurance that digital systems supporting safety, security and emergency preparedness are protected against cyber attacks up to and including the design basis threat. Regulatory Guide 5.71 Revision 1 (February 2023) describes an accepted way to do it, built around critical digital asset identification, concentric defensive levels and one-way data flows. This guide explains the regulatory regime, how critical digital assets are identified, the defensive architecture, the controls that differ from general OT practice, incident notification under 10 CFR 73.77, and how to measure the programme. It is written for licensee cyber security teams, I&C engineers, vendors supplying digital equipment and assessors. For general OT practice see the OT Security Guide; this page covers what is specific to nuclear facilities. Regulatory text checked on 27 October 2026; this is not legal advice.

Key takeaways

  • Scope is defined by function. 10 CFR 73.54(a)(1) covers digital systems tied to safety-related and important-to-safety functions, security functions, emergency preparedness functions including offsite communications, and support systems whose compromise would affect any of those (together known as SSEP).
  • Critical digital assets drive everything. RG 5.71 Rev. 1 has licensees identify CDAs by assuming worst-case compromise without credit for existing mitigations, then apply technical, operational and management controls to each.
  • Architecture is concentric and one way. RG 5.71 places safety, important-to-safety and security CDAs in Level 4, allows data to flow only outward from Level 4 to 3 and 3 to 2, and prefers hardware that physically enforces one-way communication.
  • A data diode is necessary but not sufficient. The guide requires layered controls so a single failed protection does not compromise a function, which puts removable media, maintenance laptops and supply chain on the same footing as the network.
  • Notification clocks are short. 10 CFR 73.77 requires notifying the NRC within 1, 4 or 8 hours depending on the event, recording in the corrective action programme within 24 hours and a written follow-up within 60 days for the most serious categories.

The regulatory regime

United States: NRC

Rule or guidanceWhat it does
10 CFR 73.54 Protection of digital computer and communication systems and networksRequires a cyber security programme and plan for Part 50 power reactor licensees. Licensees had to submit a cyber security plan with an implementation schedule by 23 November 2009
73.54(b) and (c)Identify the assets to protect, establish and maintain the programme, integrate it into the physical protection programme, apply security controls, use defence in depth to detect, respond to and recover from attacks, mitigate adverse effects and ensure functions are not adversely affected
73.54(d)Training for staff and contractors, cyber risk evaluation and management, assessing modifications to covered assets before implementation, and notifications under 73.77
73.54(e) and (f)A cyber security plan covering site-specific conditions and incident response and recovery; implementing policies and procedures that are not submitted for approval but are subject to NRC inspection
73.54(g) and (h)Review of the programme as part of the physical security programme under 73.55(m); records retained until licence termination, superseded portions for at least three years
10 CFR 73.77 Cyber security event notificationsTiered telephone notifications to the NRC Headquarters Operations Center, 24-hour recording, written follow-up on NRC Form 366
Regulatory Guide 5.71 Rev. 1 (February 2023) Cybersecurity Programs for Nuclear Power ReactorsAn NRC-accepted approach to meeting 73.54, including a generic cyber security plan template (Appendix A), technical controls (Appendix B) and operational and management controls (Appendix C)

International: IAEA guidance

Outside the US, national regulators set their own rules, and many draw on the IAEA Nuclear Security Series. NSS No. 17-T (Rev. 1), Computer Security Techniques for Nuclear Facilities, describes a graded approach in which systems are assigned to computer security levels according to the consequence of compromise and grouped into zones with defined boundary rules, with the most stringent level reserved for the most safety-significant functions. IAEA guidance is not binding by itself; check your national regulator's requirements. Because we could not retrieve the IAEA publication pages when writing, confirm the current edition on the IAEA site before relying on this summary.

Identifying critical digital assets

RG 5.71 Rev. 1 describes a site-specific analysis carried out by a cyber security team: authorise the assessment, form the team, identify and document CDAs, then review and validate their configurations.

  1. Start from critical systems. Identify plant systems that perform or affect SSEP functions.
  2. Assume worst case. Analyse each system as if it were compromised, without credit for existing mitigations, so the inventory reflects consequence rather than current controls.
  3. Classify digital assets. A digital asset is a CDA if it performs or is relied on for an SSEP function, could adversely affect one, provides a pathway to one, supports one, or protects one of these. Balance-of-plant equipment that could cause an unplanned reactor shutdown is also in scope; RG 5.71 describes this as generation dropping to zero within 15 minutes. NEI 10-04 is an NRC-accepted method for this step.
  4. Analyse every pathway. Include wired and wireless networks, removable media, portable maintenance devices, vendor connections and supply chain. RG 5.71 notes that air gaps and autonomous systems still need protection.
  5. Validate on the plant. Walk down configurations to confirm the documented state matches reality, including spare ports, enabled services and default accounts.

The CDA list then becomes the anchor for control application, change management (73.54(d) requires assessing modifications before they are made) and incident response.

Defensive architecture

Level (RG 5.71 Figure 6)Typical contents (illustrative; RG 5.71 assigns only Level 4 explicitly)Boundary rule
Level 4 (innermost)Safety-related, important-to-safety and security CDAs, plus support systems that could affect themProtected from all lower levels; data flows out to Level 3 only, through a device that physically enforces one-way communication
Level 3Plant data acquisition, control systems with lower consequenceData flows out to Level 2 only; boundary device enforces policy and can detect, prevent, delay, mitigate and recover from attacks
Level 2Site business systems that receive plant dataConnections initiated from lower to higher levels follow deny all, permit by exception, each justified and risk analysed
Levels 1 and 0Corporate network and external networksNo path into the inner levels

RG 5.71 speaks of unidirectional, non-software-based devices for the inner boundaries. In practice that means hardware data diodes or unidirectional gateways that replicate historian or monitoring data outward without any return path. See the Data Diodes and Unidirectional Gateways Guide and, for zone and conduit design generally, the OT Network Segmentation, Purdue Model and IEC 62443 Zones and Conduits Guide.

What crosses the boundary anyway: a one-way network does not stop the things that are carried in. Software updates, configuration files, test equipment, vendor laptops and removable media all cross inward by hand. That is why the guide's layered controls matter as much as the diode, and why media and maintenance controls are where most real-world gaps are found.

Controls that differ from general OT practice

Control area (RG 5.71 appendix)Typical nuclear practice (practitioner view, not RG text)
Access control (B.1) and identification and authentication (B.4)Many safety-related CDAs cannot run modern authentication. Compensating controls combine physical protected-area access, key-locked maintenance modes and two-person rules for changes
Audit and accountability (B.2)Logs from Level 4 leave only through the one-way path; monitoring tools sit outside the protected level and receive copies
System and communications protection (B.3)Unidirectional boundaries, wireless prohibited or tightly restricted near CDAs, no remote access into Level 4
System hardening (B.5)Remove unused services, ports and accounts; vendor-supplied default credentials are changed or disabled at receipt inspection
Media protection (C.1)Scanning kiosks, dedicated and controlled media, and tracking of every item that connects to a CDA
Personnel security (C.2)Ties into the access authorisation and insider mitigation programmes that already apply to the protected area
Maintenance (C.4)Portable maintenance and test equipment is controlled, scanned and dedicated where possible
Incident response (C.8) and contingency (C.9)Links to 73.77 notification, the emergency plan and safety analysis, so a cyber event is assessed for plant impact immediately
Supply chainDigital equipment is assessed before installation; modifications are assessed under 73.54(d) before they are made

Where identity fits

  • Shared and vendor accounts: engineering workstations and safety system maintenance tools often rely on shared or vendor default accounts. Inventory them per CDA, change defaults at receipt, and bind use to logged, escorted maintenance sessions. See the OT and ICS Identity and Access Guide.
  • Service accounts on Level 3 and 2 systems: historians, data replication and patch staging systems run as service accounts that can reach the boundary. Scope them to the minimum, vault their credentials and monitor them.
  • Insiders: 73.77 lists a suspected or actual attack by someone with physical or electronic access to the systems as a 4-hour notification, which reflects how seriously the regime treats insiders. See the Insider Threat Programme Guide.

Incident notification and response

ClockTrigger under 10 CFR 73.77Written follow-up
1 hourDiscovery of a cyber attack that adversely impacted safety-related, important-to-safety, security or emergency preparedness functions (including offsite communications), or compromised support systems resulting in such impactNRC Form 366 within 60 days
4 hoursA cyber attack that could have caused such an impact; a suspected or actual attack by someone with physical or electronic access; or notification of another agency (such as law enforcement) about a related cyber event that is not otherwise reportableForm 366 within 60 days, except for the other-agency notification
8 hoursInformation about observed behaviour that may indicate intelligence gathering or pre-operational planning against these systemsNot required
24 hoursRecord cyber security programme vulnerabilities, weaknesses, failures and deficiencies, and the NRC notifications, in the site corrective action programmeNot applicable

Response plans need a fast path from the cyber team to operations and the shift manager, because a cyber event on a CDA is first a plant safety question. Preserve evidence without disturbing safety functions: images of engineering workstations and copies of logs from the outward path are usually safer to collect than anything from Level 4 devices. See the Incident Response Plan Template.

Implementation and decision guidance

  1. Baseline the plan. Compare your cyber security plan and procedures with RG 5.71 Rev. 1 and Appendix A; note where the plant follows an earlier accepted approach and whether a plan change needs NRC review.
  2. Refresh the CDA inventory. Re-run identification for systems changed since the last assessment, using worst-case assumptions and a pathway analysis.
  3. Verify boundaries. Test that Level 4 and Level 3 boundaries are truly one way and that every exception for lower-to-higher connections is documented and risk analysed.
  4. Close carried-in pathways. Put every item of portable media and maintenance equipment under control, with scanning and tracking.
  5. Integrate change management. Make cyber review a mandatory gate in the design change process, before installation and before vendor factory acceptance where possible.
  6. Exercise notification. Run drills that start from a plausible cyber indicator and end with a timed 73.77 call and a corrective action entry.
  7. Roll back safely. Any control change on a CDA, even a hardening setting, follows plant procedures with a tested backout, because availability of safety functions takes precedence.
  • Power reactors versus other facilities: 73.54 applies to power reactor licensees; research reactors, fuel cycle facilities and decommissioning sites face different requirements, so confirm which rules apply to your licence.
  • New builds and advanced reactors: designing the defensive architecture and CDA list into the I&C design is far cheaper than retrofitting; involve cyber in vendor selection and digital I&C specifications from the start.

Measuring the programme

MetricWhat good looks like
CDAs with a current, validated configuration baselineAll, re-validated after every modification
Design changes that passed the cyber review gate before installation100%
Portable media and maintenance devices scanned and logged before use on a CDA100%, verified by sampling
Open boundary exceptions without a current risk analysisZero
Time from cyber indicator to shift manager decision in drillsWell inside the 1-hour notification window
Corrective action entries raised within 24 hours of discoveryAll, checked at self-assessment

Framework mapping

AreaNuclear requirementGeneral framework equivalent
Boundary protectionRG 5.71 levels and one-way flowsNIST SP 800-53 SC-7 Boundary Protection, AC-4 Information Flow Enforcement
Removable mediaRG 5.71 C.1SP 800-53 MP-7 Media Use; ATT&CK for ICS T0847 Replication Through Removable Media
Supply chain and modifications73.54(d)SP 800-53 SR-11 Component Authenticity, CM-3 Configuration Change Control; ATT&CK for ICS T0862 Supply Chain Compromise
Remote and vendor accessNo remote access into Level 4ATT&CK for ICS T0886 Remote Services, T0866 Exploitation of Remote Services
PersonnelAccess authorisation and insider mitigationSP 800-53 PS-3 Personnel Screening
Incident response73.54(e), 73.77SP 800-53 IR-4 Incident Handling, IR-6 Incident Reporting
ConsequenceSSEP functionsATT&CK for ICS T0880 Loss of Safety. See the MITRE ATT&CK for ICS Guide

Common failure patterns

  • Trusting the air gap. Treating isolation as complete while laptops, test sets and USB media move freely across it. Removable media is the classic pathway into isolated industrial networks; see the Removable Media and USB Control Guide.
  • Undocumented boundary exceptions. A temporary bidirectional link added for a vendor or an outage becomes permanent. Review every exception at each outage cycle.
  • Inventory drift. Plant modifications add digital components, sometimes embedded in non-digital equipment, that never enter the CDA list.
  • Cyber review too late in the design change. Problems are found after equipment is bought and installed, when the only option is a compensating control.
  • Default vendor credentials. Equipment arrives with factory accounts that are never changed because the system is "inside the protected area".
  • Notification hesitation. Teams wait for certainty before calling the NRC and miss the clock. Drill the decision criteria so the shift can call on reasonable suspicion.

Practitioner checklist

  • Confirm which NRC rules (or national rules) apply to your licence type and record the regulatory basis.
  • Re-run CDA identification with worst-case assumptions and full pathway analysis after major modifications.
  • Test that Level 4 and 3 boundaries are physically one way and justify every exception.
  • Control, scan and log every item of portable media and maintenance equipment used on a CDA.
  • Change or disable vendor default accounts at receipt inspection.
  • Make cyber assessment a mandatory gate in the design change process.
  • Inventory and scope service accounts on Level 3 and Level 2 systems that reach the boundary.
  • Drill 73.77 notifications and 24-hour corrective action entries.
  • Retain programme records until licence termination and superseded portions for at least three years.

Standards and references

Related NHI Mgmt Group resources: OT Security Guide · Data Diodes and Unidirectional Gateways Guide · Safety Instrumented Systems Security Guide · OT and ICS Identity and Access Guide. This guide summarises 10 CFR 73.54, 10 CFR 73.77 and Regulatory Guide 5.71 as checked on 27 October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.