Cyber Security IMO2021 Requirements
Cyber Security IMO2021 Requirements
Cyber Security IMO2021 Requirements
REQUIREMENTS
FOR IMO 2021
Inmarsat
Research
Programme
WHITE PAPER
NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
2 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
CYBER SECURITY
REQUIREMENTS FOR IMO 2021
CONTENTS
1 Introduction 5
2 Cyber risk management – the threat to ships 6
– Ship threats and vulnerabilities 6
– Hardware, software, personnel 8
3 The basis for IMO 2021 10
4 IMO 2021 in practice 13
– Systems inventory 14
– Risk assessment scope 15
– Responsibilities 15
5 IMO 2021 compliance 17
– Responding to, recovering from and training
for cyber attacks 18
– A pathway to compliance 18
– Compliance checklist 18
6 Fleet Secure Endpoint – an introduction 20
– Security and endpoints 21
– Fleet Secure Endpoint onboard 22
7 Fleet Secure Endpoint – supporting IMO 2021
compliance 24
– Identify, Protect, Detect, Respond and Recover 24
– Recovery, reporting, manageability 26
– Fleet Secure Endpoint compliance checklist 27
– Fleet Secure Endpoint key benefits 28
8 Fleet Secure Endpoint - installation and use 30
– Dashboard and alerting 30
– Fleet Secure Endpoint use in context 31
9 Cyber security, Crew Training and Awareness 32
10 Fleet Secure Endpoint – real case studies 34
11 Conclusion and Next Steps 36
inmarsat.com 3
White Paper
Cyber security requirements for IMO 2021
4 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
* Safety at Sea and BIMCO cyber security white paper. Downloadable at: https://www.bimco.org/-/media/bimco/about-us-and-our-
members/publications/ebooks/cyber-security-guidelines-2018.ashx
** Managing Ports’ Cyber Risks: https://www.britishports.org.uk/system/files/documents/bpa_astaara_white_paper_0.pdf
inmarsat.com 5
White Paper
Cyber security requirements for IMO 2021
6 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 7
White Paper
Cyber security requirements for IMO 2021
However, ships themselves increasingly play a fully months according to an Inmarsat analysis of its
connected data-centric role in the supply chain. Fleet Xpress customer vessels. The need for cyber
In doing so, common cyber vulnerabilities can be resilience has therefore never been greater.
found onboard existing ships, and on some new-
build ships. These may include:
– Obsolete and unsupported operating systems HARDWARE, SOFTWARE AND PERSONNEL
– Outdated or missing anti-virus software and Understandably, the ship at sea is not itself likely to
protection from malware be the focus for targeted Denial Distribution of
– Inadequate security configurations and Service (DDOS) attacks, whose targets tend to be
best practices, including the use of default corporate or more transactional. However, malware
administrator accounts and passwords, and and Ransomware can be introduced easily enough
ineffective network management to the unguarded ship network, via:
– Shipboard computer networks which lack
boundary protection measures and segmentation
– Terminal hardware
– Safety-critical equipment or systems always
– Software updates
connected with the shore side
– Misconfigured systems
– Inadequate access controls for third parties
– Inadequate integration
including contractors and service providers
– Maintenance and design of cyber-related
If these vulnerabilities are well-known, it is also systems
widely recognised that incidents onboard are
In addition, ship networks are vulnerable to cyber
under-reported. Furthermore, a hallmark of
threats arising from:
successful cyber crime will be a lack of publicity.
In fact, the full extent of the incidents affecting – Email, Phishing, social media scams, etc.
shipping is therefore hard to gauge. In one alleged – USB memory stick as a source of malware
incident, a ballast water management system – Downloaded malware
cyber breach saw a ship heeled, with control only – Connection with infected devices – cell phone,
returned to the crew after a ransom was paid. laptop, tablet
However, the owner apparently preferred to leave – Unauthorised use of bandwidth, exposing a lack
the matter unreported, subsequently denying the of network segregation
whole episode over concerns that the ship would
These second types of vulnerability relate to ‘the
not be accepted for charter.
human element’, and specifically to weaknesses
It is nonetheless fair to point out that – for the in cyber resilience brought by shortcomings
connected ship – the vulnerabilities listed above in procedures, training and awareness among
are not simply exposed to the same spread of cyber personnel.
threats as land-based counterparts: they are also
Even setting aside the operational headaches, cost
subject to the General Data Protection Regulation
of system renewal and expenditure on training that
(GDPR). Effective in EU jurisdictions from 2018, GDPR
a cyber breach can bring, ships that fall victim to a
requires businesses to demonstrate sufficient
cyber attack can expect far-reaching implications
control and protection over the data they own
that may include:
- especially if they subsequently have a breach.
Failure to comply can bring fines of up to 4 per – Claims against interruption to operations, e.g., a
cent of an organisation’s global turnover or £17.5m, virus affecting onboard systems causes costly
whichever is higher. delays in getting to port, potentially leading to
cargo claims/charter party disputes and claims
With more devices on board, and more applications
for compensation
and media channels being used than ever before,
– Loss of business-sensitive information could
some ships are doubling their data usage every six
8 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
SYSTEMIC VULNERABILITIES
IMO highlights the following ship systems as
vulnerable to cyber attack:
1. Bridge systems
2. Cargo handling and management systems
3. Propulsion and machinery management and
power control systems
4. Access control systems
5. Passenger servicing and management systems
6. Passenger facing public networks
7. Administrative and crew welfare systems
8. Communication systems
inmarsat.com 9
White Paper
Cyber security requirements for IMO 2021
10 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 11
White Paper
Cyber security requirements for IMO 2021
12 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 13
White Paper
Cyber security requirements for IMO 2021
Incorporating cyber risk into the SMS can take – IoT Systems
several months, depending on the complexity of – Navigation
the systems onboard the vessel involved. Meeting – Engine Control
the 2021 deadline, or the first inspection thereafter – Cargo Control
will require a combination of technical mitigations, – DP, Gas, Firefighting, etc.
revised (or new) procedures and staff/crew training – ICT – Business Computer System
to develop a practical and cost-effective route to – ICT – Crew Systems
compliance.
This list needs to include:
It is important to add that ISM does not prescribe a
Hardware
calendar schedule for assessing new risks, instead
advising that they are accommodated as soon – Record make, model, version, function on all your
as possible. For this reason, the SMS should be hardware
considered by owners as a ‘live’ document that is – Individual hardware (and IP address) and patch
regularly updated and improved as risks evolve. panel, power
– Take note of possible attack surface/connection
point among your hardware and work to secure
SYSTEMS INVENTORY them (USB, Ethernet, exposed wiring)
14 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
Existing documentation should be used as much as normally be responsible for the owner/manager ISM
possible (especially Technical & Engineering details. documentation system for ships, for example.
In terms of response and recovery, it is also the Critically, under IMO 2021, at a minimum a ship’s
owner’s/manager’s responsibility to formalise the SMS will identify the party ashore and onboard
workarounds that address cyber security gaps, so taking responsibility for cyber security (ICT
that the ship can continue to operate in the event Manager, Chief Security Officer, or any other).
of a cyber attack or its aftermath, or risks can be
In broad terms, that individual will take
mitigated. Workaround plans for critical systems
responsibility for:
and processes should be incorporated into the
network and system design and described for – Having an understanding of the extent of cyber
Captains in a vessel’s emergency manuals. These risks
plans should include instructions and/or checklist – Managing crew awareness of and preparedness
in the event of critical system failure, due to cyber for threats to the vessel’s systems
incident or unplanned system breakdown without – Steps to secure ship systems to minimize the
a need to request and wait for help from the shore impact if a threat is actualised
office. Given that, in line with the ISO27001 standard, IMO
The responsibility for verifying these steps when 2021 also states that the owner’s risk assessment
the ship’s Document of Compliance is due for should be auditable for the following attributes:
renewal also falls to the ship’s owner/manager. – The hardware installed
– The software in use
– Details of what is connected to the network
RISK ASSESSMENT SCOPE – How the above is protected
The goal of the assessment of a ship’s network The Fleet ICT Manager will need to work with the
and its systems and devices is to identify any Head of Crewing to ensure that Crew understands
vulnerabilities that could compromise or result the importance of cyber security and have been
in either loss of confidentiality, loss of integrity trained either in the classroom or online. A record
or result in a loss of operation of the equipment, of the crew’s performance in these training
system, network, or even the ship. As explained exercises should be kept on file by the HR/Crewing
elsewhere, these vulnerabilities and weaknesses department.
broadly fall into one of the following categories:
1. Technical such as software defects or outdated
or unpatched systems
2. Design such as access management, unmanaged
network interconnections
3. Implementation errors for example
misconfigured firewalls
4. Procedural or other user errors
RESPONSIBILITIES
IMO 2021 requirements do not cover servers or
staff onshore but they clearly have a major impact
on fleet management. For example, the individual
managing the Fleet IT policy and documentation
(usually, the ‘Fleet ICT Manager’) will would also
inmarsat.com 15
White Paper
Cyber security requirements for IMO 2021
16 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 17
White Paper
Cyber security requirements for IMO 2021
3. Has measures in place to protect systems and of backup email ID from ship-to-shore and from
software onboard shore-to-ship
4. Has response measures in place to deal with – Fall back to paper charts in case of compromised
a cyber attack, specifically related to system ECDIS
redundancy, training and workaround plans
In all cases, the Fleet ICT Manual inserted into
the Ship’s SMS/ISM Code documentation should
provide full guidance and document the Cyber
RESPONDING TO CYBER ATTACKS Security Plan for all critical on-ship systems.
The Cyber Security Plan should, at minimum,
include:
– A process for initial incident triage
TRAINING FOR CYBER ATTACKS
– Steps to quarantine all electronic traffic to and As the Plan is part of the Vessel’s ISM it is also
from ship or fleet. Procedures for alerting and essential to periodically carry out drills to test any
requesting communication vendors to check issues, train the crew, HSSE (Health, Safety, Security
traffic & Environment) team and any other stakeholders
– Procedures for keeping corporate IT security on how to respond to a cyber incident onboard ship,
department abreast of the situation and encourage a culture of continual improvement.
– Procedures to secure/establish backup This means ship owners and managers should give
communications to the affected vessel(s) cyber security drills the same weight as they give
– Steps to stabilize and isolate the infected system any regular Incident Management Drill – whether
to guard against further spread for grounding, ship fire or collision.
– Steps for gathering Intelligence and evidence
Under the new regime, cyber drills should be
from affected systems
conducted across the fleet at least once a
– Procedures for executing recovery of critical
year to test response procedures and assess
systems remotely
crew preparedness, procedures during a cyber
– Arrangements for completely replacing the ICT
incident onboard. It is essential that the Ship
system at the next safe port after a cyber event
Manager’s Incident Commander takes charge
and demonstrates effective leadership in these
exercises to ensure the security of the ship, its
RECOVERY FROM CYBER ATTACKS crew and cargo, while allowing the Fleet IT team to
Workaround plans are required to take account of concentrate on securing the ICT infrastructure and
possible failures in critical shipboard systems, with resolving the cyber issues.
the processes described in a vessel’s emergency In addition, regular anti-phishing campaigns and
manuals so that the Captain can respond without penetration testing using simulated malicious
the need to ask for help from/wait for shore-based emails can maintain high-levels of crew vigilance
colleagues. These plans should provide the Captain and test onboard systems and processes.
with instructions and/or a checklist on what to do. Penetration testing by professional ‘white-hat’
In the case of cyber resilience, workarounds plans hackers should also take place to identify technical
might include: weaknesses.
– Actions to restore crashed/ failed email clients or
degraded/failed ship-shore communication links;
use backup FleetBroadband for email/voice until
A PATHWAY TO COMPLIANCE
recovery As the leading supplier of ship-to-shore
– Actions to work around/recover failed PCs connectivity in commercial shipping, Inmarsat
– Usage of citadel telephone to send telex; testing is also a stakeholder where the development of
18 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 19
White Paper
Cyber security requirements for IMO 2021
20 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 21
White Paper
Cyber security requirements for IMO 2021
22 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
Web control R R
Two-way firewall R R
Botnet protection R R
Ransomware prevention R R
Multi-engine scanning R
Network monitoring R
Asset inventory (software, hardware,
driver, etc.) R
inmarsat.com 23
White Paper
Cyber security requirements for IMO 2021
07 PROTECT
Fleet Secure Endpoint is built around ESET Endpoint
FLEET SECURE ENDPOINT AND Security, an award-winning enterprise-grade
endpoint security product, and has special
FLEET XPRESS - SUPPORTING IMO adaptations for use in a maritime setting. It not only
detects and blocks files with known signatures
2021 COMPLIANCE from operating but monitors low-level system calls
and actively analyses software for suspicious
Fleet Secure has been designed to align with IMO’s behaviour in real time.
five pillars for cyber resilience, namely: identify; – Botnet protection shuts down malicious
detect; protect; respond; and recover, while its connections to known botnets. Botnets hijack a
reporting function has been developed with IMO machine without the owner’s knowledge to carry
compliance in mind. In addition, an ISO 27001 audit of out Distributed Denial of Service (DDOS) attacks.
Fleet Secure Endpoint conducted by DNV GL When activated, they consume processing power
describes Fleet Secure Endpoint as a single product and cause spikes in bandwidth consumption.
which can assist in achieving IMO 2021 compliance. – Multi-engine scanning broadens detection by
Although Fleet Secure Endpoint works across all of using malware signature databases from multiple
Inmarsat's maritime services, to maximise protection security vendors so that new fingerprints not
and compliance Fleet Secure Endpoint should be known by all vendors are included during
used in conjunction with Fleet Xpress, which provides inspection.
reliable high-speed internet access with the ability to – Ransomware prevention detects and prevents
separate crew and business traffic and make it easier malicious encryption attempts before they have a
to respond to and recover from attacks. chance to initiate and encrypt the device.
– Two-way endpoint firewall blocks malicious
incoming and outgoing network traffic.
IDENTIFY – Anti-spyware terminates malicious applications
designed to steal sensitive information.
Fleet Secure highlights where errors and warnings
– Anti-phishing blocks connections to sites known
have occurred in the vessel/fleet, which enables the
to extract confidential user information.
designated security personnel to quickly ascertain
– Web control allows the system administrator
potential weak spots that require further
granular control over the websites users can visit.
investigation. It does this using a powerful network
– Endpoint Threat alerting sends an email
scanning and monitoring module, called Teyla, that
notification to the system administrator listing
automatically detects devices on the local network
recently detected threats on vessels.
and checks whether Fleet Secure Endpoint is
installed. If not endpoints will be marked as ‘rogue
nodes’ and alerts are raised as an alert. The
designated security officer can either allow or deny RESPOND
network access privileges to that device. Knowing how to react during and after a cyber-
This oversight means someone on the vessel is incident is critical to a well-rounded cyber security
always aware of what is connected to their network. strategy. It is necessary to envisage a wide range of
To aid network audits, on machines where installed, potential scenarios and plan the steps needed, to
Fleet Secure Endpoint will also collect data on contain their impact on vessel operation and safety
installed software, hardware and system and secondly to restore impaired systems and
configuration. recover data in a timely fashion.
24 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 25
White Paper
Cyber security requirements for IMO 2021
Fleet Secure Endpoint can assist the response and respond by blocking it, removing it and
stage in several ways. In contrast to off-the-shelf finally reporting it. The built-in memory analysis
products, the service is enhanced by round-the- will detect both known threats and new security
clock monitoring by a dedicated team of IT experts vulnerabilities. If Fleet Secure Endpoint recognises
based in the Inmarsat Security Operating Centre, a file to be malicious, it will be stored in a dedicated
who check security events or other signs of unusual quarantine location on the device. Quarantined files
network activity on a vessel as and when they are stored in a location that ensures the malicious
occur. They are supported by marine engineers with file cannot infect the system.
extensive knowledge of different hardware and
Once a security incident has been brought under
software systems found on modern vessels.
control and the immediate threat has been
Via the portal, the ship owner’s in-house IT team neutralised, attention shifts to restoring and
can roll out updates in real-time, quickly and reconnecting systems needed for normal vessel
remotely to all computers installed with Fleet operation. Work also begins on investigating the
Secure Endpoint in the wake of an incident, in order exact cause of the incident and taking measures to
to prevent an attack spreading across the fleet and prevent a recurrence or similar event from taking
reduce exposure to similar attacks in the future. place elsewhere in the fleet.
Additionally, the shore-based portal retains a
centralised log of all flagged security events and
allows bespoke alerts to be created. For example, REPORTING
alerts can be set up to warn when a certain virus Fleet Secure Endpoint comes with extensive built-
or class of virus is detected or certain software in reporting functionality which can help in this
requires updating. exercise. A full report can be created on the vessel,
The asset management functionality incorporated containing a record of all devices connected to
into Fleet Secure Endpoint gives offers a clear the network, their hardware and the software
overview to designated security personnel and that is installed. This report can be given to port
IT staff of which devices are onboard and which state control and/or authorities to show them the
devices have Fleet Secure Endpoint installed. It also vessel has been taking adequate steps to minimise
provides detailed information on assets and the cyber security risks on board. While Fleet Secure
software environment available for responding to Endpoint implementation does not by itself achieve
an incident and for analysis during the post-incident compliance, Fleet Secure Endpoint reporting is fully
review. IMO compliant.
– Alerting offers pro-active insight on what is The Fleet Secure Endpoint Security report shows
happening on board and helps react to incidents the following:
– Alerts can be created to E-mail the user when – Network connected devices with Fleet Secure
events happen on board, such as virus detections Endpoint installed, devices without Fleet Secure
or outdated software Endpoint installed
– A single agent handles all Fleet Secure Endpoint – System specifications such as free disk space,
related activities and multiple software packages CPU and amount of memory
are not needed, saving system resources – Installed software and their version
– A 24/7 Security Operations Centre takes action – Security events such as neutralized viruses and
when needed blocked USB drives
– Acknowledgements of the Security Operations
Centre team based on security events
RECOVERY Reports are generated in formats like PDF and can
If an infection is detected onboard, Fleet Secure be printed onboard so that the master of the vessel
Endpoint will automatically detect the infection can circulate them among staff and easily integrate
26 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
them into a vessel’s safety management manual, or FLEET SECURE ENDPOINT - THE COMPLIANCE
show port inspectors that steps have taken steps CHECKLIST
to protect the vessel and its assets. Even if a vessel
1. As a ship owner/manager, to defend your IT set-
has not been the target of an attack, Inmarsat
up you MUST:
recommends that these reports are periodically
reviewed to steer ongoing improvements to a – Know what you have: all IT systems/systems
vessel’s cyber risk management plan. Any Cyber controlled by IT - including Main Engines and
Review in the Change Management Process should Navigation Systems, etc.
– Defend what you have: to fight off basic threats
– Include ICT staff when making major changes in
to your organization, systems should be designed
ship’s system
to guard against failure, using Software /
– Ensure Cyber Security is considered in the end-to-
Hardware / Ship’s Systems redundancies.
end process when supplying new equipment
– Be able to recover: workarounds and recovery
processes must be in place for ICT and Ship’s
systems, with crews trained and at least Yearly
MANAGEABILITY Incident Drills for Cyber Security.
Using the Fleet Secure web portal the ship 2. However, IMO 2021 Compliance is NOT just about
operator/owner can remotely upload configurations defending ICT against cyber threats. It is about
to be implemented onboard so that Fleet Secure Total IT Best Practice on a ship’s
Endpoint can be configured remotely. The user can
– IT system AS WELL AS
also configure alerts to reflect owner/operator
– Technical, Navigation, Safety and Mechanical
preferences, so that events such as virus detections
Systems.
or blocked network attacks are also flagged up.
3. Therefore, as an IMO 2021-compliant cyber
In common with any proposed solution, Fleet
secure ship owner/manager, you MUST:
Secure Endpoint will only assist in reaching IMO
compliance when correctly implemented: this – Know what they have – Establish and record all
means the risk assessment needs to have been the systems (ICT and Technical) used on your
completed, while the Fleet Secure Endpoint monthly ships (including make, model, version, software
report will included in the Safety Management updates, supplier, etc.).
Manual. – Defend what they have - Ensure that steps are
being taken to harden ICT and Technical systems
against cyber threats.
– Be able to recover – update all documentation
onboard to include guidance on what to do in
case of IT or Technical system failures on ship,
including IT Policy in ISM Manuals, Training for
Crew, Workarounds Process and Drills.
4. Fleet Secure Endpoint helps you, as a ship
owner/manager to:
– Step 1 Know What you have: Fleet Secure
Endpoint includes a module logging any new
hardware added to your network.
– Step 2 Defend what you have: via strong AV,
WebControl, Network Monitoring.
– Step 3 Recover – Fleet Secure Endpoint’s crew
training module covers a significant part of the
training needs demanded for IMO 2021
Compliance.
inmarsat.com 27
White Paper
Cyber security requirements for IMO 2021
28 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 29
White Paper
Cyber security requirements for IMO 2021
30 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
multiple operating systems. For Windows operating Scenario: a crew member opens a phishing email
systems, Vista and up is supported. OSX, Linux and
The Fleet Secure Endpoint response:
their mobile counterparts IOS and Android are also
supported. – Scenario 1: If Fleet Secure Endpoint is fully
updated then it should detect that virus.
Fleet Secure Endpoint is distinguished from
– 1.1: The Inmarsat Security Operations Centre is
Endpoint Detection & Response (EDR) packages.
notified of this activity.
While these solutions are highly effective, they
– Scenario 2: Fleet Secure Endpoint is not
demand strict ship networking setup to ‘signature’
updated, the virus is not detected, and the
and check every file on the vessel, consuming huge
ransomware process is not stopped.
amounts of data. Fleet Secure Endpoint addresses
– 2.1: The Inmarsat Security Operations Centre is
attacks and infections without needing to signature
notified of this activity.
each file, saving on costs and data usage. In fact,
– Scenario 3: The firewall in Fleet Secure Endpoint
Fleet Secure Endpoint frequency and control
introduces segmentation of the network so that
reporting times can be adjusted, with data usage
the virus cannot spread to other PCs as they
as low as 7MB a month. Where ships have internet
block the incoming attack.
connectivity, Inmarsat recommends more frequent
reporting of network status so that its security Fleet Secure Endpoint handles all of these
operation centre can take swift action when scenarios automatically. An option is also available
malicious traffic is detected. to block out an endpoint from the network
remotely.
In addition, Fleet Secure Endpoint can be used
onboard vessels using FleetBroadband as their
connectivity solution. In this case, trench rules
need to be set correctly and onboard firewalls
(if any) must be updated to accommodate Fleet
Secure Endpoint IPs and port numbers.
inmarsat.com 31
White Paper
Cyber security requirements for IMO 2021
32 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
inmarsat.com 33
White Paper
Cyber security requirements for IMO 2021
10
FLEET SECURE ENDPOINT - REAL CASE
STUDIES
CASE 1
CASE 2
Vessel type: Undisclosed
Vessel type: Liquid Ethylene Gas Carrier
Assailant: Multiple infections with normal anti-
virus installed Assailant: Emotet trojan, causing vessel
operations to stop
The customer was using Palo Alto cyber security
software when the vessel was hit by multiple Emotet is well-known as a trojan in banking circles
infections, including Trojans, Worms and data but was detected as infecting the majority of
exfiltration viruses infesting the system. The machines onboard a LEG Carrier, becoming active
customer decided to install Fleet Secure Endpoint whenever a PC was switched on. The virus can
as part of a shipboard trial. Inmarsat’s engineer intercept and exfiltrate data transmitted and
found 79 infections that had not previously been saved when the user is browsing banking websites,
detected. resulting in leakage of sensitive data and malicious
use of the user's banking details.
Among the significant findings, the HTTP Filter
detected users onboard unknowingly visiting As part of a Fleet Xpress agreement, the ship was
websites serving malicious code. The connection equipped with two Fleet Secure Endpoint security
was dropped, and the user informed accordingly. modules, installed across all PCs onboard:
Again, the Fleet Secure Endpoint email filter caret-right Advanced Memory Scanner – This detected
detected infected attachments, including: Emotet in the memory, terminated and blocked it
– CoinMiner.T trojan (A trojan which uses system from recurring.
resources to mine cryptocurrency for its caret-right Heuristic Intrusion Prevent System (HIPS) – This
distributor) detected the malicious code being executed and
– TrojanDownloader.Agent.OJL trojan (a trojan stopped the execution of this code.
capable of downloading and executing other The virus was successfully cleared from the
malicious code) memory on all infected devices.
– Agent.AQ trojan (A trojan agent template
frequently used as a starting point for malicious
code that can be modified to do whatever the
malicious actor wants)
The Fleet Secure Endpoint email filter disposed of
these infections, preventing further infections.
34 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
CASE 3 CASE 4
Vessel type: Undisclosed Vessel type: Bulk carrier
Assailant: Sohanad worm Assailant: CoinMiner
A USB memory stick infected with the NCB worm The vessel in question had trialled Fleet Secure
Sohanad was connected to an endpoint onboard Endpoint. After the trial’s conclusion, the ship ran
ship. Sohanad spreads via removable media and for two months without Fleet Secure Endpoint. On
shared folders: once it has infected any part of re-installation of Fleet Secure Endpoint, all devices
the network, it tries to replicate itself by infecting onboard that were tested were found to have
applications and files. been infected with a CoinMiner. CoinMiners use a
device’s processing power to mine cryptocurrency
Two Fleet Secure Endpoint security modules were
for the attacker without the user’s knowledge.
implemented:
Fleet Secure Endpoint was able to neutralise all
caret-right Real-time file system protection – Detected that
threats.
files were being infected and automatically
halted the process from accessing files so it
could be investigated by the engine.
caret-right Heuristic Intrusion Prevent System (HIPS) -
Detected the malicious code that was causing
the replication and stopped the execution of this
code.
Fleet Secure Endpoint was able to stop the infection
from continuing, cleaning 17,000 infections in the
process.
inmarsat.com 35
White Paper
Cyber security requirements for IMO 2021
11
NEXT STEPS - HOW TO PROCEED
CYBER RESILIENCE FOR IMO 2021 – NEXT STEPS
HOW TO PROCEED WITH FLEET SECURE ENDPOINT
APPOINT Appoint a person on board for cyber security planning for IMO requirements
Angle-Down
Review and check Cyber Security Plan against guidance on onboard ICT covering
REVIEW communication and ship networks for business/crew
Angle-Down
PURCHASE FLEET SECURE
Purchase Fleet Secure Endpoint – one month free trial available
ENDPOINT
Angle-Down
PREPARE Remove any existing anti-virus software on each endpoint
Angle-Down
DOWNLOAD Download and run the installer
Angle-Down
SET-UP Set-up dashboard, manage reports
Angle-Down
CREW TRAINING Crew to complete MLA e-learning module, records kept for compliance purposes
Angle-Down
Repeat crew cyber awareness training annually – periodic threat intelligence
REPEAT offered via Fleet Secure Endpoint
36 NOVEMBER 2020
White Paper
Cyber security requirements for IMO 2021
For further information and questions, please contact the Inmarsat Maritime Security Services team:
Maritime.Security@inmarsat.com
inmarsat.com 37
inmarsat.com
While the information in this document has been prepared in good faith, no representation, warranty, assurance or undertaking (express or implied)
is or will be made, and no responsibility or liability (howsoever arising) is or will be accepted by the Inmarsat group or any of its officers, employees or
agents in relation to the adequacy, accuracy, completeness, reasonableness or fitness for purpose of the information in this document. All and any such
responsibility and liability is expressly disclaimed and excluded to the maximum extent permitted by applicable law. INMARSAT is a trademark owned
by the International Mobile Satellite Organization, licensed to Inmarsat Global Limited. The Inmarsat LOGO and all other Inmarsat trade marks in this
document are owned by Inmarsat Global Limited. In the event of any conflict between the words of the disclaimer and the English version from which it is
translated, the English version shall prevail. © Inmarsat Global Limited 2020. All rights reserved. Cyber Security Requirements for IMO 2021 White Paper.
November 2020.