# Build advance-notice controls for high-significance nuclear shipments > Use 10 CFR 73.72 - Advance notice of covered shipments to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:11:38+00:00 - Modified: 2026-08-27T13:06:59+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Explainer - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 10 CFR 73.72 - Advance notice of covered shipments to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of 10 CFR 73.72 - Advance notice of covered shipments ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Frame this document as a source-led configuration and assurance check: Build advance-notice controls for high-significance nuclear shipments. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [10 CFR 73.72 – Advance notice of covered shipments](https://www.ecfr.gov/current/title-10/section-73.72) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements: - Under 10 CFR 73, a licensee who conducts an on-site transfer of spent nuclear fuel that does not travel upon or cross a public highway is exempt from the requirements of this section for that transfer. The research record locates this support at 10 CFR 73.72(b) (eCFR anchor p-73.72(b)). - Under 10 CFR 73, the rule requires that the notifications take place at the following intervals: two hours before commencement of the shipment. The research record locates this support at 10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii)). Keep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish NRC regulation for defined shipments; recipients, timing, changes, protected details, secure communications, and other transport requirements demand authorized qualified review. 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.72(b) (eCFR anchor p-73.72(b)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii)), 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. Anchor the review in the cited section and keep observation separate from interpretation. 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.72(b) (eCFR anchor p-73.72(b)); 10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator. 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.72 – Advance notice of covered shipments](https://www.ecfr.gov/current/title-10/section-73.72) — U.S. Nuclear Regulatory Commission via eCFR ## Primary reference - Name: 10 CFR 73.72 - Advance notice of covered shipments - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-10/section-73.72 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Build advance-notice controls for high-significance nuclear shipments,” DSE Security, https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.