Framework overlap

Does ISO/IEC 29100:2024 cover EASA Part-IS?

You hold ISO/IEC 29100:2024 and have been told to do EASA Part-IS. Here is how much overlaps, control by control.

47% of EASA Part-IS you already have

ISO/IEC 29100:2024 already covers about 47% of EASA Part-IS, leaving 18 of 34 controls as genuinely new work.

Already covered 0 Likely covered 16 New work 18

No control in ISO/IEC 29100:2024 maps directly to one in EASA Part-IS. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in ISO/IEC 29100:2024 reaches these. This is the list to scope.

IS.AR.200
Competent Authority Oversight
IS.AR.205
Authority Information Sharing
IS.D.OR.215
Personnel Requirements
IS.D.OR.230
Internal Reporting Scheme
IS.I.OR.100
Access Control to Aviation Information Systems
IS.I.OR.110
Cryptographic Controls
IS.I.OR.120
Operational Technology and Aircraft Systems
IS.I.OR.215
Personnel Requirements
IS.I.OR.230
Internal Reporting Scheme
IS.OR.215
Information Security Internal Reporting Scheme
IS.OR.220
Information Security Incidents Detection, Response and Recovery
IS.OR.225
Response to Findings Notified by the Competent Authority
IS.OR.230
Information Security External Reporting
IS.OR.235
Contracting of Information Security Management Activities
IS.OR.240
Personnel Requirements
IS.OR.245
Record-Keeping
IS.OR.250
Information Security Management Manual (ISMM)
IS.OR.260
Continuous Improvement
Show the 16 you already have
IS.AR.210
Findings and Corrective Actions
IS.AR.215
Information Security Incident Response
IS.D.OR.200
Information Security Management System
IS.D.OR.205
Information Security Risk Assessment
IS.D.OR.210
Information Security Risk Treatment
IS.D.OR.220
Information Security Risk Management Process
IS.D.OR.225
External Reporting of Information Security Events
IS.I.OR.200
Information Security Management System
IS.I.OR.205
Information Security Risk Assessment
IS.I.OR.210
Information Security Risk Treatment
IS.I.OR.220
Information Security Risk Management
IS.I.OR.225
External Reporting
IS.OR.200
Information Security Management System (ISMS)
IS.OR.205
Information Security Risk Assessment
IS.OR.210
Information Security Risk Treatment
IS.OR.255
Changes to the Information Security Management System

How this is calculated

Already covered means a mapping runs from a control in ISO/IEC 29100:2024 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition