text: information security

text: compromise Safety N

text: Consequences likelihood, Threat Hazards

text: consequences and

text: Risk Y

text: context Mitigative

text: Preventative Top Acceptable?

text: Barriers Barriers Event

text: Context and target information security

text: compromise Information Vulnerability Security (IS)

text: Threat Consequence s

text: Preventative Information Mitigative Likelihood

text: Controls Compromise Controls

text: Airport capacity, BPM – luggage treatment state, PHMR identification, recording terminals

text: Initial flight plan processing system (IFPS) Collaborative decision-making (CDM) ATSP

text: Daily operational briefing

text: AIS - NOTAMs Airline

text: Weather forecast and observations / METAR

text: Consolidated maintenance data, completed checklist with performed activities

text: Operational documentation

text: Software updates Production

text: QAR, FDR data AOC data

text: Centralised maintenance system (CMS), Aircraft conditioning management system (ACMS) report

text: IFPS, Target take-off time, ATC flight plan proposal, Enhanced tactical flow management, CDM

text: AIREP encountered weather info

text: Airport capacity needs, boarding pass data, TOBT, Airlines attendance, PHMR identification, PNR – passenger info, BSM – luggage data

text: EFB load, specific SW and configuration, maintenance procedures, request for intervention

text: Take-off performance data Meteo data Parking data NOTAM, Chart, QNH, Temperature Weight and Balance AOC data

text: EFB load

text: Accounts & roles management

text: Maintenance procedures

text: Software loads

text: Data Base

text: Logistic Data

text: Raw maintenance data

text: Logisitic Data

text: Consolidated maintenance data

text: Completed checklist with performed activities

text: Software loads Data Base

text: EFB loads Hardware Maintenance requests

identifier: AMC & GM to Part-IS.AR — Issue 1, Amendment 1

amnesord: Part-IS.AR - Information Security – Authority Requirements

beslut: ED Decision 2025/015/R

title: AMC & GM to Part-IS.AR — Issue 1, Amendment 1

text: This document shows deleted, new or amended text as follows: — deleted text is struck through; — new or amended text is highlighted in blue; — an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

text: N o te to t h e r e a d e r

text: In amended, and in particular in existing (that is, unchanged) text, ‘Agency’ is used interchangeably with ‘EASA’. The interchangeable use of these two terms is more apparent in the consolidated versions. Therefore, please note that both terms refer to the ‘European Union Aviation Safety Agency (EASA)’.

text: Annex to ED Decision 2025/015/R Page 1 of 36

text: AMC & GM to Part-IS.AR Issue 1, Amendment 1

text: GM1 IS.AR.200 Information security management system (ISMS)

text: An information security management system (ISMS) is a systematic approach to establish, implement, operate, monitor, review, maintain and continuously improve the state of information security of an organisation. Its objective is to protect the information assets, such that the operational and safety objectives of an organisation can be reached in a risk-aware, effective and efficient manner. Generally speaking, an ISMS establishes an information security risk management process, based upon the results of information security impact analyses, which basically determine its scope. If information security breaches may cause or contribute to aviation safety consequences, information security requirements need to limit the their impact or influence of information security breaches on levels of aviation safety, which are deemed acceptable. Hence, all roles, processes, or information systems, which may cause or contribute to aviation safety consequences, are within the scope of

text: Regulation (EU) 2023/203

text: . The ISMS provides for means to decide on needed information security controls for all architectural layers (governance, business, application, technology, data) and domains (organisational, human, physical, technical). It further allows to manage the selection, implementation, and operation of information security controls. Finally, it allows to manage the governance, risk management and compliance (GRC) within the ISMS scope. The overall risk assessment considers safety consequences influenced by information security risks. These may emerge as threats, hazards, escalation factors that weaken barriers, or direct triggers of existing hazards. When conducting this assessment, both aspects, information security and safety need to be coordinated throughout the process. This ensures mutual understanding of the objectives and the implementation of preventive measures against of all types of threats or weaknesses, as well as mitigating measures. The risk management process is thus based on aviation safety risk assessments and derived information security risk acceptance levels, which are designed to effectively treat and manage information security risks with a potential impact on aviation safety caused by threats exploiting vulnerabilities of information assets in aeronautical systems. Interacting bow-ties is one possible way that allows for a higher-level and non-exhaustive illustration of how different disciplines of risk assessment may need to collaborate to establish a common risk perspective, as depicted in Figure 1. The below Figure 1 from ICAO Doc 10204 ‘Manual on Aviation Information Security’ illustrates these interactions.

text: Annex to ED Decision 2025/015/R Page 2 of 36

text: Risk Treatment

text: Risk Assessment

text: Safety Assessment

text: Information security Assessment

text: Y

text: N

text: Risk Treatment

text: Figure 1: Bow-tie representation of management of aviation safety risks posed by information security threats

text: Annex to ED Decision 2025/015/R Page 3 of 36

text: In the drawing, the term ‘context’ in the communication between the safety assessment process (SAP) and the information security assessment process (ISAP) carries slightly different notions, which need to be understood and distinguished. In order to satisfy the safety requirements, the SAP will provide context information, such as: — the architecture of the systems and the functional descriptions of the elements within the scope, including those related to the barriers. Systems should be understood as the dynamic interaction between people, processes, and products, or services; — all identified relevant safety hazards; — the top events and their relations (e.g. triggers) to those hazards. In addition to context information, it provides the target likelihood of the related information security successful compromise. This target likelihood is commensurate with the safety objectives related to the severity of the safety consequence. However, it needs to be complemented to include information about the acceptable level of uncertainty, in order to be able to rely adequately on the results of the ISAP. In turn, the ISAP will return context information such as: — modification to the architecture of the systems and functional descriptions of the elements modified or added, whether those were safety barriers or other items; — additional threats; — potentially additional safety hazards; — additional direct triggers of hazards; — additional escalating factors affecting barriers. In addition to context information, it provides the achieved likelihood of an information security successful compromise. While this likelihood is consistent with the safety objectives set by the SAP, the achieved level of uncertainty also needs to be considered. The interaction between SAP and ISAP is iterative and continues until the safety risk is acceptable, i.e. the target likelihood of the related information security successful compromise has been achieved. The interaction can start from safety consequences identified through the SAP that fall within the scope of the ISMS risk analysis, or from existing information security assessments. The ISMS in this Regulation should bring together the information security and aviation safety competencies in most of the processes, including, for instance, identifying critical systems or threats, and assessing potential impacts on and risks to aviation safety. ISMS implementation and maintenance […] PART-IS versus ISO/IEC 27001:2022 cross reference table For a mapping between the Part-IS provisions main tasks required under Pat-IS and the clauses and associated controls in ISO/IEC 27001:2022, refer to Appendix II IV.

text: Annex to ED Decision 2025/015/R Page 4 of 36

text: GM1 IS.AR.225(c) Personnel requirements

text: NECESSARY COMPETENCE AND TRAINING PROGRAMME

text: A training programme should start from the identification of the competence required by the personnel for each role, followed by the identification of the gaps between the existing competence and the required one. In order to develop the list of competencies, a competent authority may use, as initial guidance, an existing cybersecurity competence framework such as the European e-Competence Framework (e-CF) or the NICE (National Initiative for Cybersecurity Education) based on the NIST Cybersecurity Framework (NIST CSF). In Appendix II, the main tasks of this Regulation are listed and mapped to the competencies derived from the EU e-CF or, for ease of mapping, to the functions and categories of the NIST CSF. This mapping may be used to establish a baseline to identify the aforementioned competence gaps. However, it should be noticed that existing cybersecurity/information security competence frameworks such as the NICE typically focus primarily on the protection of standard information technologies; therefore, the proposed list of competencies may need to be adapted to the technologies or integrated with processes used in the organisation. […]

text: GM1 IS.AR.235 Continuous improvement

text: […] Similar provisions for continuous improvement are provided for in other information management systems such as ISO/IEC 27001 (see Appendix II IV to this document). […]

text: Annex to ED Decision 2025/015/R Page 5 of 36

text: Appendix II — Main tasks stemming from the implementation of Part-IS, including mapping mapped to the EU e-CF and the NIST CSF 1.1 2.0 competencies and ISO/IEC 27001 clauses and controls

text: Activity type Reference EU e-CF NIST CSF 2.0 Part-IS main task Management, Part-IS Operational Competence Functions & areas & skills categories Establish and operate an information ISM (E.08) GV.OP – IS Management IS.AR.200(a) security management system (ISMS) Governance Establish the scope of the ISMS in ISM (E.08) IS.AR.205(a) GV.RM – Risk accordance with according to Part-IS Management Management requirements Implement and maintain an ISM (E.08) GV.OP – IS Management IS.AR.200(a)(1) information security policy Governance ISM (E.08), Risk Identify and review information IS.AR.200(a)(2) ID.RA – Risk Management Management security risks IS.AR.205 Assessment (E.02) PR.IP – ISM (E.08), Risk Implement information security risk IS.AR.200(a)(3) Information Management Management treatment measures IS.AR.210 Protection (E.02) Processes Implement measures to detect Incident DE.AE – information security events and IS.AR.200(a)(4) Management Management Anomalies and identify those related to aviation IS.AR.215 (C.04) Events safety Monitor compliance with this Compliance GV.RM – Risk Regulation and report findings to top Operational IS.AR.200(a)(8) (E.09) Management management Information Protect confidentiality of exchanged Security PR.DS – Data Operational IS.AR.200(a)(9) information Management Security (E.08) Implement and maintain a continuous Information GV.IA – improvement process to measure the IS.AR.200(b) Security Improvement Management effectiveness and maturity of the ISMS IS.AR.235 Management and and strive to improve it (E.08) Assessment

text: Annex to ED Decision 2025/015/R Page 6 of 36

text: Activity type Reference EU e-CF NIST CSF 2.0 Part-IS main task Management, Part-IS Operational Competence Functions & areas & skills categories Risk RS.CO – Management Communicate to the Agency changes Communicatio Operational IS.AR.200(a)(10) (E.02), ISM regarding capability and responsibilities ns (E.08) Risk RS.CO – Share information to assist other Management Communicatio competent authorities, agencies and Operational IS.AR.200(a)(11) (E.02), ISM ns organisations (E.08)

text: Implement and maintain a continuous GV.IA –

text: improvement process to measure the IS.AR.200(b) Improvement Management ISM (E.08) effectiveness and maturity of the ISMS and IS.AR.235 and

text: strive to improve it Assessment

text: GV.IA – Document and maintain all key ISM (E.08), Improvement processes, procedures, roles and Management IS.AR.200(c) Compliance and responsibilities (E.09) Assessment Risk Identify all elements which could be ID.AM – Asset Management IS.AR.205(a) Management exposed to information security risks Management (E.02) Risk Management Identify the interfaces with other ID.BE – (E.02), Business organisations which could result in Management IS.AR.205(b) Business Change exposure to information security risks Environment Management (E.07) Risk Identify information security risks and ID.RA – Risk Management IS.AR.205(c) Management assign a risk level Assessment (E.02) Risk Review and update the risk GV.RM – Risk Operational IS.AR.205(d) Management assessment based on certain criteria Management (E.02) Develop and implement measures to Risk GV.RM – Risk address risks and verify their Operational IS.AR.210(a) Management Management effectiveness (E.02)

text: Annex to ED Decision 2025/015/R Page 7 of 36

text: Activity type Reference EU e-CF NIST CSF 2.0 Part-IS main task Management, Part-IS Operational Competence Functions & areas & skills categories Risk Communicate the outcome of the risk RS.CO – Management assessment to management, other Communicatio Operational IS.AR.210(b) (E.02), ISM personnel and other organisations ns (E.08) sharing an interface DE.CM – Implement measures to detect in Security processes and operations information ISM (E.08) Operational IS.AR.215(a) Continuous security events which may have a Monitoring potential impact on aviation safety Implement measures to respond to Incident RS.RP – information security events that may Operational IS.AR.215(b) Management Response cause an information security incident (C.04) Planning Incident RC.RP – Implement measures to recover from Operational IS.AR.215(c) Management Recovery information security incidents (C.04) Planning Supplier Manage risks associated with Relationship GV.RM – Risk contracted activities with regard to the Management IS.AR.220 Management Management management of information security (E.10)

text: Define a person with the authority to ISM (E.08), establish and maintain the organisational GV.OP – IS Compliance structures, policies, processes, and Management IS.AR.225(a) Governance (E.09) procedures necessary to implement this

text: Regulation

text: Create and maintain a process to GV.PO – ensure that there is sufficient Personnel Strategy, personnel to perform all activities Management IS.AR.225(b) Development Policy, and regarding information security (D.11) Oversight management Create and maintain a process to GV.PO – Personnel ensure that the personnel have the Strategy, Development necessary competence for activities Management IS.AR.225(c) Policy, and (D.11) regarding information security Oversight management Create and maintain a process to GV.PO – ensure that the personnel Prsonnel Strategy, acknowledge the responsibilities Management IS.AR.225(d) Development Policy, and associated with the assigned roles and (D.11) Oversight tasks

text: Annex to ED Decision 2025/015/R Page 8 of 36

text: Activity type Reference EU e-CF NIST CSF 2.0 Part-IS main task Management, Part-IS Operational Competence Functions & areas & skills categories PR.AC – Verify the identity and trustworthiness Identity of personnel who have access to Management IS.AR.225(e) ISM (E.08) Management information systems and Access Control Archive, protect and retain records ISM (E.08), PR.DS – Data and ensure they are traceable for a Operational IS.AR.230 Compliance Security specified time (E.09) GV.IA – Regularly assess the effectiveness and Improvement Operational IS.AR.235(a) ISM (E.08) maturity of the ISMS and Assessment Take actions to improve the ISMS if ISM (E.08) GV.IA – required. Reassess the ISMS elements Improvement Operational IS.AR.235(b) affected by the implemented and measures. Assessment Activity type Reference

text: Part-IS main task NIST CSF Version 1.1 ISO/IEC 27001 Management, Part-IS Operational Paragraph Annex A Control Function Category Clause :2013 :2022

text: Establish and operate an

text: information security Management 4 management system IS.AR.200(a) IDENTIFY ID.RM 6.1.1 (ISMS)

text: Establish the scope of the ID.BE-2 ISMS according to Part-IS Management IS.AR.205(a) IDENTIFY ID.BE-4 4.3 requirements ID.AM-5

text: Implement and maintain

text: an information security Management IS.AR.200(a)(1) IDENTIFY ID.GV-1 5.2 A5.1 A5.1 policy

text: Identify and review 6.1.2 Management IS.AR.200(a)(2) ID.GV-4 information security risks IDENTIFY 8.1 IS.AR.205 ID.RA 8.2

text: Implement security risk 6.1.3 Management IS.AR.200(a)(3) treatment measures PROTECT PR.PT 8.1 IS.AR.210 8.3

text: Implement measures to Management IS.AR.200(a)(4) DE.AE-3 A11.1.2 A7.2 DETECT detect information IS.AR.215 DE.CM-1 A12.4.1 A8.15

