{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
        "slug": "build-advance-notice-controls-for-high-significance-nuclear-shipments",
        "url": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/build-advance-notice-controls-for-high-significance-nuclear-shipments/"
        },
        "title": "Build advance-notice controls for high-significance nuclear shipments",
        "summary": "Use 10 CFR 73.72 - Advance notice of covered shipments to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "physical-security",
            "label": "Physical security",
            "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "access-control",
                "name": "Access Control",
                "url": "https://update.dsesecurity.com/topic/access-control/"
            },
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "video-surveillance",
                "name": "Video Surveillance",
                "url": "https://update.dsesecurity.com/topic/video-surveillance/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T12:11:38+00:00",
        "modified_at": "2026-08-27T13:06:59+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 558,
        "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.",
        "primary_source": {
            "name": "10 CFR 73.72 - Advance notice of covered shipments",
            "url": "https://www.ecfr.gov/current/title-10/section-73.72",
            "published_on": null,
            "authority": "www.ecfr.gov"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>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.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-10/section-73.72\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.72 &#8211; Advance notice of covered shipments</a> from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:</p>\n<ul>\n<li>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 <strong>10 CFR 73.72(b) (eCFR anchor p-73.72(b))</strong>.</li>\n<li>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 <strong>10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii))</strong>.</li>\n</ul>\n<p>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&#8217;s stated conditions.</p>\n<h2>What the source does not establish</h2>\n<p>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&#8217;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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>10 CFR 73.72(b) (eCFR anchor p-73.72(b))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?</li>\n<li>What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>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.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>10 CFR 73.72(b) (eCFR anchor p-73.72(b))</strong>; <strong>10 CFR 73.72(a)(4)(ii), read with 10 CFR 73.72(a)(4) (eCFR anchor p-73.72(a)(4)(ii))</strong>. Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-10/section-73.72\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.72 &#8211; Advance notice of covered shipments</a> — U.S. Nuclear Regulatory Commission via eCFR</li>\n</ul>",
        "content_text": "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.\nSource fact:\nThe official 10 CFR 73.72 – Advance notice of covered shipments from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 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)).\nUnder 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)).\n\nKeep 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.\nWhat the source does not establish\nNRC 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.\nApplicability questions\n\nFor 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?\nFor 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?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE 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.\nTranslate 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.\nVerification and evidence\nEvidence 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.\nPreserve 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.\nOfficial references\n\n10 CFR 73.72 – Advance notice of covered shipments — U.S. Nuclear Regulatory Commission via eCFR",
        "content_markdown": "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.\n\n## Source fact:\n\nThe 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:\n\n- 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)).\n\n- 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)).\n\nKeep 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.\n\n## What the source does not establish\n\nNRC 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.\n\n## Applicability questions\n\n- 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?\n\n- 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?\n\n- Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\n\n- What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE 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.\n\nTranslate 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.\n\n## Verification and evidence\n\nEvidence 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.\n\nPreserve 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.\n\n## Official references\n\n- [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"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
                "url": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Build advance-notice controls for high-significance nuclear shipments",
                        "item": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/#article",
                "identifier": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
                "url": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/",
                "headline": "Build advance-notice controls for high-significance nuclear shipments",
                "description": "Use 10 CFR 73.72 - Advance notice of covered shipments to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 10 CFR 73.72 - Advance notice of covered shipments to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "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.\nSource fact:\nThe official 10 CFR 73.72 – Advance notice of covered shipments from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 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)).\nUnder 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)).\n\nKeep 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.\nWhat the source does not establish\nNRC 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.\nApplicability questions\n\nFor 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?\nFor 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?\nWhich owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions?\nWhat baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE 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.\nTranslate 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.\nVerification and evidence\nEvidence 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.\nPreserve 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.\nOfficial references\n\n10 CFR 73.72 – Advance notice of covered shipments — U.S. Nuclear Regulatory Commission via eCFR",
                "datePublished": "2026-08-27T12:11:38+00:00",
                "dateModified": "2026-08-27T13:06:59+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/build-advance-notice-controls-for-high-significance-nuclear-shipments/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Build advance-notice controls for high-significance nuclear shipments"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Access Control",
                        "url": "https://update.dsesecurity.com/topic/access-control/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Video Surveillance",
                        "url": "https://update.dsesecurity.com/topic/video-surveillance/"
                    }
                ],
                "wordCount": 558,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "10 CFR 73.72 - Advance notice of covered shipments",
                    "url": "https://www.ecfr.gov/current/title-10/section-73.72"
                }
            }
        ]
    }
}