ICAO Annex 17 - Aviation Security (AVSEC)vsIATA Operational Safety Audit (IOSA) Standards Manual
See exactly how ICAO Annex 17 - Aviation Security (AVSEC) controls map to IATA Operational Safety Audit (IOSA) Standards Manual. Pre-computed mappings, identified gaps, and coverage analysis.
Need this as a report you can hand to an assessor? A coverage crosswalk for this pair can be built to order.
According to the TheArtOfService Compliance Knowledge Graph:
ICAO Annex 17 - Aviation Security (AVSEC) maps to IATA Operational Safety Audit (IOSA) Standards Manual with 6% coverage across 7 directly mapped controls. Analysis of 126 ICAO Annex 17 - Aviation Security (AVSEC) controls identifies 142 compliance gaps, primarily concentrated in Chapter 4: Preventive security measures – ICAO Annex 17 - Aviation Security (AVSEC).
Source: TheArtOfService Knowledge Graph | 126 controls analysed | 705 frameworks | 309K+ cross-framework mappings
Control Mappings
Showing 13 of 13 mapped controls across 1 domains. Sign up to explore all 309K+ mappings across 705 frameworks.
Superseded batch representation – ICAO Annex 17 - Aviation Security (AVSEC)(13 mappings)
A ICAO Annex 17 - Aviation Security (AVSEC) to IATA Operational Safety Audit (IOSA) Standards Manual crosswalk, built to order
The table above lists candidate mappings. A crosswalk answers the narrower question you are probably here for: which IATA Operational Safety Audit (IOSA) Standards Manual controls your existing ICAO Annex 17 - Aviation Security (AVSEC) work already satisfies, which are real gaps, and the reasoning behind every claim so you can check it. One pair, $299, one time.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
This direction has not been through crosswalk review and sign off, so no coverage figure is published for it. Reporting an unreviewed number would be worse than reporting none. It can be built to order at the same price as a pair that is already on the shelf.
If the two frameworks turn out to have too little in common for a crosswalk to help you, we say so and refund it rather than send a number worth nothing.
- Every evidenced control, with the reasoning behind it
- Every gap, with what it requires
- Its level of review stated plainly, not a bare number
Why this page shows two different percentages. The 6% in the header counts how many ICAO Annex 17 - Aviation Security (AVSEC) controls carry at least one candidate mapping in the graph, before any review. The crosswalk percentage counts something stricter: how many IATA Operational Safety Audit (IOSA) Standards Manual controls are actually evidenced, after a pass that argued against each mapping and kept only what survived. They answer different questions and they are not meant to agree.
A crosswalk narrows the work. It does not replace an audit, and your assessor may take a different view on individual controls. Mappings between frameworks are judgements, not text printed in either standard, which is why every claim in the report shows its reasoning. Questions go to support@theartofservice.com.
Related Comparisons
Other ICAO Annex 17 - Aviation Security (AVSEC) comparisons
Other IATA Operational Safety Audit (IOSA) Standards Manual comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 705 frameworks, at a fraction of consulting costs.
Free
- ✓ 705 framework browser
- ✓ Cross-framework mappings (309K+)
- ✓ 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 IATA Operational Safety Audit (IOSA) Standards Manual?
ICAO Annex 17 - Aviation Security (AVSEC) has 126 controls across its framework, while IATA Operational Safety Audit (IOSA) Standards Manual covers 214 controls. Direct mapping analysis identifies 7 overlapping controls (6% coverage). The frameworks diverge most significantly in Chapter 4: Preventive security measures – ICAO Annex 17 - Aviation Security (AVSEC), where 62 ICAO Annex 17 - Aviation Security (AVSEC) controls have no direct IATA Operational Safety Audit (IOSA) Standards Manual equivalent.
How many controls map between ICAO Annex 17 - Aviation Security (AVSEC) and IATA Operational Safety Audit (IOSA) Standards Manual?
Of 126 total ICAO Annex 17 - Aviation Security (AVSEC) controls, 7 map directly to IATA Operational Safety Audit (IOSA) Standards Manual controls, representing 6% coverage. The remaining 142 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 IATA Operational Safety Audit (IOSA) Standards Manual?
142 ICAO Annex 17 - Aviation Security (AVSEC) controls have no direct equivalent in IATA Operational Safety Audit (IOSA) Standards Manual. The highest concentration of gaps is in Chapter 4: Preventive security measures – ICAO Annex 17 - Aviation Security (AVSEC) with 62 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 IATA Operational Safety Audit (IOSA) Standards Manual?
The domain with the highest gap count is Chapter 4: Preventive security measures – ICAO Annex 17 - Aviation Security (AVSEC) (62 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.