What you need to know
Use 33 CFR 105.245 -- 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.245 -- 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.
Frame this document as a source-led configuration and assurance check: Use Declarations of Security to assign shared facility-vessel security duties. Only the official source and traced locations below supply facts. Confirm applicability before acting.
Source fact:
The official 33 CFR 105.245 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:
- Under 33 CFR 105, the rule requires that each facility owner or operator ensure procedures are established for requesting a DoS and for handling DoS requests from a vessel. The research record locates this support at 33 CFR 105.245(a) (eCFR anchor p-105.245(a)).
- Under 33 CFR 105, the COTP may require, at any time, at any MARSEC Level, any facility subject to this part to implement a DoS with the VSO prior to any vessel-to-facility interface when he or she deems it necessary. The research record locates this support at 33 CFR 105.245(h) (eCFR anchor p-105.245(h)).
Keep the evidence boundary at these traced claims. They support a review of access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths; 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, and treat examples or options as conditional inputs rather than defaults.
Applicability questions
- For source statement 1 at 33 CFR 105.245(a) (eCFR anchor p-105.245(a)), which observable configuration, record, or test can confirm applicability here?
- For source statement 2 at 33 CFR 105.245(h) (eCFR anchor p-105.245(h)), 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. Anchor the review in the cited section and keep observation separate from interpretation. 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.
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.
Verification and evidence
Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations 33 CFR 105.245(a) (eCFR anchor p-105.245(a)); 33 CFR 105.245(h) (eCFR anchor p-105.245(h)). Favor asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, linked to stable identifiers, time, and operator.
Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.
Official references
- 33 CFR 105.245 — Maritime Security: Facilities — U.S. Coast Guard via eCFR
Review the official source
33 CFR 105.245 -- Maritime Security: Facilities · Verified August 26, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE