After this lesson you can describe how a shore-based SOC monitors a fleet over limited links; compare in-house, contracted and on-demand monitoring models using NIST SP 800-61; explain what the IACS UR E26 incident response plan must contain and how it guides ship–shore communication; set guardrails for remote response actions; and identify the reporting and record-keeping duties in the IMO Guidelines, E26 surveys and the U.S. Coast Guard rule.
Lesson 31 hunted for attackers on board, and Lesson 32 turned that knowledge into detection rules. This lesson, the last of PART 10, asks who is watching when those rules fire. For most ships, the answer is a security operations centre (SOC) on shore, looking after many ships at once.
A maritime SOC uses the same building blocks as any SOC — collection, a SIEM, analysts, playbooks — but it works under conditions no office SOC faces: data that arrives over limited satellite links, ships spread across every time zone, and a crew who are both the people affected and the first responders. The master stays responsible for the ship; the SOC's role is to see early, advise clearly and support the response.
As in the rest of this PART, the architectures and procedures here are teaching examples. Requirements quoted come from IACS, IMO, NIST and the U.S. Coast Guard documents listed at the end.
1. How a Fleet Is Watched from Shore
A ship cannot carry a full security operations centre. There is no room for a team of analysts, and the crew already has a ship to run. So monitoring is usually extended from shore: data collected on board travels over the ship's communication links to a shore-side SOC (Lesson 16), where analysts watch the whole fleet. IACS UR E26 anticipates this link between ship and shore — its rationale for the incident response plan says that designated personnel ashore should be integrated with the ship in the event of a cyber incident.
A useful fleet view answers a few plain questions for the analyst at the start of each shift: which ships are reporting, which are silent, which have open alerts, and which have a remote-access session in progress.
2. Who Watches — In-house, Provider or Both
NIST SP 800-61 Rev.3, the U.S. incident response guide, describes three ways an organisation can have incident handlers: on staff (its own team), on contract (for example, outsourcing a SOC to a managed security services provider, or MSSP), and available when needed (from a parent organisation, a cybersecurity services provider, a partner or law enforcement). It notes that many organisations combine them — performing basic incident response internally and engaging third parties for certain incidents. Shipping companies use the same three models.
3. When the SOC Calls the Ship
When the SOC sees something worrying, the first step is not a technical one: it is a call to the ship. The analyst should be able to tell the officer on watch, in plain terms, what was seen, which system it concerns, what the crew should check, and whether anything needs to be done now. Every contact is recorded as part of the incident record.
What the crew does next should already be written down. IACS UR E26 4.4.1 requires the shipowner to have an incident response plan with predetermined instructions or procedures to detect, respond to and limit the consequences of incidents, and sets out what it must contain as a minimum:
E26 also requires the plan to be kept in hard copy in case all electronic devices that would give access to it are lost, and to be kept up to date during the ship's life. For a shore SOC, this plan is the script both sides follow: the SOC can refer to a breakpoint or a response option by name, and the crew already knows what it means.
4. Acting from Shore — and Its Limits
Some shore teams can act on the ship directly — closing a remote session, blocking an address at the ship's firewall, or isolating an office PC through endpoint software (Lesson 20). These are powerful tools and need clear limits, because a mistaken action on a ship at sea can create a safety problem.
5. Reporting, Records and Surveys
Monitoring is only complete when incidents are reported and records are kept. Several layers of requirements apply, depending on the flag and the company's own rules.
The hardest part of maritime monitoring is not the technology; it is the conversation between shore and ship. A SOC that cannot reach the right person on board, or a crew that does not know what to do when called, turns a good detection into a missed one.
The simplest preparation costs almost nothing: a short contact sheet in the incident response plan, kept in hard copy as E26 requires — who the SOC calls, on which channel, who on board answers, and the first actions for the most likely alerts. Exercise it, as the U.S. rule and the IMO Guidelines' emphasis on drills suggest, before it is needed.
This completes PART 10. PART 11 turns to the rules themselves, starting with Lesson 34 — IACS UR E26: Cyber Resilience of Ships.
- Fleet monitoring has three layers: collection on board, a limited satellite link, and correlation and decision ashore. E26 expects designated shore personnel to be integrated with the ship during an incident.
- NIST SP 800-61 Rev.3 describes incident handlers on staff, on contract (such as an MSSP) or available when needed; most shipping companies combine them.
- Contracts with monitoring providers should define authority to act, information flows and restrictions on operational decisions; providers need OT skills and are themselves potential targets.
- The E26 incident response plan must include isolation breakpoints, alarms and indicators, expected consequences, response options that avoid shutdown where possible, and independent and local control information — and must be kept in hard copy.
- Remote actions from shore need agreed limits, preference for the least disruptive option, caution with automation and a known fallback on board.
- Reporting and records come from several layers: the IMO Guidelines, E26 survey evidence, national rules such as 33 CFR 101.650(g) for U.S.-flagged vessels, and contractual terms.
- IACS UR E26 Rev.1 (Nov 2023) — Cyber resilience of ships
- IMO MSC-FAL.1/Circ.3/Rev.4 — Guidelines on maritime cyber risk management (28 May 2026)
- NIST SP 800-61 Rev.3 — Incident Response Recommendations and Considerations for Cyber Risk Management (April 2025)
- NIST SP 800-82 Rev.3 — Guide to Operational Technology (OT) Security (September 2023)
- eCFR — 33 CFR Part 101, Subpart F: Cybersecurity (U.S. Coast Guard)
The architecture, procedures and guardrails in this lesson are this course's teaching illustrations, not a description of any particular company's SOC. Regulatory statements are taken from the documents listed above; 33 CFR Part 101 Subpart F applies to U.S.-flagged vessels and U.S. facilities, and other flag States set their own reporting rules.
Captain Paul writes the Maritime Cybersecurity Learning Roadmap on ShipPaulJobs — a step-by-step course that takes readers from security fundamentals to the cyber resilience rules that now apply to ships.
← Course Index LinkedIn⚓ Join the ShipPaulJobs Community
Join →

Comments
Post a Comment