ICAO Annex 17 - Aviation Security (AVSEC)vsIACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems
See exactly how ICAO Annex 17 - Aviation Security (AVSEC) controls map to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
ICAO Annex 17 - Aviation Security (AVSEC) maps to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems with 10% coverage across 1 directly mapped controls. Analysis of 10 ICAO Annex 17 - Aviation Security (AVSEC) controls identifies 9 compliance gaps — primarily concentrated in ICAO Annex 17 Chap 5 - Contingency + Response.
Source: TheArtOfService Knowledge Graph | 10 controls analysed | 706 frameworks | 324K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 324K+ mappings across 706 frameworks.
ICAO Annex 17 Chap 4 - Access Control + Personnel(1 mappings)
Related Comparisons
Other ICAO Annex 17 - Aviation Security (AVSEC) 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 706 frameworks — at a fraction of consulting costs.
Free
- ✓ 706 framework browser
- ✓ Cross-framework mappings (324K+)
- ✓ 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 ICAO Annex 17 - Aviation Security (AVSEC) and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?
ICAO Annex 17 - Aviation Security (AVSEC) has 10 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 1 overlapping controls (10% coverage). The frameworks diverge most significantly in ICAO Annex 17 Chap 5 - Contingency + Response, where 1 ICAO Annex 17 - Aviation Security (AVSEC) controls have no direct IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems equivalent.
How many controls map between ICAO Annex 17 - Aviation Security (AVSEC) and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?
Of 10 total ICAO Annex 17 - Aviation Security (AVSEC) controls, 1 map directly to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems controls — representing 10% coverage. The remaining 9 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping ICAO Annex 17 - Aviation Security (AVSEC) to IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?
9 ICAO Annex 17 - Aviation Security (AVSEC) 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 ICAO Annex 17 Chap 5 - Contingency + Response with 1 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 ICAO Annex 17 - Aviation Security (AVSEC) and IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems?
The domain with the highest gap count is ICAO Annex 17 Chap 5 - Contingency + Response (1 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.