Cross-Framework Mapping

3GPP SecurityvsIMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)

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

6
Controls Mapped
25
Gaps Found
16%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

3GPP Security maps to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) with 16% coverage across 5 directly mapped controls. Analysis of 31 3GPP Security controls identifies 26 compliance gaps — primarily concentrated in 3GPP Security: Communications Security.

Source: TheArtOfService Knowledge Graph | 31 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 6 of 6 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

3GPP Security: Information Security Policies(1 mappings)

3GPP-SEC-04Roles and responsibilities definition
IMO-CY-1.3Roles and Responsibilities

3GPP Security: Access Control(3 mappings)

3GPP-SEC-12User access management and provisioning
IMO-CY-2.1Access Control
3GPP-SEC-13Authentication and password management
IMO-CY-2.1Access Control
3GPP-SEC-14Privileged access management
IMO-CY-2.1Access Control

3GPP Security: Operations Security(2 mappings)

3GPP-SEC-23Backup and recovery procedures2 targets
IMO-CY-4.1Response Planning
IMO-CY-5.1Recovery Planning

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 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 3GPP Security and IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?

3GPP Security has 31 controls across its framework, while IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) covers 12 controls. Direct mapping analysis identifies 5 overlapping controls (16% coverage). The frameworks diverge most significantly in 3GPP Security: Communications Security, where 5 3GPP Security controls have no direct IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) equivalent.

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

Of 31 total 3GPP Security controls, 5 map directly to IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2) controls — representing 16% coverage. The remaining 26 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

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

26 3GPP Security controls have no direct equivalent in IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2). The highest concentration of gaps is in 3GPP Security: Communications Security 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 3GPP Security and IMO Maritime Cybersecurity Guidelines (MSC-FAL.1/Circ.3/Rev.2)?

The domain with the highest gap count is 3GPP Security: Communications Security (5 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.