{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "item": { "id": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "slug": "notify-the-nrc-within-15-minutes-of-specified-physical-security-threats", "url": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats.md", "json": "https://update.dsesecurity.com/api/v1/posts/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/" }, "title": "Notify the NRC within 15 minutes of specified physical-security threats", "summary": "Use 10 CFR 73.1200 - Notification of physical security events to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "explainer", "name": "Explainer" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "access-control", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" }, { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-08-27T12:09:53+00:00", "modified_at": "2026-08-27T13:12:22+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 589, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.1200 - Notification of physical security events", "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.1200 - Notification of physical security events", "url": "https://www.ecfr.gov/current/title-10/section-73.1200", "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": "

Frame this document as a source-led configuration and assurance check: Notify the NRC within 15 minutes of specified physical-security threats. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.1200 – Notification of physical security events from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

\n\n

The source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths in the applicable environment, not to imply a wider guarantee.

\n

What the source does not establish

\n

This covers only facility events and licensees within 10 CFR 73.1200(a). Other subsections, written follow-up duties, emergency actions, and agency instructions remain separate. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.

\n

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.

\n

Verification and evidence

\n

Build a reproducible chain from 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)); 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; label every item with scope, timestamp, collector, and stable identifier.

\n

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

\n

Official references

\n", "content_text": "Frame this document as a source-led configuration and assurance check: Notify the NRC within 15 minutes of specified physical-security threats. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.1200 – Notification of physical security events from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nA covered facility licensee must notify the NRC Headquarters Operations Center as soon as possible, but within 15 minutes, after initiating a security response to imminent or actual hostile action. The research record locates this support at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)).\nThat NRC notification must identify the facility and briefly state the event type and whether the threat is imminent, in progress, or neutralized. The research record locates this support at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)).\n\nThe source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThis covers only facility events and licensees within 10 CFR 73.1200(a). Other subsections, written follow-up duties, emergency actions, and agency instructions remain separate. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)); 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; label every item with scope, timestamp, collector, and stable identifier.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n10 CFR 73.1200 – Notification of physical security events — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Frame this document as a source-led configuration and assurance check: Notify the NRC within 15 minutes of specified physical-security threats. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.1200 – Notification of physical security events](https://www.ecfr.gov/current/title-10/section-73.1200) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- A covered facility licensee must notify the NRC Headquarters Operations Center as soon as possible, but within 15 minutes, after initiating a security response to imminent or actual hostile action. The research record locates this support at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)).\n\n- That NRC notification must identify the facility and briefly state the event type and whether the threat is imminent, in progress, or neutralized. The research record locates this support at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)).\n\nThe source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThis covers only facility events and licensees within 10 CFR 73.1200(a). Other subsections, written follow-up duties, emergency actions, and agency instructions remain separate. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\n\n## Verification and evidence\n\nBuild a reproducible chain from 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)); 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; label every item with scope, timestamp, collector, and stable identifier.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [10 CFR 73.1200 – Notification of physical security events](https://www.ecfr.gov/current/title-10/section-73.1200) — 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/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "url": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Notify the NRC within 15 minutes of specified physical-security threats", "item": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/#article", "identifier": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "url": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/", "headline": "Notify the NRC within 15 minutes of specified physical-security threats", "description": "Use 10 CFR 73.1200 - Notification of physical security events to review this narrow operational decision without extending the source beyond its stated…", "abstract": "Use 10 CFR 73.1200 - Notification of physical security events to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Frame this document as a source-led configuration and assurance check: Notify the NRC within 15 minutes of specified physical-security threats. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.1200 – Notification of physical security events from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nA covered facility licensee must notify the NRC Headquarters Operations Center as soon as possible, but within 15 minutes, after initiating a security response to imminent or actual hostile action. The research record locates this support at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)).\nThat NRC notification must identify the facility and briefly state the event type and whether the threat is imminent, in progress, or neutralized. The research record locates this support at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)).\n\nThe source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThis covers only facility events and licensees within 10 CFR 73.1200(a). Other subsections, written follow-up duties, emergency actions, and agency instructions remain separate. A correct source interpretation can still be inapplicable to a particular design. Confirm identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(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. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from 10 CFR 73.1200(a)(1), read with 10 CFR 73.1200(a) (eCFR anchor p-73.1200(a)(1)); 10 CFR 73.1200(a)(3)(i) and 73.1200(a)(3)(ii), read with 10 CFR 73.1200(a)(3) (eCFR anchors p-73.1200(a)(3)(i) and p-73.1200(a)(3)(ii)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; label every item with scope, timestamp, collector, and stable identifier.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\n10 CFR 73.1200 – Notification of physical security events — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:09:53+00:00", "dateModified": "2026-08-27T13:12:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/" }, "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/notify-the-nrc-within-15-minutes-of-specified-physical-security-threats/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Notify the NRC within 15 minutes of specified physical-security threats" }, "articleSection": [ "Access Control", "Cybersecurity", "Video Surveillance" ], "keywords": [ "Access Control", "Cybersecurity", "Video Surveillance", "Explainer", "Advisory priority" ], "genre": "Explainer", "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": 589, "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.1200 - Notification of physical security events", "url": "https://www.ecfr.gov/current/title-10/section-73.1200" } } ] } }