Cross-Framework Mapping

IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)vsAPI 1164

See exactly how IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls map to API 1164. Pre-computed mappings, identified gaps, and coverage analysis.

25
Controls Mapped
7
Gaps Found
19%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) maps to API 1164 with 19% coverage across 0 directly mapped controls. Analysis of 32 IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls identifies 32 compliance gaps — primarily concentrated in Protect.

Source: TheArtOfService Knowledge Graph | 32 controls analysed | 704 frameworks | 357K+ cross-framework mappings

Control Mappings

Showing 20 of 25 mapped controls across 5 domains. Sign up to explore all 357K+ mappings across 704 frameworks.

IMO MSC-FAL Detect Function(2 mappings)

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 Observation2 targets
API1164-13Business Continuity and Recovery
API1164-13Business Continuity and Recovery

IMO MSC-FAL Identify Function(5 mappings)

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 + DPA5 targets
API1164-07Remote Access
API1164-07Remote Access
API1164-21TSA Pipeline Security Directive Alignment
API1164-21TSA Pipeline Security Directive Alignment
API1164-24Vulnerability assessment for critical systems

IMO MSC-FAL Protect Function(6 mappings)

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 Media6 targets
API1164-06Access Control
API1164-06Access Control
API1164-07Remote Access
API1164-07Remote Access
API1164-09Patch and Vulnerability Management
API1164-09Patch and Vulnerability Management

IMO MSC-FAL Recover Function(6 mappings)

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 + Resilience6 targets
API1164-17Wireless and Field Communications
API1164-17Wireless and Field Communications
API1164-18Field Device Security
API1164-18Field Device Security
API1164-19Safety Instrumented Systems Interface
API1164-19Safety Instrumented Systems Interface

IMO MSC-FAL Respond Function(1 mappings)

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 + CIRT
API1164-17Wireless and Field Communications

+5 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 704 frameworks.

Create Free Account →

Free forever — no credit card required

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 704 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 704 framework browser
  • Cross-framework mappings (357K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) and API 1164?

IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) has 32 controls across its framework, while API 1164 covers 24 controls. Direct mapping analysis identifies 0 overlapping controls (19% coverage). The frameworks diverge most significantly in Protect, where 8 IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls have no direct API 1164 equivalent.

How many controls map between IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) and API 1164?

Of 32 total IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls, 0 map directly to API 1164 controls — representing 19% coverage. The remaining 32 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) to API 1164?

32 IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls have no direct equivalent in API 1164. The highest concentration of gaps is in Protect with 8 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) and API 1164?

The domain with the highest gap count is Protect (8 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.