Apply passenger and ferry facility controls to unattended vehicles and screening areas

Frame this document as a source-led configuration and assurance check: Apply passenger and ferry facility controls to unattended vehicles and screening areas. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, passenger and ferry facilities must segregate unchecked people and personal effects from those already checked. The research record locates this support at 33 CFR 105.285(a)(1), read with 33 CFR 105.285(a) (eCFR anchor p-105.285(a)(1)).
• Under 33 CFR 105, passenger and ferry facilities must screen unaccompanied vehicles before loading them on passenger vessels. The research record locates this support at 33 CFR 105.285(a)(3), read with 33 CFR 105.285(a) (eCFR anchor p-105.285(a)(3)).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths 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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

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

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before and after the test, and store only sanitized operational evidence.

Verification and evidence

Keep the source locations 33 CFR 105.285(a)(1), read with 33 CFR 105.285(a) (eCFR anchor p-105.285(a)(1)); 33 CFR 105.285(a)(3), read with 33 CFR 105.285(a) (eCFR anchor p-105.285(a)(3)) adjacent to the sanitized artifacts used for comparison. Prefer asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings, with enough identity and timing data for an independent recheck.

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