Verify cargo before handling and protect it from tampering at regulated facilities

Use this document to connect an official requirement or behavior to observable evidence: Verify cargo before handling and protect it from tampering at regulated facilities. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, cargo-handling security measures must be implemented to deter tampering. The research record locates this support at 33 CFR 105.265(a)(1), read with 33 CFR 105.265(a) (eCFR anchor p-105.265(a)(1)).
• Under 33 CFR 105, MARSEC Level 1 measures must, unless unsafe, routinely check cargo, cargo transport units, and cargo storage areas before and during handling for evidence of tampering. The research record locates this support at 33 CFR 105.265(b)(1), read with 33 CFR 105.265(b) (eCFR anchor p-105.265(b)(1)).

The source support ends with the statements listed above. Use them to examine access control, video, intrusion detection, communications, supporting facilities, operators, and documented response paths 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, 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.265(a)(1), read with 33 CFR 105.265(a) (eCFR anchor p-105.265(a)(1)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.265(b)(1), read with 33 CFR 105.265(b) (eCFR anchor p-105.265(b)(1)), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.

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, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Build a reproducible chain from 33 CFR 105.265(a)(1), read with 33 CFR 105.265(a) (eCFR anchor p-105.265(a)(1)); 33 CFR 105.265(b)(1), read with 33 CFR 105.265(b) (eCFR anchor p-105.265(b)(1)) to the observed environment. Useful domain evidence includes asset and firmware inventories, configuration exports, event tests, inspections, alarm response records, and maintenance findings; 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.265 — Maritime Security: Facilities — U.S. Coast Guard via eCFR