{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
        "slug": "close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss",
        "url": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/"
        },
        "title": "Close the loop on strategic-material shipment departure, arrival, and loss",
        "summary": "Use 10 CFR 73.27 - Notification requirements to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "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:09:54+00:00",
        "modified_at": "2026-08-27T13:12:22+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 545,
        "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.",
        "primary_source": {
            "name": "10 CFR 73.27 - Notification requirements",
            "url": "https://www.ecfr.gov/current/title-10/section-73.27",
            "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>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.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.ecfr.gov/current/title-10/section-73.27\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.27 &#8211; Notification requirements</a> from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:</p>\n<ul>\n<li>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 <strong>10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1))</strong>.</li>\n<li>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 <strong>10 CFR 73.27(c) (eCFR anchor p-73.27(c))</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>10 CFR 73.27(c) (eCFR anchor p-73.27(c))</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. 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.</p>\n<p>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.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>10 CFR 73.27(a)(1) (eCFR anchor p-73.27(a)(1))</strong>; <strong>10 CFR 73.27(c) (eCFR anchor p-73.27(c))</strong> 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.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-10/section-73.27\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.27 &#8211; Notification requirements</a> — U.S. Nuclear Regulatory Commission via eCFR</li>\n</ul>",
        "content_text": "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.\nSource fact:\nThe official 10 CFR 73.27 – Notification requirements from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nA 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)).\nA 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)).\n\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nFor 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?\nFor 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?\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. 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.\nFor 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.\nVerification and evidence\nBuild 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.\nRetain 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.\nOfficial references\n\n10 CFR 73.27 – Notification requirements — U.S. Nuclear Regulatory Commission via eCFR",
        "content_markdown": "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.\n\n## Source fact:\n\nThe 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:\n\n- 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)).\n\n- 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)).\n\nThe 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.\n\n## What the source does not establish\n\nThis 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.\n\n## Applicability questions\n\n- 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?\n\n- 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?\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. 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.\n\nFor 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.\n\n## Verification and evidence\n\nBuild 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.\n\nRetain 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.\n\n## Official references\n\n- [10 CFR 73.27 – Notification requirements](https://www.ecfr.gov/current/title-10/section-73.27) — 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/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
                "url": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Close the loop on strategic-material shipment departure, arrival, and loss",
                        "item": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/#article",
                "identifier": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
                "url": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/",
                "headline": "Close the loop on strategic-material shipment departure, arrival, and loss",
                "description": "Use 10 CFR 73.27 - Notification requirements to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 10 CFR 73.27 - Notification requirements to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "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.\nSource fact:\nThe official 10 CFR 73.27 – Notification requirements from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nA 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)).\nA 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)).\n\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nFor 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?\nFor 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?\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. 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.\nFor 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.\nVerification and evidence\nBuild 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.\nRetain 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.\nOfficial references\n\n10 CFR 73.27 – Notification requirements — U.S. Nuclear Regulatory Commission via eCFR",
                "datePublished": "2026-08-27T12:09:54+00:00",
                "dateModified": "2026-08-27T13:12:22+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/"
                },
                "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/close-the-loop-on-strategic-material-shipment-departure-arrival-and-loss/#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": "Close the loop on strategic-material shipment departure, arrival, and loss"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "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": 545,
                "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.27 - Notification requirements",
                    "url": "https://www.ecfr.gov/current/title-10/section-73.27"
                }
            }
        ]
    }
}