📚 Series Maritime Cybersecurity Learning Roadmap | PART 9 Lesson 29 — 2 of 3 in this PART · Course Index →

Shipboard IT and OT Architecture

The bridge · the engine room · cargo and safety systems · the office and crew networks · the links to shore · and how IACS UR E26 asks you to divide all of it into security zones.

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

After this lesson you can name the main computer-based systems found on a merchant ship and what each one does — ECDIS, AIS, radar, GNSS, GMDSS, VDR, IAS, AMS, PMS and propulsion and steering control — tell which are IT and which are OT, describe the paths that connect them to each other and to shore, and explain the security-zone rules in IACS UR E26 section 4.2.1, including which systems must be kept apart and which must be physically separated.

Maritime Cybersecurity Learning Roadmap

Lesson 28 explained why a ship is a different place to defend. Before we can talk about attacks (Lesson 30) or defences, we need a map: what is actually on board, and how is it wired together? A security officer who cannot draw the ship's network is in the same position as a navigator without a chart.

The IMO Guidelines on maritime cyber risk management give a useful first list of the systems that matter: bridge systems; cargo, bunkering, ballast and other pumping systems; propulsion, machinery and power control; security and access control; passenger and crew servicing systems; public-facing networks for passengers and crew; administrative and crew welfare systems; ship-port interfaces; and ship-to-shore integrated systems. This lesson walks through them from the bridge down.

The descriptions of equipment below are generic and simplified for teaching. Every ship is different, and the real answer for any vessel is in its own asset inventory and network drawings.

1. The Bridge — Navigation and Communication

The bridge holds the systems the officer of the watch uses to know where the ship is, what is around it, and how to call for help. IACS UR E26 includes in its scope the “navigational systems required by statutory regulations” and the “internal and external communication systems required by class rules and statutory regulations”.

Main bridge systems
1
ECDIS — Electronic Chart Display and Information System

The electronic chart table. It shows official electronic charts with the ship's position, heading and route on top, and raises alarms, for example when the planned track runs into shallow water. It needs chart and software updates from shore.

2
GNSS receiver

Receives satellite navigation signals (GPS and others) and turns them into position, speed and time. Many other systems — ECDIS, AIS, radar overlays, the VDR, even satellite communications — take their position or time from it.

3
Radar

Detects other ships, land and obstacles by radio echoes. It works without any outside signal, which makes it an important cross-check on GNSS.

4
AIS — Automatic Identification System

A VHF radio system that broadcasts the ship's identity, position, course and speed, and receives the same from others. Its technical characteristics are set out in ITU-R Recommendation M.1371. Lesson 30 explains why its messages should not be taken at face value.

5
GMDSS — Global Maritime Distress and Safety System

The radio and satellite equipment used for distress alerts, safety messages and routine calls. It must work when everything else has failed.

6
VDR — Voyage Data Recorder

The ship's “black box”. It records bridge audio, radar images, position and other data so that an accident can be investigated. It collects data from many systems, so it is connected to many of them.

Many of these systems exchange data over the bridge's sensor network using maritime interface standards. E26 notes that navigation and radio equipment approved to IEC 61162-460 — a standard for securing these maritime networks — or an equivalent standard may be accepted in place of the E27 security capabilities, provided E26 itself is met.

2. The Engine Room — Automation, Power and Propulsion

Below decks, computers watch and control the machinery that keeps the ship moving and powered. E26 lists the functions whose control systems must be considered: propulsion, steering, anchoring and mooring, electrical power generation and distribution, fire detection and extinguishing, bilge and ballast systems and the loading computer, watertight integrity and flooding detection, lighting, and required safety systems such as emergency shutdown and gas detection.

Typical machinery systems
1
IAS — Integrated Automation System

Brings the engine room's monitoring and control together on workstations in the engine control room and, often, on the bridge. It is usually the largest OT network on board.

