What you need to know
Use 33 CFR 105.415 -- 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.415 -- 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.
Use this document to connect an official requirement or behavior to observable evidence: Audit the Facility Security Plan annually and amend it after material change. Only the official source and traced locations below supply facts. Confirm applicability before acting.
Source fact:
The official 33 CFR 105.415 — Maritime Security: Facilities from U.S. Coast Guard via eCFR supports the following bounded statements:
- Under 33 CFR 105, the FSO must ensure an annual FSP audit beginning within one year after initial approval and attach a letter certifying that the plan meets applicable part 105 requirements. The research record locates this support at 33 CFR 105.415(b)(1) (eCFR anchor p-105.415(b)(1)).
- Under 33 CFR 105, the FSP must be audited after a change in facility ownership or operator, or after modifications to physical structure, emergency procedures, security measures, or operations. The research record locates this support at 33 CFR 105.415(b)(2) (eCFR anchor p-105.415(b)(2)).
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.415(b)(1) (eCFR anchor p-105.415(b)(1)), which observable configuration, record, or test can confirm applicability here?
- For source statement 2 at 33 CFR 105.415(b)(2) (eCFR anchor p-105.415(b)(2)), 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.
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
Tie each conclusion back to 33 CFR 105.415(b)(1) (eCFR anchor p-105.415(b)(1)); 33 CFR 105.415(b)(2) (eCFR anchor p-105.415(b)(2)) 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.
Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.
Official references
- 33 CFR 105.415 — Maritime Security: Facilities — U.S. Coast Guard via eCFR
Review the official source
33 CFR 105.415 -- 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