NEGU Moves Superyacht Vendor Remote Access Ashore for IACS E26

NEGU has launched a secure remote-access service aimed at superyachts preparing for IACS Unified Requirement E26 cyber-resilience requirements. The company is targeting a common weakness in yacht networks: individual equipment suppliers leaving persistent screen-sharing or vendor-access tools on bridge, AV, HVAC or automation computers.

Its alternative is to place the principal remote-access gateway ashore rather than on the yacht. Engineers and vendors connect to a dedicated jump host on NEGU infrastructure, while an encrypted private connection links that controlled environment to only the onboard network zone that the crew has authorised for the session.

The vessel keeps control of the connection

NEGU says the system is designed around crew approval rather than standing vendor access. Remote sessions use multi-factor authentication, can be enabled or terminated from on board, and are centrally logged so the yacht can establish who connected, when the session occurred and which controlled path was used.

That addresses an operational problem familiar to many large yachts. Over time, individual contractors may install their own remote tools for diagnostics or support, creating multiple entry points that are difficult for the captain or ETO to inventory and difficult for management to audit after crew or supplier personnel change.

Segmentation matters more than the remote-desktop brand

NEGU's design separates navigation, automation, guest, crew and other networks into defined security zones and confines vendor access to the zone required for the job. The company argues that the weakness is not necessarily the screen-sharing software itself, but the way persistent credentials and flat onboard networks can turn one remote session into access to unrelated systems.

The shore-side jump host also means a vendor does not need a direct public-internet path to the yacht's control-system computer. NEGU uses encrypted SpeedFusion connectivity into its managed network and can extend a private Layer 2 environment to the shore server, while the crew retains the ability to drop the connection from the vessel.

Why IACS E26 changes the conversation

IACS E26 makes cyber resilience part of the class process for new ships within its scope, covering identification, protection, detection, response and recovery for onboard computer-based systems and networks. NEGU notes that large classed newbuild yachts are increasingly encountering those requirements during design and plan approval, particularly where remote access crosses the vessel's cyber boundary.

The practical consequence is that an informal vendor login can no longer be treated as a harmless convenience on a new classed yacht. Builders and integrators need documented access paths, authentication, segmentation, session control and evidence that the configuration works as intended, while existing yachts may choose to adopt similar controls during major refits even when not retroactively required.

Remote support still has to remain operationally useful

Large yachts rely heavily on remote specialists for AV/IT, HVAC, propulsion controls, bridge electronics and automation. A security design that makes support impossible during a breakdown would create its own operational risk, so the challenge is to preserve fast specialist access while removing uncontrolled permanent backdoors.

NEGU's launch is therefore relevant beyond the individual product. It reflects a broader shift in superyacht technology from convenience-led remote support toward controlled, logged and surveyable access, with the captain and crew able to decide when the digital door to the vessel is actually open.