API 1164vsIMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)
See exactly how API 1164 controls map to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
API 1164 maps to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) with 38% coverage across 9 directly mapped controls. Analysis of 24 API 1164 controls identifies 15 compliance gaps — primarily concentrated in API 1164: Asset Identification & Governance.
Source: TheArtOfService Knowledge Graph | 24 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
API 1164: Access Management(4 mappings)
API 1164: Systems Security(1 mappings)
API 1164: Incident Response & Recovery(6 mappings)
API 1164: Supply Chain & Configuration(2 mappings)
Related Comparisons
Other API 1164 comparisons
Other IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between API 1164 and IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?
API 1164 has 24 controls across its framework, while IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) covers 12 controls. Direct mapping analysis identifies 9 overlapping controls (38% coverage). The frameworks diverge most significantly in API 1164: Asset Identification & Governance, where 5 API 1164 controls have no direct IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) equivalent.
How many controls map between API 1164 and IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?
Of 24 total API 1164 controls, 9 map directly to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls — representing 38% coverage. The remaining 15 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping API 1164 to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?
15 API 1164 controls have no direct equivalent in IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2). The highest concentration of gaps is in API 1164: Asset Identification & Governance with 5 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 API 1164 and IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?
The domain with the highest gap count is API 1164: Asset Identification & Governance (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.