ICAO Annex 17 - Aviation Security (AVSEC)vsAWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)
See exactly how ICAO Annex 17 - Aviation Security (AVSEC) controls map to AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
ICAO Annex 17 - Aviation Security (AVSEC) maps to AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) with 20% coverage across 2 directly mapped controls. Analysis of 10 ICAO Annex 17 - Aviation Security (AVSEC) controls identifies 8 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 4 of 4 mapped controls across 2 domains. Sign up to explore all 324K+ mappings across 706 frameworks.
ICAO Annex 17 Chap 2 - Threat + Risk + Cyber(3 mappings)
ICAO Annex 17 Chap 4 - Cargo + Mail + Catering(1 mappings)
Related Comparisons
Other ICAO Annex 17 - Aviation Security (AVSEC) comparisons
Other AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) 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 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)?
ICAO Annex 17 - Aviation Security (AVSEC) has 10 controls across its framework, while AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) covers 37 controls. Direct mapping analysis identifies 2 overlapping controls (20% 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 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) equivalent.
How many controls map between ICAO Annex 17 - Aviation Security (AVSEC) and AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)?
Of 10 total ICAO Annex 17 - Aviation Security (AVSEC) controls, 2 map directly to AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls — representing 20% coverage. The remaining 8 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 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)?
8 ICAO Annex 17 - Aviation Security (AVSEC) controls have no direct equivalent in AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association). 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 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)?
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.