Prepare for a Coast Guard Cybersecurity Audit
The Coast Guard conducts inspections. The vessel or facility operator arranges the independent audit of its cybersecurity plan. Use this guide and workbook to prepare for both, starting with one operating function and the records that show how your team protects it.
Establish who owns the plan
Find the applicable security plan, its approval letter and the owner or operator named on it. For a passenger vessel, record the flag, vessel type and whether Part 104 requires a plan. For a terminal, confirm Part 105 applicability and the approved facility boundary. Subpart F also addresses covered Outer Continental Shelf facilities under Part 106. Use the relevant authority when the answer is uncertain.
A foreign flagged ship calling in Miami follows a different route. Check its flag administration, applicable ISM safety management and U.S. port requirements. A vessel operator, terminal operator, tenant and vendor can share a service while carrying different legal or contract duties. Record a name and a reason for each assignment.
Put the right dates on the calendar
For covered operators the initial required training for personnel with IT or OT access fell due January 12, 2026. Check role specific and contractor coverage, attendance and annual refreshers. Capture evidence of training for new personnel under the applicable procedure.
By July 16, 2027, designate the Cybersecurity Officer in writing, complete the initial Cybersecurity Assessment and submit the Cybersecurity Plan for Coast Guard approval. Under NVIC 02-26, prepare to operate to the requirements and submitted plan by that date. The Coast Guard makes approval decisions. Keep your submission receipt, the agency’s response and any conditions together.
The assessment recurs annually and sooner after an ownership change. Separately, the CySO arranges the audit of the plan and its implementation. Section 101.630(f) ties the first annual audit to initial approval. NVIC 02-26 uses July 16, 2027 as the recurring schedule anchor for early approvals. A change in owner or operator or a change to cybersecurity measures can also require an audit. Record the approval date and how you calculated your next due date.
Schedule two cybersecurity drills each calendar year and an exercise each calendar year, with no more than 18 months between exercises, under the applicable implementation schedule. An exercise can be tabletop. Save objectives, participants, decisions, deficiencies and proof of corrective action.
- 33 CFR Part 101, Subpart F | Coverage, assessments, plans and audits
- U.S. Coast Guard | NVIC 02-26 implementation guidance, including the plan crosswalk
- Signed copy of Coast Guard NVIC 02-26 | Maritime Exchange document library
- U.S. Coast Guard | Maritime industry cybersecurity resources and current guidance
Trace one operation to its supporting records
Ask the master or terminal operations lead which function must be restored first on a difficult shift. List the equipment, business service, outside support and decision makers that function depends on. The CySO determines critical IT and OT against the transportation security incident criterion in the rule.
For navigation, pick a bridge function such as electronic chart display. Ask for a dated service record, the responsible officer and the approved alternate procedure. For a terminal, choose a boarding gate, baggage or cargo handling function. Ask who authorized the last vendor visit, what record shows it ended and when operations verified the return to service.
Then trace one ordinary IT dependency, such as identity management, backups or shore communications. Sample access approval, removal, a recent recovery record and the operating team’s signoff. Record each document reference, its date, the custodian and what the reviewer could verify. Agree operational limits with the master or facility lead before any activity on equipment.
Follow one passenger or crew record
Start with one type of record, such as a manifest, crew roster or terminal access record. Identify who collects it, who receives it ashore, what the supplier retains, who authorizes access and how long each copy is kept. Use an example field name or redacted evidence reference. Keep the underlying record in the operator’s controlled system.
Have privacy counsel determine the jurisdictions, applicable duties, notices and clocks. Florida § 501.171 has defined entities, protected data and triggers. Its notice duties can run from determination of a breach or reason to believe one occurred. Its definition and thresholds are distinct from the Coast Guard’s reportable cyber incident test. Maritime reporting can also be triggered by actual or reasonably potential disclosure of, or unauthorized access to, nonpublic personal information of a significant number of individuals.
Rehearse the first notifications
Give the watch and duty manager a current reporting card owned by the CySO. Record who handles immediate safety, who contacts authorities, the time of the first observation and the authority’s reference. Use approved maritime safety and emergency procedures immediately when needed.
Follow the applicable branch of NVIC 02-24 Change 1. For actual or threatened cyber incidents within 33 CFR 6.16-1, report immediately. Under the Coast Guard guidance, calling the National Response Center at 800-424-8802 satisfies the Coast Guard Captain of the Port and FBI notifications. Report separately to CISA at 844-729-2472. For a covered reportable cyber incident not already reported to the Coast Guard under Part 6, § 101.650(g)(1) requires reporting to the NRC without delay. For a transportation security incident on a Part 104 vessel or at a Part 105 facility, notify the local Captain of the Port without delay, then immediately follow the security plan. A Part 106 offshore facility instead notifies the cognizant District Commander without delay, then immediately follows its plan. Maintain the appropriate local contacts and reporting routes for your operation.
Keep official reporting contacts and commercial incident support clearly labeled on the duty card. Record each actual notification and direct sensitive follow up through the approved channel.
Prepare for an independent audit and close findings
Build an evidence index covering governance, the assessment, training, exercises, equipment and vendor records, access, backups and recovery, protected communications, and incident handling. Map each entry to the relevant plan section. Keep required records under § 101.640 and the relevant vessel or facility provisions. Use a controlled reference for security plans and other Sensitive Security Information.
For the annual internal audit, document the auditor’s knowledge, absence of regularly assigned cybersecurity duties for the entity being audited, and independence from the measures being evaluated. Assign readiness assistance and subsequent audit work with those conditions in mind. The CySO attaches the required audit report to the plan.
For each open item, record the requirement, evidence sampled, consequence, accountable owner, target date and proof required to close. Have an independent reviewer verify the fix. If the audit requires a plan amendment, § 101.630(f)(5) calls for submission to the Coast Guard within 30 days after completing the audit. Save the submission and agency correspondence with the finding.
Use the evidence workbook
Save a blank copy for each vessel or facility. It includes a coverage decision, due date record, IT and OT evidence sample, privacy and notification checks, and a corrective action with a reviewer and verification date. Enter document references and dates. Keep sensitive source material in its controlled repository.
Download the fillable workbook (PDF)Bring your first open item to GDF
Choose the team that fits your operation. On the first call we will identify the plan owner, your deadline and which records you already have.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Reviewed .