{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
        "slug": "protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission",
        "url": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/"
        },
        "title": "Protect stored spent fuel and high-level waste as a distinct facility mission",
        "summary": "Use 10 CFR 73.51 - Stored spent fuel and high-level radioactive waste to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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:47+00:00",
        "modified_at": "2026-08-27T13:06:59+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 605,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.51 - Stored spent fuel and high-level radioactive waste",
        "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.51 - Stored spent fuel and high-level radioactive waste",
            "url": "https://www.ecfr.gov/current/title-10/section-73.51",
            "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 connect an official requirement or behavior to observable evidence: Protect stored spent fuel and high-level waste as a distinct facility mission. 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.51\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.51 &#8211; Stored spent fuel and high-level radioactive waste</a> from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:</p>\n<ul>\n<li>Under 10 CFR 73, the rule requires that each licensee subject to this section establish and maintain a physical protection system with the objective of providing high assurance that activities involving spent nuclear fuel and high-level radioactive waste do not constitute an unreasonable risk to public health and safety. The research record locates this support at <strong>10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1))</strong>.</li>\n<li>Under 10 CFR 73, the rule requires that spent nuclear fuel and high-level radioactive waste be stored only within a protected area so that access to this material requires passage through or penetration of two physical barriers, one barrier at the perimeter of the protected area and one barrier offering substantial penetration resistance. The research record locates this support at <strong>10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1))</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 defined storage installations and material; licensing basis, site configuration, response, and protected security information require authorized technical and legal 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.51(b)(1) (eCFR anchor p-73.51(b)(1))</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1))</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>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.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1))</strong>; <strong>10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1))</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>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.51\" target=\"_blank\" rel=\"noopener noreferrer\">10 CFR 73.51 &#8211; Stored spent fuel and high-level radioactive waste</a> — U.S. Nuclear Regulatory Commission via eCFR</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Protect stored spent fuel and high-level waste as a distinct facility mission. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.51 – Stored spent fuel and high-level radioactive waste from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that each licensee subject to this section establish and maintain a physical protection system with the objective of providing high assurance that activities involving spent nuclear fuel and high-level radioactive waste do not constitute an unreasonable risk to public health and safety. The research record locates this support at 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)).\nUnder 10 CFR 73, the rule requires that spent nuclear fuel and high-level radioactive waste be stored only within a protected area so that access to this material requires passage through or penetration of two physical barriers, one barrier at the perimeter of the protected area and one barrier offering substantial penetration resistance. The research record locates this support at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)).\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 defined storage installations and material; licensing basis, site configuration, response, and protected security information require authorized technical and legal 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.51(b)(1) (eCFR anchor p-73.51(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)), 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.\nAn 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.\nVerification and evidence\nA reviewer should be able to retrace the decision from 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)); 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)) 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.\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.51 – Stored spent fuel and high-level radioactive waste — U.S. Nuclear Regulatory Commission via eCFR",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Protect stored spent fuel and high-level waste as a distinct facility mission. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.51 – Stored spent fuel and high-level radioactive waste](https://www.ecfr.gov/current/title-10/section-73.51) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, the rule requires that each licensee subject to this section establish and maintain a physical protection system with the objective of providing high assurance that activities involving spent nuclear fuel and high-level radioactive waste do not constitute an unreasonable risk to public health and safety. The research record locates this support at 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)).\n\n- Under 10 CFR 73, the rule requires that spent nuclear fuel and high-level radioactive waste be stored only within a protected area so that access to this material requires passage through or penetration of two physical barriers, one barrier at the perimeter of the protected area and one barrier offering substantial penetration resistance. The research record locates this support at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)).\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 defined storage installations and material; licensing basis, site configuration, response, and protected security information require authorized technical and legal 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.51(b)(1) (eCFR anchor p-73.51(b)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)), 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\nAn 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.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)); 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)) 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\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.51 – Stored spent fuel and high-level radioactive waste](https://www.ecfr.gov/current/title-10/section-73.51) — 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/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
                "url": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Protect stored spent fuel and high-level waste as a distinct facility mission",
                        "item": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/#article",
                "identifier": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
                "url": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/",
                "headline": "Protect stored spent fuel and high-level waste as a distinct facility mission",
                "description": "Use 10 CFR 73.51 - Stored spent fuel and high-level radioactive waste to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use 10 CFR 73.51 - Stored spent fuel and high-level radioactive waste to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Protect stored spent fuel and high-level waste as a distinct facility mission. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.51 – Stored spent fuel and high-level radioactive waste from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that each licensee subject to this section establish and maintain a physical protection system with the objective of providing high assurance that activities involving spent nuclear fuel and high-level radioactive waste do not constitute an unreasonable risk to public health and safety. The research record locates this support at 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)).\nUnder 10 CFR 73, the rule requires that spent nuclear fuel and high-level radioactive waste be stored only within a protected area so that access to this material requires passage through or penetration of two physical barriers, one barrier at the perimeter of the protected area and one barrier offering substantial penetration resistance. The research record locates this support at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)).\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 defined storage installations and material; licensing basis, site configuration, response, and protected security information require authorized technical and legal 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.51(b)(1) (eCFR anchor p-73.51(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)), 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.\nAn 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.\nVerification and evidence\nA reviewer should be able to retrace the decision from 10 CFR 73.51(b)(1) (eCFR anchor p-73.51(b)(1)); 10 CFR 73.51(d)(1) (eCFR anchor p-73.51(d)(1)) 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.\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.51 – Stored spent fuel and high-level radioactive waste — U.S. Nuclear Regulatory Commission via eCFR",
                "datePublished": "2026-08-27T12:11:47+00:00",
                "dateModified": "2026-08-27T13:06:59+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/"
                },
                "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/protect-stored-spent-fuel-and-high-level-waste-as-a-distinct-facility-mission/#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": "Protect stored spent fuel and high-level waste as a distinct facility mission"
                },
                "articleSection": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance"
                ],
                "keywords": [
                    "Access Control",
                    "Cybersecurity",
                    "Video Surveillance",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "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": 605,
                "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.51 - Stored spent fuel and high-level radioactive waste",
                    "url": "https://www.ecfr.gov/current/title-10/section-73.51"
                }
            }
        ]
    }
}