26% of EASA Part-IS you already have
APRA CPS 234 already covers about 26% of EASA Part-IS, leaving
25 of 34 controls as genuinely new work.
Already covered 6
Likely covered 3
New work 25
What is genuinely new work
Nothing in APRA CPS 234 reaches these. This is the list to scope.
IS.AR.200Competent Authority Oversight
IS.AR.205Authority Information Sharing
IS.D.OR.200Information Security Management System
IS.D.OR.215Personnel Requirements
IS.D.OR.220Information Security Risk Management Process
IS.D.OR.230Internal Reporting Scheme
IS.I.OR.100Access Control to Aviation Information Systems
IS.I.OR.110Cryptographic Controls
IS.I.OR.120Operational Technology and Aircraft Systems
IS.I.OR.200Information Security Management System
IS.I.OR.215Personnel Requirements
IS.I.OR.230Internal Reporting Scheme
IS.OR.200Information Security Management System (ISMS)
IS.OR.205Information Security Risk Assessment
IS.OR.210Information Security Risk Treatment
IS.OR.215Information Security Internal Reporting Scheme
IS.OR.220Information Security Incidents Detection, Response and Recovery
IS.OR.225Response to Findings Notified by the Competent Authority
IS.OR.230Information Security External Reporting
IS.OR.235Contracting of Information Security Management Activities
IS.OR.240Personnel Requirements
IS.OR.250Information Security Management Manual (ISMM)
IS.OR.255Changes to the Information Security Management System
IS.OR.260Continuous Improvement
Show the 9 you already have
IS.AR.215Information Security Incident Response
IS.D.OR.210Information Security Risk Treatment
IS.D.OR.225External Reporting of Information Security Events
IS.I.OR.210Information Security Risk Treatment
IS.I.OR.220Information Security Risk Management
IS.I.OR.225External Reporting
IS.AR.210Findings and Corrective Actions
IS.D.OR.205Information Security Risk Assessment
IS.I.OR.205Information Security Risk Assessment
How this is calculated
Already covered means a mapping runs from a control in APRA CPS 234 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