What you need to know
Use 33 CFR 105.205 -- 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.205 -- 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.
Keep this document to one review outcome: Give the Facility Security Officer authority, access, and continuous contact coverage. Only the official source and traced locations below supply facts. Confirm applicability before acting.
Source fact:
The official 33 CFR 105.205 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:
- Under 33 CFR 105, in addition to those responsibilities and duties specified elsewhere in this part, the FSO must, for each facility for which he or she has been designated: ensure that the Facility Security Assessment (FSA) is conducted. The research record locates this support at 33 CFR 105.205(c)(1), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(1)).
- Under 33 CFR 105, in addition to those responsibilities and duties specified elsewhere in this part, the FSO must, for each facility for which he or she has been designated: ensure the security awareness and vigilance of the facility personnel. The research record locates this support at 33 CFR 105.205(c)(6), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(6)).
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.205(c)(1), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(1)), which observable configuration, record, or test can confirm applicability here?
- For source statement 2 at 33 CFR 105.205(c)(6), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(6)), 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.
For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.
Verification and evidence
A reviewer should be able to retrace the decision from 33 CFR 105.205(c)(1), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(1)); 33 CFR 105.205(c)(6), read with 33 CFR 105.205(c) (eCFR anchor p-105.205(c)(6)) 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.
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.205 — Maritime Security: Facilities — U.S. Coast Guard via eCFR
Review the official source
33 CFR 105.205 -- 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