text: Annex to ED Decision 2025/015/R Page 9 of 36

text: Activity type Reference

text: security events and DE.CM-2 A12.4.3 A5.28

text: identify those related to DE.CM-3 A16.1.7

text: aviation safety

text: Monitor compliance with

text: this Regulation and report Operational A18.2.1 A5.35 findings to top IS.AR.200(a)(8) IDENTIFY ID.GV-3 9.2 A18.2.2 A5.36 management

text: Protect confidentiality of Operational PR.DS-1 A8.2.2 A5.13 exchanged information IS.AR.200(a)(9) PROTECT PR.DS-2 A13.2 A5.14

text: Communicate to the

text: Agency changes regarding Operational capability and IS.AR.200(a)(10) A6.1.3 A5.5

text: responsibilities

text: ID.RA-2 IDENTIFY Share information to ID.BE-2

text: assist other competent Operational PROTECT PR.IP-8 authorities, agencies and IS.AR.200(a)(11) A6.1.4 A5.6

text: organisations RS.CO-3 RESPOND RS.CO-5

text: ID.RA-6 IDENTIFY ID.SC-4

text: Implement and maintain PR.IP-7 PROTECT a continuous PR.IP-10 4.4 improvement process to A5.1.2 A5.1 9.1 measure the Management IS.AR.200(b) A16.1.7 A5.28 DETECT DE.DP-5 9.3 effectiveness and IS.AR.235 A17.1.3 A5.29 10.1 maturity of the ISMS and A18.2.1 A5.35 10.2 RS.MI-3 strive to improve it RESPOND RS.IM-2

text: RECOVER RC.IM-2

text: IDENTIFY ID.RM-1

text: ID.SC-2 Document and maintain

text: all key processes, 4.2 PR.AT-2 A5.1 A5.1 Management procedures, roles and IS.AR.200(c) 5.2 PR.AT-4 A6.1.1 A5.2 PROTECT 5.3 responsibilities PR.AT-5

text: DETECT DE.DP-1

text: RS.CO-1 RESPOND RS.AN-5

text: Annex to ED Decision 2025/015/R Page 10 of 36

text: Activity type Reference

text: Identify all elements ID.AM-1 which could be exposed Management ID.AM-2 to information security IS.AR.205(a) IDENTIFY 4.3 A8.1.1 A5.9 ID.AM-4 risks ID.AM-5

text: Identify the interfaces with other organisations ID.BE-1 which could result in Management ID.BE-2 IS.AR.205(b) IDENTIFY 4.3 exposure to information ID.BE-4 security risks ID.BE-5

text: ID.RA-1 Identify information ID.RA-2 security risks and assign a Management IS.AR.205(c) IDENTIFY ID.RA-3 6.1.2 risk level ID.RA-4 ID.RA-5

text: Review and update the risk assessment based on Operational IS.AR.205(d) IDENTIFY ID.RM 8.2 A5.7 certain criteria

text: Develop and implement measures to address risks Operational PR.IP 6.1.3 and verify their IS.AR.210(a) PROTECT PR.PT 8.3 effectiveness

text: ID.AM-3 ID.BE-1 ID.BE-2 Communicate the IDENTIFY ID.BE-4 outcome of the risk ID.RM-3 assessment to ID.SC-3 management, other Operational IS.AR.210(b) 8.1 personnel and other PROTECT PR.IP-7

text: organisations sharing an interface DE.AE-2 DETECT DE.AE-3 DE.AE-5

text: A11.1.2 A7.2 Implement measures to DE.AE A12.4.1 A8.8 detect in processes and DETECT DE.CM A12.6.1 A8.15 operations information Operational DE.DP A16.1.1 A8.16 security events which IS.AR.215(a) A16.1.2 A5.24 may have a potential A16.1.3 A5.25 impact on aviation safety PROTECT PR.PT-1 A16.1.4 A5.26 A16.1.5 A6.8

text: Implement measures to respond to information RS.RP Operational security events that may IS.AR.215(b) RESPOND RS.AN A16.1.5 A5.26 cause a security incident RS.MI

text: Annex to ED Decision 2025/015/R Page 11 of 36

text: Activity type Reference

text: Implement measures to recover from information Operational RC.RP-1 A16.1.5 A5.26 IS.AR.215(c) RECOVER security incidents RC.IM-1 A16.1.6 A5.27

text: Manage risks associated with contracted activities A5.19 with regard to the Management ID.SC-1 A15.1 A5.20 IS.AR.220 IDENTIFY management of ID.SC-2 A15.2 A5.21 information security A5.22

text: Define a person with the authority to establish and maintain the organisational structures, Management policies, processes, and IS.AR.225(a) IDENTIFY ID.AM-6 7.1 A6.1.1 A5.2 procedures necessary to implement this Regulation

text: Create and maintain a process to ensure that there is sufficient ID.AM-5 personnel to perform all Management IS.AR.225(b) IDENTIFY ID.AM-6 7.1 A6.1.1 A5.2 activities regarding ID.GV-2 information security management

text: Create and maintain a ID.AM-5 process to ensure that IDENTIFY ID.AM-6 the personnel have the necessary competence Management IS.AR.225(c) 7.2 A7.2.2 A6.3 for activities regarding information security PROTECT PR.AT-1 management

text: Create and maintain a process to ensure that the personnel acknowledge the Management ID.GV-2 7.3 IS.AR.225(d) IDENTIFY A7.1.2 A6.2 responsibilities associated ID.GV-3 7.4 with the assigned roles and tasks

text: Verify the identity and trustworthiness of personnel who have Management PR.AC-6 IS.AR.225(e) PROTECT 7.1 A7.1.1 A6.1 access to information PR.IP-11 systems

text: IS.AR.230 IDENTIFY ID.RA-4 7.5 A8.2.2 A5.10

text: Annex to ED Decision 2025/015/R Page 12 of 36

text: Activity type Reference

text: A8.2.3 A5.13 PR.AC-2 A11.1.3 A7.3 PR.AC-3 A11.1.4 A7.5 PR.AC-4 A12.1.3 A8.6 PR.DS-1 A12.3.1 A8.10 PR.DS-4 PROTECT A12.4.1 A8.13 PR.DS-5 A12.4.2 A8.15 PR.DS-6 Archive, protect and A12.4.3 Operational PR.IP-4 retain records traceability for a specified time PR.IP-6

text: RS.CO-3 RESPOND RS.CO-4

text: RECOVER RC.CO-3

text: Regularly assess the A5.1.2 A5.1 effectiveness and Operational IS.AR.235(a) 9 A12.7.1 A5.27 maturity of the ISMS A16.1.6 A8.34

text: Take actions to improve

text: the ISMS if required.

text: Reassess the Operational IS.AR.235(b) 10 A5.1.2 A5.1 implemented measures

text: of the ISMS elements.

text: Annex to ED Decision 2025/015/R Page 13 of 36

text: Appendix III — Examples of aviation services and interfaces

text: AVIATION SERVICES The following is a non-exhaustive and non-complete list of aviation services that can be used as a basis to identify the scope of risk assessment for the organisation: — aerodrome & ATM-MET service providers — aeronautical digital mapping services — aeronautical information management (AIM) – external, national, regional — airports — air traffic control (ATC) – external, superior — air traffic management (ATM) — approach (APP) & area control (ACC) Services – ER ACC, APP ACC — cargo and passenger loading — civil & state airspace user (AU) operations centres — communication infrastructure — flight information & traffic information services (FIS/TIS) data integrator — fuel calculation — navigation infrastructure – ground-based, satellite-based — non-ATM meteorological (MET) service providers — mass & balance calculation — non-aviation users (external) — regional & sub-regional airspace management (ASM) and air traffic flow & capacity management (ATFCM) — static aeronautical data services — sub-regional demand & capacity balancing (DCB) common service providers — surveillance infrastructure – airport, en-route, terminal manoeuvring area (TMA) — route planning — time reference services (external) — tower (TWR) services • aerodrome ATM-MET services provider • aeronautical digital map service • AIM (external)

text: Annex to ED Decision 2025/015/R Page 14 of 36

text: • airport • APP ACC • ATC (external) • ATC superior • ATM • ATM-MET services provider • civil AU operations centre • communication infrastructure • ER ACC • FIS/TIS data integrator • national AIM • navigation infrastructure — ground-based • navigation Infrastructure — satellite-based • non-ATM-MET services provider • non-aviation users (external) • regional AIM • regional ASM • regional ATFCM • state AU operations centre • static aeronautical data service • sub-regional DCB common service provision • sub-regional/local ATFCM • sub-regional/national ASM • surveillance infrastructure airport • surveillance infrastructure en-route • surveillance infrastructure TMA • time reference (external) • tower (TWR)

text: Annex to ED Decision 2025/015/R Page 15 of 36

text: INTERFACES Below are some examples of data exchange at the interfaces between organisations interacting in different functional chains, which can be used as a basis for identifying the scope of the risk assessment for the organisation. Note 1: These examples are graphical representations based on the ‘Examples of ecosystem data exchange’ provided in EUROCAE ED-201A, Appendix B - Tables B-14, which can be consulted for further information. Note 2: Although it is not an organisation, an aircraft has been included in all these examples for the sake of completeness of the description of the data exchange. The aircraft should be considered as an element within the scope of the ISMS of the organisation to which it belongs (typically the airline). Any data exchange between aircraft and other systems within the organisation should take into account existing security measures that may have been evaluated as part of aircraft certification (see also GM1 IS.AR.205(c)).

text: Airport

text: AISP

text: METSP

text: Maintenance

text: Design and

text: Aircraft

text: Figure 1: Interfaces of other organisations with an airline operator

text: Annex to ED Decision 2025/015/R Page 16 of 36

text: ATC METSP Airline Airport Maintenance Aircraft

text: Figure 2: Interfaces of an airline operator with other organisations

text: Design and Production Maintenance Airline Aircraft

text: Figure 3: Interfaces of other organisations with a maintenance service provider

text: Annex to ED Decision 2025/015/R Page 17 of 36

text: Figure 4: Interfaces of a maintenance service provider with other organisations

text: Annex to ED Decision 2025/015/R Page 18 of 36

text: Appendix IV — Part-IS requirements mapping to ISO/IEC 27001:2022 clauses and controls, and considerations on differences

text: Although Part-IS does not credit ISO/IEC 27001 certification, the practices and methods typically adopted for implementing and maintaining an ISMS under ISO/IEC 27000 largely align with the objectives of this regulation. Therefore, entities that have already implemented an ISMS under ISO/IEC 27001 can use this as a basis for Part-IS compliance. The following provides guidance on how competent authorities that have already implemented an ISMS compliant with ISO/IEC 27001:2022 can integrate Part-IS requirements into their existing ISMS. Specifically, the table below illustrates how to incorporate the ‘Part-IS particularity’ of each requirement into an existing ISO/IEC 27001-based ISMS in order to achieve Part-IS compliance. This is referred to as ‘Guidance on Part-IS implementation’. Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement IS.AR.200(a) Related ISO/IEC 27001:2022 clauses and controls 4. Context of the organisation 6.1.1 Actions to address risks and opportunities - General Part-IS particularity An ISMS designed in the context of an ISO/IEC 27001:2022 ISMS, which is currently not connected to the management systems required by the delegated and implementing acts of

text: Regulation (EU) 2018/1139

text: , including Part-IS, may differ if these different systems do not address the same goals. Part-IS focuses on information security requirements meeting the applicable aviation safety objectives, which have an influence on elements of the ISMS. Also, the ‘interested parties’ and the ‘internal and external issues’ as laid down in Chapter 4 of ISO/IEC 27001:2022 may be adapted to address the requirements of Part-IS for the competent authority. Guidance on Part-IS implementation Please note that the point IS.AR.200 requirement points to many other Part-IS requirements that the ISMS has to comply with, namely points 205, 210, 215, 220, 225, 230 and 235. Further details are provided in the specific chapters on the particular requirement. Regarding the other remaining requirements, not pointing out to other Part-IS requirements, and comparing them with ISO/IEC 27001:2022, there are five requirements left, namely points IS.AR.200(a)(1), IS.AR.200(a)(8), IS.AR.200(a)(9), IS.AR.200(a)(10) and IS.AR.200(a)(11). IS.OR.200(a)(1) Related ISO/IEC 27001:2022 clauses and controls 5.2 Policy A.5.1 Policies for information securities Part-IS particularity

text: Annex to ED Decision 2025/015/R Page 19 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement An ISMS designed in the context of an ISO/IEC 27001:2022 ISMS, which is currently not connected to the management systems required by the delegated and implementing acts of

text: Regulation (EU) 2018/1139

text: , may differ as these different systems do often not address the same goals. Part-IS focuses on information security requirements influencing the applicable aviation safety objectives, which in their turn have an influence on the elements of the ISMS. Guidance on Part-IS implementation The policy on information security established in an ISO/IEC 27001:2022 context has to be updated with regard to the potential impact of the risks on aviation safety. At least the elements of AMC1 IS.AR.200(a)(1) have to be mentioned in the policy. Therefore, the following elements may need to be added to an existing ISMS policy. The elements in bold and italics are additional guidance that might also be considered. (a) committing to complying with applicable legislation, considering relevant standards and best practices, including safety- and cybersecurity-related standards and guidance published or prescribed by ICAO or EASA; (b) setting objectives and performance measures for managing information security, updated to ensure meeting the applicable aviation safety objectives; (c) defining general principles, activities, processes for the competent authority to appropriately secure information and communication technology systems and data, in relation to the information security / safety risk assessment required by point IS.AR.205; (d) committing to applying ISMS requirements into the processes of the competent authority; (e) committing to continually improving towards higher levels of information security process maturity as per point IS.AR.235; (f) committing to satisfying applicable requirements regarding information security and its proactive and systematic management and to the provision of appropriate resources for its implementation and operation; (g) assigning information security as one of the essential responsibilities for all managers; (h) committing to promoting the information security policy through training or awareness sessions within the competent authority to all personnel on a regular basis or upon modifications; (i) encouraging the implementation of a ‘just-culture’ and the reporting of vulnerabilities, suspicious/anomalous events and/or information security incidents; (j) committing to communicating the information security policy to all relevant parties, as appropriate.

text: Annex to ED Decision 2025/015/R Page 20 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement IS.AR.200(a)(8) Related ISO/IEC 27001:2022 clauses and controls 9.2. Internal audit 9.3 Management review 10.2 Non-conformity and corrective action A5.36 Compliance with policies, rules and standards for information security Part-IS particularity This requirement is strongly related to the internal audit system and the independent checking function of ISO/IEC 27001:2022. The required feedback system to the person referred to in point IS.AR.225(a) fits into the requirement of 9.3. In addition, all delegated and implementing acts for the specific domains require a similar ‘compliance monitoring function’, where information security should be integrated as described in AMC1 IS.AR.200(a)(8). Guidance on Part-IS implementation The requirements of ISO/IEC 27001:2022 and the delegated and implementing acts of

text: Regulation (EU) 2018/1139

text: are compatible. Therefore, it will be easy to integrate Part-IS into the audit scope of the ISO/IEC 27001:2022 internal audit system. The role of the the person referred to in point IS.AR.225 (a) has to be addressed accordingly in the feedback loop if the role is not already addressed in the management review process. This person is required to be personally briefed on the key findings so that appropriate decisions can be made. Refer also to GM1 IS.AR.200(a)(8). Note: ISO 19011:2018 provides guidance on the establishment of an internal audit system. Specifically, Chapter A.7 ‘Auditing compliance within a management system’ provides useful guidance on how to integrate a compliance monitoring function into an internal audit system. IS.AR.200(a)(9) Related ISO/IEC 27001:2022 clauses and controls 7.5.3. Control of documented information (Note) A5.12 Classification of information A5.34 Privacy and protection of personal identifiable information (PII) A8.12 Data leakage prevention Part-IS particularity This requirement is limited to ‘information related to oversight activities and received through the organisation’s external reporting scheme’ and to confidentiality. ISO/IEC 27001:2022 does not differentiate between type of information (as laid down e.g. in ISO 9001:2015 Chapter 8.5.3). The only reference is made in the note in Chapter 7.5.3.

text: Annex to ED Decision 2025/015/R Page 21 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Part-IS stresses protection of information related oversight activities and external information received due to the sensitivity it may have regarding incidents and vulnerabilities disclosure. Insufficient confidentiality protection may result in exploitation of vulnerabilities affecting safety that the original provider of information may not have perceived. Guidance on Part-IS implementation The protection of information, specifically regarding confidentiality (as in ISO/IEC 27002:2022), is related to a set of controls that can be found in Table A.1 (Matrix of controls and attribute values) of ISO/IEC 27002:2022. See also the definition in ISO 27002:2022: 3.1.7 confidential information information that is not intended to be made available or disclosed to unauthorized individuals, entities or processes. The competent authority having implemented these controls should take special care that they apply to external information that may result in information security threats if known by unauthorised actors. When this kind of information is further shared with other entities, appropriate confidentiality procedures must be put in place and followed (TLP marking for instance). IS.AR.200(a)(10) Related ISO/IEC 27001:2022 clauses and controls and A5.5 Contact with authorities Part-IS particularity These requirements are not directly addressed in ISO/IEC 27001:2022. Guidance on Part-IS implementation This is not covered by the requirements of ISO/IEC 27001:2022, so it is not possible to adapt existing policies and procedures under ISO/IEC 27001:2022 for these provisions. To ensure compliance with these requirements, please refer exclusively to the related AMC and GM. IS.AR.200(b) Related ISO/IEC 27001:2022 clauses and controls 10.1 Continual improvement Part-IS particularity Part-IS and ISO/IEC 27001:2022 are very similar regarding this requirement. See points IS.AR.235 (a) and (b) for subtle differences. Guidance on Part-IS implementation See point IS.AR.235 in this table. IS.AR.200(c) Related ISO/IEC 27001:2022 clauses and controls 6.3 Planning of changes 7.5.3 Control of documented information

text: Annex to ED Decision 2025/015/R Page 22 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Part-IS particularity Control of documented information is one of the key processes in each ISO management system standard, following the ISO ‘high-level structure’ (ISO/IEC Directives part 1 Annex SL), such as ISO/IEC 27001:2022. In addition, most of the delegated and implementing acts for the specific domains require a similar need to document, where information security should be integrated. Guidance on Part-IS implementation Additional guidance is provided under GM1 IS.AR.200(c). IS.AR.200 (d) Related ISO/IEC 27001:2022 clauses and controls 4.3 Determining the scope of the information security management system. Part-IS particularity The scope statement and the ‘statement of applicability’ (SOA) are the best references to apply the ‘nature and complexity’. In addition, most of the delegated and implementing acts for the specific domains require a similar need to document, where information security should be integrated. Guidance on Part-IS implementation When determining the scope, it should be noted that Part-IS is delimited to the subject matter as defined in Article 1 of the Regulation(s), which refers to identification and management of information security risks with potential impact on aviation safety. Considering this, the scope of an ISMS under ISO/IEC 27001:2022 may be broader than that required by Part-IS. Some organisational units, processes or locations may fall under what is covered by the ISMS under ISO/IEC 27001:2022, but not within the scope of Part-IS. The opposite may happen too: the scope under ISO/IEC 27001:2022 may be narrower than the one Part-IS would require (e. g. the ISO/IEC 27001:2022 scope covers only the IT department). In both situations, scope definitions have to be compared and adjusted when necessary. Note: See also guidance on point IS.AR.205(a) in this table. The scope statement in the ISO/IEC 27001:2022 context is the right place where this clarification is made. IS.AR.205(a) Related ISO/IEC 27001:2022 clauses and controls 4.3 Determining the scope of the information security management system 6.1.2 Information security risk assessment Part-IS particularity

text: Annex to ED Decision 2025/015/R Page 23 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement This requirement of Part-IS is in line with ISO/IEC 27001:2022, however ISO/IEC 27001:2022 allows a wider focus, whereas Part-IS puts the focus on safety already from the element’s identification stage. In addition, all of the delegated and implementing acts for the specific domains require a risk assessment process, where information security can be integrated. Guidance on Part-IS implementation AMC1 IS.AR.205(a) explains that when conducting an information security risk assessment, the competent authority should ensure that each relevant aviation safety impact is identified and included in the ISMS scope, which might not be the case when using ISO/IEC 27001:2022. On the other hand, an ISO/IEC 27001:2022 ISMS focuses its security risk assessment mainly on the business impact of infringement on confidentiality, integrity and availability, their risks and the impact on assets (e. g. loss of IT infrastructure, breach of data). This means that, starting from an ISMS based on ISO/IEC 27001:2022, a complementary analysis has to be made to take into account all the elements related to aviation safety. To bridge the two approaches of safety management systems (SMS) and ISMS, an identified information security risk may be entered as a ‘cause’ or ‘contributing event’ in the aviation-safety-focused risk assessment required by the domain-specific implementing or delegated act. The figure in GM1.IS.AR.205(c) provides a good indication of how this bridge could be built. IS.AR.205(b) Related ISO/IEC 27001:2022 clauses and controls 4.1 Understanding the organisation and its context 4.3 Determining the scope of the information security management system A5.19 Information security in supplier relationships A5.21 Managing information security in the information and communication technology (ICT) supply chain Part-IS particularity Point IS.AR.205(b) focuses on the identification of interfaces with the other parties. ISO/IEC 27001:2022 4.3 requires considering in point c) the interfaces at and dependencies between activities performed by the competent authority and those that are performed by other parties. So, there is more in Part-IS than that required by ISO/IEC 27001:2022, provided that the scope considered includes safety, as required by point IS.AR.205(a). The controls A5.19 and A5.21 are a profound foundation for the requirements of point IS.AR.205(b). Guidance on Part-IS implementation

text: Annex to ED Decision 2025/015/R Page 24 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement ISO/IEC 27001:2022 A5.19 requires the identification of risks associated with the use of suppliers’ products or services. ISO 27002 A5.19 contains additional guidance in points f) to j) on how to manage the risk exposure. ISO/IEC 27001:2022 A5.21 requires the management of information security risks associated with the ICT products and services supply chain. ISO 27002 A5.21 contains additional guidance in points f), k), l) and m) on how to manage risks through the supply chain. The Part-IS notion about interfaces and supply chain goes beyond the respective ISO/IEC 27001:2022 notion. GM1 IS.AR.205(b) requests interfacing entities to share information about mutual risk exposure (including all data flows) and urges competent authorities to use ED-201A for that. Point IS.AR.205(c) also requires accounting for information acquired by interfacing entities, which underlines the two-way nature of the considerations. IS.AR.205(c) Related ISO/IEC 27001:2022 clauses and controls 6.1.2 Information security risk assessment Part-IS particularity Point IS.AR.205(c) is the ‘heart’ of Part-IS. ISO/IEC 27001:2022 6.1.2 opens a ‘framework’ where the requirements of point IS.AR.205 may fit in. It has to be assured that the risk management systems of the ISMS and those required by the SMS-regulations (see point IS.AR.205(a)) do NOT operate independently, as there might be difficulties in connecting the two systems. Guidance on Part-IS implementation Further to this provision, a proper risk assessment has to be made, taking into account the scope and interfaces described in points IS.AR.205(a) and IS.AR.205(b). It has to be noted (see also GM1 IS.AR.205(c)) that point IS.AR.205 does not require the use of any specific information security risk assessment framework, such as ISO31000, NIST or others to develop the risk assessment. ISO/IEC 27001:2022 tends to lean towards using ISO 27005 as a risk assessment standard; however, it does not make it mandatory. The key point is that the risk assessment carried out in the application of ISO/IEC 27001:2022 6.1.2 does not necessarily consider safety risks, and may focus on different types of risks. With respect to safety, conditions that may lead to safety consequences are identified as hazards. Their materialisation may be either directly triggered or caused by information security threats which have not been successfully prevented. Information security can thus cause or contribute to a safety consequence in four different ways: (1) it can act as a safety threat; (2) it can have a negative effect on a safety barrier, rendering it less effective than before; (3) it can directly trigger the materialisation of an already identified hazard; or (4) it can constitute a new, not yet identified, hazard, which can obviously also materialise.

text: Annex to ED Decision 2025/015/R Page 25 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement By using e.g. the ‘bow-tie method’ regarding information security, a ‘hazard’ would be replaced by a ‘vulnerability’, which can be exploited resulting in information security consequences (e.g. lack or reduction of confidentiality, integrity, availability, authenticity properties). Hence, from a methodology perspective, both considerations are very similar and can be designed to interact (e. g. consequences of the information security bow-tie may connect as causes of the ‘safety bow-tie’). Where the authority has implemented an SMS and operates an ISMS under voluntary compliance with ISO/IEC 27001:2022, it may operate two risk management systems, one for safety and one for information security. The latter may ultimately be certified by an ISO/IEC 27001:2022 accredited body. Each potential risk identified by the ISMS risk management has to be systematically assessed for its potential impact on safety. To establish the connection between the systems, the following approach should be used: (1) If a safety risk assessment is available, it should be able to provide its context and determined target likelihoods for acceptable information security risks to the information security risk assessment process. The context consists of the system architecture, including its preventative and mitigative barriers, the hazards assessed and the safety risks identified. Based upon the information provided, the information security risk assessment can be conducted. Modifications to the system architecture, or any modifications of properties of the preventative or mitigative barriers, as well as the achieved risk properties need to be communicated back to the safety risk assessment process. Based upon this communication, the safety risk assessment has to be updated. In other words: mitigation measures put in place as a result of the information security risk assessment should also be considered as they may not only mitigate, but possibly also create a negative safety impact. (2) If a safety risk assessment is available, but the information security assessment process identifies a new hazard that was previously unknown to the safety risk assessment, a full hazard assessment of all safety aspects has to be conducted to ensure that the safety risk assessment contains the ‘full picture’ of the newly addressed hazard. (3) The safety risk and the information security risk assessments need to be repeated as described above until all acceptability requirements for all aspects are met. IS.AR.205(d) Related ISO/IEC 27001:2022 clauses and controls 6.3 Planning of changes 8.2 Information security risk assessment Part-IS particularity

text: Annex to ED Decision 2025/015/R Page 26 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Point IS.AR.205(d) is about the subsequent changes to the original risk assessment, due to a change of context or interfaces or knowledge about the risks or lessons learnt. This is equivalent to ISO/IEC 27001:2022 8.2. In both frameworks the reviews are planned and documented. Guidance on Part-IS implementation The same process as that already in place in an ISO/IEC 27001:2022 context can be used to implement point IS.AR.205(d), provided that this process has been updated to include safety criteria evaluation of changes that trigger an unplanned update of the risk assessment. Those competent authorities that have most experienced risk assessment updates at planned intervals will need to be proactive to trigger such updates more often in the situations listed in points IS.AR.205(d) (1), (2), (3), and (4) that could affect safety. The triggering criteria and the process should be documented and tested before implementation, for example through table-top exercises. The change management process is key to keep a management system in a solid and stable condition. Considering an established ISMS according to ISO/IEC 27001:2022, the regular updates of the risk assessment based on changes and lessons learned should be effective. The essential focus, introduced by Part-IS, is the ‘impact on safety’, which drives the update assessment. Change management processes focusing on changes that may have impact on safety are also set out in all domain-specific implementing and delegated acts. Without the ‘bridge’ of Part-IS, both systems (ISMS and SMS) are implemented independently, often without considering interdependencies. Part-IS implies the need (and provides the opportunity) to interlink the systems to provide a common risk picture for the competent authority, with a focus on safety, but also opening the horizon to information security. IS.AR.210(a) Related ISO/IEC 27001:2022 clauses and controls 6.1.3 Information security risk treatment 8.3 Information security risk treatment Part-IS particularity Point IS.AR.210(a) is about Information security risk treatment, which is widely covered by ISO/IEC 27001:2022, its Appendix A, and ISO/IEC 27002. Point IS.AR.210(a) provides however some additional inputs related to the risks that may have a safety impact. Guidance on Part-IS implementation ISO/IEC 27001:2022 6.1.3 is about the definition of the risk treatment plan, while ISO/IEC 27001:2022 8.3 deals with the implementation of the plan, and both are relevant. ISO/IEC 27001:2022 Annex A contains a list of possible information security controls, and therefore should also be used in addition to the already existing

text: Annex to ED Decision 2025/015/R Page 27 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement controls, to mitigate information security risks having an impact of safety. All the controls of Annex A are detailed in ISO/IEC 27002. Point IS.AR.210(a) specifies that the measures selected in the plan have to reduce the consequences on aviation safety associated with the materialisation of the threat scenario. This is in line with IS.AR.205 since the risk treatment phase is a consequence of the risk assessment phase and has to be address all the risks that have been evaluated. Point IS.AR.210(a) also stipulates that those (protection) measures shall not introduce any new potential unacceptable risks to aviation safety. This is an area that is not directly covered by either ISO/IEC 27001:2022 or ISO/IEC 27002. The requirement addresses the so-called ‘side effects’ when introducing measures into a system (a well-known issue in software development which is also very relevant for information security measures). Preventive or mitigative measures specifically (e.g. physical security, access control) could lead to unintended side effects. Also, the risk treatment of the identified risks should focus on addressing safety via the same linkage/integration of ISMS and safety management. IS.AR.210(b) Related ISO/IEC 27001:2022 clauses and controls 6.1.3.f Information security risk treatment 7.3 Awareness 9.3 Management review A5.19 Information security in supplier relationships A5.21 Managing information security in the ICT supply chain Part-IS particularity Point IS.AR.210(b) requires key personnel in the competent authority to be informed about the risks, the corresponding threat scenarios and the security risk treatment measures, which result in specific controls covered by Annex A to ISO/IEC 27001:2022 and ISO/IEC 27002. It partially covers point IS.AR.210(b) by the following requirement: obtain risk owners’ approval of the information security risk treatment plan and acceptance of the residual information security risks. Point IS.AR.210(b) has two specific requirements that also have equivalent requirements in ISO/IEC 27001:2022 and ISO/IEC 27002: — Inform the person referred to in point IS.AR.225(a) of the risk treatment plan — which is a mandatory input to the management review. — Inform the interfacing entities (the same as in point IS.AR.205(b)) of all risks shared with them — which is stated in A5.19 Guidance point l).

text: Annex to ED Decision 2025/015/R Page 28 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Guidance on Part-IS implementation In addition to the risk owner’s approval requested by ISO/IEC 27001:2022 6.1.3.f, the competent authority will need to inform: — the person referred to in point IS.AR.225(a) of the risk treatment plan. ISO/IEC 27001:2022 9.3. f) defines ‘results of risk assessment and status of risk treatment plan’ as mandatory input for the management review which is the vehicle to inform the person referred to in point IS.AR.225(a); — the interfacing entities (the same as in point IS.AR.205(b)) of all risks shared with them. ISO/IEC 27002 A5.21 states in point f) ‘defining rules for sharing of information and any potential issues and compromises between the organisations’. GM1 IS.AR.205(b) and ED-201A may also be used as guidance on risk sharing. IS.AR.215(a) Related ISO/IEC 27001:2022 clauses and controls A5.24 Information security incident management planning and preparation A5.25 Assessment and decision on information security events A5.26 Response to information security incidents A5.27 Learning from information security incidents A5.28 Collection of evidence A5.29 Information security during disruption A7.5 Physical security monitoring A8.16 Monitoring activities Part-IS particularity Fully covered by the requirements of A5.24 to A5.29, and A7.5 for physical security and A8.16 for technical monitoring. Guidance on Part-IS implementation The requirements of the controls (both reactive and proactive) mentioned above and the guidance in ISO/IEC 27002:2022 are comprehensive to fulfil the requirements of point IS.AR.215(a). Again, the impact on safety needs to be assessed, and measures shall be taken to ensure safety. Part-IS refers to ‘unsafe conditions’, which have to be mitigated to an acceptable level. A re-assessment of risks that are related to incidents that have occurred or to a vulnerability that has been identified is mandatory in Part- IS to ensure that no risk becomes unacceptable. Note: Due to historical reasons, information security and safety management use different wording when referring to situations which are more or less the same. The term ‘incident’ is used in a similar way (an event which already happened and infringes safety/security). A vulnerability in the sense of information security

text: Annex to ED Decision 2025/015/R Page 29 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement could be mapped to the term ‘hazard’ in the area of safety (a situation identified, which is possible to happen, but has not happened so far). IS.AR.215(b) Related ISO/IEC 27001:2022 clauses and controls A5.26 Response to information security incidents A5.29 Information security during disruption A7.5 Physical security monitoring A8.8 Management of technical vulnerabilities Part-IS particularity Fully covered by the requirements of A5.26 and A5.29. Guidance on Part-IS implementation The requirements of the control A5.26 and the guidance in ISO/IEC 27002:2022 are comprehensive to fulfil the requirements of point IS.AR.215(b). IS.AR.215(c) Related ISO/IEC 27001:2022 clauses and controls A5.26 Response to information security incidents A5.29 Information security during disruption Part-IS particularity This requirement is covered by the requirements of A5.26 and A5.29, with the difference that the recovery here is not intended to continuously ensure confidentiality, integrity, availability and integrity; instead, it is intended to maintain or return to an acceptable level of safety. Guidance on Part-IS implementation Coupled with the requirements of controls A5.26 and A5.28 and the guidance in ISO/IEC 27002:2022, AMC1.IS.AR.215(c) should be applied in order to revert as quickly as possible to a safe state. IS.AR.220 Related ISO/IEC 27001:2022 clauses and controls A5.19 Information security in supplier relationships A5.21 Managing information security in the information and communication technology (ICT) supply chain A5.22 Monitoring, review and change management of supplier services Part-IS particularity ISO/IEC 27001:2022 controls A5.19, A5.21 and A5.29 may cover this requirement. The difference in the requirements of point IS.AR.220 is that they are limited to those activities directly related to the ISMS (e. g. internal audits, consultancy for risk assessments, etc.).

text: Annex to ED Decision 2025/015/R Page 30 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Guidance on Part-IS implementation This requirement relates only to ISMS activities (e.g. internal audits, risk assessments), not to those activities not directly related to ISMS itself (e. g. hardware, software, IT and OT). The difference in the requirements of point IS.AR.220 is that they are limited to those activities directly related to the ISMS (e. g. internal audits, consultancy for risk assessments, etc.). The controls in ISO/IEC 27001:2022 do not exclude those kinds of services, but sometimes they will not be in the focus of the competent authority. Therefore, there is no need to establish an independent system for those contractors referred to in point IS.AR.220. The list of suppliers should be reviewed to ensure that the suppliers providing the services mentioned in point IS.AR.220 are covered. IS.AR.225(a) Related ISO/IEC 27001:2022 clauses and controls 5.1 Leadership and commitment 5.3 Organisational roles, responsibilities and authorities 7.1 Resources A5.2 Information security roles and responsibilities Part-IS particularity ISO/IEC 27001:2022 does not require a specific role. Guidance on Part-IS implementation The implementation of the requirements of point IS.AR.225(a) can be covered by the implementation of ISO/IEC 27001:2022 requirements mentioned above, provided that the role of the person referred to in point point IS.AR.225(a) is clearly defined and meets the requirements in point IS.AR.225(a). IS.AR.225(b) Related ISO/IEC 27001:2022 clauses and controls 7.1 Resources Part-IS particularity The requirements of 7.1 should be implemented. Guidance on Part-IS implementation A systematic capacity planning of human resources is a key element of any management system. Therefore, such a process should be established in an ISMS. The possible additional requirement stemming from Part-IS has to be assessed and the capacity planning updated accordingly. The targeted safety levels set in the safety/information security assessment should never be jeopardised by a lack of resources, even temporarily. AMC1 IS.AR.225(b) should be considered.

text: Annex to ED Decision 2025/015/R Page 31 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement IS.AR.225(c) Related ISO/IEC 27001:2022 clauses and controls 7.2 Competency A6.3 Information security awareness, education and training Part-IS particularity The implementation of the requirements of 7.2 and A6.3 is sufficient to cover the requirement. Guidance on Part-IS implementation A systematic competency management process of staff is a key element of any management system. Therefore, such a process should have been established in an ISMS. The possible additional requirement stemming from Part-IS has to be assessed and the competency requirements updated accordingly. AMC1 IS.AR.225(c) should be considered. IS.AR.225(d) Related ISO/IEC 27001:2022 clauses and controls A6.2 Terms and conditions of employment Part-IS particularity The implementation of the requirements of A6.2 with some adaptation would be sufficient to cover the provision of point IS.AR.225(d). Guidance on Part-IS implementation Point IS.AR.225(d) is (at least partially) covered by ISO/IEC 27001:2022 A.6.2 ‘The employment contractual agreements have to be state the personnel’s and the organisation’s responsibilities for information security.’ and A.6.4 ‘disciplinary process’ (see ‘Just Culture’). It depends on the organisational culture and on whether job descriptions or role assignments need to be formally acknowledged. In many cases, the assigned jobs and roles are mutually acknowledged by performing the tasks assigned. IS.AR.225(e) Related ISO/IEC 27001:2022 clauses and controls A5.19 Information security in supplier relationships A6.1 Screening A7.2 Physical entry A8.3 Information access restriction A8.5 Secure authentication Part-IS particularity The implementation of the requirements of A5.19, A6.1, A7.2, A8.3 and A8.5 might be sufficient controls to cover this requirement for the personnel of the competent authority, as well as for contractors and suppliers.

