Screen people, baggage, and stores entering cruise-ship terminals

Use this document to connect an official requirement or behavior to observable evidence: Screen people, baggage, and stores entering cruise-ship terminals. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, the rule requires that when a provision is fulfilled by a vessel, the applicable section of the terminal security program (TSP) refer to that fact. The research record locates this support at 33 CFR 105.290(a) (eCFR anchor p-105.290(a)).
• Under 33 CFR 105, the rule requires that at all MARSEC Levels, in coordination with a vessel moored at the facility, the facility owner or operator ensure the following security measures: provide additional security personnel to designated holding, waiting, or embarkation areas within the facility’s secure area. The research record locates this support at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces and the conditions the source actually describes.

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.290(a) (eCFR anchor p-105.290(a)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.

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 sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Keep the source locations 33 CFR 105.290(a) (eCFR anchor p-105.290(a)); 33 CFR 105.290(d), read with the unnumbered introductory paragraph of 33 CFR 105.290 (eCFR anchor p-105.290(d)) adjacent to the sanitized artifacts used for comparison. Prefer approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records, with enough identity and timing data for an independent recheck.

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

Official references

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