Cross-Framework Mapping

OWASP ASVSvsICAO Annex 17 - Aviation Security (AVSEC)

See exactly how OWASP ASVS controls map to ICAO Annex 17 - Aviation Security (AVSEC). Pre-computed mappings, identified gaps, and coverage analysis.

6
Controls Mapped
8
Gaps Found
21%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

OWASP ASVS maps to ICAO Annex 17 - Aviation Security (AVSEC) with 21% coverage across 3 directly mapped controls. Analysis of 14 OWASP ASVS controls identifies 11 compliance gaps — primarily concentrated in V14 Configuration.

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

Control Mappings

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

V1 Architecture and Threat Modelling(1 mappings)

OWASPASVS-1Architecture, Design and Threat Modelling (V1)
ICAO-ANX17-Chap1-Definitions-Scope-Chicago-Convention-AVSECICAO Annex 17 Chapter 1 - Definitions + Scope + Chicago Convention Article 37 + AVSEC Coverage

V2 Authentication(2 mappings)

OWASPASVS-2Authentication and Credential Storage (V2 + V2.4)2 targets
ICAO-ANX17-Chap2-ThreatAssessment-RiskManagement-Cyber-GASePICAO Annex 17 Chapter 2 - Threat Assessment + Risk Management + Cyber Threats to Critical Aviation Systems (Amendment 17/18)
ICAO-ANX17-Chap4-AccessControl-AirsideRestricted-Personnel-BackgroundICAO Annex 17 Chapter 4 - Access Control + Airside + Security Restricted Area + Personnel Background Checks + Vetting

V4 Access Control(3 mappings)

OWASPASVS-4Access Control (V4 + V4.3)3 targets
ICAO-ANX17-Chap2-ThreatAssessment-RiskManagement-Cyber-GASePICAO Annex 17 Chapter 2 - Threat Assessment + Risk Management + Cyber Threats to Critical Aviation Systems (Amendment 17/18)
ICAO-ANX17-Chap4-AccessControl-AirsideRestricted-Personnel-BackgroundICAO Annex 17 Chapter 4 - Access Control + Airside + Security Restricted Area + Personnel Background Checks + Vetting
ICAO-ANX17-Chap4-SpecialCategories-Weapons-InFlightSecurity-CockpitDoorICAO Annex 17 Chapter 4 - Special Categories of Passengers + Weapons + In-Flight Security Officers + Flight Crew Compartment Door

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 OWASP ASVS and ICAO Annex 17 - Aviation Security (AVSEC)?

OWASP ASVS has 14 controls across its framework, while ICAO Annex 17 - Aviation Security (AVSEC) covers 10 controls. Direct mapping analysis identifies 3 overlapping controls (21% coverage). The frameworks diverge most significantly in V14 Configuration, where 1 OWASP ASVS controls have no direct ICAO Annex 17 - Aviation Security (AVSEC) equivalent.

How many controls map between OWASP ASVS and ICAO Annex 17 - Aviation Security (AVSEC)?

Of 14 total OWASP ASVS controls, 3 map directly to ICAO Annex 17 - Aviation Security (AVSEC) controls — representing 21% coverage. The remaining 11 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping OWASP ASVS to ICAO Annex 17 - Aviation Security (AVSEC)?

11 OWASP ASVS controls have no direct equivalent in ICAO Annex 17 - Aviation Security (AVSEC). The highest concentration of gaps is in V14 Configuration 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 OWASP ASVS and ICAO Annex 17 - Aviation Security (AVSEC)?

The domain with the highest gap count is V14 Configuration (1 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.