MDS2 (Medical Device)vsICAO Annex 17 - Aviation Security (AVSEC)
See exactly how MDS2 (Medical Device) controls map to ICAO Annex 17 - Aviation Security (AVSEC). Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
MDS2 (Medical Device) maps to ICAO Annex 17 - Aviation Security (AVSEC) with 50% coverage across 4 directly mapped controls. Analysis of 8 MDS2 (Medical Device) controls identifies 4 compliance gaps — primarily concentrated in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2.
Source: TheArtOfService Knowledge Graph | 8 controls analysed | 718 frameworks | 330K+ cross-framework mappings
Control Mappings
Showing 5 of 5 mapped controls across 4 domains. Sign up to explore all 330K+ mappings across 718 frameworks.
Audit Logging Integrity and Cybersecurity Risk - MDS2(2 mappings)
PHI Data Handling Storage and Transmission - MDS2(1 mappings)
Authentication and Authorization - MDS2(1 mappings)
Physical Security Workstation Disposal and Backup - MDS2(1 mappings)
Related Comparisons
Other MDS2 (Medical Device) comparisons
Other ICAO Annex 17 - Aviation Security (AVSEC) 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 (330K+)
- ✓ 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 MDS2 (Medical Device) and ICAO Annex 17 - Aviation Security (AVSEC)?
MDS2 (Medical Device) has 8 controls across its framework, while ICAO Annex 17 - Aviation Security (AVSEC) covers 10 controls. Direct mapping analysis identifies 4 overlapping controls (50% coverage). The frameworks diverge most significantly in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2, where 1 MDS2 (Medical Device) controls have no direct ICAO Annex 17 - Aviation Security (AVSEC) equivalent.
How many controls map between MDS2 (Medical Device) and ICAO Annex 17 - Aviation Security (AVSEC)?
Of 8 total MDS2 (Medical Device) controls, 4 map directly to ICAO Annex 17 - Aviation Security (AVSEC) controls — representing 50% coverage. The remaining 4 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping MDS2 (Medical Device) to ICAO Annex 17 - Aviation Security (AVSEC)?
4 MDS2 (Medical Device) controls have no direct equivalent in ICAO Annex 17 - Aviation Security (AVSEC). The highest concentration of gaps is in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2 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 MDS2 (Medical Device) and ICAO Annex 17 - Aviation Security (AVSEC)?
The domain with the highest gap count is Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2 (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.