{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "item": { "id": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "slug": "scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance", "url": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance.md", "json": "https://update.dsesecurity.com/api/v1/posts/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/" }, "title": "Scale fixed-site and transit protection to special nuclear material significance", "summary": "Use 10 CFR 73.67 - Special nuclear material of moderate and low strategic significance 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:40+00:00", "modified_at": "2026-08-27T13:06:59+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 647, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.67 - Special nuclear material of moderate and low strategic significance", "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.67 - Special nuclear material of moderate and low strategic significance", "url": "https://www.ecfr.gov/current/title-10/section-73.67", "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": "

Use this document to resolve one bounded operational decision: Scale fixed-site and transit protection to special nuclear material significance. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.67 – Special nuclear material of moderate and low strategic significance from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

\n\n

Keep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; they do not support conclusions outside the source’s stated conditions.

\n

What the source does not establish

\n

NRC regulation with material-category thresholds and specific licensee duties; classification, aggregation, transit, and site controls require 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

Applicability questions

\n\n

DSE recommendation:

\n

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.

\n

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.

\n

Verification and evidence

\n

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)); 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

\n

Official references

\n", "content_text": "Use this document to resolve one bounded operational decision: Scale fixed-site and transit protection to special nuclear material significance. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.67 – Special nuclear material of moderate and low strategic significance from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, each licensee who arranges for the in-transit physical protection of special nuclear material of moderate strategic significance, or who takes delivery of this material free on board (f.o.b.) the point at which it is delivered to a carrier for transport must establish and maintain written response procedures for dealing with threats of thefts or thefts of this material. The research record locates this support at 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)).\nUnder 10 CFR 73, each licensee who possesses, uses or transports special nuclear material of moderate or low strategic significance must establish and maintain a physical protection system that will achieve the following objectives: facilitate the location and recovery of missing special nuclear material. The research record locates this support at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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 with material-category thresholds and specific licensee duties; classification, aggregation, transit, and site controls require 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.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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.\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)); 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(ii)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\n10 CFR 73.67 – Special nuclear material of moderate and low strategic significance — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Use this document to resolve one bounded operational decision: Scale fixed-site and transit protection to special nuclear material significance. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.67 – Special nuclear material of moderate and low strategic significance](https://www.ecfr.gov/current/title-10/section-73.67) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, each licensee who arranges for the in-transit physical protection of special nuclear material of moderate strategic significance, or who takes delivery of this material free on board (f.o.b.) the point at which it is delivered to a carrier for transport must establish and maintain written response procedures for dealing with threats of thefts or thefts of this material. The research record locates this support at 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)).\n\n- Under 10 CFR 73, each licensee who possesses, uses or transports special nuclear material of moderate or low strategic significance must establish and maintain a physical protection system that will achieve the following objectives: facilitate the location and recovery of missing special nuclear material. The research record locates this support at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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 with material-category thresholds and specific licensee duties; classification, aggregation, transit, and site controls require 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.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)); 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [10 CFR 73.67 – Special nuclear material of moderate and low strategic significance](https://www.ecfr.gov/current/title-10/section-73.67) — 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/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "url": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Scale fixed-site and transit protection to special nuclear material significance", "item": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/#article", "identifier": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "url": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/", "headline": "Scale fixed-site and transit protection to special nuclear material significance", "description": "Use 10 CFR 73.67 - Special nuclear material of moderate and low strategic significance to review this narrow operational decision without extending the…", "abstract": "Use 10 CFR 73.67 - Special nuclear material of moderate and low strategic significance to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Use this document to resolve one bounded operational decision: Scale fixed-site and transit protection to special nuclear material significance. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.67 – Special nuclear material of moderate and low strategic significance from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, each licensee who arranges for the in-transit physical protection of special nuclear material of moderate strategic significance, or who takes delivery of this material free on board (f.o.b.) the point at which it is delivered to a carrier for transport must establish and maintain written response procedures for dealing with threats of thefts or thefts of this material. The research record locates this support at 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)).\nUnder 10 CFR 73, each licensee who possesses, uses or transports special nuclear material of moderate or low strategic significance must establish and maintain a physical protection system that will achieve the following objectives: facilitate the location and recovery of missing special nuclear material. The research record locates this support at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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 with material-category thresholds and specific licensee duties; classification, aggregation, transit, and site controls require 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.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(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.\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.67(e)(3)(iv), read with 10 CFR 73.67(e)(3) (eCFR anchor p-73.67(e)(3)(iv)); 10 CFR 73.67(a)(1)(ii), read with 10 CFR 73.67(a)(1) (eCFR anchor p-73.67(a)(1)(ii)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\n10 CFR 73.67 – Special nuclear material of moderate and low strategic significance — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:11:40+00:00", "dateModified": "2026-08-27T13:06:59+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/" }, "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/scale-fixed-site-and-transit-protection-to-special-nuclear-material-significance/#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": "Scale fixed-site and transit protection to special nuclear material significance" }, "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": 647, "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.67 - Special nuclear material of moderate and low strategic significance", "url": "https://www.ecfr.gov/current/title-10/section-73.67" } } ] } }