704
4 REAL LIFE SCENARIOS OF CYBERTHREATS AT
SEA
The identification of cyber vulnerabilities in maritime
systems together with a review on cybersecurity
practices, provided the structural foundation for the
development of scenario-based training materials.
Recognizing that the theoretical mapping of
vulnerabilities must be anchored in operational
realities to be pedagogically effective, next task focused
on compiling, structuring, and analysing a
comprehensive set of cyber incident scenarios. These
were drawn from three complementary sources: (1)
well-documented real-world maritime cyberattacks,
(2) lesser-known or confidential incidents partially
disclosed in industry and academic channels, and (3)
hypothetical, yet technically plausible, threat situations
extrapolated from similar sectors or system
architectures. Each scenario was developed with
reference to one of the ten critical maritime subsystems
mentioned in chapter 2: navigation, propulsion, power,
communication, satellite connectivity, cargo, weather
monitoring, entertainment, integrated bridge, and
crew/passenger systems.
Each scenario developed in WP2.T4 follows a
standardized analytical structure, intended to enable
reproducibility, pedagogical clarity, and operational
relevance. The framework includes the following
elements:
− Description of Incident: A factual or constructed
narrative detailing how the cyber event unfolded,
including method of access, targeted system, and
timeline.
− Identified Threat: A succinct technical formulation
of the core cyber threat (e.g., ransomware, spoofing,
malware injection).
− Result of Threat: Operational and/or safety-related
outcomes of the attack (e.g., cargo rerouting, denial
of propulsion, communication blackout).
− How to Identify / What to Monitor: Practical
indicators for detection and awareness (e.g.,
abnormal sensor readings, system lag, unknown
logins).
− Solutions / Mitigation Measures: Proposed
countermeasures, often aligning with existing best
practices (e.g., multi-factor authentication, endpoint
hardening).
− Sources: Documentation or references supporting
the scenario ’ s construction (academic articles,
incident reports, news sources, etc.).
A total of 34 scenarios were developed. While the
scenarios span a wide spectrum of complexity and
origin, several cross-cutting themes emerge that
highlight the evolving threat landscape in maritime
cyber risk. In navigation systems, scenarios focused on
GPS spoofing, AIS manipulation, and ECDIS malware
infections. One example involved the deliberate
falsification of vessel position data via GNSS spoofing,
leading to near-grounding events in congested traffic
zones. Scenarios emphasize the need for redundant
position sources (e.g., radar-based fixes) and crew
training on anomaly recognition in bridge displays.
Cargo management system scenarios were particularly
rich, including high-profile cases such as the NotPetya
attack on Maersk. Another detailed a criminal
organization’s compromise of an Australian customs
database, enabling illicit cargo routing. These cases
illustrated how supply chain integration and shore-
side access vectors can cascade into onboard
consequences, particularly when authentication and
access logging are weak. In power and propulsion
systems, threats ranged from remote command
injection via insecure remote maintenance channels to
malware disrupting engine control units. For instance,
one scenario described the infiltration of an auxiliary
power system during shore-side servicing, which led
to propulsion failure mid-voyage. Satellite and
communication systems were often targeted through
jamming, signal interference, or unencrypted
backchannel exploitation. One real-life case involved a
transatlantic vessel approaching the Port of New York
whose control systems were degraded by malware
delivered via a crew USB stick. Scenarios involving
crew and passenger systems typically illustrated
threats of a social engineering nature—phishing,
credential harvesting, and SQL injection into manifest
or personnel databases. Suggested mitigations
included phishing awareness drills, MFA, and audit
logging with anomaly detection. Even systems such as
onboard entertainment and weather monitoring—
often considered peripheral—were shown to be
exploitable. A DDoS attack on an infotainment server
was found to spread laterally due to poor network
segmentation, affecting navigation displays. These
highlight the importance of treating all IT-connected
systems as part of a unified security perimeter.
The analysis reveals that most incidents share a
common vulnerability: the human-system interface.
Whether through poor credential practices, unverified
device use, or the misinterpretation of corrupted data,
crew behaviour plays a central role in either amplifying
or mitigating cyber impact. Therefore, scenario-based
training should not only deliver technical know-how,
but also cultivate situational awareness, discipline in
procedural compliance, and the confidence to act
decisively under uncertainty.
5 DEVELOPMENT OF PROTOCOLS
The last step of the research was to develop procedural
guides designed to support timely, informed, and
consistent responses to cyber threats within critical
shipboard and port-related systems. These protocols
goal was enabling both reactive and preventive
capabilities among maritime personnel. Each protocol
was intended to address a particular category of
system risk, in alignment with the defined previously
risk domains and enriched through scenario-based
analysis.
Each protocol follows a unified structure
comprising:
− Purpose and Scope
− Applicable Regulations and Standards (e.g., IMO
MSC-FAL.1/Circ.3, ISO/IEC 27001, NIS2)
− Roles and Responsibilities
− Risk Assessment and Threat Identification
− Technical and Procedural Cybersecurity Controls
− Incident Response and Recovery Procedures
− Training and Awareness Requirements
− Communication and Coordination Measures
− Audit, Compliance, and Review Cycles