{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "item": { "id": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "slug": "apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility", "url": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility.md", "json": "https://update.dsesecurity.com/api/v1/posts/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/" }, "title": "Apply non-power-reactor physical-protection requirements to the actual facility", "summary": "Use 10 CFR 73.60 - Physical protection at non-power reactors to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "playbook", "name": "Playbook" }, "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:41+00:00", "modified_at": "2026-08-27T13:06:59+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 568, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.60 - Physical protection at non-power reactors", "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.60 - Physical protection at non-power reactors", "url": "https://www.ecfr.gov/current/title-10/section-73.60", "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": "

Keep this document to one review outcome: Apply non-power-reactor physical-protection requirements to the actual facility. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.60 – Physical protection at non-power reactors from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

\n\n

Only the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.

\n

What the source does not establish

\n

NRC regulation for defined non-power reactors; material, facility, license conditions, exemptions, plans, and protected security information 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. Begin by recording scope and current state before deciding whether a change is warranted. 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

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.

\n

Verification and evidence

\n

Tie each conclusion back to 10 CFR 73.60(f) (eCFR anchor p-73.60(f)); 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\n

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’s observation is not a continuing guarantee.

\n

Official references

\n", "content_text": "Keep this document to one review outcome: Apply non-power-reactor physical-protection requirements to the actual facility. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.60 – Physical protection at non-power reactors from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, in addition to the fixed-site requirements set forth in this section and in section 73.67, the Commission may require, depending on the individual facility and site conditions, any alternate or additional measures deemed necessary to protect against radiological sabotage at non-power reactors licensed to operate at or above a power level of 2 megawatts thermal. The research record locates this support at 10 CFR 73.60(f) (eCFR anchor p-73.60(f)).\nUnder 10 CFR 73, the rule requires that intrusion alarms, physical barriers, and other devices used for material protection be maintained in operable condition. The research record locates this support at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\nWhat the source does not establish\nNRC regulation for defined non-power reactors; material, facility, license conditions, exemptions, plans, and protected security information 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.60(f) (eCFR anchor p-73.60(f)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(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. Begin by recording scope and current state before deciding whether a change is warranted. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to 10 CFR 73.60(f) (eCFR anchor p-73.60(f)); 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.60 – Physical protection at non-power reactors — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Keep this document to one review outcome: Apply non-power-reactor physical-protection requirements to the actual facility. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.60 – Physical protection at non-power reactors](https://www.ecfr.gov/current/title-10/section-73.60) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, in addition to the fixed-site requirements set forth in this section and in section 73.67, the Commission may require, depending on the individual facility and site conditions, any alternate or additional measures deemed necessary to protect against radiological sabotage at non-power reactors licensed to operate at or above a power level of 2 megawatts thermal. The research record locates this support at 10 CFR 73.60(f) (eCFR anchor p-73.60(f)).\n\n- Under 10 CFR 73, the rule requires that intrusion alarms, physical barriers, and other devices used for material protection be maintained in operable condition. The research record locates this support at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\n\n## What the source does not establish\n\nNRC regulation for defined non-power reactors; material, facility, license conditions, exemptions, plans, and protected security information 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.60(f) (eCFR anchor p-73.60(f)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(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. Begin by recording scope and current state before deciding whether a change is warranted. 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\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nTie each conclusion back to 10 CFR 73.60(f) (eCFR anchor p-73.60(f)); 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.60 – Physical protection at non-power reactors](https://www.ecfr.gov/current/title-10/section-73.60) — 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/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "url": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Apply non-power-reactor physical-protection requirements to the actual facility", "item": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/#article", "identifier": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "url": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/", "headline": "Apply non-power-reactor physical-protection requirements to the actual facility", "description": "Use 10 CFR 73.60 - Physical protection at non-power reactors to review this narrow operational decision without extending the source beyond its stated…", "abstract": "Use 10 CFR 73.60 - Physical protection at non-power reactors to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Keep this document to one review outcome: Apply non-power-reactor physical-protection requirements to the actual facility. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.60 – Physical protection at non-power reactors from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, in addition to the fixed-site requirements set forth in this section and in section 73.67, the Commission may require, depending on the individual facility and site conditions, any alternate or additional measures deemed necessary to protect against radiological sabotage at non-power reactors licensed to operate at or above a power level of 2 megawatts thermal. The research record locates this support at 10 CFR 73.60(f) (eCFR anchor p-73.60(f)).\nUnder 10 CFR 73, the rule requires that intrusion alarms, physical barriers, and other devices used for material protection be maintained in operable condition. The research record locates this support at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)).\n\nOnly the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match.\nWhat the source does not establish\nNRC regulation for defined non-power reactors; material, facility, license conditions, exemptions, plans, and protected security information 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.60(f) (eCFR anchor p-73.60(f)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(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. Begin by recording scope and current state before deciding whether a change is warranted. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to 10 CFR 73.60(f) (eCFR anchor p-73.60(f)); 10 CFR 73.60(d)(1) (eCFR anchor p-73.60(d)(1)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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.60 – Physical protection at non-power reactors — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:11:41+00:00", "dateModified": "2026-08-27T13:06:59+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/" }, "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/apply-non-power-reactor-physical-protection-requirements-to-the-actual-facility/#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": "Apply non-power-reactor physical-protection requirements to the actual facility" }, "articleSection": [ "Access Control", "Cybersecurity", "Video Surveillance" ], "keywords": [ "Access Control", "Cybersecurity", "Video Surveillance", "Playbook", "Advisory priority" ], "genre": "Playbook", "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": 568, "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.60 - Physical protection at non-power reactors", "url": "https://www.ecfr.gov/current/title-10/section-73.60" } } ] } }