Superyacht cyber security and network segmentation
Most yacht cyber risk comes from flat networks where everything can reach everything else. Separating them behind a managed firewall, with proper remote access and ongoing monitoring, removes most of that risk.
Good superyacht cyber security starts with segmentation. Guest, crew, AV and vessel/OT systems should sit on separate networks behind a managed firewall, with access between them controlled by explicit rules. A specialist integrator should design, install, document and monitor the setup, not leave it to whoever last fitted a router.
Each part of that is straightforward on its own. The problems come from yachts where networks have grown piecemeal over refits and supplier visits until nobody can say with confidence what is connected to what. This article covers what to segment, how remote access and updates should work, and what to ask a supplier.
Why flat networks are the real risk
On a flat network, every device can see every other device. A guest's compromised laptop, a crew member's phone or an unpatched smart TV sits on the same network as the CCTV recorders, the AV control processors and, in the worst cases, systems connected to machinery or navigation. One weak device then exposes the rest of the vessel.
Yachts make this worse in particular ways:
- Many different suppliers install equipment, each with its own access needs and default passwords.
- Crew turnover means credentials and knowledge leave the boat regularly.
- Satellite and 4G/5G links put the vessel online almost everywhere, and expose it almost everywhere.
- Guests bring their own devices and expect them to work at once, without friction.
Segmentation does not stop every attack. It limits how far an attack can spread, makes unusual traffic easier to spot, and lets you set security policy that suits each group of users and systems.
What to segment on a superyacht
Exact zones vary by vessel, but a well-designed yacht network usually separates at least the following.
Guest network
Internet access only, with client isolation so guest devices cannot see each other. Guests should reach permitted AV and entertainment functions, such as casting to a cabin screen, through controlled rules rather than by joining the AV network itself.
Crew network
Kept apart from guests, with its own bandwidth policy so crew streaming does not degrade guest service or operational traffic. Crew welfare connectivity matters, but it is not trusted traffic.
AV and entertainment
Media servers, displays, audio, lighting and control processors belong on their own network. These devices are often updated less often than IT equipment, which is exactly why they should be isolated.
Vessel and OT systems
Monitoring, CCTV, access control and any connections to machinery or alarm systems need the strictest separation. Bridge and navigation systems are usually supplied and supported by their manufacturers. Segmentation should isolate them, not alter them, and any change should be agreed with the relevant OEM.
Owner, office and management
The owner's and management company's business traffic often deserves its own zone. Network infrastructure such as switches, access points and the firewall itself should be managed from a dedicated management network that ordinary users cannot reach.
How segmentation works in practice
The usual tools are VLANs and a properly configured yacht firewall. VLANs divide the physical switching infrastructure into logically separate networks. The firewall then decides what, if anything, may pass between them. Good practice looks like this:
- Default deny between zones. Traffic between networks is blocked unless a documented rule allows it.
- Separate wireless networks per zone, mapped to the right VLAN, rather than a single SSID with a shared password.
- Deliberate wired port assignment, so a cable plugged into a spare socket does not land on a sensitive network.
- Physical separation where it is justified, for systems where logical separation alone is not enough.
- Connectivity policy at the edge. When VSAT, Starlink Maritime and cellular links are combined, the firewall should decide which zones use which link and in what priority, so operational traffic is protected when bandwidth is limited.
The design, the documentation and the rule set matter more than any particular brand of hardware. A capable firewall with a vague rule set gives little protection. Our maritime network design and installation work starts with mapping every system and data flow before any configuration begins.
Remote access without opening the front door
Remote support saves time and money, but it is also where many yacht networks are most exposed. Port forwards left open after a commissioning visit, shared vendor logins and unmanaged remote-desktop tools are common findings. A sound approach:
- No direct inbound access to onboard systems from the internet.
- Remote access through a VPN or secure gateway, with individual accounts and multi-factor authentication.
- Each supplier limited to the systems they support, ideally with time-limited access that the captain or ETO approves.
- Every remote session logged, so you can see afterwards who connected, when and to what.
This also keeps the vessel in control. Suppliers get what they need without permanent access to everything.
Updates, monitoring and ongoing care
A network that was secure at delivery will not stay secure by itself. Ongoing care should include:
- Planned firmware and software updates for firewalls, switches, access points and AV/IT devices, scheduled around the yacht's programme rather than in the middle of a charter.
- Configuration backups, so a failed device can be replaced and restored quickly, wherever the vessel is.
- Monitoring and alerting on link health, device status and unusual behaviour, with a clear agreement on who responds and how quickly.
- Credential housekeeping, especially at crew changeovers and after supplier visits.
- Living documentation: network diagrams, IP plans and rule sets that are updated whenever something changes.
Monitoring is where segmentation pays off. When each zone has a defined purpose, traffic that does not fit stands out.
What to ask a supplier
Whether you are commissioning a new build, planning a refit or reviewing an existing installation, these questions show quickly whether a supplier understands yacht network security:
- How will you discover and document what is currently on the network?
- Which zones do you propose, and what traffic is allowed between them, and why?
- How will remote access work for you and for other suppliers, and how is it logged?
- How are updates planned, tested and rolled back if something goes wrong?
- What do you monitor, who receives alerts, and what happens out of hours or in remote cruising areas?
- What documentation and credentials will the vessel hold at handover, and who owns them?
- How do you coordinate with OEMs for bridge, machinery and other specialist systems?
Vague answers to any of these deserve a follow-up.
Who can help
OceanEdge Systems is a superyacht network integrator. We design, install and support segmented networks for yachts. That covers guest and crew Wi-Fi, AV and control systems, VSAT and Starlink Maritime, and the firewalls that link them. We work alongside captains, ETOs, management companies and other suppliers rather than replacing them, and we coordinate with equipment manufacturers where their systems are involved.
You can see the hardware we deploy, including ruggedised edge computing and network equipment, on our products page. If you would like a review of an existing network or input on a new build or refit, get in touch with our team.