Protect export shipments of low-significance special nuclear material

Use 10 CFR 73.73 - Export shipments of low-significance special nuclear material to review this narrow operational decision without extending the source beyond its stated scope.

Integrated video surveillance and controlled entry at a modern commercial facility.
DSE visual intelligencePhysical securityGuide · 3 min read
Executive summary

What you need to know

Use 10 CFR 73.73 - Export shipments of low-significance special nuclear material 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.73 - Export shipments of low-significance special nuclear material

DSE recommendation

Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.

Use this document to connect an official requirement or behavior to observable evidence: Protect export shipments of low-significance special nuclear material. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official 10 CFR 73.73 – Export shipments of low-significance special nuclear material from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

  • Under 10 CFR 73, the rule requires that a licensee authorized to export special nuclear material of low strategic significance notify in writing the Director, Office of Nuclear Security and Incident Response, by email (preferred method) to AdvanceNotifications.Resource@nrc.gov or by using any appropriate method listed in section 73.4. The research record locates this support at 10 CFR 73.73(a)(1), read with 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(1)).
  • Under 10 CFR 73, the rule requires that a licensee authorized to export special nuclear material of low strategic significance include the following information in the notification: the estimated time and date of arrival of the shipment at the destination. The research record locates this support at 10 CFR 73.73(a)(3)(v), read with 10 CFR 73.73(a)(3) and 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(3)(v)).

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 exports; material category, destination, handoffs, notices, international obligations, and protected transport details require authorized 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.73(a)(1), read with 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(1)), which observable configuration, record, or test can confirm applicability here?
  • For source statement 2 at 10 CFR 73.73(a)(3)(v), read with 10 CFR 73.73(a)(3) and 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(3)(v)), 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.

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.73(a)(1), read with 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(1)); 10 CFR 73.73(a)(3)(v), read with 10 CFR 73.73(a)(3) and 10 CFR 73.73(a) (eCFR anchor p-73.73(a)(3)(v)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

Primary reference

Review the official source

10 CFR 73.73 - Export shipments of low-significance special nuclear material · Verified August 26, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE