Coordinate MARSEC level changes and implement the approved measures on time

Keep this document to one review outcome: Coordinate MARSEC level changes and implement the approved measures on time. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

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

• Under 33 CFR 105, at MARSEC Level 3, in addition to the requirements in this part, a facility owner or operator may be required to implement additional measures, pursuant to 33 CFR part 6, 160, or 165, as appropriate, which may include but are not limited to use of armed security personnel to control access to the facility and to deter, to the maximum extent practical, a transportation security incident. The research record locates this support at 33 CFR 105.230(e)(2), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(2)).
• Under 33 CFR 105, at MARSEC Level 3, in addition to the requirements in this part, a facility owner or operator may be required to implement additional measures, pursuant to 33 CFR part 6, 160, or 165, as appropriate, which may include but are not limited to use of waterborne security patrol. The research record locates this support at 33 CFR 105.230(e)(1), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(1)).

Only the traced statements above are asserted as source facts. Apply the review to essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives after confirming that the source and deployed context match.

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, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at 33 CFR 105.230(e)(2), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(2)), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at 33 CFR 105.230(e)(1), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(1)), which observable configuration, record, or test can confirm applicability here?
• Which owner can attest to the recorded state of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, including exceptions?
• What baseline for identity, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery 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. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of essential functions, upstream providers, recovery sequences, alternate work paths, and tested recovery objectives, 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, DNS, communications, facilities, suppliers, and the people authorized to invoke recovery in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

Tie each conclusion back to 33 CFR 105.230(e)(2), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(2)); 33 CFR 105.230(e)(1), read with 33 CFR 105.230(e) (eCFR anchor p-105.230(e)(1)) and to observable material such as business-impact records, dependency maps, exercise results, recovery timings, and open corrective actions. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• 33 CFR 105.230 — Maritime Security: Facilities — U.S. Coast Guard via eCFR