# Keep maritime-security communications available among facilities, vessels, authorities, and personnel > Use 33 CFR 105.235 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/keep-maritime-security-communications-available-among-facilities-vessels-authorities-and-personnel/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:11:15+00:00 - Modified: 2026-08-27T13:09:37+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Briefing - DSE priority: Advisory - Topics: Business Continuity, Cybersecurity - Reading time: 3 minutes ## What you need to know Use 33 CFR 105.235 -- 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.235 -- 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: Keep maritime-security communications available among facilities, vessels, authorities, and personnel. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [33 CFR 105.235 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.235) from U.S. Coast Guard via eCFR supports the following bounded statements: - Under 33 CFR 105, the rule requires that communication systems and procedures allow effective and continuous communications between the facility security personnel, vessels interfacing with the facility, the cognizant COTP, and national and local authorities with security responsibilities. The research record locates this support at 33 CFR 105.235(b) (eCFR anchor p-105.235(b)). - Under 33 CFR 105, the rule requires that the Facility Security Officer have a means to effectively notify facility personnel of changes in security conditions at the facility. The research record locates this support at 33 CFR 105.235(a) (eCFR anchor p-105.235(a)). Keep the evidence boundary at these traced claims. They support a review of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives; they do not support conclusions outside the source’s stated conditions. ## 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. No current deployment state or change approval follows from the source alone. Validate identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at 33 CFR 105.235(b) (eCFR anchor p-105.235(b)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 33 CFR 105.235(a) (eCFR anchor p-105.235(a)), which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions? - What baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, observed and expected states, owner, and reason for deviation. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery and sanitize protected material before retention. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.235(b) (eCFR anchor p-105.235(b)); 33 CFR 105.235(a) (eCFR anchor p-105.235(a)). Favor business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions, linked to stable identifiers, time, and operator. 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.235 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.235) — U.S. Coast Guard via eCFR ## Primary reference - Name: 33 CFR 105.235 -- Maritime Security: Facilities - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-33/section-105.235 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Keep maritime-security communications available among facilities, vessels, authorities, and personnel,” DSE Security, https://update.dsesecurity.com/updates/keep-maritime-security-communications-available-among-facilities-vessels-authorities-and-personnel/ 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.