Designate and protect restricted maritime-facility areas based on operations and risk

Frame this document as a source-led configuration and assurance check: Designate and protect restricted maritime-facility areas based on operations and risk. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, a facility owner or operator must designate restricted areas to protect the facility. The research record locates this support at 33 CFR 105.260(a)(3), read with 33 CFR 105.260(a) (eCFR anchor p-105.260(a)(3)).
• Under 33 CFR 105, restricted areas must be clearly marked to show that access is restricted and unauthorized presence constitutes a security breach. The research record locates this support at 33 CFR 105.260(c)(6), read with 33 CFR 105.260(c) (eCFR anchor p-105.260(c)(6)).

The source support ends with the statements listed above. Use them to examine credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces in the applicable environment, not to imply a wider guarantee.

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 sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at 33 CFR 105.260(a)(3), read with 33 CFR 105.260(a) (eCFR anchor p-105.260(a)(3)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.260(c)(6), read with 33 CFR 105.260(c) (eCFR anchor p-105.260(c)(6)), which observable configuration, record, or test can confirm applicability here?
• Which owner can attest to the recorded state of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, including exceptions?
• What baseline for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces, 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 sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before and after the test, and store only sanitized operational evidence.

Verification and evidence

Build a reproducible chain from 33 CFR 105.260(a)(3), read with 33 CFR 105.260(a) (eCFR anchor p-105.260(a)(3)); 33 CFR 105.260(c)(6), read with 33 CFR 105.260(c) (eCFR anchor p-105.260(c)(6)) to the observed environment. Useful domain evidence includes approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records; label every item with scope, timestamp, collector, and stable identifier.

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.260 — Maritime Security: Facilities — U.S. Coast Guard via eCFR