🔔 Subscribe to ShipUniverse Weekly →
SHIPUNIVERSE / TECH · NOVEMBER 18, 2026 · SALE & PURCHASE
A ship changes hands at the delivery ceremony. Its digital keys don't always change with it. The previous manager may still have a satellite portal login; a service engineer may have a dormant remote connection to an engine controller; a navigation workstation may run software nobody supports. Maersk's recent legacy-system incident was ashore, not aboard a ship, but it makes the same point for secondhand buyers: equipment can outlive the people and companies responsible for securing it.
Why the Maersk story matters without exaggerating it
Confirmed / InferenceUnauthorized access to an acquired local system
On November 11, Maersk disclosed data extraction from a local legacy IT system inherited in a previous corporate acquisition. It said the incident appeared isolated and that it did not expect customer operational disruption.
The handover may leave digital access behind
Separate buyer risk: former managers, suppliers and satellite service providers may retain accounts or access routes unless they are identified and revoked. Maersk did not report a shipboard compromise.
Make it part of the pre-purchase inspection. A physical survey can find a failed pump, but it usually won't reveal an old service VPN, unsupported PLC firmware or whose account still owns the ship's cloud dashboard.
The 10 digital checks before closing
Demand proof, not assurancesStart with a seller-supplied asset register and a supervised, read-only review. Do not run intrusive vulnerability scans, reboot controllers or interrupt navigation, cargo or machinery networks on an operating ship without an approved plan.
Who still holds administrator credentials?
Identify local, domain, cloud and emergency accounts, including service passwords shared across crew changes. Agree a controlled rekey and revocation event at delivery.
Evidence: Privileged-account register, credential custody plan, time-stamped revocation confirmation and tested new-owner recovery access.
Delivery conditionWhich vendors can still connect remotely?
Inventory OEM modems, VPNs, remote desktop tools, cloud gateways and scheduled support sessions to engines, cargo controls, ballast systems and alarm stations.
Evidence: Remote-access register, approvals, last-use logs, vendor contacts and confirmation old access is disabled or transferred under buyer control.
Delivery conditionCan office or crew Wi-Fi reach operational technology?
Trace actual links among administration PCs, satellite routers, crew welfare, navigation and machinery networks. A drawing that has not been updated after refits is not enough.
Evidence: As-built topology, firewall rules, switch configuration backups and an approved plan for any unsafe IT-to-OT pathway.
Survey before price agreedWhich computers and controllers are already obsolete?
Record operating systems, ECDIS versions, industrial PCs, HMIs, PLC firmware, antivirus support and last available security updates. An unsupported device may need isolation or an expensive OEM-controlled replacement.
Evidence: Hardware/software inventory by model and serial, vendor end-of-support notices, approved mitigations and fixed-scope quotes.
Price adjustment candidateWhose name is on the communications terminals?
Check VSAT and L-band equipment, routers, SIMs, airtime contracts, shore gateways, terminal management accounts and any flag/registration activation steps.
Evidence: Service-provider transfer instructions, terminal IDs, billing handover, security reconfiguration and functioning ship-to-shore test.
Delivery conditionWill the ECDIS and chart services still work after delivery?
Verify approved software status, chart permits, update service, navigation backup, time sync and access to OEM support. Avoid security changes that accidentally invalidate certified configurations.
Evidence: Chart-service and ECDIS licensing transfer, approved versions, recent update records and a witnessed operational continuity check.
Delivery conditionWho owns and can export the ship's records?
Planned maintenance, technical history, sensor trends, inspection findings and safety-management records may sit in the seller's cloud tenant or with a third-party manager.
Evidence: Data-export inventory, lawful retention rules, assignable licences, access permissions and an import test in the buyer's systems.
Contract scheduleCan a failed workstation or controller be restored?
Count offline configuration images, OEM-approved backups, tested recovery procedures, replacement storage media and the people authorized to restore a safety-related system.
Evidence: Recent backup logs, sample restore results, documented recovery times and safe fallback operation; never erase statutory records.
Survey before price agreedWhat unknown Wi-Fi, USB or network gear is onboard?
Look for contractor laptops, unmanaged switches, rogue wireless access points, removable media and forgotten monitoring boxes installed during repairs or temporary charters.
Evidence: Port/device inventory, physical walk-through, approved removable-media policy and supervised removal of unauthorized devices.
Handover inventoryWhat cyber problems and exceptions remain open?
Request incident reports, unresolved vulnerabilities, class or flag observations, cyber risk assessments, SMS procedures and a list of exceptions accepted by the previous manager.
Evidence: Seller disclosure schedule, agreed remedial owner and deadline, class/flag status, and new-manager cyber response contacts.
Contract scheduleWhen a digital defect should affect the purchase price
Four examples| Finding | Immediate consequence | Buyer response | Transaction treatment |
|---|---|---|---|
| Unrevoked former-owner remote access | Unknown party may retain a path to ship systems | Require supervised disablement and proof that essential OEM access still works under new authority | Resolve at delivery |
| Unsupported engine or cargo HMI | Unplanned upgrade, isolation or OEM support expense | Price exact compatible replacement and approved mitigation; plan availability | Quantified allowance |
| No current IT/OT network drawing | Unpriced exposure and difficult recovery planning | Commission a controlled mapping exercise with a named reviewer | Survey / escrow discussion |
| Non-transferable chart or software rights | System access or update service may lapse | Require legal licence transfer and witnessed activation before relying on it | Delivery condition |
Negotiation principle: use contractor or OEM quotations, not a made-up per-vessel cyber penalty. The agreement should specify which party pays, who authorizes system changes, what records transfer and how unresolved defects are handled. Counsel should adapt any warranties, escrow or holdback to the sale contract.
What the rules actually require
No blanket retrofit orderIACS UR E26 and E27
Cyber resilience requirements generally apply to relevant ships contracted for construction from July 1, 2024. ClassNK confirmed in June 2026 that a change of owner or manager alone does not newly trigger them for an otherwise exempt older ship.
IMO cyber SMS + IACS Rec. 194
IMO MSC.428(98) puts cyber risks in safety-management arrangements. Current IMO guidance is MSC-FAL.1/Circ.3/Rev.4; IACS Rec. 194 offers a non-mandatory existing-ship controls benchmark. Applicable flag, class and national rules still need checking.
U.S.-flagged buyers: for vessels covered by the Coast Guard's 33 CFR 101.650 regime, the cyber assessment framework includes reassessment following ownership change. The general initial assessment/plan deadline is July 16, 2027, so confirm applicability and transition timing rather than treating the provision as a universal rule for international ship sales.
The safest digital handover is staged
Buyer / Seller / OEMGet the exposure list
Asset inventory, remote-access list, licences, known incidents and quotes for high-cost obsolete controls.
Agree change controls
Signed access-revocation plan, data export, approved test scope, outage window and people on call.
Transfer control safely
Rotate credentials, transfer providers, validate logs and backups, then witness critical systems with operators.
Close the residual risks
Controlled hardening, monitoring, system restoration exercise, crew training and outstanding class/flag actions.
Never “factory reset the vessel.” Navigation systems, propulsion controllers, VDRs, GMDSS equipment and survey-related records require controlled OEM/class/flag-aware procedures. Preserve evidence and safety functions throughout transfer.
What could inherited digital defects add to the purchase price?
Build a rough buyer-side remediation reserve before closing. Select a one-ship purchase or a portfolio, then adjust audit, obsolete equipment, network work, access transfer and possible delivery-delay exposure. All amounts are illustrative USD budgets, not published supplier quotations.
A budgeting exposure, not a recommended escrow amount or automatically justified price deduction.
All figures illustrative, USD. Gross initial allowance = vessels × (survey + unsupported system count × average remediation per system + network work + access/licensing/backup work) × (1 + contingency). Buyer-funded reserve deducts an assumed seller contribution. Expected delay exposure = vessels × probability of delay × days lost if it occurs × net cost/day. Three-year cash scenario adds buyer-funded reserve, expected delay exposure and three years of additional cyber support without discounting. Results are neither actual supplier prices nor predictions of incidents. Any work on live operational technology must be professionally authorized, tested and planned to preserve safe operation.
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch