International (IMO)

IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.4)

53 controls. 117 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

53 controls 117 frameworks share controls with it International (IMO) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
IMO-MSC-FAL-Detect-AnomalyDetection-OT-IT-Monitoring-Reporting-BridgeAlarmsIMO MSC-FAL Detect Function - Anomaly Detection + OT and IT System Monitoring + Bridge Alarms + Log Aggregation + Incident Reporting Channels + Crew Observation19
IMO-MSC-FAL-FrameworkAlignment-NISTCSF-Identify-Protect-Detect-Respond-Recover-IndustryGuidelinesV4-IEC62443IMO MSC-FAL Framework Alignment - 5 Functional Elements Map to NIST CSF + Industry Guidelines on Cyber Security Onboard Ships v4 + IEC 62443 + ISO 27001 + USCG NVIC + EU NIS2 + Cla0
IMO-MSC-FAL-Govern-ThirdParty-SupplyChain-Manufacturer-Yard-PortFacility-IACS-E26-E27IMO MSC-FAL Govern - Third Party Cyber Risk + Supply Chain + Equipment Manufacturer + Yard + Port Facility + IACS UR E26/E27 + Continuous Improvement + Audit0
IMO-MSC-FAL-Identify-AssetInventory-ThreatsVulnerabilities-CyberRiskAssessment-RolesResponsibilitiesIMO MSC-FAL Identify Function - OT/IT Asset Inventory + Threats + Vulnerabilities + Cyber Risk Assessment + Roles and Responsibilities + Crew + CSO + DPA104
IMO-MSC-FAL-Protect-AccessControl-NetworkSegmentation-MalwareDefence-Patch-Awareness-DataSecurityIMO MSC-FAL Protect Function - Access Control + Network Segmentation + Malware Defence + Patch Management + Awareness Training + Data Security + Crew BYOD + Removable Media41
IMO-MSC-FAL-Recover-BackupRestore-ContinuityOfNavigation-LessonsLearned-DrillsIMO MSC-FAL Recover Function - Backup and Restore + Continuity of Navigation + Continuity of Cargo Operations + Continuity of Propulsion + Lessons Learned + Drills + Resilience27
IMO-MSC-FAL-Respond-IncidentResponse-Communication-FlagState-PortAuthority-CIRT-USCGNVICIMO MSC-FAL Respond Function - Incident Response Plan + Containment + Communication + Flag State + Port Authority + USCG NVIC + Class Society Notification + CIRT28
IMO-MSC-FAL-Scope-MSC-FAL1Circ3Rev2-MSC42898-2017-1Jan2021-ISMCode-SMSIMO Maritime Cyber Risk Management Scope - MSC-FAL.1/Circ.3 + Rev.2 + Resolution MSC.428(98) + ISM Code Safety Management System Integration + 1 January 2021 Effective + Senior Man0
11 Introduction0
2.12.1 Key definitions0
2.22.2 Background: systems at risk, IT and OT, threats and vulnerabilities0
2.32.3 Application0
3.23.1 and 3.2 Definition and goal of maritime cyber risk management0
3.33.3 Senior management leadership, training and cyber risk culture0
3.43.4 Current and desired posture comparison and risk-based prioritisation0
3.53.5 Functional elements and minimum controls0
3.5.13.5.1 Govern: strategy, policies, roles and continuity0
3.5.1.13.5.1.1 Accountable person or entity for cybersecurity0
3.5.1.23.5.1.2 Authority, support and competence of the accountable party0
3.5.23.5.2 Identify: current cyber risk to ships and ship/port interfaces0
3.5.2.13.5.2.1 Critical systems, dependencies and supply chains0
3.5.2.23.5.2.2 Inventory of onboard digital systems and connections0
3.5.2.33.5.2.3 Risk assessment of critical systems0
3.5.33.5.3 Protect: risk controls and contingency planning0
3.5.3.13.5.3.1 User credentials, privileged accounts and leavers0
3.5.3.23.5.3.2 Passwords, authentication and secured communications0
3.5.3.33.5.3.3 Exposure, approvals, logging, segmentation and secure acquisition0
3.5.3.43.5.3.4 Protection of connected systems and cryptography0
3.5.3.53.5.3.5 Unauthorized removable media0
3.5.3.63.5.3.6 Cybersecurity training, familiarization and testing0
3.5.3.73.5.3.7 Backups, software updates and incident response plans0
3.5.3.83.5.3.8 Supply chain security policy for critical systems0
3.5.3.93.5.3.9 Assessing effectiveness and reviewing measures0
3.5.43.5.4 Detect: timely detection of cyber incidents0
3.5.4.13.5.4.1 Threat list and active monitoring0
3.5.4.23.5.4.2 Training to recognise an ongoing incident0
3.5.53.5.5 Respond: plans, resilience and containment0
3.5.5.13.5.5.1 Incident reporting within set time frames0
3.5.5.23.5.5.2 Records of cyber incidents0
3.5.5.33.5.5.3 Training on responding to an incident0
3.5.63.5.6 Recover: restoring onboard CBS and networks0
3.5.6.13.5.6.1 Recovery and reinstatement strategies0
3.5.6.23.5.6.2 Training on recovery0
3.5.6.33.5.6.3 Root cause analysis of incidents0
3.63.6 Ongoing process and protection of cyber documents0
3.6-3.83.6 to 3.8 Supporting provisions0
3.73.7 Awareness proportionate to roles0
3.83.8 Cyber-resilient equipment and systems0
44 Standards and best practices for implementation0
MSC.428Resolution MSC.428(98): preamble and non-operative paragraphs0
MSC.428-1MSC.428(98) paragraphs 1 and 2: cyber risk management within the approved safety management system0
circularThe circular and its revision history0
statusEdition status and the IMO work programme0

Tell me when IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.4) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Backup schedule and restore test results
  • Restore priority list for critical systems
  • Backup or redundant OT for navigation and propulsion
  • Risk-based security plan covering encryption, pseudonymisation, resilience and restoration
  • Results of periodic security testing and control effectiveness reviews
  • Staff security awareness records

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.4), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition