Join nuclear cyber protection to safety, security, and emergency systems

Keep this document to one review outcome: Join nuclear cyber protection to safety, security, and emergency systems. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official 10 CFR 73.54 – Digital computer and communication systems from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

• Under 10 CFR 73, the rule requires that the licensee protect digital computer and communication systems and networks associated with: support systems and equipment which, if compromised, would adversely impact safety, security, or emergency preparedness functions. The research record locates this support at 10 CFR 73.54(a)(1)(iv), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iv)).
• Under 10 CFR 73, the rule requires that the licensee protect digital computer and communication systems and networks associated with: emergency preparedness functions, including offsite communications. The research record locates this support at 10 CFR 73.54(a)(1)(iii), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iii)).

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.

What the source does not establish

NRC regulation for covered reactor licensees; security architecture and vulnerabilities can be sensitive, and compliance requires the full rule, license basis, orders, and NRC guidance. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at 10 CFR 73.54(a)(1)(iv), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iv)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 10 CFR 73.54(a)(1)(iii), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iii)), which observable configuration, record, or test can confirm applicability here?
• Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?
• What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?
• Which success, stop, and escalation criteria are written before testing begins?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

A reviewer should be able to retrace the decision from 10 CFR 73.54(a)(1)(iv), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iv)); 10 CFR 73.54(a)(1)(iii), read with 10 CFR 73.54(a)(1) (eCFR anchor p-73.54(a)(1)(iii)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• 10 CFR 73.54 – Digital computer and communication systems — U.S. Nuclear Regulatory Commission via eCFR