Authentication answers a limited question
A digitally authenticated message can establish that it came through a recognized identity and was not altered in transit. It cannot prove that the sender's sensor, route, intention or judgment was correct.
IMO adopted the VDES framework
At MSC 111 in May 2026, IMO introduced the VHF Data Exchange System into the regulatory framework and allowed it as an alternative to AIS under amendments expected to enter into force on 1 January 2028.
Two resolutions anchor the change
MSC.592(111) introduces VDES into the IMO framework, while MSC.593(111) establishes shipborne performance standards. Owners should follow final flag and class implementation rather than relying on product marketing.
VDES carries more data
IMO describes ship-to-ship, ship-to-shore and shore-to-ship terrestrial and satellite exchange at higher data rates than AIS. More capacity can improve services and also increase information-management demands.
Authentication targets spoofing risk
VDES can authenticate AIS messages, which IMO says may help address spoofing. The word help matters: authentication is one layer, not a guarantee of physical truth.
A valid sensor can be wrong
An authenticated ship may transmit position derived from jammed or spoofed GNSS. The message's origin can be genuine while its coordinates are false.
A valid operator can make an error
Wrong destination, draft, navigational status or route may enter through authorized controls. Data validation and bridge cross-checks remain necessary.
Credentials can be compromised
Stolen keys, poor access control or unauthorized maintenance could allow an attacker to act through a legitimate identity. Cyber risk management must protect the full credential lifecycle.
Revocation must reach ships
When a credential is compromised, vessels need current revocation information and a safe degraded mode. An authenticated symbol should not remain trusted indefinitely after its authority is withdrawn.
Time is part of trust
Expired certificates, stale messages and replayed data may pass superficial identity checks. Systems need trusted time, freshness checks and clear age display.
GNSS time creates dependency
If message validation relies on compromised satellite time, authentication may behave unpredictably. Resilient PNT and communications security need joint design.
Mixed fleets will persist
During transition, some ships will use AIS, some VDES and some neither because of carriage thresholds or exemptions. The traffic picture will remain incomplete.
AIS limitations still apply
IMO Resolution A.1106(29) says AIS is an additional navigation source and should not replace radar or compliance with collision regulations. VDES does not repeal that operational hierarchy.
Radar remains physical evidence
Correlate authenticated targets with radar and visual observations. A certificate cannot create a radar return where no vessel exists.
Display design needs restraint
Do not use a green lock symbol that implies the target is safe. Separate identity authentication, data integrity, sensor quality, message age and track confidence.
Failure states must be explicit
Distinguish unauthenticated, invalid, expired, revoked, unknown, unavailable and verification-service offline. One red icon cannot guide the right response to every state.
Alarm design matters
Authentication failures in dense traffic could create floods. Prioritize material changes and preserve raw status without distracting the officer from collision avoidance.
Satellite and terrestrial paths differ
Coverage, delay, capacity and threat exposure may vary. Show which path delivered the message and when, especially where regional interference affects one layer.
Software maintenance becomes critical
Keys, algorithms, trust stores and protocol versions require controlled updates. An obsolete but functioning unit may reject valid traffic or accept insecure methods.
Type approval and interoperability need testing
Ships should verify operation with shore services and representative equipment under approved procedures. Compliance on paper does not guarantee every regional service is reachable.
MSI needs recognized provenance
Digitally delivered warnings should preserve official warning number, issuer, time, geographic scope and cancellation. Authentication should reinforce, not replace, established MSI processes.
Privacy and security can conflict
Richer data exchange may expose voyage or identity information. Limit collection and access while preserving safety functions and lawful authority needs.
Logging supports accountability
Record message, signature status, certificates, time, path, display action and operator response. VDR integration and shore logs should support later reconstruction.
Owners need a transition architecture
Inventory AIS, VDES, antennas, networks, software, certificates, displays and shore contracts. Identify which functions change in 2028 and what remains on legacy equipment.
Traders need provenance without overconfidence
Authenticated position and route data may improve operational visibility, but cargo desks should preserve the message time, issuer and trust status. They must not convert a signed transmission into proof of safe passage, sanctions compliance, cargo condition or contractual performance.
Incident response needs key preservation
After a suspected spoofing or credential event, save messages, certificates, revocation status, trust-store versions, system time and update logs. Replacing keys too quickly can protect operations while destroying the evidence needed to understand how trust failed.
Crews need trust training
Officers should understand authenticated does not mean accurate, and unauthenticated does not prove malicious. Training must connect status labels to navigation actions.
Masters need degraded procedures
Define speed, watch, radar plotting, reporting and route limits when authentication services fail. The vessel cannot stop applying collision rules because a trust server is offline.
Charterers should not demand digital clearance
A signed message cannot transfer the master's navigational judgment. Commercial teams should preserve source and authority without treating cryptographic validity as route approval.
Brokers must avoid secure-data shorthand
Calling VDES unspoofable overstates the technology and can mislead clients. Describe the authenticated element and remaining sensor or credential risks.
Insurers need control evidence
Cyber, hull and P&I reviews may examine credential management, updates, failure handling, logs and bridge correlation. Authentication evidence should accompany physical-navigation evidence.
Hypothetical: the signed false position
A genuine ship transmits an authenticated position affected by GNSS spoofing. Radar shows the physical contact elsewhere. The bridge trusts identity but rejects location.
Hypothetical: the replayed clearance
An old signed route message reappears after mine conditions changed. Freshness and cancellation checks block it despite a valid historic signature.
Hypothetical: the verification outage
The trust service becomes unavailable during congestion. The bridge marks status unknown, increases independent tracking and follows degraded procedures rather than deleting every target.
Forecast
VDES will support richer safety services and stronger provenance, but fleets will confront certificate, update, interoperability and interface complexity. Explainable trust status will become a core bridge skill.
ZeaClub view
Authentication protects origin and integrity, not reality. Correlate every message with sensor quality, time, authority and physical evidence. VDES can reduce spoofing risk only if the bridge understands exactly what the digital signature proves.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- IMO, Introduction of VDES into the regulatory framework, MSC.592(111)Accessed 2026-11-19
- IMO, Performance standards for shipborne VDES, MSC.593(111)Accessed 2026-11-19
- IMO, Maritime Safety Committee 111th session summaryAccessed 2026-11-19
- IMO, Revised guidelines for onboard operational use of shipborne AIS, A.1106(29)Accessed 2026-11-19
- IMO, Guidelines on maritime cyber risk management, MSC-FAL.1/Circ.3/Rev.3Accessed 2026-11-19