The Coast Guard's final rule on cybersecurity in the Marine Transportation System added Subpart F to 33 CFR Part 101. It took effect on July 16, 2025, and applies to owners and operators of U.S.-flagged vessels, waterfront facilities and OCS facilities already regulated under 33 CFR Parts 104, 105 and 106. Cybersecurity Plans are due to the Coast Guard for review and approval by July 16, 2027.
That is less time than it sounds. Most of the work in a Subpart F plan is not writing; it is finding out what you actually have. These are the practices we see separate facilities that will be ready from those that will be scrambling.
1. Start with an honest asset and network inventory
You cannot assess, segment or defend what you have not enumerated. For a terminal or vessel that means IT systems, but also the operational technology that keeps cargo moving: crane controls, gate and access-control systems, terminal operating systems, fuel and utility controls, CCTV, and the remote-access paths vendors use to support them.
Build the inventory from the network outward, not from procurement records. Procurement tells you what was bought; the network tells you what is talking.
2. Designate the Cybersecurity Officer early
Subpart F requires a designated Cybersecurity Officer (CySO). The common failure is naming someone on paper who has neither the authority nor the time. The CySO needs:
- A clear line to the people who control IT, OT and physical security budgets
- Enough technical grounding to challenge a vendor or an internal team
- Time protected for drills, reviews and incident reporting
If your facility security officer also carries the CySO role, be explicit about how the workload is split. For smaller operators, a fractional CySO is often more defensible than an overloaded employee.
3. Treat the Cybersecurity Assessment as the foundation, not a formality
The plan should be a consequence of the assessment, not the other way around. A defensible assessment identifies your critical systems, the threats and vulnerabilities that realistically apply to them, and the controls you have (or lack). Every control statement in your plan should trace back to something the assessment found.
Reviewers can tell when a plan was written from a template. Specificity is what makes it credible.
4. Map the technical measures to your real environment
The rule calls for baseline measures in areas such as account security (including multi-factor authentication), device security, data security, network segmentation, risk management and resilience. Do not copy control language verbatim. For each measure, record:
- What the control is in your environment
- Where it is deployed and where it is not
- The owner, and how you will evidence it
- Any documented compensating control where a measure is not technically feasible, particularly on legacy OT
The goal is not a plan that sounds compliant. It is a plan that an operator can follow at 2 a.m. during an incident.
5. Plan drills before you need them
Subpart F expects cyber drills and exercises, and incident reporting to the National Response Center is already part of the picture. Run a tabletop early, even before your plan is approved. It is the fastest way to discover that nobody knows who calls the NRC, or that your OT vendor's emergency number is out of date.
6. Build evidence as you go
Approval is only the beginning. Inspectors will ask for proof that the plan is operating: training records, drill after-action reports, patch and access reviews, assessment updates. Decide now where that evidence lives and who is responsible for refreshing it. Manual spreadsheets work until the first personnel change; this is exactly the problem ccSentinel was built to solve.
Where to begin this quarter
If you have not started, a sensible order is: inventory, CySO designation, assessment, gap remediation plan, plan drafting, then drill. Work backward from July 2027 and leave room for Coast Guard review comments.
This article is general guidance, not legal advice. Always confirm requirements against the current text of 33 CFR Part 101 Subpart F.


