Use an Alternative Security Program only within its approved scope and conditions

Use 33 CFR 105.140 -- Maritime Security: Facilities to review this narrow operational decision without extending the source beyond its stated scope.

Integrated video surveillance and controlled entry at a modern commercial facility.
DSE visual intelligencePhysical securityBriefing · 3 min read
Executive summary

What you need to know

Use 33 CFR 105.140 -- 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.140 -- 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.

Use this document to resolve one bounded operational decision: Use an Alternative Security Program only within its approved scope and conditions. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

  • Under 33 CFR 105, the rule requires that a facility owner or operator using an Alternative Security Program approved under section 101.120 of this subchapter complete and submit to the cognizant COTP a Facility Vulnerability and Security Measures Summary (Form CG-6025). The research record locates this support at 33 CFR 105.140(b) (eCFR anchor p-105.140(b)).
  • Under 33 CFR 105, a facility owner or operator may use an Alternative Security Program approved under section 101.120 of this subchapter if: the Alternative Security Program is appropriate to that facility. The research record locates this support at 33 CFR 105.140(a)(1), read with 33 CFR 105.140(a) (eCFR anchor p-105.140(a)(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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel before translating the source into an operational decision.

Applicability questions

  • For source statement 1 at 33 CFR 105.140(b) (eCFR anchor p-105.140(b)), which observable configuration, record, or test can confirm applicability here?
  • For source statement 2 at 33 CFR 105.140(a)(1), read with 33 CFR 105.140(a) (eCFR anchor p-105.140(a)(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.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include identity, Windows DNS where used, time, networks, power, life-safety systems, vendors, and monitoring personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

Build a reproducible chain from 33 CFR 105.140(b) (eCFR anchor p-105.140(b)); 33 CFR 105.140(a)(1), read with 33 CFR 105.140(a) (eCFR anchor p-105.140(a)(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.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

Primary reference

Review the official source

33 CFR 105.140 -- Maritime Security: Facilities · Verified August 26, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE