{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "item": { "id": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "slug": "keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence", "url": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence.md", "json": "https://update.dsesecurity.com/api/v1/posts/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/" }, "title": "Keep NRC physical-protection records linked to the requirement they evidence", "summary": "Use 10 CFR 73.70 - Records to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "checklist", "name": "Checklist" }, "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:39+00:00", "modified_at": "2026-08-27T13:06:59+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 559, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.70 - Records", "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.70 - Records", "url": "https://www.ecfr.gov/current/title-10/section-73.70", "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": "

Treat this document as a focused evidence review: Keep NRC physical-protection records linked to the requirement they evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.70 – Records 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; exact record types, retention periods, protected information, electronic systems, license conditions, and inspections require full-rule and 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

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

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.70(a) (eCFR anchor p-73.70(a)); 10 CFR 73.70(e) (eCFR anchor p-73.70(e)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.

\n

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.

\n

Official references

\n", "content_text": "Treat this document as a focused evidence review: Keep NRC physical-protection records linked to the requirement they evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.70 – Records from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that the licensee retain this record of currently designated authorized individuals for the period during which the licensee possesses the appropriate type and quantity of special nuclear material requiring this record under each license that authorizes the activity that is subject to the recordkeeping requirement and, for three years thereafter. The research record locates this support at 10 CFR 73.70(a) (eCFR anchor p-73.70(a)).\nUnder 10 CFR 73, the rule requires that the licensee retain the documentation for these events for three years from the date of documenting each event. The research record locates this support at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)).\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; exact record types, retention periods, protected information, electronic systems, license conditions, and inspections require full-rule and 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.70(a) (eCFR anchor p-73.70(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)), 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.\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.70(a) (eCFR anchor p-73.70(a)); 10 CFR 73.70(e) (eCFR anchor p-73.70(e)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\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.70 – Records — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Treat this document as a focused evidence review: Keep NRC physical-protection records linked to the requirement they evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.70 – Records](https://www.ecfr.gov/current/title-10/section-73.70) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, the rule requires that the licensee retain this record of currently designated authorized individuals for the period during which the licensee possesses the appropriate type and quantity of special nuclear material requiring this record under each license that authorizes the activity that is subject to the recordkeeping requirement and, for three years thereafter. The research record locates this support at 10 CFR 73.70(a) (eCFR anchor p-73.70(a)).\n\n- Under 10 CFR 73, the rule requires that the licensee retain the documentation for these events for three years from the date of documenting each event. The research record locates this support at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)).\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; exact record types, retention periods, protected information, electronic systems, license conditions, and inspections require full-rule and 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.70(a) (eCFR anchor p-73.70(a)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)), 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\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.70(a) (eCFR anchor p-73.70(a)); 10 CFR 73.70(e) (eCFR anchor p-73.70(e)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\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.70 – Records](https://www.ecfr.gov/current/title-10/section-73.70) — 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/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "url": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep NRC physical-protection records linked to the requirement they evidence", "item": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/#article", "identifier": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "url": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/", "headline": "Keep NRC physical-protection records linked to the requirement they evidence", "description": "Use 10 CFR 73.70 - Records to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use 10 CFR 73.70 - Records to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Treat this document as a focused evidence review: Keep NRC physical-protection records linked to the requirement they evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.70 – Records from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that the licensee retain this record of currently designated authorized individuals for the period during which the licensee possesses the appropriate type and quantity of special nuclear material requiring this record under each license that authorizes the activity that is subject to the recordkeeping requirement and, for three years thereafter. The research record locates this support at 10 CFR 73.70(a) (eCFR anchor p-73.70(a)).\nUnder 10 CFR 73, the rule requires that the licensee retain the documentation for these events for three years from the date of documenting each event. The research record locates this support at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)).\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; exact record types, retention periods, protected information, electronic systems, license conditions, and inspections require full-rule and 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.70(a) (eCFR anchor p-73.70(a)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.70(e) (eCFR anchor p-73.70(e)), 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.\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\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 10 CFR 73.70(a) (eCFR anchor p-73.70(a)); 10 CFR 73.70(e) (eCFR anchor p-73.70(e)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.\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.70 – Records — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:11:39+00:00", "dateModified": "2026-08-27T13:06:59+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/" }, "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/keep-nrc-physical-protection-records-linked-to-the-requirement-they-evidence/#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": "Keep NRC physical-protection records linked to the requirement they evidence" }, "articleSection": [ "Access Control", "Cybersecurity", "Video Surveillance" ], "keywords": [ "Access Control", "Cybersecurity", "Video Surveillance", "Checklist", "Advisory priority" ], "genre": "Checklist", "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": 559, "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.70 - Records", "url": "https://www.ecfr.gov/current/title-10/section-73.70" } } ] } }