Train cruise-terminal screeners before independent screening duties

Frame this document as a source-led configuration and assurance check: Train cruise-terminal screeners before independent screening duties. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, in addition to the requirements for facility personnel with security duties in section 105.210, screening personnel at cruise ship terminals must demonstrate knowledge, understanding, and proficiency in the following areas as part of their security-related familiarization: the purpose and contents of the cruise ship terminal PIL. The research record locates this support at 33 CFR 105.535(c), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(c)).
• Under 33 CFR 105, in addition to the requirements for facility personnel with security duties in section 105.210, screening personnel at cruise ship terminals must demonstrate knowledge, understanding, and proficiency in the following areas as part of their security-related familiarization: terminal-specific response procedures when a dangerous substance or device is detected. The research record locates this support at 33 CFR 105.535(e), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(e)).

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. 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.535(c), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(c)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.535(e), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(e)), 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.

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

Build a reproducible chain from 33 CFR 105.535(c), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(c)); 33 CFR 105.535(e), read with the unnumbered introductory paragraph of 33 CFR 105.535 (eCFR anchor p-105.535(e)) 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.

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