# Base the Facility Security Plan on an approved assessment and site-specific operations > Use 33 CFR 105.400 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/base-the-facility-security-plan-on-an-approved-assessment-and-site-specific-operations/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:10:55+00:00 - Modified: 2026-08-27T13:09:38+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 33 CFR 105.400 -- Maritime Security: Facilities 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 33 CFR 105.400 -- Maritime Security: Facilities ## 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: Base the Facility Security Plan on an approved assessment and site-specific operations. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [33 CFR 105.400 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.400) from U.S. Coast Guard via eCFR supports the following bounded statements: - Under 33 CFR 105, an FSP must address every vulnerability identified in the Facility Security Assessment. The research record locates this support at 33 CFR 105.400(a)(3), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(3)). - Under 33 CFR 105, an FSP may cover multiple facilities with similar designs and operations only when the cognizant COTP authorizes and approves that scope. The research record locates this support at 33 CFR 105.400(a)(5), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(5)). Only the traced statements above are asserted as source facts. Apply the review to access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths after confirming that the source and deployed context match. ## What the source does not establish Applies only to facilities within 33 CFR part 105 and the cited section. Confirm Coast Guard jurisdiction, the approved Facility Security Plan, the current MARSEC level, and any approved alternatives; this is not legal advice or a universal facility-design standard. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision. ## Applicability questions - For source statement 1 at 33 CFR 105.400(a)(3), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(3)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 33 CFR 105.400(a)(5), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(5)), which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths, including exceptions? - What baseline for identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Tie each conclusion back to 33 CFR 105.400(a)(3), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(3)); 33 CFR 105.400(a)(5), read with 33 CFR 105.400(a) (eCFR anchor p-105.400(a)(5)) and to observable material such as asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Preserve provenance and stable identifiers without copying secrets into the evidence set. 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. ## Official references - [33 CFR 105.400 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.400) — U.S. Coast Guard via eCFR ## Primary reference - Name: 33 CFR 105.400 -- Maritime Security: Facilities - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-33/section-105.400 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Base the Facility Security Plan on an approved assessment and site-specific operations,” DSE Security, https://update.dsesecurity.com/updates/base-the-facility-security-plan-on-an-approved-assessment-and-site-specific-operations/ 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.