# Control vessel stores and bunkers from arrival through delivery > Use 33 CFR 105.270 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/control-vessel-stores-and-bunkers-from-arrival-through-delivery/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:11:06+00:00 - Modified: 2026-08-27T13:09:38+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: Access Control, Cybersecurity, Video Surveillance - Reading time: 3 minutes ## What you need to know Use 33 CFR 105.270 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of 33 CFR 105.270 -- Maritime Security: Facilities ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Control vessel stores and bunkers from arrival through delivery. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [33 CFR 105.270 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.270) from U.S. Coast Guard via eCFR supports the following bounded statements: - Under 33 CFR 105, MARSEC Level 1 measures must require advance notice of vessel-stores or bunker deliveries, including a stores list, driver information, and vehicle-registration information. The research record locates this support at 33 CFR 105.270(b)(2), read with 33 CFR 105.270(b) (eCFR anchor p-105.270(b)(2)). - Under 33 CFR 105, facilities serving vessels routinely must establish standing arrangements with the vessel and its suppliers for delivery notice, timing, and documentation. The research record locates this support at 33 CFR 105.270(a)(4), read with 33 CFR 105.270(a) (eCFR anchor p-105.270(a)(4)). 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.270(b)(2), read with 33 CFR 105.270(b) (eCFR anchor p-105.270(b)(2)), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at 33 CFR 105.270(a)(4), read with 33 CFR 105.270(a) (eCFR anchor p-105.270(a)(4)), 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. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Build a reproducible chain from 33 CFR 105.270(b)(2), read with 33 CFR 105.270(b) (eCFR anchor p-105.270(b)(2)); 33 CFR 105.270(a)(4), read with 33 CFR 105.270(a) (eCFR anchor p-105.270(a)(4)) 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. 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.270 — Maritime Security: Facilities](https://www.ecfr.gov/current/title-33/section-105.270) — U.S. Coast Guard via eCFR ## Primary reference - Name: 33 CFR 105.270 -- Maritime Security: Facilities - Authority: www.ecfr.gov - URL: https://www.ecfr.gov/current/title-33/section-105.270 - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Control vessel stores and bunkers from arrival through delivery,” DSE Security, https://update.dsesecurity.com/updates/control-vessel-stores-and-bunkers-from-arrival-through-delivery/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.