Cross-Framework Mapping

ISO/IEC 27011:2024vsIACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems

See exactly how ISO/IEC 27011:2024 controls map to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems. Pre-computed mappings, identified gaps, and coverage analysis.

11
Controls Mapped
33
Gaps Found
18%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO/IEC 27011:2024 maps to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems with 18% coverage across 10 directly mapped controls. Analysis of 44 ISO/IEC 27011:2024 controls identifies 40 compliance gaps — primarily concentrated in Technological.

Source: TheArtOfService Knowledge Graph | 44 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 11 of 11 mapped controls across 6 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Clause 5: Organizational Controls for Telecommunications(1 mappings)

27011-5.3Segregation of duties
IACS-UR-E26-Protect-AccessControl-Authentication-IAM-RolesIACS UR E26 Protect Goal - Access Control + Identity + Authentication + Authorization + User Management

People(1 mappings)

27011-6.3Awareness and Training
IACS-UR-E26-Protect-NetworkSegmentation-Zones-Conduits-BoundaryIACS UR E26 Protect Goal - Network Segmentation + Zones + Conduits + Boundary Defence + Data Diodes

Clause 6: People Controls for Telecommunications(1 mappings)

27011-6.3Awareness and Training
IACS-UR-E26-Protect-NetworkSegmentation-Zones-Conduits-BoundaryIACS UR E26 Protect Goal - Network Segmentation + Zones + Conduits + Boundary Defence + Data Diodes

Clause 7: Physical Controls for Telecommunications(2 mappings)

27011-7.1Physical security perimeters
IACS-UR-E26-Protect-RemoteAccess-Wireless-Physical-BoundaryIACS UR E26 Protect Goal - Remote Access + Wireless + Physical Security + Boundary Protection
27011-7.3Equipment protection
IACS-UR-E26-Protect-RemoteAccess-Wireless-Physical-BoundaryIACS UR E26 Protect Goal - Remote Access + Wireless + Physical Security + Boundary Protection

Technological(1 mappings)

27011-8.1User Endpoint Devices
IACS-UR-E26-Protect-AccessControl-Authentication-IAM-RolesIACS UR E26 Protect Goal - Access Control + Identity + Authentication + Authorization + User Management

Clause 8: Technological Controls for Telecommunications(5 mappings)

27011-8.1User Endpoint Devices
IACS-UR-E26-Protect-AccessControl-Authentication-IAM-RolesIACS UR E26 Protect Goal - Access Control + Identity + Authentication + Authorization + User Management
27011-8.2Network security and segregation
IACS-UR-E26-Protect-NetworkSegmentation-Zones-Conduits-BoundaryIACS UR E26 Protect Goal - Network Segmentation + Zones + Conduits + Boundary Defence + Data Diodes
27011-8.4Logging and monitoring2 targets
IACS-UR-E26-Detect-Logging-Monitoring-Audit-AlertingIACS UR E26 Detect Goal - Logging + Network Monitoring + Audit Trail + Alerting + SIEM
IACS-UR-E27-Logging-Forensics-EventCaptureIACS UR E27 - Equipment Logging + Forensic Readiness + Event Capture + Tamper Detection
27011-8.6Data protection and backup
IACS-UR-E26-Respond-Recover-IncidentResponse-Recovery-Backup-LessonsIACS UR E26 Respond + Recover Goals - Incident Response + Communication + Recovery + Backup + Lessons Learned

Related Comparisons

Other ISO/IEC 27011:2024 comparisons

Other IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems comparisons

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 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 ISO/IEC 27011:2024 and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?

ISO/IEC 27011:2024 has 44 controls across its framework, while IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems covers 19 controls. Direct mapping analysis identifies 10 overlapping controls (18% coverage). The frameworks diverge most significantly in Technological, where 10 ISO/IEC 27011:2024 controls have no direct IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems equivalent.

How many controls map between ISO/IEC 27011:2024 and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?

Of 44 total ISO/IEC 27011:2024 controls, 10 map directly to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls — representing 18% coverage. The remaining 40 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO/IEC 27011:2024 to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?

40 ISO/IEC 27011:2024 controls have no direct equivalent in IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems. The highest concentration of gaps is in Technological with 10 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 ISO/IEC 27011:2024 and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?

The domain with the highest gap count is Technological (10 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.