📚 Series Maritime Cybersecurity Learning Roadmap | PART 10 Lesson 33 — 3 of 3 in this PART · Course Index →

Maritime SOC and Shore-based Cyber Monitoring

Collecting on board, correlating ashore · in-house, provider or both · when the SOC calls the ship · guardrails for acting from shore · and the reporting and records that follow.

Captain Paul
Captain Paul
Maritime Cybersecurity · IACS UR E26/E27
November 2026
🎯 Lesson Objective

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.

Maritime Cybersecurity Learning Roadmap

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.

Three layers of fleet monitoring
1
On board — collect and keep

Monitoring required by E26 4.3.1 runs on board: network monitoring, alarms on malfunction or degraded capacity, audit records of security events, and any passive sensor (Lessons 31 and 32). A local collector gathers these events, keeps them during communication outages and forwards them when the link allows, with the most serious alerts first.

2
The link — limited and shared

Satellite bandwidth is shared with navigation, business and crew traffic. Summaries and alerts travel; full traffic captures usually stay on board unless an investigation needs them. The SOC must expect gaps and delayed data, and treat a ship that suddenly goes silent as something to check.

3
Ashore — correlate and decide

The shore SIEM (Lesson 17) receives events from every ship, labels each with the vessel and zone, and correlates them with company IT events. Because the analysts see many ships, they can notice the same pattern appearing on several vessels at once — something no single ship could see.

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.

Points to settle with a monitoring provider
1
Who may do what

NIST calls this a shared responsibility model and says the contract should define responsibilities, information flows, coordination and the authority to act on behalf of the organisation — including any restrictions on the provider making operational decisions, such as deactivating services to contain an incident. On a ship, any action that could affect navigation, propulsion or power should require the ship's agreement.

2
OT skills

NIST SP 800-82 Rev.3 says that when third parties monitor security controls, the people involved should have the skills to analyse OT environments. A provider that knows Windows servers but not ship systems will misread normal OT behaviour.

3
The provider as a target

NIST SP 800-82 warns that a third party which aggregates monitoring data from many organisations may be a desirable target for adversaries, and SP 800-61 notes that service providers often hold privileged access. Remote access by the provider is remote access to the ship, and falls under the same E26 4.2.6 controls: acceptance on board, logging and termination.

4
The benefit

SP 800-61 also notes that a service provider may detect malicious activity sooner because it can correlate events across its customers. For shipping, that cross-fleet view is often the main reason to use one.

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:

Minimum content of the E26 incident response plan
1
Breakpoints for isolation

Where compromised systems can be cut off — the points at which a zone can be disconnected (see also E26 4.4.3).

2
Alarms and indicators

A description of the alarms and indicators that signal a detected cyber event or abnormal symptoms caused by one.

3
Expected major consequences

What could happen to the ship's functions if each system is affected.

4
Response options

Prioritising options that do not rely on shutting down or transferring to independent or local control, where such options exist.

5
Independent and local control

Information for operating independently of the system that failed, as applicable (E26 4.4.2).

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.

Guardrails for acting from shore
1
Agree actions in advance

List which remote actions the SOC may take on its own, which need the master's or chief engineer's agreement, and which are never taken remotely. NIST SP 800-61's advice to define the provider's authority to act applies equally to an in-house team.

2
Prefer the least disruptive option

E26 asks the plan to prioritise response options that do not depend on shutdown or a switch to local control. Closing a supplier session is usually safer than disconnecting a whole zone.

3
Be careful with automation

NIST SP 800-82 asks organisations to consider the impact of automated responses on OT before deploying them. An automatic block that works well in an office network may cut a control link on a ship.

4
Know the fallback

If a zone must be isolated, the crew must be ready to run the affected function independently. E26 4.4.2 and 4.4.4 require independent local control where needed and systems that fall back to a minimal risk condition.

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.

Reporting and records
1
IMO Guidelines (Rev.4)

Under Respond, report incidents to the necessary parties within the time frames defined by the Administration, and keep records of cyber incidents. Under Recover, carry out root cause analysis so that underlying issues are resolved.

2
IACS UR E26 surveys

At the first annual survey the shipowner must show records that the CBSs are routinely monitored for anomalies and that any cyber incidents were responded to in accordance with the incident response plans. The SOC's case records and shift logs are part of that evidence.

3
U.S. Coast Guard rule (U.S.-flagged vessels)

33 CFR 101.650(g) requires reportable cyber incidents to be reported to the National Response Center without delay (for entities not already reporting under 33 CFR 6.16-1), a Cyber Incident Response Plan that is developed, maintained and exercised, and backups of critical IT and OT systems that are protected and tested.

4
Contracts and insurance

Charter parties, insurance policies and supplier contracts may contain their own notification terms. The SOC's escalation list should include whoever in the company is responsible for those notifications.

Check the rules that apply to your ships: Reporting duties differ by flag State and by the type of ship or facility. The U.S. rule above applies to U.S.-flagged vessels and U.S. facilities; other Administrations set their own time frames.
⚓ 6. Maritime Connection — Prepare the Ship–Shore Conversation

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.

✅ Key Takeaways — Lesson 33
  • 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.
📎 Official Sources & Further Reading

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.

📚 PART 10 — Maritime Threat Detection and Resilience
DoneLesson 31 — Threat Hunting in Maritime OT DoneLesson 32 — Detection Engineering for Maritime OT
Current LessonLesson 33 — Maritime SOC and Shore-based Cyber Monitoring
← Previous lesson
Lesson 32 — Detection Engineering for Maritime OT
Next lesson →
Lesson 34 — IACS UR E26: Cyber Resilience of Ships (PART 11, coming next)
Captain Paul
Captain Paul
Maritime Cybersecurity · IACS UR E26/E27 · ShipPaulJobs

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 →
Share

Comments

Top Ranked · Last 30 Days

Popular Posts