{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
        "slug": "coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit",
        "url": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/"
        },
        "title": "Coordinate physical protection for irradiated reactor fuel in transit",
        "summary": "Use 10 CFR 73.37 - Irradiated reactor fuel in transit to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "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:50+00:00",
        "modified_at": "2026-08-27T13:06:59+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 574,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.37 - Irradiated reactor fuel in transit",
        "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.37 - Irradiated reactor fuel in transit",
            "url": "https://www.ecfr.gov/current/title-10/section-73.37",
            "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>Use this document to resolve one bounded operational decision: Coordinate physical protection for irradiated reactor fuel in transit. 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.37\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.37 &#8211; Irradiated reactor fuel in transit</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 must protect spent-fuel transit Safeguards Information under sections 73.21 and 73.22, including information about defensive tactics and capabilities. The research record locates this support at <strong>10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H))</strong>.</li>\n<li>Under 10 CFR 73, a movement control center must be continuously staffed by someone authorized to monitor the shipment and coordinate physical-protection activities. The research record locates this support at <strong>10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii))</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.</p>\n<h2>What the source does not establish</h2>\n<p>NRC regulation for covered shipments; security plans, routes, schedules, escorts, communications, and response details can be sensitive and require authorized 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.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(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. Start with applicability, then compare the observed state with the cited source. 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>A reviewer should be able to retrace the decision from <strong>10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H))</strong>; <strong>10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii))</strong> through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.</p>\n<p>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&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.ecfr.gov/current/title-10/section-73.37\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.37 &#8211; Irradiated reactor fuel in transit</a> — U.S. Nuclear Regulatory Commission via eCFR</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Coordinate physical protection for irradiated reactor fuel in transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.37 – Irradiated reactor fuel in transit from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, a licensee must protect spent-fuel transit Safeguards Information under sections 73.21 and 73.22, including information about defensive tactics and capabilities. The research record locates this support at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)).\nUnder 10 CFR 73, a movement control center must be continuously staffed by someone authorized to monitor the shipment and coordinate physical-protection activities. The research record locates this support at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.\nWhat the source does not establish\nNRC regulation for covered shipments; security plans, routes, schedules, escorts, communications, and response details can be sensitive and 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.\nApplicability questions\n\nFor source statement 1 at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(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. Start with applicability, then compare the observed state with the cited source. 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\nA reviewer should be able to retrace the decision from 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)); 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.\nClose 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.\nOfficial references\n\n10 CFR 73.37 – Irradiated reactor fuel in transit — U.S. Nuclear Regulatory Commission via eCFR",
        "content_markdown": "Use this document to resolve one bounded operational decision: Coordinate physical protection for irradiated reactor fuel in transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.37 – Irradiated reactor fuel in transit](https://www.ecfr.gov/current/title-10/section-73.37) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, a licensee must protect spent-fuel transit Safeguards Information under sections 73.21 and 73.22, including information about defensive tactics and capabilities. The research record locates this support at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)).\n\n- Under 10 CFR 73, a movement control center must be continuously staffed by someone authorized to monitor the shipment and coordinate physical-protection activities. The research record locates this support at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.\n\n## What the source does not establish\n\nNRC regulation for covered shipments; security plans, routes, schedules, escorts, communications, and response details can be sensitive and 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.\n\n## Applicability questions\n\n- For source statement 1 at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(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. Start with applicability, then compare the observed state with the cited source. 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\nA reviewer should be able to retrace the decision from 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)); 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.\n\nClose 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.\n\n## Official references\n\n- [10 CFR 73.37 – Irradiated reactor fuel in transit](https://www.ecfr.gov/current/title-10/section-73.37) — 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/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
                "url": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Coordinate physical protection for irradiated reactor fuel in transit",
                        "item": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/#article",
                "identifier": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
                "url": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/",
                "headline": "Coordinate physical protection for irradiated reactor fuel in transit",
                "description": "Use 10 CFR 73.37 - Irradiated reactor fuel in transit to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use 10 CFR 73.37 - Irradiated reactor fuel in transit to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Coordinate physical protection for irradiated reactor fuel in transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.37 – Irradiated reactor fuel in transit from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, a licensee must protect spent-fuel transit Safeguards Information under sections 73.21 and 73.22, including information about defensive tactics and capabilities. The research record locates this support at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)).\nUnder 10 CFR 73, a movement control center must be continuously staffed by someone authorized to monitor the shipment and coordinate physical-protection activities. The research record locates this support at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.\nWhat the source does not establish\nNRC regulation for covered shipments; security plans, routes, schedules, escorts, communications, and response details can be sensitive and 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.\nApplicability questions\n\nFor source statement 1 at 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(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. Start with applicability, then compare the observed state with the cited source. 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\nA reviewer should be able to retrace the decision from 10 CFR 73.37(b)(1)(viii)(H), read with 10 CFR 73.37(b)(1)(viii)|73.37(b)(1) (eCFR anchor p-73.37(b)(1)(viii)(H)); 10 CFR 73.37(b)(3)(ii) (eCFR anchor p-73.37(b)(3)(ii)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.\nClose 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.\nOfficial references\n\n10 CFR 73.37 – Irradiated reactor fuel in transit — U.S. Nuclear Regulatory Commission via eCFR",
                "datePublished": "2026-08-27T12:11:50+00:00",
                "dateModified": "2026-08-27T13:06:59+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/"
                },
                "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/coordinate-physical-protection-for-irradiated-reactor-fuel-in-transit/#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": "Coordinate physical protection for irradiated reactor fuel in transit"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "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": 574,
                "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.37 - Irradiated reactor fuel in transit",
                    "url": "https://www.ecfr.gov/current/title-10/section-73.37"
                }
            }
        ]
    }
}