Build a cruise-terminal screening program around documented procedures and prohibited items

Keep this document to one review outcome: Build a cruise-terminal screening program around documented procedures and prohibited items. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, the rule requires that the TSP document all procedures that are employed to ensure all persons, baggage, and personal effects are screened at the cruise ship terminal prior to being allowed into a cruise ship terminal’s secure areas or onto a cruise ship. The research record locates this support at 33 CFR 105.505(a)(1), read with 33 CFR 105.505(a) (eCFR anchor p-105.505(a)(1)).
• Under 33 CFR 105, the rule requires that the TSP include the procedures used when prohibited items are detected. The research record locates this support at 33 CFR 105.505(c)(10), read with 33 CFR 105.505(c) (eCFR anchor p-105.505(c)(10)).

Only the traced statements above are asserted as source facts. Apply the review to credentials, readers, controllers, panels, door hardware, access decisions, monitoring, and life-safety interfaces 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 sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators before translating the source into an operational decision.

Applicability questions

• For source statement 1 at 33 CFR 105.505(a)(1), read with 33 CFR 105.505(a) (eCFR anchor p-105.505(a)(1)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.505(c)(10), read with 33 CFR 105.505(c) (eCFR anchor p-105.505(c)(10)), 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. Begin by recording scope and current state before deciding whether a change is warranted. 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.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for identity sources, DNS where used, time, networks, power, fire systems, monitoring, and authorized operators and sanitize protected material before retention.

Verification and evidence

Tie each conclusion back to 33 CFR 105.505(a)(1), read with 33 CFR 105.505(a) (eCFR anchor p-105.505(a)(1)); 33 CFR 105.505(c)(10), read with 33 CFR 105.505(c) (eCFR anchor p-105.505(c)(10)) and to observable material such as approved configuration exports, access-event tests, controller state, door inspections, alarm handling, and exception records. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

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