text: Annex to ED Decision 2025/015/R Page 32 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement Guidance on Part-IS implementation All the controls established in an ISO/IEC 27001:2022-compliant ISMS are designed to ensure the confidentiality and integrity of information. The implementation of those controls will provide sufficient protection to ensure compliance with this requirement. AMC1 IS.AR.225(e) should be considered. IS.AR.230(a) Related ISO/IEC 27001:2022 clauses and controls 7.5 Documented information A5.9 Inventory of information and other associated assets A5.13 Labelling of information A8.10 Information deletion A8.13 Information backup Part-IS particularity Record-keeping and retention are an inherent part of the document control system under 7.5 of ISO/IEC 27001:2022. The controls A5.9, A5.13, A8.10 and A8.13 also apply. Guidance on Part-IS implementation Chapter 7.5.1 b) states that the ISMS has to be include ‘documented information determined by the competent authority as being necessary for the effectiveness of the information security management system.’ This includes the records defined in point IS.AR.230(a)(1). Chapter 7.5.3 requires, under f), also document control for retention and disposition. Part-IS requirements have to be integrated into the existing system, especially the minimum duration of record-keeping of five years. The minimum set of records, as defined in point IS.AR.230(a)(1) should be covered in the inventory of assets. For the coverage, the content of GM1 IS.AR.230 also applies. As records are not only information assets, the requested ‘record retention policy’ may be integrated into a wider policy as recommended by ISO/IEC 27002:2022 above. AMC1 IS.AR.230(a)(1)(iv)&(a)(4) should be implemented. IS.AR.230(b) Related ISO/IEC 27001:2022 clauses and controls 7.5 Documented information A5.9 Inventory of information and other associated assets A5.10 Acceptable use of information and other associated assets A5.13 Labelling of information A5.34 Privacy and protection of personal identifiable information (PII) A8.10 Information deletion

text: Annex to ED Decision 2025/015/R Page 33 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement A8.13 Information backup Part-IS particularity Record-keeping and retention are an inherent part of the document control system under 7.5 of ISO/IEC 27001:2022. The controls A5.9, A5.13, A8.10 and A8.13 will also apply and, due to GDPR issues specifically, also A5.10 and A5.34. Guidance on Part-IS implementation Chapter 7.5.1 b) states that the ISMS has to be include ‘documented information determined by the competent authority as being necessary for the effectiveness of the information security management system.’ This includes the records defined in point IS.AR.230(a)(1). Chapter 7.5.3 requires, under f), also document control for retention and disposition. Part-IS requirements have to be integrated into the existing system, especially the minimum duration of record-keeping of five years. However, whereas there is no retention duration specified in ISO/IEC 27001:2022, point IS.AR.230(b) specifies three years after the person has left the competent authority. As these records fall under the GDPR Regulation, each competent authority has to ensure that they are handled accordingly. It is recommended that the procedures are used not only for records related to ISMS, but also for the entire HR personnel files of the staff. IS.AR.230(c) Related ISO/IEC 27001:2022 clauses and controls 7.5 Documented information A5.13 Labelling of information Part-IS particularity Record-keeping and retention are an inherent part of the document control system under 7.5 of ISO/IEC 27001:2022 as well as the control A5.13. Guidance on Part-IS implementation Chapter 7.5.3, under a), requires for the information that ‘it is available and suitable for use, where and when it is needed’. Part-IS requirements have to be integrated into the existing system. ISO 27002:2022 A5.13 states ‘Procedures for information labelling should cover information and other associated assets in all formats.’; therefore, the Part-IS requirement is fulfilled with control A5.13. IS.AR.230(d) Related ISO/IEC 27001:2022 clauses and controls 7.5 Documented information A5.10 Acceptable use of information and other associated assets A5.12 Classification of information A5.33 Protection of records

text: Annex to ED Decision 2025/015/R Page 34 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement A8.12 Data leakage prevention Part-IS particularity Record-keeping and retention are an inherent part of the document control system under 7.5 of ISO/IEC 27001:2022. The controls A5.10, A5.12, A5.33 and A8.12 will also apply. Guidance on Part-IS implementation Chapter 7.5.3, under d), requires ‘storage and preservation, including the preservation of legibility’. Part-IS requirements have to be integrated into the existing system. The application of A5.33 and A8.12 has a strong relationship to A7.5 (Protecting against physical and environmental threats), A7.10 (Storage media), A8.3 (Information access restriction), A8.13 (Information backup), A8.14 (Redundancy of information processing facilities), A8.15 (Logging), A8.17 (Clock synchronization) and A8.24 (Use of cryptography). IS.AR.235(a) Related ISO/IEC 27001:2022 clauses and controls 9.3 Management review 10.1 Continual improvement A5.35 Independent review of information security Part-IS particularity This requirement reflects a combination of requirements 9.3 and 10.1 of ISO/IEC 27001:2022 with references to requirements 4.4 and 5.2. While ISO/IEC 27001:2022 focuses on ISMS suitability, adequacy and effectiveness, point IS.AR.235(a) requires also a periodical maturity assessment of the ISMS. Guidance on Part-IS implementation ISO/IEC 27001:2022, 4.4 shows a clear requirement (‘shall’) for ISMS maintenance and improvement. The top management has a responsibility for continuous ISMS improvement as per ISO/IEC 27001:2022 5.2(d). The planning section also requires continuous improvement (ISO/IEC 27001:2022 6.1.1(c)). Point IS.AR.235(a) requires an assessment of the effectiveness and maturity of the ISMS on a calendar basis or following an information security incident. This assessment should be performed by using indicators. ISO/IEC 27001:2022 Chapter 9.3.1 defines a very similar approach for the management review process. Chapter 10.1 indicates a more independent process to improve the ISMS. The process in Chapter 10.1 is seen as more of a bottom-up approach, whereas that in Chapter 9.3 is intended to be top-down. The results from A5.35 should all be used as inputs for continuous improvement. Point IS.AR.235(a) requires also a maturity assessment of the ISMS. Each competent authority should establish which maturity model will be followed and which targeted maturity level is expected to be reached and by when.

text: Annex to ED Decision 2025/015/R Page 35 of 36

text: Part-IS ISO/IEC 27001:2022 mapping and specific guidance requirement For the maturity assessment, point (b) of AMC1 IS.AR.235(a) and GM1 IS.AR.235(a) provide guidance on how to ensure compliance with point IS.AR.235(a). IS.AR.235(b) Related ISO/IEC 27001:2022 clauses and controls 10.2 Non-conformity and corrective action A5.7 Threat intelligence Part-IS particularity Point IS.AR.235(b) addresses the improvement measures, i.e. corrections and corrective actions for the deficiencies detected in point IS.AR.235(a) and the continuous improvement process. This requirement reflects mainly requirement 10.2 of ISO/IEC 27001:2022, even if the term used is ‘non-conformity’, while point IS.AR.235(b) uses the term ‘deficiencies’. Deficiency has a broader meaning than non-conformity. It encompasses the case of a targeted maturity level that would not be reached at the planned date; that would be a deficiency but not necessarily a nonconformity. Guidance on Part-IS implementation The provisions listed in ISO/IEC 27001:2022 10.2 can be used to take corrective actions, to resolve both non-conformities and maturity level gaps.

text: Annex to ED Decision 2025/015/R Page 36 of 36