# Prevent split nuclear shipments from bypassing aggregate protection thresholds > Use 10 CFR 73.24 - Prohibitions to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/prevent-split-nuclear-shipments-from-bypassing-aggregate-protection-thresholds/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:09:57+00:00 - Modified: 2026-08-27T13:12:22+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Guide - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 10 CFR 73.24 - Prohibitions 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.24 - Prohibitions ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to connect an official requirement or behavior to observable evidence: Prevent split nuclear shipments from bypassing aggregate protection thresholds. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [10 CFR 73.24 – Prohibitions](https://www.ecfr.gov/current/title-10/section-73.24) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements: - Absent specific NRC approval, a special-nuclear-material shipment above the stated plutonium, uranium-233, or uranium-235 thresholds may not travel on passenger aircraft. The research record locates this support at 10 CFR 73.24(a) (eCFR anchor p-73.24(a)). - When individually sub-formula shipments could collectively reach a formula quantity in transit, a licensee must log confirmed arrivals and schedule shipments below that aggregate threshold, unless it supplies the specified physical protection. The research record locates this support at 10 CFR 73.24(b)(1) and 73.24(b)(2), read with 10 CFR 73.24(b) (eCFR anchors p-73.24(b)(1) and p-73.24(b)(2)). 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 This covers only the shipment prohibitions and aggregation controls in 10 CFR 73.24. It does not select carriers, routes, packaging, or safeguards for a particular shipment. 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.24(a) (eCFR anchor p-73.24(a)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 10 CFR 73.24(b)(1) and 73.24(b)(2), read with 10 CFR 73.24(b) (eCFR anchors p-73.24(b)(1) and p-73.24(b)(2)), 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.24(a) (eCFR anchor p-73.24(a)); 10 CFR 73.24(b)(1) and 73.24(b)(2), read with 10 CFR 73.24(b) (eCFR anchors p-73.24(b)(1) and p-73.24(b)(2)). 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.24 – Prohibitions](https://www.ecfr.gov/current/title-10/section-73.24) — U.S. Nuclear Regulatory Commission via eCFR ## Primary reference - Name: 10 CFR 73.24 - Prohibitions - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-10/section-73.24 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Prevent split nuclear shipments from bypassing aggregate protection thresholds,” DSE Security, https://update.dsesecurity.com/updates/prevent-split-nuclear-shipments-from-bypassing-aggregate-protection-thresholds/ 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.