{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "item": { "id": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "slug": "translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes", "url": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes.md", "json": "https://update.dsesecurity.com/api/v1/posts/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/" }, "title": "Translate the NRC physical-protection performance objective into testable outcomes", "summary": "Use 10 CFR 73.20 - General performance objective and requirements 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:55+00:00", "modified_at": "2026-08-27T13:06:59+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 641, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.20 - General performance objective and requirements", "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.20 - General performance objective and requirements", "url": "https://www.ecfr.gov/current/title-10/section-73.20", "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: Translate the NRC physical-protection performance objective into testable outcomes. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.20 – General performance objective and requirements from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:

\n\n

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths and the conditions the source actually describes.

\n

What the source does not establish

\n

NRC regulation for specifically covered licensees, material, and activities; applicability, exemptions, orders, license conditions, and current NRC guidance require qualified legal and technical review. 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. Use a two-person review for the source interpretation and the resulting operational decision. 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

Build a reproducible chain from 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)); 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)) 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

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: Translate the NRC physical-protection performance objective into testable outcomes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.20 – General performance objective and requirements from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that provides the performance capabilities described in section 73.25 for in-transit protection or in section 73.45 for fixed site protection unless otherwise authorized by the Commission. The research record locates this support at 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)).\nUnder 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that is designed with sufficient redundancy and diversity to ensure maintenance of the capabilities described in section section 73.25 and 73.45. The research record locates this support at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths and the conditions the source actually describes.\nWhat the source does not establish\nNRC regulation for specifically covered licensees, material, and activities; applicability, exemptions, orders, license conditions, and current NRC guidance require qualified legal and technical review. 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.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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\nBuild a reproducible chain from 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)); 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)) 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.\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.20 – General performance objective and requirements — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Use this document to resolve one bounded operational decision: Translate the NRC physical-protection performance objective into testable outcomes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.20 – General performance objective and requirements](https://www.ecfr.gov/current/title-10/section-73.20) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that provides the performance capabilities described in section 73.25 for in-transit protection or in section 73.45 for fixed site protection unless otherwise authorized by the Commission. The research record locates this support at 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)).\n\n- Under 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that is designed with sufficient redundancy and diversity to ensure maintenance of the capabilities described in section section 73.25 and 73.45. The research record locates this support at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths and the conditions the source actually describes.\n\n## What the source does not establish\n\nNRC regulation for specifically covered licensees, material, and activities; applicability, exemptions, orders, license conditions, and current NRC guidance require qualified legal and technical review. 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.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)), which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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\nBuild a reproducible chain from 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)); 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)) 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\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.20 – General performance objective and requirements](https://www.ecfr.gov/current/title-10/section-73.20) — 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/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "url": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Translate the NRC physical-protection performance objective into testable outcomes", "item": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/#article", "identifier": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "url": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/", "headline": "Translate the NRC physical-protection performance objective into testable outcomes", "description": "Use 10 CFR 73.20 - General performance objective and requirements to review this narrow operational decision without extending the source beyond its…", "abstract": "Use 10 CFR 73.20 - General performance objective and requirements to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Use this document to resolve one bounded operational decision: Translate the NRC physical-protection performance objective into testable outcomes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.20 – General performance objective and requirements from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that provides the performance capabilities described in section 73.25 for in-transit protection or in section 73.45 for fixed site protection unless otherwise authorized by the Commission. The research record locates this support at 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)).\nUnder 10 CFR 73, the rule requires that to achieve the general performance objective of paragraph (a) of this section a licensee establish and maintain, or arrange for, a physical protection system that is designed with sufficient redundancy and diversity to ensure maintenance of the capabilities described in section section 73.25 and 73.45. The research record locates this support at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths and the conditions the source actually describes.\nWhat the source does not establish\nNRC regulation for specifically covered licensees, material, and activities; applicability, exemptions, orders, license conditions, and current NRC guidance require qualified legal and technical review. 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.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)), which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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\nBuild a reproducible chain from 10 CFR 73.20(b)(1), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(1)); 10 CFR 73.20(b)(2), read with 10 CFR 73.20(b) (eCFR anchor p-73.20(b)(2)) 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.\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.20 – General performance objective and requirements — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:11:55+00:00", "dateModified": "2026-08-27T13:06:59+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/" }, "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/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/#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": "Translate the NRC physical-protection performance objective into testable outcomes" }, "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": 641, "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.20 - General performance objective and requirements", "url": "https://www.ecfr.gov/current/title-10/section-73.20" } } ] } }