Maritime cyber security has moved from an IT concern to a safety and compliance obligation. A modern vessel carries navigation, propulsion, cargo and communications systems that were designed to operate in isolation, now connected to shore by high-speed satellite links, remote diagnostics and crew networks. Every one of these, albeit useful, widens the attack surface.
The maritime cyber security regulatory position has hardened accordingly. Cyber risk is now something flag states, classification societies and port state control expect to see managed, documented and tested.
Maritime Cyber Security: Why Vessels Are a Different Problem to Offices
Shore-side cyber security protects data. Maritime cyber security protects a moving industrial asset with people aboard, and that changes the priorities.
Operational technology sits alongside IT. Engine monitoring, ballast control, ECDIS and cargo systems are operational technology. They frequently run outdated software, cannot be patched on a normal cycle, and were never designed with authentication in mind. Compromise here has physical consequences.
The perimeter is unusually porous. Crew personal devices, contractor laptops, USB drives carrying chart updates, and vendor remote access sessions all cross onto vessel networks routinely, often without oversight.
Response times are constrained. A compromised system ashore gets a technician within the hour. Mid-ocean, the crew are the incident response team, working over a satellite link that may itself be degraded.
Turnover is constant. Rotating crews means security awareness has to be embedded in procedure rather than in individuals.
Maritime Cyber Security: The Threat Picture
The incidents that affect shipping tend to fall into a handful of recognisable patterns.
Ransomware reaching the vessel from ashore. Most maritime ransomware begins in the shore office and travels via shared systems, email or remote connections. The commercial disruption is usually greater than the technical damage.
Uncontrolled vendor remote access. Remote diagnostics have become standard for engines, cargo systems and navigation equipment. Where those sessions are permanently enabled, unlogged, or use shared credentials, they represent a route onto operational systems that bypasses every other control.
Removable media. Chart and software updates delivered on USB remain a common infection route, particularly onto systems that are otherwise offline.
GNSS jamming and spoofing. Interference with position and timing signals has become widespread in several regions. It is rarely aimed at a specific vessel, but the operational effect on navigation and any system dependent on GNSS timing is the same.
Credential and phishing attacks against crew. Better crew connectivity has brought personal email and social media aboard, and with them the standard social engineering routes.
Flat networks. Where crew Wi-Fi, ship business systems and operational technology share one subnet, a compromised personal device has a direct path to navigation and machinery systems. This is the single most common structural weakness found aboard.
Maritime Cyber Security: The Regulatory Framework
Four regimes account for most of what operators are actually asked to demonstrate for maritime cyber security.
IMO Resolution MSC.428(98) requires cyber risk to be addressed within the Safety Management System under the ISM Code. It has been verified through Document of Compliance annual verification since the first such verification after 1 January 2021. It is deliberately non-prescriptive: it does not tell you what controls to deploy, it requires you to show that risks have been identified and managed. Supporting guidance sits in MSC-FAL.1/Circ.3.
IACS UR E26 and E27 are the class requirements, and they apply to new ships contracted for construction on or after 1 July 2024. Earlier versions carrying a January 2024 date were withdrawn and superseded. E26 treats the vessel as a single cyber-resilient system across design, commissioning, operation and maintenance, structured around identify, protect, detect, respond and recover. E27 addresses the security capabilities of individual systems and equipment, placing obligations on third-party suppliers. Applicability is categorised as mandatory or non-mandatory depending on vessel type and size. Existing vessels are not retrospectively caught, though the requirements are widely treated as a benchmark for retrofits.
The USCG cybersecurity rule applies to US-flagged vessels and regulated facilities. The final rule was published in January 2025 and took effect on 16 July 2025, with a cybersecurity training deadline in January 2026 and phased compliance running to 2027. It requires a cybersecurity plan, a designated cybersecurity officer, and incident reporting to the National Response Center within 12 hours of discovery. Non-US operators calling at US ports should confirm their exposure.
NIS2 (Directive EU 2022/2555) brings certain maritime operators within EU-wide cyber governance and incident reporting obligations, with implementation via national transposition.
Maritime Cyber Security Framework
Applies to
What it asks for
IMO MSC.428(98)
All vessels under the ISM Code
Cyber risk managed within the SMS, verified at DOC audit
IACS UR E26
New ships contracted from 1 July 2024
Whole-vessel cyber resilience across the lifecycle
IACS UR E27
Systems and equipment on those ships
Security capabilities built into supplied equipment
Governance, risk management and incident reporting
Maritime Cyber Security: Where Operators Actually Fail Audits
The gap is rarely advanced attack techniques. It is almost always the basics.
Unclear ownership. Nobody can say definitively who is accountable for cyber risk on a given vessel, or the named individual left the company.
Uncontrolled remote access. Vendor sessions that are always on, shared, or unlogged, with no record of who connected and what they changed.
Untested backups. Backups exist, but nobody has ever proved a restore. An untested backup is a hope, not a control.
A plan that does not match the ship. An incident response procedure written ashore that assumes support availability, bandwidth or staffing the vessel does not have.
No asset inventory. You cannot protect systems you have not listed. Inventory is the first function under E26 for good reason.
Maritime Cyber Security: Controls That Hold Up
Network segregation. Separating operational technology from ship business systems and crew networks is the highest-value single measure available. It limits what a compromised device can reach and makes everything downstream easier to defend.
Governed remote access. Vendor connections enabled on request, logged, time-limited, and using individual credentials rather than shared ones.
Controlled change management. Software updates to critical systems applied through a documented process, with a tested rollback, rather than opportunistically over an available link.
Traffic control at the network edge. Filtering and prioritisation applied on board, so operational traffic is protected and unnecessary exposure is reduced before anything leaves the vessel.
Proven recovery. Backups tested by actually restoring them, on a schedule, with the result recorded.
Crew procedure, not crew awareness. Training helps, but controls that depend on judgement fail under pressure. Removable media policies, joining procedures and reporting routes need to be procedural.
Does IMO MSC.428(98) apply to existing vessels? Yes. It applies through the Safety Management System under the ISM Code, regardless of build date, and is verified at Document of Compliance audit.
Do IACS UR E26 and E27 apply to my existing fleet? Not retrospectively. They apply to ships contracted for construction on or after 1 July 2024. Existing vessels remain subject to IMO requirements, flag state rules, and USCG requirements when calling at US ports.
Is maritime cyber security part of port state control inspection? Cyber risk management is examined as part of ISM verification, and inspection regimes increasingly look for evidence that it is managed in practice rather than only on paper.
What is the fastest meaningful improvement? For most vessels, network segregation, followed by getting control of vendor remote access.
Building Maritime Cyber Security Into Vessel Connectivity
Maritime cyber security is inseparable from how a vessel connects. Network design determines what can reach operational systems, what visibility a superintendent has, and how much of the risk is structural rather than behavioural.
AST Networks works with commercial operators on connectivity architecture that supports segregated, controlled and monitored vessel networks. To discuss how your fleet's connectivity supports your maritime cyber security obligations, contact the AST Networks team.
Ask an expert
Have a question? Ask our team
Whether you are comparing networks, choosing equipment or checking what your vessel needs, our team will give you a straight answer. We usually reply within one working day.