2
AMS — Alarm Monitoring System

Watches hundreds of sensors — temperatures, pressures, levels — and raises alarms to the engineers. On many ships it is part of the IAS.

3
PMS — Power Management System

Starts, stops and shares load between generators so that electrical power is always available. A fault here can lead to a blackout.

4
Propulsion and steering control

Controls the main engine or electric propulsion, propeller pitch and thrusters, and passes the rudder orders from the bridge to the steering gear.

Inside these systems sit PLCs (programmable logic controllers): small, rugged computers that read sensors and drive valves, pumps and motors. IACS UR E27 lists the kinds of equipment it covers as network devices (routers, managed switches), security devices (firewalls, intrusion detection), computers (workstations, servers), automation devices such as PLCs, and cloud-hosted virtual machines.

Seamanship analogy: the IAS is the engine room's nervous system. Like a nervous system, it is most dangerous when it gives a false picture — an engineer will trust a gauge that reads normal.

3. Cargo, Safety and the Ship's Office

Cargo systems depend on the ship type: cargo pumps and tank gauging on a tanker, reefer monitoring on a container ship, ballast control and the loading computer on almost every ship. Safety systems — fire detection, fixed fire-extinguishing release, flooding detection and emergency shutdown — protect life and must work every time.

Alongside the OT sits ordinary IT: the master's and chief engineer's office computers, a server or file share for the ship's documents, email, and the planned-maintenance and procurement software that reports to the office ashore. Then there is the crew welfare network, giving crew members Internet access for their own phones and laptops, and on passenger ships the passenger networks.

E26 is precise about where these belong. Administrative networks, crew welfare systems, passenger networks and passenger servicing systems are not themselves in the scope of the rule, but any IP-based communication interface between an in-scope OT system and them is in scope. Anything outside the scope is treated as an untrusted network.

4. The Paths That Join Everything

On paper, IT and OT are separate. In practice data has to move between them, and between ship and shore. These paths are where most security work happens:

Common connection paths
1
Ship to shore

Satellite and radio links carry email, reports, engine performance data sent to the office or the engine maker, weather routing and, increasingly, remote monitoring.

2
Remote maintenance

Suppliers connect from shore to diagnose and update their equipment. E26 4.2.6 requires secure, authenticated, encrypted connections, logging, and that a session is not possible until explicitly accepted by a responsible role on board; for remote maintenance it adds further requirements, including multi-factor authentication of the remote user.

3
Updates and data transfer

Chart updates, software patches and cargo plans may arrive over the network or on USB drives. E26 4.2.7 limits mobile and portable devices to necessary activities, authorised people and authorised devices — and requires interface ports to be physically blocked on any system that cannot meet these controls.

4
Wireless

Wi-Fi access points and wireless sensors are convenient and reach further than cables. E26 requires wireless devices to sit in their own dedicated security zones.

5
Integration links

Data from one system feeds another: GNSS into ECDIS and VDR, machinery data into the bridge displays, the loading computer into ballast control. Each link is a path that must be documented.

5. Security Zones — How E26 Divides the Ship

A security zone, in E26's definition, is a collection of computer-based systems that meet the same security requirements, with an access-control policy applied to its interfaces. Think of the ship's watertight bulkheads: a breach in one compartment should not flood the next. Zones do the same for a cyber incident. E26 explains that segmentation reduces the attack surface and prevents attackers from moving laterally between systems.

The core requirements of E26 section 4.2.1, in plain words:

