# Close the loop on strategic-material shipment departure, arrival, and loss > Use 10 CFR 73.27 - Notification requirements to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:09:54+00:00 - Modified: 2026-08-27T13:12:22+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 10 CFR 73.27 - Notification requirements 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.27 - Notification requirements ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Close the loop on strategic-material shipment departure, arrival, and loss. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [10 CFR 73.27 – Notification requirements](https://www.ecfr.gov/current/title-10/section-73.27) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements: - A licensee shipping formula quantities of strategic special nuclear material must immediately tell the consignee the departure time and confirm the transportation method, carriers, and estimated arrival time. The research record locates this support at 10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1)). - A licensee responsible for shipment protection must immediately trace a shipment that remains lost or unaccounted for after its estimated arrival and report it under sections 73.1200 and 73.1205. The research record locates this support at 10 CFR 73.27(c) (eCFR anchor p-73.27(c)). The source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths in the applicable environment, not to imply a wider guarantee. ## What the source does not establish This applies only to covered formula-quantity shipments and the notifications and tracing required by 10 CFR 73.27. It does not prescribe a complete transport-security plan. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at 10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 10 CFR 73.27(c) (eCFR anchor p-73.27(c)), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Build a reproducible chain from 10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1)); 10 CFR 73.27(c) (eCFR anchor p-73.27(c)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; label every item with scope, timestamp, collector, and stable identifier. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [10 CFR 73.27 – Notification requirements](https://www.ecfr.gov/current/title-10/section-73.27) — U.S. Nuclear Regulatory Commission via eCFR ## Primary reference - Name: 10 CFR 73.27 - Notification requirements - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-10/section-73.27 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Close the loop on strategic-material shipment departure, arrival, and loss,” DSE Security, https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/ 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.