ICAO Annex 17 - Aviation Security (AVSEC)vsUS Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements
See exactly how ICAO Annex 17 - Aviation Security (AVSEC) controls map to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
ICAO Annex 17 - Aviation Security (AVSEC) maps to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements 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 | 718 frameworks | 332K+ cross-framework mappings
Control Mappings
Showing 1 of 1 mapped controls across 1 domains. Sign up to explore all 332K+ mappings across 718 frameworks.
ICAO Annex 17 Chap 4 - Cargo + Mail + Catering(1 mappings)
Related Comparisons
Other ICAO Annex 17 - Aviation Security (AVSEC) comparisons
Other US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.
Free
- ✓ 718 framework browser
- ✓ Cross-framework mappings (332K+)
- ✓ 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
ICAO Annex 17 - Aviation Security (AVSEC) has 10 controls across its framework, while US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements covers 4 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements equivalent.
How many controls map between ICAO Annex 17 - Aviation Security (AVSEC) and US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
Of 10 total ICAO Annex 17 - Aviation Security (AVSEC) controls, 1 map directly to US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
9 ICAO Annex 17 - Aviation Security (AVSEC) controls have no direct equivalent in US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements. 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 US Maritime Transportation Security Act (MTSA) and USCG Cybersecurity Requirements?
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.