IACS UR E26 4.2.1 — security zone rules
RuleWhat it means on board
Group every in-scope system into zonesEach zone has defined security policies and capabilities. Zones are either air-gapped or connected only through devices that control the data passing between them — E26 gives firewalls/routers, simplex serial links, TCP/IP diodes and dry contacts as examples.
Only explicitly allowed trafficNothing crosses a zone boundary unless it has been deliberately allowed and documented (for example, as firewall rules).
Safety systems apartSystems providing required safety functions go in separate zones and must be physically segmented from other zones.
Bridge apart from machineryNavigation and communication systems must not share a zone with machinery or cargo systems.
Wireless apartWireless devices go in dedicated zones.
Untrusted networks physically apartSystems outside the scope — office IT, crew welfare and the like — are untrusted networks and must be physically segmented from the required zones.
Isolate without losing the functionIt must be possible to isolate a zone without affecting the primary functionality of the systems in it — which supports the network isolation requirement in E26 4.4.3.

At the design stage E26 asks for drawings showing the zones, the systems in each and where they are physically located, every network communication within and between zones and with untrusted networks, and the boundary devices with the traffic they permit. At commissioning, the class society verifies that the zones are built as approved and that boundaries allow only the documented traffic. Boundaries must be protected by firewalls or equivalent means (4.2.2), and networks in scope must be continuously monitored, with alarms if malfunctions or degraded capacity occur (4.3.1).

A word on vocabulary: the idea of zones joined by controlled connections comes from the industrial security world — the IEC 62443 standards call those connections “conduits”. IACS UR E27 maps many of its equipment requirements to IEC 62443-3-3 and IEC 62443-4-1, so the two families fit together.
⚓ 6. Maritime Connection — Draw Your Ship

A real case shows why the map matters. In July 2019 the U.S. Coast Guard issued Marine Safety Alert 06-19 about a deep-draft vessel bound for New York and New Jersey that reported a significant cyber incident in February 2019. Malware had significantly degraded the onboard computer system, although essential vessel control systems were not affected. The Coast Guard noted that the same shipboard network used for crew members' personal tasks was also used for official business — updating electronic charts, managing cargo data and communicating with shore — and that USB drives with cargo data were routinely plugged into the ship's computers without being scanned first.

The first measure the Coast Guard recommended was to segment networks, warning that “flat” networks let an adversary move easily to any system connected to them. That is exactly what E26's zones are for.

A useful exercise for any ship manager: take the ship's asset inventory (E26 4.1.1) and draw every network, every connection between networks, every link to shore and every place a USB drive or laptop is plugged in. Mark which connections pass through a controlled boundary and which do not. If nobody can draw it, that gap comes before any other control.

Lesson 30 now uses this map to look at the threats that travel along these paths.

✅ Key Takeaways — Lesson 29
  • A ship carries bridge systems (ECDIS, GNSS, radar, AIS, GMDSS, VDR), machinery automation (IAS, AMS, PMS, propulsion and steering control), cargo and safety systems, plus office IT and crew welfare networks.
  • IACS UR E26 covers OT for propulsion, steering, power, fire, bilge and ballast, watertight integrity, safety systems, and required navigation and communication systems — plus any IP interface from them to other systems.
  • Office, crew welfare and passenger networks are “untrusted networks” in E26 and must be physically segmented from the required zones.
  • The main paths in are ship-to-shore links, remote maintenance, updates and USB devices, wireless, and integration links between systems — each must be controlled and documented.
  • E26 4.2.1: group systems into zones, allow only explicit traffic, keep safety systems physically apart, keep bridge systems apart from machinery and cargo, put wireless in its own zone, and make zones isolatable without losing their primary function.
  • The USCG's 2019 safety alert shows the risk of a flat, shared network and unscanned USB drives; its first recommendation was to segment networks.
📎 Official Sources & Further Reading

Equipment descriptions are generic teaching summaries; the systems on any particular ship are defined by its own asset inventory and approved documentation. IACS requirements are paraphrased from the Rev.1 texts; consult the original for exact wording.

📚 PART 9 — Maritime Cybersecurity
DoneLesson 28 — What Makes Maritime Cybersecurity Different?
Current LessonLesson 29 — Shipboard IT and OT Architecture
Coming nextLesson 30 — Cyber Threats Against Maritime IT/OT
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