# Translate the NRC physical-protection performance objective into testable outcomes > Use 10 CFR 73.20 - General performance objective and requirements to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:11:55+00:00 - Modified: 2026-08-27T13:06:59+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Briefing - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 10 CFR 73.20 - General performance objective and requirements to review this narrow operational decision without extending the source beyond its stated scope. ## 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. ## Article 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. ## Source fact: The 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: - 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)). - 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)). 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. ## What the source does not establish 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. ## Applicability questions - 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? - 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? - 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? - 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? - Who approves the conclusion, exception, test window, and rollback threshold? ## DSE recommendation: 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. 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. ## Verification and evidence 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. 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. ## Official references - [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 ## Primary reference - Name: 10 CFR 73.20 - General performance objective and requirements - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-10/section-73.20 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Translate the NRC physical-protection performance objective into testable outcomes,” DSE Security, https://update.dsesecurity.com/updates/translate-the-nrc-physical-protection-performance-objective-into-testable-outcomes/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.