Make regulated maritime-facility owners accountable for approved-plan operation and security coordination

Use this document to connect an official requirement or behavior to observable evidence: Make regulated maritime-facility owners accountable for approved-plan operation and security coordination. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official 33 CFR 105.200 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:

• Under 33 CFR 105, the rule requires that for each facility, the facility owner or operator ensure that adequate coordination of security issues takes place between the facility and vessels that call on it, including the execution of a Declaration of Security (DoS) as required by this part. The research record locates this support at 33 CFR 105.200(b)(8), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(8)).
• Under 33 CFR 105, the rule requires that for each facility, the facility owner or operator ensure that a Facility Security Assessment (FSA) is conducted. The research record locates this support at 33 CFR 105.200(b)(3), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(3)).

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths only where the source and recorded environment align.

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.200(b)(8), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(8)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.200(b)(3), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(3)), 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. Start with applicability, then compare the observed state with the cited source. 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

A reviewer should be able to retrace the decision from 33 CFR 105.200(b)(8), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(8)); 33 CFR 105.200(b)(3), read with 33 CFR 105.200(b) (eCFR anchor p-105.200(b)(3)) through asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings. Record what was collected, where, when, by whom, and which system or role it represents.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• 33 CFR 105.200 — Maritime Security: Facilities — U.S. Coast Guard via eCFR