{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "item": { "id": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "slug": "verify-transportation-physical-protection-subsystems-as-an-integrated-whole", "url": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole.md", "json": "https://update.dsesecurity.com/api/v1/posts/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/" }, "title": "Verify transportation physical-protection subsystems as an integrated whole", "summary": "Use 10 CFR 73.26 - Transportation physical protection systems 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:51+00:00", "modified_at": "2026-08-27T13:06:59+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 551, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of 10 CFR 73.26 - Transportation physical protection systems", "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.26 - Transportation physical protection systems", "url": "https://www.ecfr.gov/current/title-10/section-73.26", "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: Verify transportation physical-protection subsystems as an integrated whole. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official 10 CFR 73.26 – Transportation physical protection systems 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 defined materials and shipments; routes, times, response, communications, and other protected security details must remain restricted and receive qualified 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

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.

\n

Verification and evidence

\n

Build a reproducible chain from 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)); 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)) 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

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

\n

Official references

\n", "content_text": "Keep this document to one review outcome: Verify transportation physical-protection subsystems as an integrated whole. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.26 – Transportation physical protection systems from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that operational tests and inspections be conducted for physical protection related subsystems and components to assure their maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)).\nUnder 10 CFR 73, the rule requires that preventive maintenance programs be established for physical protection related subsystems and components to assure their continued maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)).\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 defined materials and shipments; routes, times, response, communications, and other protected security details must remain restricted and receive qualified 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.26(h)(3) (eCFR anchor p-73.26(h)(3)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)), 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nBuild a reproducible chain from 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)); 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)) 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.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\n10 CFR 73.26 – Transportation physical protection systems — U.S. Nuclear Regulatory Commission via eCFR", "content_markdown": "Keep this document to one review outcome: Verify transportation physical-protection subsystems as an integrated whole. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [10 CFR 73.26 – Transportation physical protection systems](https://www.ecfr.gov/current/title-10/section-73.26) from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\n- Under 10 CFR 73, the rule requires that operational tests and inspections be conducted for physical protection related subsystems and components to assure their maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)).\n\n- Under 10 CFR 73, the rule requires that preventive maintenance programs be established for physical protection related subsystems and components to assure their continued maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)).\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 defined materials and shipments; routes, times, response, communications, and other protected security details must remain restricted and receive qualified 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.26(h)(3) (eCFR anchor p-73.26(h)(3)), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)), 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nBuild a reproducible chain from 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)); 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)) 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\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [10 CFR 73.26 – Transportation physical protection systems](https://www.ecfr.gov/current/title-10/section-73.26) — 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/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "url": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Verify transportation physical-protection subsystems as an integrated whole", "item": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/#article", "identifier": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "url": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/", "headline": "Verify transportation physical-protection subsystems as an integrated whole", "description": "Use 10 CFR 73.26 - Transportation physical protection systems to review this narrow operational decision without extending the source beyond its stated…", "abstract": "Use 10 CFR 73.26 - Transportation physical protection systems to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Keep this document to one review outcome: Verify transportation physical-protection subsystems as an integrated whole. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official 10 CFR 73.26 – Transportation physical protection systems from U.S. Nuclear Regulatory Commission via eCFR supports the following bounded statements:\n\nUnder 10 CFR 73, the rule requires that operational tests and inspections be conducted for physical protection related subsystems and components to assure their maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)).\nUnder 10 CFR 73, the rule requires that preventive maintenance programs be established for physical protection related subsystems and components to assure their continued maintenance in an operable and effective condition. The research record locates this support at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)).\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 defined materials and shipments; routes, times, response, communications, and other protected security details must remain restricted and receive qualified 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.26(h)(3) (eCFR anchor p-73.26(h)(3)), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)), 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nBuild a reproducible chain from 10 CFR 73.26(h)(3) (eCFR anchor p-73.26(h)(3)); 10 CFR 73.26(h)(4) (eCFR anchor p-73.26(h)(4)) 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.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\n10 CFR 73.26 – Transportation physical protection systems — U.S. Nuclear Regulatory Commission via eCFR", "datePublished": "2026-08-27T12:11:51+00:00", "dateModified": "2026-08-27T13:06:59+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/" }, "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/verify-transportation-physical-protection-subsystems-as-an-integrated-whole/#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": "Verify transportation physical-protection subsystems as an integrated whole" }, "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": 551, "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.26 - Transportation physical protection systems", "url": "https://www.ecfr.gov/current/title-10/section-73.26" } } ] } }