hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
142241be1ea90643e055df0a41f4debe | 119 540 | 5.7 Environmental and sustainability models of Smart Contracts | This topic, although essential, is not treated in the present document. 5.8 Underlying networks to support the deployment and execution of Smart Contracts As cited from eIDAS2 [i.2]: "(49) To ensure the proper functioning of European Digital Identity Wallets, European Digital Identity Wallet providers need effective interoperability and fair, reasonable and non-discriminatory conditions for the European Digital Identity Wallets to access specific hardware and software features of mobile devices. Those components could include, in particular, near field communication antennas and secure elements, including universal integrated circuit cards, embedded secure elements, microSD cards and Bluetooth Low Energy. Access to those components could be under the control of mobile network operators and equipment manufacturers. Therefore, where needed to provide the services of European Digital Identity Wallets, original equipment manufacturers of mobile devices or providers of electronic communication services should not refuse access to such components. In addition, the undertakings that are designated as gatekeepers for core platform services as listed by the Commission pursuant to Regulation (EU) 2022/1925 of the European Parliament and of the Council should remain subject to the specific provisions of that Regulation, building on Article 6(7) thereof". Though Smart Contracts can be provided as an overlay service on top of a network infrastructure, the elements as well as the whole underlying networks will need to be considered when deploying the services. As the article (49) of eIDAS2 requires, EUDIW should be treated equally when accessing the underlying networks. Particularly, components on mobile devices (e.g. NFC, SIM card and eSIM) should fully support functioning EUDIW; in addition, for accessing the Smart Contracts over the mobile devices should be supported and operated by the mobile networks. In sum, both mobile device manufacturers, component vendors (e.g. card vendors) and network equipment vendors should fully support EUDIW and Smart Contract services. The role of the underlying networks matters to the adoption of Smart Contracts. On the one hand, some nationwide/worldwide network infrastructures directly decide the accessibility and coverage of the deployed dAPPs offering reachability to EUDIW. Without the underlying networks' participation, especially nationwide mobile network infrastructure, the service range will be quite limited. On the other hand, underlying networks usually are usually built and operated by large operators (e.g. mobile network operators), thus a large number of subscribers are already gathered. Therefore, behind the underlying networks, the nature of the trusts from them plays a big role when offering dAPPs based on Electronic Ledger. As a result, underlying networks such as critical network infrastructures should stake their reputation to become a QTSP thus make the Smart Contracts highly trustworthy. 6 Synthetizing the Chain of Trust as a roadmap for ETSI TS 119 541 and ETSI TS 119 542 6.1 Essential Overview The present clause synthetizes all the issues raised by the Chain of Trust presented in Clause 5. Ideally, it passes the baton to technical specifications ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16] that will translate in formal requirements. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 45 Some remarks are in order to understand the next two ETSI Technical Specifications [i.12] and [i.16]: • They should specify whether there is the need for the mentioned specification to be certified or not, and in case yes, by whom and under which schema this certification should be carried out. • They should specify whether there is the need for the mentioned SC Compiler and SC Virtual Machine to be certified or not, and in case yes, by whom and under which schemas these certifications should be carried out. • They should specify the requirements for identification of the SC Compiler and the requirements for the seals on the SC Byte Code. • They should specify the requirements for identification of the mentioned entities and the requirements for the signatures on the Smart Contract and of the Electronic Ledger. • They should specify the requirements for identification of the Smart Contract caller and the requirements for this signed declaration. The present clause will proceed by collecting potential issues worth of study by the following categories: • Electronic identity issues. • Cybersecurity issues. • Privacy issues. • Governance issues. • Programming tools issues. • Legal issues. • Data sharing issues. • Centralized and decentralized execution issues. • Interoperability issues. • Network issues. • Open-source issues. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.2 Electronic identity issues | Based on the evaluation of electronic identity issues, a family of electronic identity schemes should be selected as standardized schemes for Smart Contracts. In addition, for those that could not fulfil the EU Regulations, clear guidance should be suggested for electronic identity scheme migration (especially for legacy information and communication technology systems). The Chain of Trust lies in a fundamental usage of electronic identity. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.3 Cybersecurity issues | Trust service providers for Electronic Ledgers and Smart Contracts are required to meet the requirements of the NIS2 Directive [i.11]. Moreover, ETSI EN 319 401 [i.13] defines general policy and requirements for the security of trust service providers aimed at meeting the requirements of NIS2 [i.11]. At the time of writing of the present document, hackers have maliciously substituted some Smart Contracts code with another (refers as the "Bybit hack 2025"): it is difficult to fully understand what happened and all involved actors. The Bybit hack 2025 would not be possible using entities and interactions as in Chain of Trust. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 46 |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.4 Privacy issues | Privacy is an important factor to be taken into account for identification applied to Smart Contracts, in particular with regards to identification of the contracting parties. eIDAS signatures and eIDAS2 wallets support a number of features which support privacy. eIDAS electronic signatures and seals allow for the use of pseudonyms when identifying a natural or legal person. This allows for the full identity of the person to be replaced with some other unique reference which does not directly identify the person. However, this still allows for a degree of traceability / linkability of a person's activity. eIDAS2 identities support a number of features which assure privacy. If particular, through use of selective disclosure of attributes (see ETSI TR 119 476 [i.10]) it is possible using EU Regulation on Digital Identity Wallets to reveal only selected attribute of the person without revealing their full identity. In considering the application of privacy measures, such as described above, the requirement that contracting parties cannot later deny in a court of law having agreed to the Smart Legal Contract based on Electronic Ledgers needs to be taken into account. Further security may be afforded through security measure applied to the Electronic Ledger (e.g. use of secure records held off-chain referenced from the ledger) may be used to ensure the privacy of identities recorded in an Electronic Ledger. Privacy issues are clearly described in the Chain of Trust. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.5 Governance and Audit issues | Governance and audit issues are fundamental in the Chain of Trust. Three areas of issues need to be taken into account in considering the governance of systems supporting Smart Contracts: 1) eIDAS2 [i.2] Requirements for Electronic Ledgers i) Under definition for Electronic Ledgers as specified in eIDAS2 [i.2] Article 3 (53) the integrity and the accuracy of their chronological ordering of electronic data records which form the ledger needs to be ensured. ii) Under eIDAS2 [i.2] Article 45i: Requirements for Qualified Electronic Ledgers they following specific requirements apply to Qualified Electronic Ledgers: a) they are created and managed by one or more Qualified Trust Service Provider (QTSP) or providers; b) they establish the origin of data records in the ledger; c) they ensure the unique sequential chronological ordering of data records in the ledger; d) they record data in such a way that any subsequent change to the data is immediately detectable, ensuring their integrity over time. iii) Under eIDAS2 each QTSP is required to be supervised and audited under eIDAS [i.2] Article 20 and 21 and Article 24.2 including the requirements of NIS 2 [i.11]. 2) Requirements for eIDAS2 Electronic Ledgers involving Multiple QTSPs - Where more than one QTSP is involved in the creation and management of an Electronic Ledger the overall trust service, as provided by a community of QTSPs, needs to meet the requirements i) and ii) above in a common way. In addition, each QTSP needs to meet the requirement of iii) above. 3) Requirements of Smart Contracts - The additional requirement of Smart Contracts, as specified in the definition given Data Act Article 2(39), in addition to use of an electric ledger, is "the computer program used for the automated execution of an agreement or part thereof". ETSI ETSI TR 119 540 V1.1.1 (2025-10) 47 - Firstly, the execution environment needs to be secure. If this is in a QTSP then this would be addressed by the general requirements of eIDAS2. Otherwise, similar NIS2 based controls can be used to ensure general security of the execution environment. If a cloud-based execution environment is used it might be sufficient to use a cloud environment certified under the EU Regulation on certification scheme. However, further analysis is required to ensure that any specific concerns for Smart Contracts are met the whichever approach is taken. - Secondly, the "computer program" used needs to be considered trustworthy. This aspect needs specific consideration, because is very generic. The main role of the governance regime is to assure the trustworthiness of Smart Contracts and the underlying system infrastructure. Governance of an individual QTSP is provided through the eIDAS2 [i.2] supervision and audit regime. Governance of a community of QTSPs providing an Electronic Ledger requires governance through a previsioning regime whereby not only the QTSPs are accepted under [i.2] supervision and audit regime, but also it is demonstrated that they apply a common Electronic Ledger policy for achieving the requirements of an eIDAS ledger in a collaborative manner. This permissioning regime requires a community governance permissioning system which issues its "trusted" information (e.g. trusted list) based on the results of an eIDAS audit including the audit against the requirements of the common Electronic Ledger policy. Assurance that a computer program used for the automated execution of an agreement or part thereof needs its own governance regime. It can use eIDAS signing certificates but also the CA/Browser Baseline Requirements for the Issuance and Management of Publicly Trusted Code Signing Certificates should be taken into account. Additional requirements need to be placed on the origin of the computer program to ensure that the code is developed in a trustworthy manner and allows the parties agreeing to a contract to understand the basis of the agreement. ISO, ETSI, CEN, and ITU-T X are quite active in governance issues concerning Smart Contracts, Electronic Ledgers, and distributed ledgers. Because of the rapid growth of use and development standards sometimes overlap, become obsolete, or have conflicts. At the time of publication of the present document, the text below reflects the status of affairs in governance and audit issues that are fundamental in the Chain of Trust. ETSI TC ESI provides general security controls aimed at meeting the requirements of Regulation (EU) 2024/1183 [i.2] TSPs including the requirements of NIS 2 [i.11]: • ETSI TS 119 541 [i.12] specifies the policy and security requirements for Smart Contracts using Electronic Ledgers as defined in eIDAS2 [i.2], and with other trustworthy tools, taking into account the framework of requirements identified in the present document. • ETSI TS 119 542 [i.16] specifies the use of EU Regulation on Digital Identity Wallets, and advanced or Qualified Electronic Signatures and Seals conforming to the requirements of eIDAS2 [i.2]. The Advanced or Qualified Electronic Signatures and Seals in the present document are implemented using digital signatures. • An audit of an individual QTSP that meets the specific requirements for Smart Contracts using Electronic Ledgers can be based on trust service policy and security requirements in line with the general audit and cyber security framework for trust services presented in ETSI EN 319 401 [i.13] and ETSI EN 319 403-1 [i.14]. ETSI GR PDL 017 [i.49] describes the features of a distributed ledger to be applicable as a Qualified Electronic Ledger and in support for eIDAS2 [i.2] trust services: it analyses the properties that a PDL can have to be an enabler for eIDAS regulation for electronic identification, authentication and signatures, and also for using eIDAS2 [i.2] in other areas of the Digital Economy. ETSI ISG PDL, at the time of publication of the present document, is merged in ETSI TC DATA. The ETSI TS 104 172 [i.23] will distill, among others, formal recommendations from ETSI GR PDL 017 [i.49] respecting compatibility and avoiding overlapping with ETSI TS 119 541 [i.12], ETSI TS 119 542 [i.16]. CEN JTC 19, at the time of the publication of the present document, is working on a specification for policy and security requirements for trust service providers providing Electronic Ledger services, following ETSI EN 319 401 [i.13] respecting compatibility and avoiding overlapping with ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. ISO provides principles on which a community governance regime may be based ISO/TS 23635 [i.15]. Recommendation ITU-T X.1403 [i.33] provides telecom-specific privacy and security considerations for using distributed ledgers data in identity management. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 48 |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.6 Programming tools issues | SC Language Specification Team, SC Compiler Team, SC Virtual Machine Team, SC Language Publisher, SC Compiler Publisher, SC Virtual Machine Publisher, should cooperate in the production of the SC Compiler and a SC Virtual Machine. SC Developer Team and SC Legal Team and SC Publisher should cooperate to write a Smart Legal Contract. The entity(ies) identified in the Smart Contract as either the entity originating the Smart Contract, or the entities that agree to be bound by the Smart Contract, should also sign it. The SC Byte Code, generated by the SC Compiler, should be sealed by the SC Language Publisher. In case that the caller is not one of the entities identified in the Smart Contract but another entity who accepts to be bound by its terms and conditions, there is the need of a signed declaration of acceptance of these terms and conditions of the mentioned Smart Contract. ETSI TS 119 542 [i.16] should specify the requirements for identification of the Smart Contract caller and the requirements for this signed declaration. Formal Verification: The SC Language Publisher, SC Compiler Publisher, and SC Virtual Machine Publisher may (at the highest level of security) include formal verification tools to ensure that Smart Contracts are mathematically proven to be correct, secure, and free from vulnerabilities: • SC Compiler and SC Virtual Machine Consistency: The Language Publisher, SC Compiler Publisher, and SC Virtual Machine Publisher should ensure that the SC Compiler translates code consistently and accurately across different environments, with no discrepancies in the generated SC Byte Code. They should ensure that the SC Virtual Machine execute SC Byte Code consistently and accurately, even across different environments, with no discrepancies. • Automated Testing: The Language Publisher, SC Compiler Publisher, and SC Virtual Machine Publisher should support automated testing frameworks that can run unit tests, integration tests, and stress tests to validate the behavior of the Smart Contract. • Error Reporting: The Language Publisher, SC Compiler Publisher, and SC Virtual Machine Publisher should provide detailed error reporting and debugging tools to identify and resolve issues during the development process. • Security Audits: The Language Publisher, SC Compiler Publisher, and SC Virtual Machine Publisher should integrate security auditing tools that can analyse Smart Contracts for common vulnerabilities like reentrancy, overflow, and underflow. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.7 (Smart) legal issues | • Legal Compliance: The SC Publisher should ensure that Smart Contracts comply with relevant legal frameworks and can be validated against legal standards. • Contract-to-Code Translation: The SC Publisher should provide mechanisms to accurately translate Legal Contracts into executable Smart Legal Contracts, ensuring that all legal terms are faithfully represented in the SC Byte Code. • Audit: The SC Publisher should maintain an immutable audit that documents every change made to the Smart Contract, ensuring transparency and traceability. • Reverse Engineering: The SC Publisher should allow for the extraction of legal documents from Smart Contracts to ensure they can be reviewed and understood in legal contexts. • Dispute Resolution Integration: The SC Publisher should include tools for integrating dispute resolution mechanisms within Smart Contracts to handle legal disputes automatically or semi-automatically. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.8 Data sharing issues | • Data Privacy: The (Qualified) Electronic Ledger should ensure that all shared data is encrypted and access- controlled to protect sensitive information from unauthorized access. • Data Integrity: The (Qualified) Electronic Ledger should implement mechanisms to verify that data has not been tampered with during transmission or storage. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 49 • Interoperability: The (Qualified) Electronic Ledger should support standard data formats and protocols to enable seamless sharing of data across different systems and platforms. • Scalability: The (Qualified) Electronic Ledger should be able to handle large volumes of data efficiently without compromising performance. • Compliance: The (Qualified) Electronic Ledger should ensure that data sharing practices comply with relevant regulations, such as GDPR [i.7], to protect user privacy and rights. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.9 Decentralized execution issues | • Performance: The SC Publisher and the (Qualified) Electronic Ledger should execute efficiently, with minimal latency and resource consumption to ensure smooth operation across the network. • Reliability: The SC Publisher and the (Qualified) Electronic Ledger should ensure that Smart Contracts execute reliably under all conditions, including network congestion or high transaction volumes. • Scalability: The SC Publisher and the (Qualified) Electronic Ledger should support scaling, allowing Smart Contracts to handle increased loads without degrading performance. • Fail-Safe Mechanisms: The SC Publisher and the (Qualified) Electronic Ledger should include fail-safe mechanisms to gracefully handle execution failures, should ensure that contracts can recover or roll back in case of errors. • Auditability: The SC Publisher and the (Qualified) Electronic Ledger should provide tools to audit the execution of Smart Contracts, should ensure that every action taken by the contract can be traced and verified. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.10 Interoperability issues | • Cross-Platform Compatibility: The (Qualified) Electronic Ledger should ensure that Smart Contracts can interact with other blockchains or systems, using standardized protocols and interfaces. • Data Standardization: The (Qualified) Electronic Ledger should use standardized data formats to ensure that information can be shared and understood across different platforms. • Protocol Support: The (Qualified) Electronic Ledger should support multiple communication protocols to enable interoperability between various networks and external systems. • API Integration: The (Qualified) Electronic Ledger should provide robust APIs that allow external systems to interact with Smart Contracts, facilitating integration with other services and platforms. • Security: The (Qualified) Electronic Ledger should ensure that interoperability does not compromise the security of the Smart Contracts or the connected systems. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.11 Networks issues | • Pervasiveness: The network should support the users to access to the Smart Contracts with high availability and ubiquity (e.g. across urban and rural areas, fixed or mobile coverage). • Reliability: The network should support the users to access to the Smart Contracts with high service continuity (e.g. the reliable connectivity either wired or wireless). • Trustworthiness endorsement: The networks should contribute to maintain the high trustworthiness of the provided Smart Contract. • Security: The network should ensure security from attacks, including distributed denial of service, sybil, and other common network-based threats. • Decentralization: The network should be sufficiently decentralized to prevent any single entity from gaining control over the system. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 50 • Scalability: The network should support scalability to handle a growing number of nodes and transactions without performance degradation. • Redundancy: The network should implement redundancy and fault-tolerant mechanisms to ensure network reliability even if some nodes fail. • Low Latency: The network should offer low-latency communication to ensure timely execution of Smart Contracts and transactions. |
142241be1ea90643e055df0a41f4debe | 119 540 | 6.12 Open-source vs. Closed-source issues | Open-source may be a model to assess code during the software construction and maintenance: in this model Governance is distributed with a (un)limited number of participants (for example: Linux kernel™, GNU C-compiler). Open-source is also used by Governments as an extra non legal service to official services. As an example, the Etalab initiative of the French government. Closed-source model may be also a possible model to assess code, but it should be assessed ex ante, using possibly Governance(s) that fund the software construction and validation. |
142241be1ea90643e055df0a41f4debe | 119 540 | 7 Conclusions | The Chain of Trust V1, at the time of the publication of the present document, represent a first attempt to list a sufficient set of interactions between entities, results produced, identification and assurance needs. A precise interaction between two or more entities is shown. The Chain of Trust V1 is translated in formal requirements in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 51 Annex A: An example of the Chain of Trust A.1 Essential Overview This annex provides an explanatory example of the processes involved in designing, assigning a legal value, deploying and executing a Smart Legal Contract in an Electronic Ledger. The example is presented by means of four figures. The particular case of a deployment and execution of a Smart Legal Contract on a distributed ledger as defined in ISO 22739 [i.3] solution is presented. The figures identify all the relevant actors, artifacts, hardware, networks and tools, emphasizing the critical points where security and identity issues are paramount. This description is described by means of the Chain of Trust introduced in Clause 5, considering all involved entities and their relations. The Chain of Trust occurs at many abstraction levels: in the particular case of a distributed environment, extra difficulties arise. The security of deploying and executing Smart Legal Contracts can be significantly compromised by an incomplete validation chain, which exposes users to various risks, including fraud and attacks. Summarizing, the entities involved in the Chain of Trust in a distributed setting are defined in Clause 3.1 and described in Clause 5. A.2 Figures as an example of the Chain of Trust Figure A.1, Figure A.2, Figure A.3 and Figure A.4 present the "fine-grained" implementation of the Chain of Trust as suggested in Table 1, instantiated to distributed ledgers as defined in ISO 22739 [i.3]: entities, their relations participating in the production, deployment, and execution of Smart Legal Contracts and the design of the SC Languages are represented. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 52 Figure A.1: Chain of Trust: SC Language design ETSI ETSI TR 119 540 V1.1.1 (2025-10) 53 Figure A.2: Chain of Trust: Smart Legal Contract design ETSI ETSI TR 119 540 V1.1.1 (2025-10) 54 Figure A.3: Chain of Trust: Smart Contract deployment on a distributed ledger ETSI ETSI TR 119 540 V1.1.1 (2025-10) 55 Figure A.4: Chain of Trust: Smart Contract execution on a distributed ledger ETSI ETSI TR 119 540 V1.1.1 (2025-10) 56 Annex B: Chain of Trust: Architectural Elements (schematic) Figure B.1 ETSI ETSI TR 119 540 V1.1.1 (2025-10) 57 Annex C: Comparative overview of definitions Legal definitions are technology-neutral and designed to support regulatory enforceability. ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16] rely on the legal definitions to address legal compliance, and when it is the case, can reference ETSI or other standard definitions for implementation guidance. Table C.1: Legal Definitions Term Source Definition Comment Smart Contract Regulation (EU) 2023/2854 [i.1], Article 2(39) (Data Act) "A computer program used for the automated execution of an agreement or part thereof, using a sequence of electronic data records and ensuring their integrity and the accuracy of their chronological ordering." Legal basis under the Data Act EU Law [i.1]. Smart Contract as per [i.1], are referred as SC Byte Code in the present document. The definition of Smart Contract in [i.1] and in the present document is more general than the definition of smart contract in ISO 22739 [i.3]. Electronic Ledger Regulation (EU) 2024/1183 [i.2], Article 3(52) (eIDAS2) "Electronic ledgers are a sequence of electronic data records which should ensure their integrity and the accuracy of their chronological ordering. Electronic ledgers should establish a chronological sequence of data records […] The process of creating and updating an electronic ledger depends on the type of ledger used, namely whether it is centralized or distributed. This Regulation should ensure technological neutrality, namely neither favoring, nor discriminating against, any technology used to implement the new trust service for electronic ledgers […]" Legal basis under eIDAS2 EU Law [i.2]. Because an Electronic Ledger can be centralized or distributed, the definition of Electronic Ledger in [i.2] and in the present document is more general than a distributed ledger in ISO 22739 [i.3]. Table C.2: Technical Definitions Term Source Definition Comment smart contract ISO 22739[i.3] Computer program stored in a distributed ledger technology (DLT) system wherein the outcome of any execution of the program is recorded on the distributed ledger DLT-specific; may not align with legally neutral approach. Because of the specificity of the input of the computer program to be defined only with a DLT, the definition of the output of the computer program can be undefined in case of centralized Electronic Ledgers. The definition of Smart Contract in [i.1] diverges with the definition of smart contract in ISO 22739 [i.3]. distributed ledger ISO 22739 [i.3] Ledger that is shared across a set of distributed ledger technology (DLT) nodes and synchronized between the DLT nodes using a consensus mechanism Contrasts with broader legal definition of "Electronic Ledger". Because an Electronic Ledger can be centralized or distributed, the definition of Electronic Ledger in [i.2] is more general definition that a distributed ledger in ISO 22739 [i.3]. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 58 Annex D: Change history Date Version Information about changes February 2024 0.0.1a Bootstrapping of the present document and few Editor annotations in RED (Inria) March 2024 0.0.1b Some Sections names proposals and more editor annotations in RED taken from the STF 655 contract (Inria) 23 April 2024 0.0.1c Fix TR name according to the STF 655 contract. Discuss the first ToC V0 (Inria) and modify to ToC V1 (Inria, INFOCERT, UPC, Observatorium, Nokia) 30 April 2024 0.0.1d Improve ToC according to the STF 655 contract, by Inria, INFOCERT and Nokia 30 April 2024 0.0.1e Formatting (Inria) 7 Mai 2024 0.0.1f Set up Clauses 1, 2, 3, References, Introduction. Simplifying and clustering ToC (Inria, Huawei, INFOCERT). Adding Editor annotations in RED 21 Mai 2024 0.0.1g Refactoring of all Clauses keeping the contents (Inria, SSA, UPC, INFOCERT, Observatorium, Huawei). Adding Editor annotations in RED 28 Mai 2024 0.0.1h Last review of all Clauses (SSA, Inria, InfoCert, CCC, Huawei). Adding Editor annotations in RED 11 Juin 2024 0.0.1i Adding Editor annotations on Clauses 5 and 6 (SSA, UPC, Inria, Huawei) in RED 11 September 2024 0.0.1l Including all Experts contributions, with a minimal formatting (Inria) 3 October 2024 0.0.1m Expanding and including all Experts contributions, with formatting (Inria) 7 October 2024 0.0.2a Clause 4 and clause 5 stabilized (Inria, UPC, INFOCERT) 17 October 2024 0.0.2b Clause 5 moved to Clause 3 (Terms), including discussions on terms, rearranging Clause 5 (formerly 6), and Claude 6 (formerly 7), and inclusion all Huawei and Inria contributions (Inria) 17 October 2024 0.0.2c Inclusions of all comments of the last meeting and few sanity checks (Inria) 17 October 2024 0.0.2c Added bibliography and better Table 1 fitting Chain of Trust figures (Inria, SSA) 17 October 2024 0.0.2d Drawing Chain of Trust figures, harmonizing Clause 4 (Inria) 22 October 2024 0.0.2d Harmonizing Clause 5 and 6 (Inria) 30 October 2024 0.0.2d Final pass (Inria) 20 November 2024 0.0.2e NEW HANDY TABLE (See CR Meeting 19 November Inria) 3 December 2024 0.0.2f Actual status of the Table 1 as per SSA/INFOCERT/Inria is Installed in Clause 5.1, Terms are installed in Clause 3.1, Clause 5.10 is deleted, and Figures are now in Appendix. Prose in Clause 5 is unstable 20 December 2024 0.0.3a The Inria inspired and tuned by SSA and INFOCERT "Chain of Trust", agreed by ALL in the last two weekly meeting (3/12 and 10/12) is installed in Clause 5.2. A NEW Clause 3.1 (Terms) according to Table 5.2 is installed in RED. The Chain of Trust and its Terminology will be synchronized in the TS x541 and TS x542 7 January 2025 0.0.3b Fixing Clause 3.1 (Terms) respecting UE terminology, and taking into account SSA and JTC19 comments (Inria) 14 January 2025 0.0.3c Clause 4 (INFOCERT and Inria) 21 January 2025 0.0.3d Merging and implementing dispositions (Inria) 23-25 January 2025 0.0.3e Alignment with SSA and JTC19 on Terminology and on the "Chain of Trust" (Inria) 31 January 2025 0.0.4a General improvements according to ETSI rules (Inria) 3 February 2025 0.0.5a General last-minute improvements (Inria) 3 February 2025 0.0.6a General last-minute improvements (ETSI) April 2025 0.0.7a Implementation of dispositions of comments for v0.0.6 producing a major new version (Inria) April 2025 0.0.7b Implementation of ETSI suggestions (ETSI) May 2025 0.0.7c Implementation of disposition of comments (Inria) Juin 2025 0.0.8a Various alignments with x541 and x542 and implementation of ETSI suggestions July 2025 0.0.8b Various alignments with x541 and x542 and implementation of C3L July 2025 0.0.8c Various alignments with x541 and x542 and implementation of C3L & UPC suggestions during the 10/07/25 meeting September 2025 0.0.9a Wrapping up and final tuning (Inria) September 2025 0.0.9b UPC last comment resolution (Inria) September 2025 0.0.10a Implementation of ETSI suggestions September 2025 0.0.11a Implementation of ETSI suggestions September 2025 0.0.12a Implementation of ETSI suggestions ETSI ETSI TR 119 540 V1.1.1 (2025-10) 59 History Document history V1.1.1 October 2025 Publication |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 1 Scope | The present document supports the preparation of the answer to C(2025)4135 - Standardisation Request M/614 [i.3] further on called "SReq" in the present document. The present document is based on the input from ETSI TR 104 409 [i.1]. Both reports (the present document and ETSI TR 104 409 [i.1]) will prepare the normative work to satisfy the SReq [i.3]. The present document is structured as follows: • Clauses 1 to 3 set the scene and provide references as well as definitions of terms, symbols and abbreviations, which are used in the present document. • Clause 4 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how oneM2M fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It presents guidelines about how oneM2M can be used to fulfil as much as possible the standardization requirements of these two documents without the need for changes to oneM2M specifications. Additionally, this clause lists potential Change Requests (CRs) that would enable oneM2M to fulfil some of the aspects of these two documents (i.e. ETSI TR 104 409 [i.1] and the present document) that are currently not covered. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make oneM2M compliant with the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. Some requirements of the two documents fall outside the scope of oneM2M specifications. Where possible, this clause provides clarification of such boundaries together with additional guidelines that may help define a clear positioning for oneM2M in the context of the two documents. • Clause 5 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how SAREF fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It lists feasible improvements that would enable SAREF [i.4] to fulfil the standardization requirements of these two documents. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make SAREF compliant with the two documents. Clause 5 provides possible additional guidelines for aligning SAREF with the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. • Clause 6 provides a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how NGSI-LD fulfils the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. It provides guidelines about how NGSI-LD can be used to fulfil as much as possible the two documents without carrying out changes within the NGSI-LD methodology. Clause 6 lists feasible improvements that would enable NGSI-LD to fulfil the standardization requirements of these two documents. The content focuses on improvements that can be implemented in a reasonable manner according with the timing available to make NGSI-LD compliant with the EU Data Act [i.2] with particular reference to Article 33 and the EU Standardisation Request, e.g. the definition of the mappings between NGSI-LD and DCAT-AP provided in [i.7]. • Clause 7 provides insights about if the union of the three assets enables the fulfilment of the EU Data Act [i.2] with particular reference to Article 33 and the SReq [i.3]. • Clause 8 provides a summary of conclusions from the standardization suggestions. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 2 References | |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 2.1 Normative references | Normative references are not applicable in the present document. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 7 |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ETSI TR 104 409: "Data Solutions (DATA); Data Act (art. 33) requirement and references analysis". [i.2] Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act). [i.3] C(2025)4135 – Standardisation request M/614: "Commission Implementing Decision of 1.7.2025 on a standardisation request to the European standardisation organisations as regards a European Trusted Data Framework in support of Regulation (EU) 2023/2854 of the European Parliament and of the Council". [i.4] ETSI SAREF portal. [i.5] ETSI EN 303 760: "SmartM2M; SAREF Guidelines for IoT Semantic Interoperability; Develop, apply and evolve Smart Applications ontologies". [i.6] ETSI GS CIM 006: "Context Information Management (CIM); NGSI-LD Information Model". [i.7] ETSI GR CIM 048: "Context Information Management (CIM); Handling of data catalogues and data services with NGSI-LD". [i.8] DCAT-AP 3.0.1 profile. [i.9] ETSI TS 104 414: "Data Solutions (DATA); Ontology Web Server - Functional Interfaces and Architectural Specification". [i.10] ETSI TS 104 415: "Data Solutions (DATA); IoT Ontology Web Server - User Interfaces and Use Cases". [i.11] ETSI TR 104 416: "Data Solutions (DATA); IoT Ontology Web Server - Security, Deployment, and Support". |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 3 Definition of terms, symbols and abbreviations | |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 3.1 Terms | For the purposes of the present document, the following terms apply: ACME CSE: open source CSE Middleware for Education connected product: item that obtains, generates or collects data concerning its use or environment and that is able to communicate product data via an electronic communications service, physical connection or on-device access, and whose primary function is not the storing, processing or transmission of data on behalf of any party other than the user data holder: natural or legal person that has the right or obligation, in accordance with the EU Data Act [i.2], applicable Union law or national legislation adopted in accordance with Union law, to use and make available data, including, where contractually agreed, product data or related service data which it has retrieved or generated during the provision of a related service ETSI ETSI TR 104 410 V1.1.1 (2025-10) 8 data processing service: digital service that is provided to a customer and that enables ubiquitous and on-demand network access to a shared pool of configurable, scalable and elastic computing resources of a centralized, distributed or highly distributed nature that can be rapidly provisioned and released with minimal management effort or service provider interaction data recipient: natural or legal person, acting for purposes which are related to that person's trade, business, craft or profession, other than the user of a connected product or related service, to whom the data holder makes data available, including a third party following a request by the user to the data holder or in accordance with a legal obligation under Union law or national legislation adopted in accordance with Union law EU Data Act: Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 on harmonised rules on fair access to and use of data and amending Regulation (EU) 2017/2394 and Directive (EU) 2020/1828 (Data Act) [i.2] GeoDCAT-AP: extension of DCAT-AP for the representation of geographic metadata public sector body: national, regional or local authorities of the Member States and bodies governed by public law of the Member States, or associations formed by one or more such authorities or one or more such bodies smart contract: computer program used for the automated execution of an agreement or part thereof, using a sequence of electronic data records and ensuring their integrity and the accuracy of their chronological ordering SReq: Standardisation Request to the European Committee for Standardization (CEN), the European Committee for Electrotechnical Standardization (CENELEC) and the European Telecommunications Standards Institute (ETSI) as regards to a European Trusted Data Framework [i.3] |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 3.2 Symbols | Void. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface CEN European Committee for Standardization CENELEC European Committee for Electrotechnical Standardization CR Change Request DCAT Data CATalogue vocabulary DCAT-AP Data CATalogue vocabulary Application Profile DSSC Data Spaces Support Centre ETSI European Telecommunications Standards Institute EU European Union GDPR General Data Protection Regulation HTTP HyperText Transfer Protocol IoT Internet of Things JSON JavaScript Object Notation KPI Key Performance Indicator LLM Large Language Model MCP Model Context Protocol MQTT Message Queuing Telemetry Transport NGSI-LD Next Generation Service Interface-Linked Data RDF Resource Description Framework SAREF Smart Applications REFerence ontology SReq Standardisation Request TR Technical Report W3C® World Wide Web Consortium Web World Wide Web ETSI ETSI TR 104 410 V1.1.1 (2025-10) 9 |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 4 oneM2M | |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 4.1 Introduction | The present clause gives a summary of the findings highlighted in ETSI TR 104 409 [i.1] about how oneM2M fulfils the EU Data Act [i.2] with particular reference to Article 33 and the EU Standardisation Request [i.3]. The summary guides the content of the remaining sub-clauses. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 4.2 Use as it is to fulfil the EU Data Act and the SReq | oneM2M as it is does satisfy a substantial part of the SReq [i.3], especially in the following areas: • General Framework and Architecture: - oneM2M provides a comprehensive interoperability framework designed for seamless communication across various protocols and data models. - It supports a service layer that can be integrated into diverse hardware and software systems (this includes also access to devices, thanks to its legacy from IoT domain). • Terminology, Concepts, and Mechanisms: - oneM2M specifications clearly define: Terminology (e.g. "Application Entity," "Common Services Entity"). Architectural concepts (e.g. hierarchical resource structure). Mechanisms for data sharing, access control, and interoperability. oneM2M supports data sharing by design. API queries are supported, both simple ones and semantic based, also in distributed contexts. oneM2M by design supports distributed architectures. Thanks to its legacy as an IoT Platform, access to devices is native. • Interoperability Requirements: - Data sharing & API access: Fully specifies protocols (HTTP, MQTT, etc.) and RESTful APIs for automatic data transmission. - oneM2M specifies interoperability mechanisms allowing data exchange with other oneM2M instances and non-oneM2M systems while preserving data security and access rights. - It supports API queries, both simple and semantic based, even in distributed contexts. - Distributed architectures: native support for IoT devices and cross-platform data exchange. • Implementation Framework for Semantic Assets: - has good support for semantics, including storage, management, and discovery of ontologies, (e.g. SAREF, and custom ones). - Machine-readable data: Resources are represented in JSON, enabling semantic annotation. - It offers capabilities to discover resources based on semantic descriptions and content. • Trustworthiness Requirements: - oneM2M provides advanced granular access control incorporating roles, tokens, identity verification, time-based restrictions, and location-based conditions. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 10 - It specifies sophisticated access control policies able to handle demanding scenarios. - Consent management support is available, considering GDPR and similar regulations in other parts of the world. - Data integrity: Versioning ("container instances") tracks changes. - License management: Explicitly specified for data sharing. As such, oneM2M can contribute to provide a solid framework for the implementation of "services" in the sense of the DSSC Blueprint, especially in the context of Technical Building Blocks. The Blueprint takes the stance that services can vary widely among Data Spaces, especially since specialized protocols may be in use according to individual vertical application. For that reason, the Blueprint cites examples but does not endorse one specific solution. oneM2M follows a different approach, i.e. that it assumes that most of the use cases can be tackled by using a single framework. Even in the cases where consolidated protocols/data layout are well established for a given vertical industry, a clear path for dealing with that (via the use of Application Entities) is outlined. This way, the effort needed to adapt to a new vertical is reduced to a minimum and clearly confined to easily identified sections of the software implementing the platform. Application Entities exchange data and information with the oneM2M core via messages, following to APIs that are well specified. This approach makes the code implementing the Application Entity to be disjoint from that of the oneM2M core: in this way, existing libraries for the existing/consolidated use cases can be leveraged, and there are no constraints regarding the programming language used. This is by design, with the intention of reusing as much as possible, avoiding reinventing the wheel each time. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 4.3 Potential improvements | There are areas where oneM2M allows some room for potential improvements (work may be already being done to address some of said improvements): • Master Catalogue: - oneM2M does not provide a single master catalogue for listing available data. Considering the potential dimensions and the tremendous diversity of services, applications and of the related data sets, oneM2M provides advanced functionality to discover applications and related data, so that data catalogues can be easily built as oneM2M services. - Another work item, recently approved, calls for studying and specifying the interworking between oneM2M and Model Context Protocol (MCP). - This provides an alternative approach, in line with modern developments in LLMs and Agentic AI. There will be challenges as well, most notably about balancing the (typically greedy) access by AI against the granularity of access control allowed by the oneM2M specifications. • Data collection methodology, data quality, and uncertainty: - The oneM2M specifications only guarantee correct handling and transfer of data items between digital entities. - It is implicitly assumed that assessment of data quality is left either to human actors (who can have knowledge of the quality of data and related collection methodology) or to automated tools (that can, e.g. assess quality related information according to given KPIs). - A possible improvement, that can be considered by the oneM2M community, is to define a standardized way to convey information about quality of a given data item to participants of the Data Space. - Similar considerations might apply also to concepts like KPIs or reporting structure for Data Space maturity. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 11 • Auditability of data transactions: - oneM2M provides users with a mechanism for data versioning (so called "content instances" in oneM2M jargon of any resource are kept available and can be accessed by users, subject to access control policies). - A possible improvement to this scheme is to standardize the recording of aspects of the actors that caused such changes to occur. In this way it becomes possible to ensure full accountability of the actors that operate on a given Data Space. Such a feature could be graduated according to the required degree of accountability, from none to who caused data changes up to who just accessed any resource for the most demanding cases. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 4.4 Additional guidelines | Clauses 6.1.1 and 6.1.2 of ETSI TR 104 409 [i.1] explain that oneM2M is more that the specification of an IoT platform, stating it is well suited to support Data Spaces. These capabilities, however, are not currently advertised on the oneM2M.org website. A possible improvement is to augment the website content to reflect these considerations. oneM2M specifications are technical in nature and describe APIs, mechanisms for managing information, etc. There are guidelines and best practices for implementation and usage of the specifications but, currently, they are oriented towards technical users. To better meet some of the requirements from the SReq [i.3], additional guidelines can be provided, articulated in practical, non-legal language that is accessible to all potential stakeholders. Such additional guidelines should cover not only the way oneM2M compliant frameworks can be implemented/deployed, but also explaining how oneM2M features map to requirements of the SReq [i.3], including coverage of the way to meet domain-specific (non-regulatory) requirements |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 5 SAREF | |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 5.1 Introduction | ETSI TR 104 409 [i.1] provides an analysis about how the SAREF methodology fulfils the EU Data Act [i.2], with particular reference to the Article 33 and the EU Standardisation Request [i.3]. There have been two main aspects making SAREF well positioned compared to the EU Data Act [i.2]. The first one is that the SAREF methodology is mentioned within the SReq [i.3] as a virtuous example of support to achieve data interoperability. This point paves the way to adopting the SAREF methodology to build data repositories and to making them compliant with the SReq [i.3]. The second one concerns the structure of the SAREF methodology, i.e. a set of Technical Specifications containing the description of each element and examples of concrete specifications. Their quality enables independent developers to develop conformant implementations. As part of the specifications, terminology, concepts and mechanisms used are clearly specified. Clause 5.2 provides a description about the impact of the SAREF methodology, concerning its current level of compliance with the EU Data Act [i.2], if it is used as it is. Instead, clause 5.3 describes a set of action that should be put in place to enhance the compliance level of the SAREF methodology to make it fully compliant with the EU Data Act [i.2] and EU SReq [i.3]. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 5.2 Use of SAREF to fulfil the EU Data Act and the SReq | The content of the present clause refers to the version of SAREF published at the date in which the present document is written. Any subsequent updates of SAREF may affect the validity of the content provided below. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 12 The SAREF methodology is described in ETSI EN 303 760 [i.5] where there are provided the good practices about how the SAREF methodology can be used to grant semantic interoperability for IoT smart applications in a set of high-level outcome-focused provisions. Through the methodology described within ETSI EN 303 760 [i.5], it is possible to support all parties involved in the development and manufacturing of IoT smart applications and products with guidance on making them interoperable in compliance to the SAREF framework. The provisions give organizations and companies the flexibility to innovate and implement SAREF-compliant semantic interoperability solutions appropriate for their products and applications. Indeed, through the adoption of the described methodology, the datasets produced meets completely the following aspects of the SReq [i.3]: • Paragraph 1 (c) of the EU Data Act [i.2], Article 33; • Harmonised standards on Trusted Data Transactions - Part 1: Terminology, concepts and mechanisms; • Harmonised standards on Trusted Data Transactions - Part 2: Trustworthiness requirements; • Technical specification(s) on an implementation framework for semantic assets; • European standard on a quality framework for internal data governance; and partially: • Paragraph 1 (a) of the EU Data Act [i.2], Article 33; • Harmonised standards on Trusted Data Transactions - Part 3: Interoperability requirements. In particular, the SAREF methodology is fully compliant with the accessibility requirement. This enables the creation of datasets that, in turn, will be all compliant with the SReq [i.3]. Indeed, by adopting the SAREF methodology, datasets can be published by using the RDF Turtle language, a machine-readable format recommended by the W3C®. This way, it is possible to understand the structure of the datasets built by using the SAREF methodology in a clear manner. The usage of the SAREF methodology in its current version leaves open some gaps before fulfilling completing the SReq [i.3]. Clause 5.3 provides a list of possible actions to improve the SAREF methodology. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 5.3 Potential improvements | The present clause provides a set of actions that should be considered to improve the SAREF methodology, and a mention to possible assets that would make the SAREF ecosystem fully compliant with the EU Data Act [i.2] and the SReq [i.3]. Particularly, three feasible actions can be implemented to enhance the fulfilment of SReq [i.3]. The SReq [i.3] explicitly requires reliance on existing communities and well-established specifications, in particular DCAT-AP and some extensions. Therefore, DCAT-AP is intended to serve as the baseline methodology for dataset and catalogue metadata, while SAREF can provide domain-specific semantics enriching DCAT-AP descriptions. First, the SAREF methodology ensures the management of metadata catalogues describing the resource. The vocabulary recommended by the EU SReq is DCAT-AP [i.8] and some existing extensions. Through DCAT-AP, it is possible to generate a DCAT-AP extension or mapping for each dataset built by using the SAREF methodology. This new application profile allows to provide metadata describing such datasets to make them compliant with the SReq [i.3]. Indeed, currently, datasets built by using the SAREF methodology are, on the one hand, equipped with some descriptors coming from the RDF language. But, on the other hand, each dataset is not associated with a datasheet providing all the necessary information required by the SReq [i.3] (e.g. data quality descriptors). To satisfy this requirement, it is necessary to integrate the management of DCAT-AP extensions into the SAREF methodology. This way, the data structures, data formats, vocabularies, classification schemes, taxonomies and code lists, will be described in a publicly available and consistent manner with other Data Spaces to allowing the publication of SAREF-based datasets within the Common European Data Spaces catalogue and ensuring cross-domain interoperability. Second, to provide a SAREF-based query endpoint. The ontologies instantiating the SAREF methodology are available for download through the dedicated portal. However, it is still missing an endpoint to query datasets built by using the SAREF methodology (i.e. instantiating the SAREF ontologies) with the aim of extracting knowledge about their structures and contents. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 13 Third, to implement and deploy a SAREF-compliant web server. The SAREF ecosystem comes with a collection of synthetic examples showing how the ontologies instantiating the SAREF methodology can be used. However, the type of scenarios specified in the SReq [i.3] is not addressed since, currently, the SAREF methodology does not include an accompanying web server enabling the mentioned type of access. Currently, even SAREF is available for download through its website, it is not equipped with a facility allowing the access to the structured data produced by using SAREF. This issue is going to be addressed through the adoption of the ETSI IoT Ontology Web Server [i.9], [i.10], [i.11]. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 6 NGSI-LD | |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 6.1 Introduction | ETSI TR 104 409 [i.1] provides an analysis about which components of NGSI-LD fulfils the EU Data Act [i.2], with particular reference to the Article 33 and the EU Standardisation Request [i.3]. NGSI-LD [i.6] is information model and API for publishing, querying and subscribing to context information. It enables structured information sharing across multiple domains like smart cities, smart industries, and digital twins. The NGSI-LD information model represents Context Information as entities that have properties and relationships to other entities. It is derived from property graphs, with semantics formally defined on the basis of RDF and the semantic web framework. There have been two main aspects making NGSI-LD aligned to the EU Data Act [i.2]. The first one is that with NGSI-LD it is possible to describes both data points and datasets with a set of metadata making this information accessible. The possibility of describing datasets put NGSI-LD at the same semantic level of DCAT by making NGSI-LD compliant with the SReq [i.3]. The second one is how the accessibility requirement is satisfied by the NGSI-LD standard. The specifications provide a complete documentation concerning the accessing mechanisms to all the data stored by using such a standard. NGSI-LD comes also with a set of open-source implementations of web service that can be used to access data collections stored by using the NGSI-LD format. Clause 6.2 provides a description about the impact of NGSI-LD, concerning its current level of compliance with the EU Data Act [i.2], if it is used as it is. Instead, clause 6.3 describes a set of action that should be put in place to enhance the compliance level of NGSI-LD to make it fully compliant with the EU Data Act [i.2] and EU SReq [i.3]. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 6.2 Use of NGSI-LD to fulfil the EU Data Act and the SReq | The content of this clause refers to the version of NGSI-LD published at the date in which the present document is written. Any subsequent updates of NGSI-LD may affect the validity of the content provided below. The NGSI-LD specifications are described in [i.6] where there are provided the good practices about how NGSI-LD can be used to grant semantic interoperability for IoT smart applications in a set of high-level outcome-focused provisions. Through the specifications described in [i.6], it is possible to support all parties involved in the development and manufacturing of IoT smart applications and products with guidance on making them. The provisions give organizations and companies the flexibility to innovate and implement NGSI-LD compliant semantic interoperability solutions appropriate for their products and applications. Indeed, through the adoption of the described methodology, the datasets produced meets completely the following aspects of the SReq [i.3]: • Paragraph 1 (c) of the EU Data Act [i.2], Article 33; • Paragraph 3 and Paragraph 8 of the EU Data Act [i.2], Article 33; • Harmonised standards on Trusted Data Transactions - Part 2: Trustworthiness requirements; • Technical specification(s) on a data catalogue implementation framework; and partially: • Paragraph 1 (a) of the EU Data Act [i.2], Article 33; • Harmonised standards on Trusted Data Transactions - Part 1: Terminology, concepts and mechanisms; • Harmonised standards on Trusted Data Transactions - Part 3: Interoperability requirements; ETSI ETSI TR 104 410 V1.1.1 (2025-10) 14 • Technical specification(s) on an implementation framework for semantic assets; • European standard on a quality framework for internal data governance. The usage of NGSI-LD in its current version leaves open same gaps before fulfilling completing the SReq [i.3]. Clause 6.3 provides a list of possible actions to improve NGSI-LD. A key development in this area is ETSI GR CIM 048 [i.7], which provides a detailed mapping between NGSI-LD and DCAT-AP. This mapping demonstrates how NGSI-LD annotations at the entity level can be systematically expressed in DCAT-AP compliant metadata records, thereby bridging dataset semantics with the catalogue-level requirements mandated by the SReq [i.3] ensuring discoverability. |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 6.3 Potential improvements | This Clause provides a set of actions that should be considered to improve NGSI-LD, and a mention to possible assets that would make NGSI-LD fully compliant with the EU Data Act [i.2] and the SReq [i.3]. In the previous clause, it has been mentioned that NGSI-LD satisfies the accessibility requirement by including information about its content, use restrictions, and licences in a machine-readable format, to allow the recipient to find, access and use the data. Concerning the aspects related to information about the data collection methodology, data quality and uncertainty, they are not applicable in the case of NGSI-LD since it is defined as a vocabulary to annotate data that have been previously collected. Hence, such a verification is demanded to the creator of the dataset annotated with the NGSI-LD vocabulary. The NGSI-LD information model consists of a specification. Their quality enables independent developers to develop conformant implementations. As part of the specifications, terminology, concepts and mechanisms used are clearly specified. These can be contributed to define the subset of the SReq [i.3] that can be covered by NGSI-LD. Concerning the specific requirement of terminology specification, the NGSI-LD specifications play the role of drivers to build assets being compliant with the SReq [i.3]. Hence, the appropriate adoption of NGSI-LD specifications would allow the fulfilment of all aspects mentioned by this requirement when constructing new data resources. Finally, also the requirement concerning the evaluation of the maturity and the interoperability of the NGSI-LD specifications cannot be fulfilled by NGSI-LD since the evaluation procedure within the Common European Data Space is still under development. 7 oneM2M, SAREF and NGSI-LD cooperation to fulfil EU Data Act and SReq Previous clauses describe how each single asset fulfil the SReq [i.3]. The present clause provides insights and recommendations about how the interplay between them may mitigate current gaps. First, the interplay between oneM2M and SAREF can satisfy the requests regarding various aspects of semantics that come from the SReq [i.3]. In particular, the aspect of managing data tagging since SAREF provides the methodology to describe the semantic meaning of data, while oneM2M provides the actual data. This is slightly different than just stating that oneM2M allows (multiple) ontologies to be loaded and to perform tagging and queries. Indeed, in the case of such an interplay, this aspect becomes more concrete. Second, the interplay of oneM2M and NGSI-LD could equip oneM2M datasets with a light-semantic index facilitating the discoverability of data managed by oneM2M. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 15 |
2dcee41e2baaaa33138eef97ae9b5cc3 | 104 410 | 8 Conclusions | The present document provides a set of guidelines that may drive future activities on oneM2M, SAREF and NGSI-LD in the context of their usage concerning the implementation of data spaces that intend to be compliant with the EU Data Act [i.2]. For each asset, there are reported which points of the SReq [i.3] are already fulfilled and which actions can be put in place to fill the current gaps. Of course, by considering the nature of each asset and their purpose, not all aspects of the SReq [i.3] can be achieved (e.g. to exploit the outcomes of the ongoing work of CEN/CENELEC on dataset quality aspects, to equip the SAREF methodology with such capability). Finally, the present document provides an analysis of how the interplay between oneM2M, SAREF and NGSI-LD can increase the fulfilment of SReq [i.3]. ETSI ETSI TR 104 410 V1.1.1 (2025-10) 16 Annex A: Change history Date Version Information about changes 23.04.25 V0.0.1 Initial structure of Early Draft including all headlines and a description for each about the intended content of the clause 24.04.25 V0.1.0 Early Draft provided to TC DATA for acceptance as basis for further drafting 29.08.25 V0.2.0 Final Draft V0.2.0 provided for approval 15.09.25 V0.2.1 Incorporation of comments received during the Remote Consensus Phase of V0.2.0 06.10.25 V0.2.2 Incorporation of further comments received ETSI ETSI TR 104 410 V1.1.1 (2025-10) 17 History Document history V1.1.1 October 2025 Publication |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 1 Scope | The present document provides a mapping between the Critical Security Controls and DORA provisions. |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 2 References | |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 2.1 Normative references | Normative references are not applicable in the present document. |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014, (EU) No 909/2014 and (EU) 2016/1011. [i.2] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive). [i.3] 2020/0266 (COD), COM(2020) 595 final: "Proposal for a Regulation of the European Parliament and of the Council on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014 and (EU) No 909/2014". [i.4] Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 on the resilience of critical entities and repealing Council Directive 2008/114/EC. [i.5] Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act). [i.6] Council Directive 2008/114/EC of 8 December 2008 on the identification and designation of European critical infrastructures and the assessment of the need to improve their protection. [i.7] Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act). [i.8] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). [i.9] Center for Internet Security: "CIS Controls v8.1 Mapping to DORA". [i.10] ETSI TS 103 305-1: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 1: The Critical Security Controls". [i.11] ETSI TR 103 305-4: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 4: Facilitation Mechanisms". ETSI ETSI TR 104 169 V1.1.1 (2025-09) 6 [i.12] ETSI TR 103 305-5: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 5: Privacy and personal data protection enhancement". [i.13] ETSI TR 103 866: "Cyber Security (CYBER); Implementation of the Revised Network and Information Security (NIS2) Directive applying Critical Security Controls". [i.14] ETSI TS 103 960: "Cyber Security (CYBER); Implementation of the Digital Operational Resilience Act (DORA)". [i.15] NIST CSF PR.DS-7: "The development and testing environment(s) are separate from the production environment". [i.16] NIST CSF PR.DS-3: "Assets are formally managed throughout removal, transfers, and disposition". |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 3 Definition of terms, symbols and abbreviations | |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 3.1 Terms | Void. |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 3.2 Symbols | Void. |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization, and Accounting COTS Commercial Off The Shelf CSC Critical Security Controls CSF Computer Security Framework DHCP Dynamic Host Configuration Protocol DORA Digital Operational Resilience Act ERM Enterprise Risk Management IG1 Implementation Group 1 IG2 Implementation Group 2 IG3 Implementation Group 3 SSO Single Sign-On ETSI ETSI TR 104 169 V1.1.1 (2025-09) 7 4 Applying the Critical Security Controls for effective implementation of DORA |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 4.1 Methodology and use | Methodology The methodology used to create the mapping can be useful to anyone attempting to understand the relationships between the Critical Security Controls and DORA. The overall goal for Control mappings is to be as specific as possible, leaning towards under-mapping versus over-mapping. The general strategy used is to identify all of the aspects within a control and attempt to discern if both items state the same thing. For instance: Control 6.1 - Establish an Access Granting Process Establish and follow a process, preferably automated, for granting access to enterprise assets upon new hire, rights grant, or role change of a user. For a defensive mitigation to map to this CSC Safeguard it is required by DORA to have at least one of the following: • A clearly documented process, covering both new employees and changes in access. • All relevant enterprise access control is required by DORA to be covered under this process, there can be no separation where different teams control access to different assets. • Automated tools are ideally used, such as a SSO provider or routing access control through a directory service. • The same process is followed every time a user's rights change, so a user never amasses greater rights access without documentation. If the two concepts are effectively equal, they are mapped with the relationship "equivalent". If they are not equal but still related, the exact type of relationship between two defensive mitigations can be further explored. The relationships can be further analysed to understand how similar or different the two defensive mitigations are. The relationship column will contain one of four possible values: • Equivalent: The defensive mitigation contains the exact same security concept as the Control. • Superset: The Control is partially or mostly related to the defensive mitigation in question, but the Control is broader in concept. • Subset: The Safeguard is partially or mostly related yet is still subsumed within the defensive mitigation. The defensive mitigation in question is broader in concept than the Control. • No relationship: This will be represented by a blank cell. The relationships should be read from left to right, like a sentence. Control Safeguard X is Equivalent to this < >. EXAMPLES: • Safeguard 16.8 "Separate Production and Non-Production Systems" is equivalent to NIST CSF PR.DS-7 [i.15]. • Safeguard 3.5 "Securely Dispose of Data" is a subset of NIST CSF PR.DS-3 [i.16]. The Critical Security Controls are written with certain principles in mind, such as only having one ask per Safeguard. This means many of the mapping targets are written in a way that contain multiple Safeguards within the same defensive mitigation, so the relationship can often be "Subset". Mappings are available from a variety of sources online, and different individuals may make their own decisions on the type of relationship. Critical Security Controls mappings are intended to be as objective as possible, and improvements are encouraged. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 8 Use The clauses in the Critical Security Controls [i.10] concerning delineation of Asset Types, Security Functions, and Implementation Groups apply to the mappings below. For reference, these delineations are repeated in part here. Asset Types are shown in Figure 4.1-1. Figure 4.1-1 Security Functions include: • GOVERN - The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored. The GOVERN Function provides outcomes to inform what an organization may do to achieve and prioritize the outcomes of the other five Functions in the context of its mission and stakeholder expectations. Governance activities are critical for incorporating cybersecurity into an organization's broader Enterprise Risk Management (ERM) strategy. GOVERN addresses an understanding of organizational context; the establishment of cybersecurity strategy and cybersecurity supply chain risk management; roles, responsibilities, and authorities; policy; and the oversight of cybersecurity strategy. • IDENTIFY - The organization's current cybersecurity risks are understood. Understanding the organization's assets (e.g. data, hardware, software, systems, facilities, services, people), suppliers, and related cybersecurity risks enables an organization to prioritize its efforts consistent with its risk management strategy and the mission needs identified under GOVERN. This Function also includes the identification of improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. • PROTECT - Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e. securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 9 • DETECT - Possible cybersecurity attacks and compromises are found and analysed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. • RESPOND - Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. • RECOVER - Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts. Implementation Groups include: • IG1. An IG1 enterprise is small to medium-sized with limited IT and cybersecurity expertise to dedicate toward protecting IT assets and personnel. The principal concern of these enterprises is to keep the business operational, as they have a limited tolerance for downtime. The sensitivity of the data that they are trying to protect is low and principally surrounds employee and financial information. Safeguards selected for IG1 should be implementable with limited cybersecurity expertise and aimed to thwart general, non-targeted attacks. These Safeguards will also typically be designed to work in conjunction with small or home office Commercial Off-The-Shelf (COTS) hardware and software. • IG2 (Includes IG1). An IG2 enterprise employs individuals responsible for managing and protecting IT infrastructure. These enterprises support multiple departments with differing risk profiles based on job function and mission. Small enterprise units can have regulatory compliance burdens. IG2 enterprises often store and process sensitive client or enterprise information and can withstand short interruptions of service. A major concern is loss of public confidence if a breach occurs. Safeguards selected for IG2 help security teams cope with increased operational complexity. Some Safeguards will depend on enterprise-grade technology and specialized expertise to properly install and configure. • IG3 (Includes IG1 and IG2). An IG3 enterprise employs security experts that specialize in the different facets of cybersecurity (e.g. risk management, penetration testing, application security). IG3 assets and data contain sensitive information or functions that are subject to regulatory and compliance oversight. An IG3 enterprise is required by DORA to address availability of services and the confidentiality and integrity of sensitive data. Successful attacks can cause significant harm to the public welfare. Safeguards selected for IG3 is required by DORA to abate targeted attacks from a sophisticated adversary and reduce the impact of zero-day attacks. |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 4.2 Applicability Overview | Table 4.2-1 below provides a mapping by the Critical Security Controls community to the DORA provisions to support the indicated requirements [i.9]. Table 4.2-1: Applicability of the Critical Security Controls to DORA Control Safeguard Title Applicability 1 Inventory and Control of Enterprise Assets 1 of 5 2 Inventory and Control of Software Assets 1 of 7 3 Data Protection 8 of 14 4 Secure Configuration of Enterprise Assets and Software 0 of 12 5 Account Management 0 of 6 6 Access Control Management 3 of 8 7 Continuous Vulnerability Management 2 of 9 8 Audit Log Management 0 of 12 9 Email and Web Browser Protections 0 of 7 10 Malware Defences 0 of 7 11 Data Recovery 4 of 5 12 Network Infrastructure Management 1 of 8 13 Network Monitoring and Defence 5 of 11 ETSI ETSI TR 104 169 V1.1.1 (2025-09) 10 Control Safeguard Title Applicability 14 Security Awareness and Skills Training 2 of 9 15 Service Provider Management 6 of 7 16 Application Software Security 0 of 14 17 Incident Response Management 7 of 9 18 Penetration Testing 0 of 5 ETSI ETSI TR 104 169 V1.1.1 (2025-09) 11 |
f960b0d45a0b4ade0630eb1df8c4dec1 | 104 169 | 4.3 Applying the Critical Security Controls and Safeguards | Table 4.3-1 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 1 Inventory and Control of Enterprise Assets 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Subset 8.1 Identification As part of the ICT risk management framework referred to in Article 6(1), financial entities shall identify, classify and adequately document all ICT supported business functions, roles and responsibilities, the information assets and ICT assets supporting those functions, and their roles and dependencies in relation to ICT risk. Financial entities shall review as needed, and at least yearly, the adequacy of this classification and of any relevant documentation. 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Subset 8.4 Identification Financial entities shall identify all information assets and ICT assets, including those on remote sites, network resources and hardware equipment, and shall map those considered critical. They shall map the configuration of the information assets and ICT assets and the links and interdependencies between the different information assets and ICT assets. 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in paragraph 3 occurs. 1.2 Devices Respond Address Unauthorized Assets x x x 1.3 Devices Detect Utilize an Active Discovery Tool x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 12 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 1.4 Devices Identify Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory x x 1.5 Devices Detect Use a Passive Asset Discovery Tool x 2 Inventory and Control of Software Assets 2.1 Software Identify Establish and Maintain a Software Inventory x x x Subset 8.1 Identification As part of the ICT risk management framework referred to in Article 6(1), financial entities shall identify, classify and adequately document all ICT supported business functions, roles and responsibilities, the information assets and ICT assets supporting those functions, and their roles and dependencies in relation to ICT risk. Financial entities shall review as needed, and at least yearly, the adequacy of this classification and of any relevant documentation. 2.1 Software Identify Establish and Maintain a Software Inventory x x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in 3 occurs. 2.2 Software Identify Ensure Authorized Software is Currently Supported x x x 2.3 Software Respond Address Unauthorized Software x x x 2.4 Software Detect Utilize Automated Software Inventory Tools x x 2.5 Software Protect Allowlist Authorized Software x x 2.6 Software Protect Allowlist Authorized Libraries x x 2.7 Software Protect Allowlist Authorized Scripts x 3 Data Protection 3.1 Data Govern Establish and Maintain a Data Management Process x x x Subset 9.3, Point (d) Protection and Prevention Ensure that data is protected from risks arising from data management, including poor administration, processing-related risks and human error. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 13 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 3.1 Data Govern Establish and Maintain a Data Management Process x x x Subset 9.4, Point (a) Protection and Prevention Develop and document an information security policy defining rules to protect the availability, authenticity, integrity and confidentiality of data, information assets and ICT assets, including those of their customers, where applicable. 3.2 Data Identify Establish and Maintain a Data Inventory x x x Subset 8.1 Identification As part of the ICT risk management framework referred to in Article 6(1), financial entities shall identify, classify and adequately document all ICT supported business functions, roles and responsibilities, the information assets and ICT assets supporting those functions, and their roles and dependencies in relation to ICT risk. Financial entities shall review as needed, and at least yearly, the adequacy of this classification and of any relevant documentation. 3.2 Data Identify Establish and Maintain a Data Inventory x x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in 3 occurs. 3.3 Data Protect Configure Data Access Control Lists x x x 3.4 Data Protect Enforce Data Retention x x x 3.5 Data Protect Securely Dispose of Data x x x 3.6 Data Protect Encrypt Data on End-User Devices x x x 3.7 Data Identify Establish and Maintain a Data Classification Scheme x x Subset 9.4, Point (d) Protection and Prevention Implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys whereby data is encrypted based on results of approved data classification and ICT risk assessment processes. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 14 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 3.8 Data Identify Document Data Flows x x Subset 8.4 Identification Financial entities shall identify all information assets and ICT assets, including those on remote sites, network resources and hardware equipment, and shall map those considered critical. They shall map the configuration of the information assets and ICT assets and the links and interdependencies between the different information assets and ICT assets. 3.8 Data Identify Document Data Flows x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in 3 occurs. 3.9 Data Protect Encrypt Data on Removable Media x x 3.10 Data Protect Encrypt Sensitive Data in Transit x x Subset 9.3, Point (a) Protection and Prevention Ensure the security of the means of transfer of data. 3.11 Data Protect Encrypt Sensitive Data at Rest x x Subset 9.3, Point (b) Protection and Prevention Minimize the risk of corruption or loss of data, unauthorized access and technical flaws that may hinder business activity. 3.12 Data Protect Segment Data Processing and Storage Based on Sensitivity x x Subset 9.4, Point (b) Protection and Prevention Following a risk-based approach, establish a sound network and infrastructure management structure using appropriate techniques, methods and protocols that may include implementing automated mechanisms to isolate affected information assets in the event of cyber-attacks. 3.13 Data Protect Deploy a Data Loss Prevention Solution x Subset 9.3, Point (b) Protection and Prevention Minimize the risk of corruption or loss of data, unauthorized access and technical flaws that may hinder business activity. 3.13 Data Protect Deploy a Data Loss Prevention Solution x Subset 9.3, Point (c) Protection and Prevention Prevent the lack of availability, the impairment of the authenticity and integrity, the breaches of confidentiality and the loss of data. 3.14 Data Detect Log Sensitive Data Access x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 15 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 4 Secure Configuration of Enterprise Assets and Software 4.1 Documentation Govern Establish and Maintain a Secure Configuration Process x x x 4.2 Documentation Govern Establish and Maintain a Secure Configuration Process for Network Infrastructure x x x 4.3 Devices Protect Configure Automatic Session Locking on Enterprise Assets x x x 4.4 Devices Protect Implement and Manage a Firewall on Servers x x x 4.5 Devices Protect Implement and Manage a Firewall on End-User Devices x x x 4.6 Devices Protect Securely Manage Enterprise Assets and Software x x x 4.7 Users Protect Manage Default Accounts on Enterprise Assets and Software x x x 4.8 Devices Protect Uninstall or Disable Unnecessary Services on Enterprise Assets and Software x x 4.9 Devices Protect Configure Trusted DNS Servers on Enterprise Assets x x 4.10 Devices Protect Enforce Automatic Device Lockout on Portable End- User Devices x x 4.11 Data Protect Enforce Remote Wipe Capability on Portable End-User Devices x x 4.12 Data Protect Separate Enterprise Workspaces on Mobile End-User Devices x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 16 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 5 Account Management 5.1 Users Identify Establish and Maintain an Inventory of Accounts x x x 5.2 Users Protect Use Unique Passwords x x x 5.3 Users Protect Disable Dormant Accounts x x x 5.4 Users Protect Restrict Administrator Privileges to Dedicated Administrator Accounts x x x 5.5 Users Identify Establish and Maintain an Inventory of Service Accounts x x 5.6 Users Protect Centralize Account Management x x 6 Access Control Management 6.1 Documentation Govern Establish an Access Granting Process x x x 6.2 Documentation Govern Establish an Access Revoking Process x x x 6.3 Users Protect Require MFA for Externally- Exposed Applications x x x 6.4 Users Protect Require MFA for Remote Network Access x x x 6.5 Users Protect Require MFA for Administrative Access x x x 6.6 Software Identify Establish and Maintain an Inventory of Authentication and Authorization Systems x x Subset 9.4, Point (d) Protection and Prevention Implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys whereby data is encrypted based on results of approved data classification and ICT risk assessment processes. 6.7 Users Protect Centralize Access Control x x Subset 9.4, Point (d) Protection and Prevention Implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys whereby data is encrypted based on results of approved data classification and ICT risk assessment processes. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 17 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 5.2, Point (c) Governance and Organization Set clear roles and responsibilities for all ICT-related functions and establish appropriate governance arrangements to ensure effective and timely communication, cooperation and coordination among those functions. 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 8.1 Identification As part of the ICT risk management framework referred to in Article 6(1), financial entities shall identify, classify and adequately document all ICT supported business functions, roles and responsibilities, the information assets and ICT assets supporting those functions, and their roles and dependencies in relation to ICT risk. Financial entities shall review as needed, and at least yearly, the adequacy of this classification and of any relevant documentation. 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in 3 occurs. 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 9.4, Point (c) Protection and Prevention Implement policies that limit the physical or logical access to information assets and ICT assets to what is required for legitimate and approved functions and activities only, and establish to that end a set of policies, procedures and controls that address access rights and ensure a sound administration thereof. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 18 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 7 Continuous Vulnerability Management 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 9.1 Protection and Prevention For the purposes of adequately protecting ICT systems and with a view to organizing response measures, financial entities shall continuously monitor and control the security and functioning of ICT systems and tools and shall minimize the impact of ICT risk on ICT systems through the deployment of appropriate ICT security tools, policies and procedures. 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 9.4, Point (f) Protection and Prevention Have appropriate and comprehensive documented policies for patches and updates. 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 16.1, Point (c) Simplified ICT Risk Management Framework Minimize the impact of ICT risk through the use of sound, resilient and updated ICT systems, protocols and tools which are appropriate to support the performance of their activities and the provision of services and adequately protect availability, authenticity, integrity and confidentiality of data in the network and information systems. 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 16.1, Point (d) Simplified ICT Risk Management Framework Allow sources of ICT risk and anomalies in the network and information systems to be promptly identified and detected and ICT-related incidents to be swiftly handled. 7.2 Documentation Govern Establish and Maintain a Remediation Process x x x Subset 9.4, Point (f) Protection and Prevention Have appropriate and comprehensive documented policies for patches and updates. 7.3 Software Protect Perform Automated Operating System Patch Management x x x 7.4 Software Protect Perform Automated Application Patch Management x x x 7.5 Software Identify Perform Automated Vulnerability Scans of Internal Enterprise Assets x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 19 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 7.6 Software Identify Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets x x 7.7 Software Respond Remediate Detected Vulnerabilities x x 8 Audit Log Management 8.1 Documentation Govern Establish and Maintain an Audit Log Management Process x x x 8.2 Data Detect Collect Audit Logs x x x 8.3 Data Protect Ensure Adequate Audit Log Storage x x x 8.4 Network Protect Standardize Time Synchronization x x 8.5 Data Detect Collect Detailed Audit Logs x x 8.6 Data Detect Collect DNS Query Audit Logs x x 8.7 Data Detect Collect URL Request Audit Logs x x 8.8 Data Detect Collect Command-Line Audit Logs x x 8.9 Data Detect Centralize Audit Logs x x 8.10 Data Protect Retain Audit Logs x x 8.11 Data Detect Conduct Audit Log Reviews x x 8.12 Data Detect Collect Service Provider Logs x 9 Email and Web Browser Protections 9.1 Software Protect Ensure Use of Only Fully Supported Browsers and Email Clients x x x 9.2 Devices Protect Use DNS Filtering Services x x x 9.3 Network Protect Maintain and Enforce Network-Based URL Filters x x 9.4 Software Protect Restrict Unnecessary or Unauthorized Browser and Email Client Extensions x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 20 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 9.5 Network Protect Implement DMARC x x 9.6 Network Protect Block Unnecessary File Types x x 9.7 Network Protect Deploy and Maintain Email Server Anti-Malware Protections x 10 Malware Defenses 10.1 Devices Detect Deploy and Maintain Anti- Malware Software x x x 10.2 Devices Protect Configure Automatic Anti- Malware Signature Updates x x x 10.3 Devices Protect Disable Autorun and Autoplay for Removable Media x x x 10.4 Devices Detect Configure Automatic Anti- Malware Scanning of Removable Media x x 10.5 Devices Protect Enable Anti-Exploitation Features x x 10.6 Devices Protect Centrally Manage Anti- Malware Software x x 10.7 Devices Detect Use Behaviour-Based Anti- Malware Software x x 11 Data Recovery 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Equivalent 12.1, Point (a) Backup and Restoration Backup policies and procedures specifying the scope of the data that is subject to the backup and the minimum frequency of the backup, based on the criticality of information or the confidentiality level of the data. 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 12.1, Point (b) Backup and Restoration Restoration and recovery procedures and methods. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 21 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 12.2 Backup and Restoration Financial entities shall set up backup systems that can be activated in accordance with the backup policies and procedures, as well as restoration and recovery procedures and methods. The activation of backup systems shall not jeopardize the security of the network and information systems or the availability, authenticity, integrity or confidentiality of data. Testing of the backup procedures and restoration and recovery procedures and methods shall be undertaken periodically. 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 16.1, Point (f) Simplified ICT Risk Management Framework Ensure the continuity of critical or important functions, through business continuity plans and response and recovery measures, which include, at least, back-up and restoration measures. 11.2 Data Recover Perform Automated Backups x x x 11.3 Data Protect Protect Recovery Data x x x Subset 12.7 Backup and Restoration When recovering from an ICT-related incident, financial entities shall perform necessary checks, including any multiple checks and reconciliations, in order to ensure that the highest level of data integrity is maintained. These checks shall also be performed when reconstructing data from external stakeholders, in order to ensure that all data is consistent between systems. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 22 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 11.4 Data Recover Establish and Maintain an Isolated Instance of Recovery Data x x x Subset 12.3 Backup and Restoration When restoring backup data using own systems, financial entities shall use ICT systems that are physically and logically segregated from the source ICT system. The ICT systems shall be securely protected from any unauthorized access or ICT corruption and allow for the timely restoration of services making use of data and system backups as necessary. For central counterparties, the recovery plans shall enable the recovery of all transactions at the time of disruption to allow the central counterparty to continue to operate with certainty and to complete settlement on the scheduled date. Data reporting service providers shall additionally maintain adequate resources and have back-up and restoration facilities in place in order to offer and maintain their services at all times. 11.5 Data Recover Test Data Recovery x x Subset 12.2 Backup and Restoration Financial entities shall set up backup systems that can be activated in accordance with the backup policies and procedures, as well as restoration and recovery procedures and methods. The activation of backup systems shall not jeopardize the security of the network and information systems or the availability, authenticity, integrity or confidentiality of data. Testing of the backup procedures and restoration and recovery procedures and methods shall be undertaken periodically. 11.5 Data Recover Test Data Recovery x x Subset 16.1, Point (g) Simplified ICT Risk Management Framework Test, on a regular basis, the plans and measures referred to in point (f), as well as the effectiveness of the controls implemented in accordance with points (a) and (c). ETSI ETSI TR 104 169 V1.1.1 (2025-09) 23 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 12 Network Infrastructure Management 12.1 Network Protect Ensure Network Infrastructure is Up-to-Date x x x 12.2 Network Protect Establish and Maintain a Secure Network Architecture x x Subset 5.2, Point (b) Governance and Organization Put in place policies that aim to ensure the maintenance of high standards of availability, authenticity, integrity and confidentiality, of data. 12.2 Network Protect Establish and Maintain a Secure Network Architecture x x Subset 9.4, Point (b) Protection and Prevention Following a risk-based approach, establish a sound network and infrastructure management structure using appropriate techniques, methods and protocols that may include implementing automated mechanisms to isolate affected information assets in the event of cyber-attacks. 12.3 Network Protect Securely Manage Network Infrastructure x x 12.4 Documentation Govern Establish and Maintain Architecture Diagram(s) x x 12.5 Network Protect Centralize Network Authentication, Authorization, and Auditing (AAA) x x 12.6 Network Protect Use of Secure Network Management and Communication Protocols x x 12.7 Devices Protect Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure x x 12.8 Devices Protect Establish and Maintain Dedicated Computing Resources for All Administrative Work x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 24 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 13 Network Monitoring and Defense 13.1 Network Detect Centralize Security Event Alerting x x Subset 10.1 Detection Financial entities shall have in place mechanisms to promptly detect anomalous activities, in accordance with Article 17, including ICT network performance issues and ICT-related incidents, and to identify potential material single points of failure. All detection mechanisms referred to in the first subparagraph shall be regularly tested in accordance with Article 25. 13.1 Network Detect Centralize Security Event Alerting x x Subset 16.1, Point (b) Simplified ICT Risk Management Framework Continuously monitor the security and functioning of all ICT systems. 13.2 Devices Detect Deploy a Host-Based Intrusion Detection Solution x x Subset 9.1 Protection and Prevention For the purposes of adequately protecting ICT systems and with a view to organizing response measures, financial entities shall continuously monitor and control the security and functioning of ICT systems and tools and shall minimize the impact of ICT risk on ICT systems through the deployment of appropriate ICT security tools, policies and procedures. 13.2 Devices Detect Deploy a Host-Based Intrusion Detection Solution x x Subset 10.1 Detection Financial entities shall have in place mechanisms to promptly detect anomalous activities, in accordance with Article 17, including ICT network performance issues and ICT-related incidents, and to identify potential material single points of failure. All detection mechanisms referred to in the first subparagraph shall be regularly tested in accordance with Article 25. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 25 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 13.2 Devices Detect Deploy a Host-Based Intrusion Detection Solution x x Subset 10.3 Detection Financial entities shall devote sufficient resources and capabilities to monitor user activity, the occurrence of ICT anomalies and ICT-related incidents, in particular cyber-attacks. 13.3 Network Detect Deploy a Network Intrusion Detection Solution x x Subset 10.1 Detection Financial entities shall have in place mechanisms to promptly detect anomalous activities, in accordance with Article 17, including ICT network performance issues and ICT-related incidents, and to identify potential material single points of failure. All detection mechanisms referred to in the first subparagraph shall be regularly tested in accordance with Article 25. 13.4 Network Protect Perform Traffic Filtering Between Network Segments x x 13.5 Devices Protect Manage Access Control for Remote Assets x x 13.6 Network Detect Collect Network Traffic Flow Logs x x Subset 10.2 Detection The detection mechanisms referred to in paragraph 1 shall enable multiple layers of control, define alert thresholds and criteria to trigger and initiate ICT-related incident response processes, including automatic alert mechanisms for relevant staff in charge of ICT-related incident response. 13.6 Network Detect Collect Network Traffic Flow Logs x x Subset 10.3 Detection Financial entities shall devote sufficient resources and capabilities to monitor user activity, the occurrence of ICT anomalies and ICT-related incidents, in particular cyber- attacks. 13.7 Devices Protect Deploy a Host-Based Intrusion Prevention Solution x 13.8 Network Protect Deploy a Network Intrusion Prevention Solution x 13.9 Network Protect Deploy Port-Level Access Control x 13.10 Network Protect Perform Application Layer Filtering x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 26 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 13.11 Network Detect Tune Security Event Alerting Thresholds x Subset 10.2 Detection The detection mechanisms referred to in paragraph 1 shall enable multiple layers of control, define alert thresholds and criteria to trigger and initiate ICT-related incident response processes, including automatic alert mechanisms for relevant staff in charge of ICT-related incident response. 14 Security Awareness and Skills Training 14.1 Documentation Govern Establish and Maintain a Security Awareness Program x x x Superset 13.6 Learning and Evolving Financial entities shall develop ICT security awareness programmes and digital operational resilience training as compulsory modules in their staff training schemes. Those programmes and training shall be applicable to all employees and to senior management staff, and shall have a level of complexity commensurate to the remit of their functions. Where appropriate, financial entities shall also include ICT third-party service providers in their relevant training schemes in accordance with Article 30(2), point (i). 14.2 Users Protect Train Workforce Members to Recognize Social Engineering Attacks x x x 14.3 Users Protect Train Workforce Members on Authentication Best Practices x x x 14.4 Users Protect Train Workforce on Data Handling Best Practices x x x 14.5 Users Protect Train Workforce Members on Causes of Unintentional Data Exposure x x x 14.6 Users Protect Train Workforce Members on Recognizing and Reporting Security Incidents x x x 14.7 Users Protect Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates x x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 27 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 14.8 Users Protect Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks x x x 14.9 Users Protect Conduct Role-Specific Security Awareness and Skills Training x x Superset 5.4 Governance and Organization Members of the management body of the financial entity shall actively keep up to date with sufficient knowledge and skills to understand and assess ICT risk and its impact on the operations of the financial entity, including by following specific training on a regular basis, commensurate to the ICT risk being managed. 15 Service Provider Management 15.1 Users Identify Establish and Maintain an Inventory of Service Providers x x x Subset 8.5 Identification Financial entities shall identify and document all processes that are dependent on ICT third- party service providers, and shall identify interconnections with ICT third-party service providers that provide services that support critical or important functions. 15.1 Users Identify Establish and Maintain an Inventory of Service Providers x x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in paragraph 3 occurs. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 5.2, Point (b) Governance and Organization put in place policies that aim to ensure the maintenance of high standards of availability, authenticity, integrity and confidentiality, of data. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 5.2, Point (h) Governance and Organization Approve and periodically review the financial entity's policy on arrangements regarding the use of ICT services provided by ICT third-party service providers. Put in place, at corporate level, reporting channels enabling it to be duly informed of the following. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 28 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 15.3 Users Govern Classify Service Providers x x Subset 8.5 Identification Financial entities shall identify and document all processes that are dependent on ICT third-party service providers, and shall identify interconnections with ICT third-party service providers that provide services that support critical or important functions. 15.3 Users Govern Classify Service Providers x x Subset 8.6 Identification For the purposes of paragraphs 1, 4 and 5, financial entities shall maintain relevant inventories and update them periodically and every time any major change as referred to in paragraph 3 occurs. 15.3 Users Govern Classify Service Providers x x Subset 16.1, Point (e) Simplified ICT Risk Management Framework Identify key dependencies on ICT third-party service providers. 15.4 Documentation Govern Ensure Service Provider Contracts Include Security Requirements x x Subset 5.2, Point (h), Subpoint (ii) Governance and Organization The potential impact of such changes on the critical or important functions subject to those arrangements, including a risk analysis summary to assess the impact of those changes, and at least major ICT-related incidents and their impact, as well as response, recovery and corrective measures. 15.4 Documentation Govern Ensure Service Provider Contracts Include Security Requirements x x Subset 10.4 Detection Data reporting service providers shall, in addition, have in place systems that can effectively check trade reports for completeness, identify omissions and obvious errors, and request re-transmission of those reports. 15.5 Users Govern Assess Service Providers x 15.6 Data Govern Monitor Service Providers x Subset 5.2, Point (h), Subpoint (ii) Governance and Organization Any relevant planned material changes regarding the ICT third-party service providers. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 29 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 15.6 Data Govern Monitor Service Providers x Subset 5.3 Governance and Organization Financial entities, other than microenterprises, shall establish a role in order to monitor the arrangements concluded with ICT third-party service providers on the use of ICT services, or shall designate a member of senior management as responsible for overseeing the related risk exposure and relevant documentation. 15.7 Data Protect Securely Decommission Service Providers x Superset 5.2, Point (h), Subpoint (i) Governance and Organization Arrangements concluded with ICT third-party service providers on the use of ICT services. 16 Application Software Security 16.1 Documentation Govern Establish and Maintain a Secure Application Development Process x x 16.2 Documentation Govern Establish and Maintain a Process to Accept and Address Software Vulnerabilities x x 16.3 Software Protect Perform Root Cause Analysis on Security Vulnerabilities x x 16.4 Software Identify Establish and Manage an Inventory of Third-Party Software Components x x 16.5 Software Protect Use Up-to-Date and Trusted Third-Party Software Components x x 16.6 Documentation Govern Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities x x 16.7 Software Protect Use Standard Hardening Configuration Templates for Application Infrastructure x x 16.8 Network Protect Separate Production and Non-Production Systems x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 30 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 16.9 Users Protect Train Developers in Application Security Concepts and Secure Coding x x 16.10 Software Protect Apply Secure Design Principles in Application Architectures x x 16.11 Software Protect Leverage Vetted Modules or Services for Application Security Components x x 16.12 Software Protect Implement Code-Level Security Checks x 16.13 Software Detect Conduct Application Penetration Testing x 16.14 Software Protect Conduct Threat Modelling x 17 Incident Response Management 17.1 Users Respond Designate Personnel to Manage Incident Handling x x x Subset 5.2, Point (c) Governance and Organization Set clear roles and responsibilities for all ICT-related functions and establish appropriate governance arrangements to ensure effective and timely communication, cooperation and coordination among those functions. 17.1 Users Respond Designate Personnel to Manage Incident Handling x x x Superset 14.3 Communication At least one person in the financial entity shall be tasked with implementing the communication strategy for ICT-related incidents and fulfil the public and media function for that purpose. 17.1 Users Respond Designate Personnel to Manage Incident Handling x x x Superset 17.3, Point (c) ICT-related incident management process Assign roles and responsibilities that need to be activated for different ICT-related incident types and scenarios. 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 11.2, Point (e) Response and Recovery Set out communication and crisis management actions that ensure that updated information is transmitted to all relevant internal staff and external stakeholders in accordance with Article 14, and report to the competent authorities in accordance with Article 19. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 31 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 14.1 Communication As part of the ICT risk management framework referred to in Article 6(1), financial entities shall have in place crisis communication plans enabling a responsible disclosure of, at least, major ICT-related incidents or vulnerabilities to clients and counterparts as well as to the public, as appropriate. 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 17.3, Point (d) ICT-related incident management process Set out plans for communication to staff, external stakeholders and media in accordance with Article 14 and for notification to clients, for internal escalation procedures, including ICT-related customer complaints, as well as for the provision of information to financial entities that act as counterparts, as appropriate. 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 17.3, Point (e) ICT-related incident management process Ensure that at least major ICT-related incidents are reported to relevant senior management and inform the management body of at least major ICT-related incidents, explaining the impact, response and additional controls to be established as a result of such ICT-related incidents. 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 19.1 Reporting of major ICT- related incidents and voluntary notification of significant cyber threats Financial entities shall report major ICT- related incidents to the relevant competent authority as referred to in Article 46 in accordance with paragraph 4 of this Article. 17.3 Documentation Govern Establish and Maintain an Enterprise Process for Reporting Incidents x x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 32 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 5.2, Point (e) Governance and Organization Approve, oversee and periodically review the implementation of the financial entity's ICT business continuity policy and ICT response and recovery plans, referred to, respectively, in Article 11(1) and (3), which may be adopted as a dedicated specific policy forming an integral part of the financial entity's overall business continuity policy and response and recovery plan. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 11.2, Point (b) Response and Recovery Quickly, appropriately and effectively respond to, and resolve, all ICT-related incidents in a way that limits damage and prioritizes the resumption of activities and recovery actions. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 11.2, Point (c) Response and Recovery Activate, without delay, dedicated plans that enable containment measures, processes and technologies suited to each type of ICT-related incident and prevent further damage, as well as tailored response and recovery procedures established in accordance with Article 12. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 16.1, Point (f) Simplified ICT Risk Management Framework Ensure the continuity of critical or important functions, through business continuity plans and response and recovery measures, which include, at least, back-up and restoration measures. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 17.1 ICT-related incident management process Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 17.2 ICT-related incident management process Financial entities shall record all ICT-related incidents and significant cyber threats. Financial entities shall establish appropriate procedures and processes to ensure a consistent and integrated monitoring, handling and follow-up of ICT-related incidents, to ensure that root causes are identified, documented and addressed in order to prevent the occurrence of such incidents. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 33 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 17.3, Point (f) ICT-related incident management process Establish ICT-related incident response procedures to mitigate impacts and ensure that services become operational and secure in a timely manner. 17.5 Users Respond Assign Key Roles and Responsibilities x x 17.6 Users Respond Define Mechanisms for Communicating During Incident Response x x Subset 11.2, Point (e) Response and Recovery Set out communication and crisis management actions that ensure that updated information is transmitted to all relevant internal staff and external stakeholders in accordance with Article 14, and report to the competent authorities in accordance with Article 19. 17.6 Users Respond Define Mechanisms for Communicating During Incident Response x x Subset 11.6, Point (b) Response and Recovery Test the crisis communication plans established in accordance with Article 14. 17.6 Users Respond Define Mechanisms for Communicating During Incident Response x x Subset 11.7 Response and Recovery Financial entities, other than microenterprises, shall have a crisis management function, which, in the event of activation of their ICT business continuity plans or ICT response and recovery plans, shall, inter alia, set out clear procedures to manage internal and external crisis communications in accordance with Article 14. 17.7 Users Recover Conduct Routine Incident Response Exercises x x Subset 11.4 Response and Recovery Financial entities shall put in place, maintain and periodically test appropriate ICT business continuity plans, notably with regard to critical or important functions outsourced or contracted through arrangements with ICT third-party service providers. 17.7 Users Recover Conduct Routine Incident Response Exercises x x Subset 11.6, Point (a) Response and Recovery Test the ICT business continuity plans and the ICT response and recovery plans in relation to ICT systems supporting all functions at least yearly, as well as in the event of any substantive changes to ICT systems supporting critical or important functions. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 34 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.7 Users Recover Conduct Routine Incident Response Exercises x x Subset 16.1, Point (g) Simplified ICT Risk Management Framework Test, on a regular basis, the plans and measures referred to in point (f), as well as the effectiveness of the controls implemented in accordance with points (a) and (c). 17.8 Users Recover Conduct Post-Incident Reviews x x Subset 13.1 Learning and Evolving Financial entities shall have in place capabilities and staff to gather information on vulnerabilities and cyber threats, ICT-related incidents, in particular cyber-attacks, and analyse the impact they are likely to have on their digital operational resilience. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 35 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.8 Users Recover Conduct Post-Incident Reviews x x Subset 13.2 Learning and Evolving Financial entities shall put in place post ICT- related incident reviews after a major ICT- related incident disrupts their core activities, analysing the causes of disruption and identifying required improvements to the ICT operations or within the ICT business continuity policy referred to in Article 11. Financial entities, other than microenterprises, shall, upon request, communicate to the competent authorities, the changes that were implemented following post ICT-related incident reviews as referred to in the first subparagraph. The post ICT-related incident reviews referred to in the first subparagraph shall determine whether the established procedures were followed and the actions taken were effective, including in relation to the following: (a) the promptness in responding to security alerts and determining the impact of ICT-related incidents and their severity; (b) the quality and speed of performing a forensic analysis, where deemed appropriate; (c) the effectiveness of incident escalation within the financial entity; (d) the effectiveness of internal and external communication. ETSI ETSI TR 104 169 V1.1.1 (2025-09) 36 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 17.8 Users Recover Conduct Post-Incident Reviews x x Subset 13.3 Learning and Evolving Lessons derived from the digital operational resilience testing carried out in accordance with Articles 26 and 27 and from real life ICT-related incidents, in particular cyber-attacks, along with challenges faced upon the activation of ICT business continuity plans and ICT response and recovery plans, together with relevant information exchanged with counterparts and assessed during supervisory reviews, shall be duly incorporated on a continuous basis into the ICT risk assessment process. Those findings shall form the basis for appropriate reviews of relevant components of the ICT risk management framework referred to in Article 6(1). 17.9 Documentation Recover Establish and Maintain Security Incident Thresholds x Subset 10.2 Detection The detection mechanisms referred to in paragraph 1 shall enable multiple layers of control, define alert thresholds and criteria to trigger and initiate ICT-related incident response processes, including automatic alert mechanisms for relevant staff in charge of ICT-related incident response. 17.9 Documentation Recover Establish and Maintain Security Incident Thresholds x Superset 17.3, Point (a) ICT-related incident management process Put in place early warning indicators. 17.9 Documentation Recover Establish and Maintain Security Incident Thresholds x Superset 17.3, Point (b) ICT-related incident management process Establish procedures to identify, track, log, categorize and classify ICT-related incidents according to their priority and severity and according to the criticality of the services impacted, in accordance with the criteria set out in Article 18(1). 18 Penetration Testing 18.1 Documentation Govern Establish and Maintain a Penetration Testing Program x x 18.2 Network Detect Perform Periodic External Penetration Tests x x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 37 CIS Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 DORA Relationship DORA Provision DORA Category DORA Requirement Description 18.3 Network Protect Remediate Penetration Test Findings x x 18.4 Network Protect Validate Security Measures x 18.5 Network Detect Perform Periodic Internal Penetration Tests x ETSI ETSI TR 104 169 V1.1.1 (2025-09) 38 Annex A: Unmapped DORA Provisions The following DORA provisions are NOT mapped to the Critical Security Controls Safeguards. Table A.1 DORA Requirement # DORA Provision 5.1 Governance and Organization 5.2 Governance and Organization 5.2(a) Governance and Organization 5.2(d) Governance and Organization 5.2(f) Governance and Organization 5.2(g) Governance and Organization 6.1 ICT Risk Management Framework 6.2 ICT Risk Management Framework 6.3 ICT Risk Management Framework 6.4 ICT Risk Management Framework 6.5 ICT Risk Management Framework 6.6 ICT Risk Management Framework 6.7 ICT Risk Management Framework 6.8 ICT Risk Management Framework 6.8(a) ICT Risk Management Framework 6.8(b) ICT Risk Management Framework 6.8(c) ICT Risk Management Framework 6.8(d) ICT Risk Management Framework 6.8(e) ICT Risk Management Framework 6.8(f) ICT Risk Management Framework 6.8(g) ICT Risk Management Framework 6.8(h) ICT Risk Management Framework 6.9 ICT Risk Management Framework 6.1 ICT Risk Management Framework 8.2 Identification 8.3 Identification 8.7 Identification 9.2 Protection and Prevention 9.3 Protection and Prevention 9.4 Protection and Prevention 9.4(e) Protection and Prevention 11.1 Response and Recovery 11.2 Response and Recovery 11.2(a) Response and Recovery 11.2(d) Response and Recovery 11.3 Response and Recovery 11.5 Response and Recovery 11.6 Response and Recovery 11.8 Response and Recovery 11.9 Response and Recovery 11.1 Response and Recovery 11.11 Response and Recovery 12.1 Backup and Restoration 12.4 Backup and Restoration 12.5 Backup and Restoration 12.5(a) Backup and Restoration 12.5(b) Backup and Restoration 12.5(c) Backup and Restoration 12.6 Backup and Restoration 13.4 Learning and Evolving 13.5 Learning and Evolving 13.7 Learning and Evolving 14.2 Communication ETSI ETSI TR 104 169 V1.1.1 (2025-09) 39 DORA Requirement # DORA Provision 16.1(a) Simplified ICT Risk Management Framework 16.1(h) Simplified ICT Risk Management Framework 16.2 Simplified ICT Risk Management Framework 17.3 ICT-related incident management process ETSI ETSI TR 104 169 V1.1.1 (2025-09) 40 Annex B: Unmapped Critical Security Control Safeguards The following Critical Security Controls Safeguards are NOT mapping to DORA requirements. Table B.1 Safeguard Safeguard Name 1.2 Address Unauthorized Assets 1.3 Utilize an Active Discovery Tool 1.4 Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory 1.5 Use a Passive Asset Discovery Tool 2.2 Ensure Authorized Software is Currently Supported 2.3 Address Unauthorized Software 2.4 Utilize Automated Software Inventory Tools 2.5 Allowlist Authorized Software 2.6 Allowlist Authorized Libraries 2.7 Allowlist Authorized Scripts 3.3 Configure Data Access Control Lists 3.4 Enforce Data Retention 3.5 Securely Dispose of Data 3.6 Encrypt Data on End-User Devices 3.9 Encrypt Data on Removable Media 3.14 Log Sensitive Data Access 4.1 Establish and Maintain a Secure Configuration Process 4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure 4.3 Configure Automatic Session Locking on Enterprise Assets 4.4 Implement and Manage a Firewall on Servers 4.5 Implement and Manage a Firewall on End-User Devices 4.6 Securely Manage Enterprise Assets and Software 4.7 Manage Default Accounts on Enterprise Assets and Software 4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software 4.9 Configure Trusted DNS Servers on Enterprise Assets 4.1 Enforce Automatic Device Lockout on Portable End-User Devices 4.11 Enforce Remote Wipe Capability on Portable End-User Devices 4.12 Separate Enterprise Workspaces on Mobile End-User Devices 5.1 Establish and Maintain an Inventory of Accounts 5.2 Use Unique Passwords 5.3 Disable Dormant Accounts 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts 5.5 Establish and Maintain an Inventory of Service Accounts 5.6 Centralize Account Management 6.1 Establish an Access Granting Process 6.2 Establish an Access Revoking Process 6.3 Require MFA for Externally-Exposed Applications 6.4 Require MFA for Remote Network Access 6.5 Require MFA for Administrative Access 7.3 Perform Automated Operating System Patch Management 7.4 Perform Automated Application Patch Management 7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets 7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets 7.7 Remediate Detected Vulnerabilities 8.1 Establish and Maintain an Audit Log Management Process 8.2 Collect Audit Logs 8.3 Ensure Adequate Audit Log Storage 8.4 Standardize Time Synchronization 8.5 Collect Detailed Audit Logs 8.6 Collect DNS Query Audit Logs 8.7 Collect URL Request Audit Logs 8.8 Collect Command-Line Audit Logs 8.9 Centralize Audit Logs 8.1 Retain Audit Logs 8.11 Conduct Audit Log Reviews ETSI ETSI TR 104 169 V1.1.1 (2025-09) 41 Safeguard Safeguard Name 8.12 Collect Service Provider Logs 9.1 Ensure Use of Only Fully Supported Browsers and Email Clients 9.2 Use DNS Filtering Services 9.3 Maintain and Enforce Network-Based URL Filters 9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions 9.5 Implement DMARC 9.6 Block Unnecessary File Types 9.7 Deploy and Maintain Email Server Anti-Malware Protections 10.1 Deploy and Maintain Anti-Malware Software 10.2 Configure Automatic Anti-Malware Signature Updates 10.3 Disable Autorun and Autoplay for Removable Media 10.4 Configure Automatic Anti-Malware Scanning of Removable Media 10.5 Enable Anti-Exploitation Features 10.6 Centrally Manage Anti-Malware Software 10.7 Use Behaviour-Based Anti-Malware Software 11.2 Perform Automated Backups 12.1 Ensure Network Infrastructure is Up-to-Date 12.3 Securely Manage Network Infrastructure 12.4 Establish and Maintain Architecture Diagram(s) 12.5 Centralize Network Authentication, Authorization, and Auditing (AAA) 12.6 Use of Secure Network Management and Communication Protocols 12.7 Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure 12.8 Establish and Maintain Dedicated Computing Resources for All Administrative Work 13.4 Perform Traffic Filtering Between Network Segments 13.5 Manage Access Control for Remote Assets 13.7 Deploy a Host-Based Intrusion Prevention Solution 13.8 Deploy a Network Intrusion Prevention Solution 13.9 Deploy Port-Level Access Control 13.1 Perform Application Layer Filtering 14.2 Train Workforce Members to Recognize Social Engineering Attacks 14.3 Train Workforce Members on Authentication Best Practices 14.4 Train Workforce on Data Handling Best Practices 14.5 Train Workforce Members on Causes of Unintentional Data Exposure 14.6 Train Workforce Members on Recognizing and Reporting Security Incidents 14.7 Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates 14.8 Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks 15.5 Assess Service Providers 16.1 Establish and Maintain a Secure Application Development Process 16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities 16.3 Perform Root Cause Analysis on Security Vulnerabilities 16.4 Establish and Manage an Inventory of Third-Party Software Components 16.5 Use Up-to-Date and Trusted Third-Party Software Components 16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities 16.7 Use Standard Hardening Configuration Templates for Application Infrastructure 16.8 Separate Production and Non-Production Systems 16.9 Train Developers in Application Security Concepts and Secure Coding 16.1 Apply Secure Design Principles in Application Architectures 16.11 Leverage Vetted Modules or Services for Application Security Components 16.12 Implement Code-Level Security Checks 16.13 Conduct Application Penetration Testing 16.14 Conduct Threat Modelling 17.3 Establish and Maintain an Enterprise Process for Reporting Incidents 17.5 Assign Key Roles and Responsibilities 18.1 Establish and Maintain a Penetration Testing Program 18.2 Perform Periodic External Penetration Tests 18.3 Remediate Penetration Test Findings 18.4 Validate Security Measures 18.5 Perform Periodic Internal Penetration Tests ETSI ETSI TR 104 169 V1.1.1 (2025-09) 42 History Document history V1.1.1 September 2025 Publication |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 1 Scope | The present document item provides a mapping between the Critical Security Controls and NIS2 provisions. |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 2 References | |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 2.1 Normative references | Normative references are not applicable in the present document. |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive). [i.2] Regulation (EU) No. 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.3] Directive (EU) 2016/1148 of The European Parliament and of The Council of 6 July 2016 concerning measures for a high common level of security of network and information systems across the Union. [i.4] Resolution (EC) 13084/1/20: "Council Resolution on Encryption - Security through encryption and security despite encryption". [i.5] Recommendation 2003/361/EC: "Commission Recommendation of 6 May 2003 concerning the definition of micro, small and medium-sized enterprises". [i.6] 2020/0365 (COD), COM(2020) 829 Final: "Proposal for a directive of the European Parliament and of the Council on the resilience of critical entities". [i.7] Directive (EU) 2018/1972 of the European Parliament and of the Council of 11 December 2018 establishing the European Electronic Communications Code. [i.8] ETSI TR 103 456: "CYBER; Implementation of the Network and Information Security (NIS) Directive". [i.9] Center for Internet Security: "CIS Controls v8.1, Mapping to NIS2 Directive 2022/2555". [i.10] ETSI TS 103 305-1: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 1: The Critical Security Controls". [i.11] ETSI TR 103 305-4: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 4: Facilitation Mechanisms". [i.12] ETSI TR 103 305-5: "Cyber Security (CYBER); Critical Security Controls for Effective Cyber Defence; Part 5: Privacy and personal data protection enhancement". ETSI ETSI TR 104 168 V1.1.1 (2025-09) 6 [i.13] ETSI TR 103 866: "Cyber Security (CYBER); Implementation of the Revised Network and Information Security (NIS2) Directive applying Critical Security Controls". [i.14] ETSI TS 103 992: "Cyber Security (CYBER); Implementation of the Revised Network and Information Security (NIS2) Directive applying Critical Security Controls". |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 3 Definition of terms, symbols and abbreviations | |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 3.1 Terms | Void. |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 3.2 Symbols | Void. |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: COTS Commercial Off The Shelf CSC Critical Security Controls CSF Computer Security Framework DHCP Dynamic Host Configuration Protocol ERM Enterprise Risk Management IG1 Implementation Group 1 IG2 Implementation Group 2 IG3 Implementation Group 3 NIS2 Network and Information Security Directive 2 SSO Single Sign-On 4 Applying the Critical Security Controls for effective implementation of the NIS2 Directive |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 4.1 Methodology and Use | Methodology The methodology used to create the mapping can be useful to anyone attempting to understand the relationships between the Critical Security Controls and NIS2. The overall goal for Control mappings is to be as specific as possible, leaning towards under-mapping versus over-mapping. The general strategy used is to identify all of the aspects within a control and attempt to discern if both items state the same thing. For instance: Control 6.1 - Establish an Access Granting Process Establish and follow a process, preferably automated, for granting access to enterprise assets upon new hire, rights grant, or role change of a user. For a defensive mitigation to map to this CSC Safeguard it is required by NIS2 to have at least one of the following: - A clearly documented process, covering both new employees and changes in access. - All relevant enterprise access control is required by NIS2 to be covered under this process, there can be no separation where different teams control access to different assets. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 7 - Automated tools are ideally used, such as a SSO provider or routing access control through a directory service. - The same process is followed every time a user's rights change, so a user never amasses greater rights access without documentation. If the two concepts are effectively equal, they are mapped with the relationship "equivalent". If they are not equal but still related, the exact type of relationship between two defensive mitigations can be further explored. The relationships can be further analysed to understand how similar or different the two defensive mitigations are. The relationship column will contain one of four possible values: • Equivalent: The defensive mitigation contains the exact same security concept as the Control. • Superset: The Control is partially or mostly related to the defensive mitigation in question, but the Control is broader in concept. • Subset: The Safeguard is partially or mostly related yet is still subsumed within the defensive mitigation. The defensive mitigation in question is broader in concept than the Control. • No relationship: This will be represented by a blank cell. The relationships should be read from left to right, like a sentence. Control Safeguard X is Equivalent to this < >. EXAMPLES: Safeguard 16.8 "Separate Production and Non-Production Systems" is EQUIVALENT to NIST CSF PR.DS-7 "The development and testing environment(s) are separate from the production environment". Safeguard 3.5 "Securely Dispose of Data" is a SUBSET of NIST CSF PR.DS-3 "Assets are formally managed throughout removal, transfers, and disposition". The Critical Security Controls are written with certain principles in mind, such as only having one ask per Safeguard. This means many of the mapping targets are written in a way that contain multiple Safeguards within the same defensive mitigation, so the relationship can often be "Subset". Mappings are available from a variety of sources online, and different individuals may make their own decisions on the type of relationship. Critical Security Controls mappings are intended to be as objective as possible, and improvements are encouraged. Use The clauses in the Critical Security Controls concerning delineation of Asset Types, Security Functions, and Implementation Groups apply to the mappings below. For reference, these delineations are repeated in part here. Asset Types are shown in Figure 4.1-1. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 8 Figure 4.1-1 Security Functions include: • GOVERN - The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored. The GOVERN Function provides outcomes to inform what an organization may do to achieve and prioritize the outcomes of the other five Functions in the context of its mission and stakeholder expectations. Governance activities are critical for incorporating cybersecurity into an organization's broader Enterprise Risk Management (ERM) strategy. GOVERN addresses an understanding of organizational context; the establishment of cybersecurity strategy and cybersecurity supply chain risk management; roles, responsibilities, and authorities; policy; and the oversight of cybersecurity strategy. • IDENTIFY - The organization's current cybersecurity risks are understood. Understanding the organization's assets (e.g. data, hardware, software, systems, facilities, services, people), suppliers, and related cybersecurity risks enables an organization to prioritize its efforts consistent with its risk management strategy and the mission needs identified under GOVERN. This Function also includes the identification of improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. • PROTECT - Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e. securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. • DETECT - Possible cybersecurity attacks and compromises are found and analysed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. • RESPOND - Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 9 • RECOVER - Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts. Implementation Groups include: • IG1. An IG1 enterprise is small to medium-sized with limited IT and cybersecurity expertise to dedicate toward protecting IT assets and personnel. The principal concern of these enterprises is to keep the business operational, as they have a limited tolerance for downtime. The sensitivity of the data that they are trying to protect is low and principally surrounds employee and financial information. • Safeguards selected for IG1 should be implementable with limited cybersecurity expertise and aimed to thwart general, non-targeted attacks. These Safeguards will also typically be designed to work in conjunction with small or home office Commercial Off-The-Shelf (COTS) hardware and software. • IG2 (Includes IG1). An IG2 enterprise employs individuals responsible for managing and protecting IT infrastructure. These enterprises support multiple departments with differing risk profiles based on job function and mission. Small enterprise units can have regulatory compliance burdens. IG2 enterprises often store and process sensitive client or enterprise information and can withstand short interruptions of service. A major concern is loss of public confidence if a breach occurs. • Safeguards selected for IG2 help security teams cope with increased operational complexity. Some Safeguards will depend on enterprise-grade technology and specialized expertise to properly install and configure. • IG3 (Includes IG1 and IG2). An IG3 enterprise employs security experts that specialize in the different facets of cybersecurity (e.g. risk management, penetration testing, application security). IG3 assets and data contain sensitive information or functions that are subject to regulatory and compliance oversight. An IG3 enterprise should address availability of services and the confidentiality and integrity of sensitive data. Successful attacks can cause significant harm to the public welfare. Safeguards selected for IG3 should abate targeted attacks from a sophisticated adversary and reduce the impact of zero-day attacks. |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 4.2 Applicability Overview | Table 4.2-1: Applicability of the Critical Security Controls to the NIS2 Directive Control Safeguard Title Applicability 1 Inventory and Control of Enterprise Assets 1 of 5 2 Inventory and Control of Software Assets 1 of 7 3 Data Protection 9 of 14 4 Secure Configuration of Enterprise Assets and Software 4 of 12 5 Account Management 4 of 6 6 Access Control Management 8 of 8 7 Continuous Vulnerability Management 7 of 9 8 Audit Log Management 10 of 12 9 Email and Web Browser Protections 2 of 7 10 Malware Defences 3 of 7 11 Data Recovery 4 of 5 12 Network Infrastructure Management 5 of 8 13 Network Monitoring and Defence 2 of 11 14 Security Awareness and Skills Training 3 of 9 15 Service Provider Management 6 of 7 16 Application Software Security 2 of 14 17 Incident Response Management 8 of 9 18 Penetration Testing 1 of 5 ETSI ETSI TR 104 168 V1.1.1 (2025-09) 10 |
e20ec0e4001149cdfbd49276229c67c8 | 104 168 | 4.3 Applying the Critical Security Controls and Safeguards | Table 4.3-1 below provides a mapping by the Critical Security Controls community to the NIS2 provisions to support the indicated requirements [i.9]. Table 4.3-1 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 1 Inventory and Control of Enterprise Assets 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Superset 12.4 Asset inventory 12.4.1 The relevant entities shall develop and maintain a complete, accurate, up-to-date and consistent inventory of their assets. They shall record changes to the entries in the inventory in a traceable manner. 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Superset 12.4 Asset inventory 12.4.2 The granularity of the inventory of the assets shall be at a level appropriate for the needs of the relevant entities. The inventory shall include the following: (a) the list of operations and services and their description, (b) the list of network and information systems and other associated assets supporting the entities' operations and services. 1.1 Devices Identify Establish and Maintain Detailed Enterprise Asset Inventory x x x Superset 12.4 Asset inventory 12.4.3 The relevant entities shall regularly review and update the inventory and their assets and document the history of changes. 1.2 Devices Respond Address Unauthorized Assets x x x 1.3 Devices Detect Utilize an Active Discovery Tool x x 1.4 Devices Identify Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory x x 1.5 Devices Detect Use a Passive Asset Discovery Tool x 2 Inventory and Control of Software Assets 2.1 Software Identify Establish and Maintain a Software Inventory x x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 11 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 2.2 Software Identify Ensure Authorized Software is Currently Supported x x x Subset 6.6 Security patch management 6.6.2 By way of derogation from point 1(a), the relevant entities may choose not to apply security patches when the disadvantages of applying the security patches outweigh the cybersecurity benefits. The relevant entities shall duly document and substantiate the reasons for any such decision. 2.3 Software Respond Address Unauthorized Software x x x 2.4 Software Detect Utilize Automated Software Inventory Tools x x 2.5 Software Protect Allowlist Authorized Software x x 2.6 Software Protect Allowlist Authorized Libraries x x 2.7 Software Protect Allowlist Authorized Scripts x 3 Data Protection 3.1 Data Govern Establish and Maintain a Data Management Process x x x Superset 9.1 Cryptography 9.1.1 For the purpose of Article 21(2), point (h) of Directive (EU) 2022/2555, the relevant entities shall establish, implement and apply a policy and procedures related to cryptography, with a view to ensuring adequate and effective use of cryptography to protect the confidentiality, authenticity and integrity of information in line with the relevant entities' information classification and the results of the risk assessment. 3.1 Data Govern Establish and Maintain a Data Management Process x x x Subset 12.2 Handling of information and assets 12.2.1 The relevant entities shall establish, implement and apply a policy for the proper handling of information and assets in accordance with their network and information security policy, and shall communicate the policy to anyone who uses or handles information and assets. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 12 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 3.1 Data Govern Establish and Maintain a Data Management Process x x x Subset 12.2 Handling of information and assets 12.2.2 The policy shall: (a) cover the entire life cycle of the information and assets, including acquisition, use, storage, transportation and disposal; (b) provide instructions on the safe use, safe storage, safe transport, and the irretrievable deletion and destruction of the information and assets; (c) provide that equipment, hardware, software and data may be transferred to external premises only after approval by bodies authorized by management bodies in accordance with the policies, (d) provide that the transfer shall take place in a secure manner, in accordance with the type of asset or information to be transferred. 3.1 Data Govern Establish and Maintain a Data Management Process x x x Subset 12.2 Handling of information and assets 12.2.3 The relevant entities shall review and, where appropriate, update the policy at planned intervals and when significant incidents or significant changes to operations or risks occur. 3.2 Data Identify Establish and Maintain a Data Inventory x x x 3.3 Data Protect Configure Data Access Control Lists x x x Subset 11.1 Access control policy 11.1.1 For the purpose of Article 21(2), point (i) of Directive (EU) 2022/2555, the relevant entities shall establish, document and implement logical and physical access control policies for the access of persons and processes on network and information systems, based on business requirements as well as network and information system security requirements. 3.4 Data Protect Enforce Data Retention x x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 13 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 3.5 Data Protect Securely Dispose of Data x x x Subset 12.2 Handling of information and assets 12.2.2 The policy shall: (a) cover the entire life cycle of the information and assets, including acquisition, use, storage, transportation and disposal; (b) provide instructions on the safe use, safe storage, safe transport, and the irretrievable deletion and destruction of the information and assets; (c) provide that equipment, hardware, software and data may be transferred to external premises only after approval by bodies authorized by management bodies in accordance with the policies, (d) provide that the transfer shall take place in a secure manner, in accordance with the type of asset or information to be transferred. 3.6 Data Protect Encrypt Data on End-User Devices x x x Subset 9.1 Cryptography 9.1.1 For the purpose of Article 21(2), point (h) of Directive (EU) 2022/2555, the relevant entities shall establish, implement and apply a policy and procedures related to cryptography, with a view to ensuring adequate and effective use of cryptography to protect the confidentiality, authenticity and integrity of information in line with the relevant entities' information classification and the results of the risk assessment. 3.7 Data Identify Establish and Maintain a Data Classification Scheme x x Subset 12.1 Asset classification 12.1.1 For the purpose of Article 21(2), point (i) of Directive (EU) 2022/2555, the relevant entities shall lay down classification levels of all information and assets in scope of their network and information systems for the level of protection required. 3.7 Data Identify Establish and Maintain a Data Classification Scheme x x Subset 12.1 Asset classification 12.1.2 For the purpose of point 12.1.1, the relevant entities shall: (a) lay down a system of classification levels for information and assets; (b) associate all information and assets with a classification level, based on confidentiality, integrity, authenticity and availability requirements, to indicate the protection required according to their sensitivity, criticality, risk and business value, (c) align the availability requirements of the information and assets with the delivery and recovery objectives set out in their business and disaster recovery plans. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 14 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 3.7 Data Identify Establish and Maintain a Data Classification Scheme x x Subset 12.1 Asset classification 12.1.3 The relevant entities shall conduct periodic reviews of the classification levels of information and assets and update them, where appropriate. 3.8 Data Identify Document Data Flows x x 3.9 Data Protect Encrypt Data on Removable Media x x Subset 12.3 Removable media policy 12.3.1 The relevant entities shall establish, implement and apply a policy on the management of removable storage media and communicate it to their employees and third parties who handle removable storage media at the relevant entities' premises or other locations where the removable media is connected to the relevant entities' network and information systems. 3.9 Data Protect Encrypt Data on Removable Media x x Subset 12.3 Removable media policy 12.3.2 The policy shall: (a) provide for a technical prohibition of the connection of removable media unless there is an organizational reason for their use; (b) provide for disabling self-execution from such media and scanning the media for malicious code before they are used on the entities' systems; (c) provide measures for controlling and protecting portable storage devices containing data while in transit and in storage; (d) where appropriate, provide measures for the use of cryptographic techniques to protect information on removable storage media. 3.10 Data Protect Encrypt Sensitive Data in Transit x x 3.11 Data Protect Encrypt Sensitive Data at Rest x x 3.12 Data Protect Segment Data Processing and Storage Based on Sensitivity x x Subset 11.4 Administration systems 11.4.1 The relevant entities shall restrict and control the use of system administration systems. 3.12 Data Protect Segment Data Processing and Storage Based on Sensitivity x x Subset 11.4 Administration systems 11.4.2 For that purpose, the relevant entities shall: (a) only use system administration systems for system administration purposes, and not for any other operations; (b) separate logically such systems from application software not used for system administrative purposes, (c) protect access to system administration systems through authentication and encryption. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 15 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 3.13 Data Protect Deploy a Data Loss Prevention Solution x 3.14 Data Detect Log Sensitive Data Access x Subset 3.2 Monitoring and logging 3.2.3 The relevant entities shall maintain, document, and review logs. Logs shall include: (a) outbound and inbound network traffic; (b) creation, modification or deletion of users of the relevant entities' network and information systems and extension of the permissions; (c) access to systems and applications; (d) authentication-related events; (e) all privileged access to systems and applications, and activities performed by administrative accounts; (f) access or changes to critical configuration and backup files; (g) event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls; (h) use of system resources, as well as their performance; (i) physical access to facilities, where appropriate; (j) access to and use of their network equipment and devices; (k) activation, stopping and pausing of the various logs; (l) environmental events, such as flooding alarms, where appropriate. 4 Secure Configuration of Enterprise Assets and Software 4.1 Documentation Govern Establish and Maintain a Secure Configuration Process x x x Subset 6.3 Configuration management 6.3.1 The relevant entities shall establish, document, implement, and monitor configurations, including security configurations of hardware, software, services and networks. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 16 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 4.1 Documentation Govern Establish and Maintain a Secure Configuration Process x x x Subset 6.3 Configuration management 6.3.2 For the purpose of point 6.3.1, the relevant entities shall: (a) lay down configurations, including security configurations, for their hardware, software, services and networks; (b) lay down and implement processes and tools to enforce the laid down configurations, including security configurations, for hardware, software, services and networks, for newly installed systems as well as for operational systems over their lifetime. 4.1 Documentation Govern Establish and Maintain a Secure Configuration Process x x x Subset 6.3 Configuration management 6.3.3 The relevant entities shall review and, where appropriate, update configurations at planned intervals or when significant incidents or significant changes to operations or risks occur 4.2 Documentation Govern Establish and Maintain a Secure Configuration Process for Network Infrastructure x x x Subset 6.3 Configuration management 6.3.1 The relevant entities shall establish, document, implement, and monitor configurations, including security configurations of hardware, software, services and networks. 4.2 Documentation Govern Establish and Maintain a Secure Configuration Process for Network Infrastructure x x x Subset 6.3 Configuration management 6.3.2 For the purpose of point 6.3.1, the relevant entities shall: (a) lay down configurations, including security configurations, for their hardware, software, services and networks; (b) lay down and implement processes and tools to enforce the laid down configurations, including security configurations, for hardware, software, services and networks, for newly installed systems as well as for operational systems over their lifetime. 4.2 Documentation Govern Establish and Maintain a Secure Configuration Process for Network Infrastructure x x x Subset 6.3 Configuration management 6.3.3 The relevant entities shall review and, where appropriate, update configurations at planned intervals or when significant incidents or significant changes to operations or risks occur ETSI ETSI TR 104 168 V1.1.1 (2025-09) 17 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 4.3 Devices Protect Configure Automatic Session Locking on Enterprise Assets x x x Subset 11.6 Authentication 11.6.2 For that purpose, the relevant entities shall: (a) ensure the strength of authentication is appropriate to the classification of the asset to be accessed; (b) control the allocation to users and management of secret authentication information by a process that ensures the confidentiality of the information, including advising personnel on appropriate handling of authentication information; (c) require the change of authentication credentials initially, and when suspicion that the credential is revealed to an unauthorized person; (d) require the reset of authentication credentials and the blocking of users after a predefined number of unsuccessful log-in attempts; (e) terminate inactive sessions after a predefined period of inactivity; and (f) require separate credentials to access privileged access or administrative accounts. 4.4 Devices Protect Implement and Manage a Firewall on Servers x x x 4.5 Devices Protect Implement and Manage a Firewall on End-User Devices x x x 4.6 Devices Protect Securely Manage Enterprise Assets and Software x x x 4.7 Users Protect Manage Default Accounts on Enterprise Assets and Software x x x 4.8 Devices Protect Uninstall or Disable Unnecessary Services on Enterprise Assets and Software x x 4.9 Devices Protect Configure Trusted DNS Servers on Enterprise Assets x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 18 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 4.10 Devices Protect Enforce Automatic Device Lockout on Portable End- User Devices x x Subset 11.6 Authentication 11.6.2 For that purpose, the relevant entities shall: (a) ensure the strength of authentication is appropriate to the classification of the asset to be accessed; (b) control the allocation to users and management of secret authentication information by a process that ensures the confidentiality of the information, including advising personnel on appropriate handling of authentication information; (c) require the change of authentication credentials initially, and when suspicion that the credential is revealed to an unauthorized person; (d) require the reset of authentication credentials and the blocking of users after a predefined number of unsuccessful log-in attempts; (e) terminate inactive sessions after a predefined period of inactivity; and (f) require separate credentials to access privileged access or administrative accounts. 4.11 Data Protect Enforce Remote Wipe Capability on Portable End-User Devices x x 4.12 Data Protect Separate Enterprise Workspaces on Mobile End-User Devices x 5 Account Management 5.1 Users Identify Establish and Maintain an Inventory of Accounts x x x Subset 11.5 Identification 11.5.1 The relevant entities shall manage the full life cycle of identities of network and information systems and their users. 5.1 Users Identify Establish and Maintain an Inventory of Accounts x x x Subset 11.6 Authentication 11.6.4 The relevant entities shall regularly review the identities and, if no longer needed, deactivate them without delay. 5.2 Users Protect Use Unique Passwords x x x 5.3 Users Protect Disable Dormant Accounts x x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 19 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 5.4 Users Protect Restrict Administrator Privileges to Dedicated Administrator Accounts x x x Subset 11.3 Privileged accounts and system administration accounts 11.3.2 The policies referred to in point 11.3.1 shall: (a) establish strong identification, authentication such as multi-factor authentication, and authorization procedures for privileged accounts and system administration accounts; (b) set up specific accounts to be used for system administration operations exclusively, such as installation, configuration, management or maintenance; (c) individualize and restrict system administration privileges to the highest extent possible, (d) provide that system administration accounts are only used to connect to system administration systems. 5.4 Users Protect Restrict Administrator Privileges to Dedicated Administrator Accounts x x x Subset 11.6 Authentication 11.6.2 For that purpose, the relevant entities shall: (a) ensure the strength of authentication is appropriate to the classification of the asset to be accessed; (b) control the allocation to users and management of secret authentication information by a process that ensures the confidentiality of the information, including advising personnel on appropriate handling of authentication information; (c) require the change of authentication credentials initially, and when suspicion that the credential is revealed to an unauthorized person; (d) require the reset of authentication credentials and the blocking of users after a predefined number of unsuccessful log-in attempts; (e) terminate inactive sessions after a predefined period of inactivity; and (f) require separate credentials to access privileged access or administrative accounts. 5.5 Users Identify Establish and Maintain an Inventory of Service Accounts x x 5.6 Users Protect Centralize Account Management x x 6 Access Control Management ETSI ETSI TR 104 168 V1.1.1 (2025-09) 20 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 6.1 Documentation Govern Establish an Access Granting Process x x x Subset 11.2 Management of access rights 11.2.1 The relevant entities shall provide, modify, remove and document access rights to network and information systems in accordance with the access control policy referred to in point 11.1. 6.1 Documentation Govern Establish an Access Granting Process x x x Subset 11.2 Management of access rights 11.2.2 The relevant entities shall: (a) assign and revoke access rights based on the principles of need-to-know, least privilege and separation of duties; (b) ensure that access rights are modified accordingly upon termination or change of employment; (c) ensure that access to network and information systems is authorized by their owner; (d) ensure that access rights appropriately address third-party access, such as suppliers and service providers, in particular by limiting access rights in scope and in duration; EN 21 EN (e) maintain a register of access rights granted; (f) apply logging to the management of access rights. 6.2 Documentation Govern Establish an Access Revoking Process x x x Subset 10.3 Termination or change of employment procedures 10.3.2 For the purpose of point 10.3.1, the relevant entities shall: (a) include in the individual's terms and conditions of employment, contract or agreement the responsibilities and duties that are still valid after termination of employment or contract, such as confidentiality clauses; (b) put in place access control policies which ensure that access rights are modified accordingly upon the individual's termination or change of employment; (c) ensure that, after a change of employment, the employee can perform the new tasks. 6.2 Documentation Govern Establish an Access Revoking Process x x x Subset 11.2 Management of access rights 11.2.1 The relevant entities shall provide, modify, remove and document access rights to network and information systems in accordance with the access control policy referred to in point 11.1. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 21 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 6.2 Documentation Govern Establish an Access Revoking Process x x x Subset 11.2 Management of access rights 11.2.2 The relevant entities shall: (a) assign and revoke access rights based on the principles of need-to-know, least privilege and separation of duties; (b) ensure that access rights are modified accordingly upon termination or change of employment; (c) ensure that access to network and information systems is authorized by their owner; (d) ensure that access rights appropriately address third-party access, such as suppliers and service providers, in particular by limiting access rights in scope and in duration; (e) maintain a register of access rights granted; (f) apply logging to the management of access rights. 6.3 Users Protect Require MFA for Externally-Exposed Applications x x x Subset 11.7 Multi-factor authentication 11.7.1 The relevant entities shall ensure that users are authenticated by multiple authentication factors or continuous authentication mechanisms for accessing the entities' network and information systems, where appropriate, in accordance with the classification of the asset to be accessed. 6.3 Users Protect Require MFA for Externally-Exposed Applications x x x Subset 11.7 Multi-factor authentication 11.7.2 The relevant entities shall ensure that the strength of authentication is appropriate for the classification of the asset to be accessed. 6.4 Users Protect Require MFA for Remote Network Access x x x Subset 11.7 Multi-factor authentication 11.7.1 The relevant entities shall ensure that users are authenticated by multiple authentication factors or continuous authentication mechanisms for accessing the entities' network and information systems, where appropriate, in accordance with the classification of the asset to be accessed. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 22 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 6.5 Users Protect Require MFA for Administrative Access x x x Subset 11.3 Privileged accounts and system administration accounts 11.3.2 The policies referred to in point 11.3.1 shall: (a) establish strong identification, authentication such as multi-factor authentication, and authorization procedures for privileged accounts and system administration accounts; (b) set up specific accounts to be used for system administration operations exclusively, such as installation, configuration, management or maintenance; (c) individualize and restrict system administration privileges to the highest extent possible; (d) provide that system administration accounts are only used to connect to system administration systems. 6.5 Users Protect Require MFA for Administrative Access x x x Subset 11.7 Multi-factor authentication 11.7.2 The relevant entities shall ensure that the strength of authentication is appropriate for the classification of the asset to be accessed. 6.6 Software Identify Establish and Maintain an Inventory of Authentication and Authorization Systems x x Subset 11.6 Authentication 11.6.1 The relevant entities shall implement secure authentication procedures and technologies based on access restrictions and the policy on access control. 6.7 Users Protect Centralize Access Control x x Subset 11.6 Authentication 11.6.1 The relevant entities shall implement secure authentication procedures and technologies based on access restrictions and the policy on access control. 6.7 Users Protect Centralize Access Control x x Subset 11.6 Authentication 11.6.3 The relevant entities shall use state-of-the-art authentication methods, in accordance with the associated assessed risk and the classification of the asset to be accessed, and unique authentication information. 6.8 Users Govern Define and Maintain Role-Based Access Control x Superset 1.2 Roles, responsibilities and authorities 1.2.6 Roles, responsibilities and authorities shall be reviewed and, where appropriate, updated by management bodies at planned intervals and when significant incidents or significant changes to operations or risks occur. 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 11.1 Access control policy 11.1.1 For the purpose of Article 21(2), point (i) of Directive (EU) 2022/2555, the relevant entities shall establish, document and implement logical and physical access control policies for the access of persons and processes on network and information systems, based on business requirements as well as network and information system security requirements. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 23 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 11.2 Management of access rights 11.2.3 The relevant entities shall review access rights at planned intervals and shall modify them based on organizational changes. The relevant entities shall document the results of the review including the necessary changes of access rights. 6.8 Users Govern Define and Maintain Role-Based Access Control x Subset 11.3 Privileged accounts and system administration accounts 11.3.3 The relevant entities shall review access rights of privileged accounts and system administration accounts at planned intervals and be modified based on organizational changes, and shall document the results of the review, including the necessary changes of access rights. 7 Continuous Vulnerability Management 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 6.6 Security patch management 6.6.1 The relevant entities shall specify and apply procedures for ensuring that: (a) security patches are applied within a reasonable time after they become available; (b) security patches are tested before being applied in production systems; (c) security patches come from trusted sources and are checked for integrity; (d) additional measures are implemented and residual risks are accepted in cases where a patch is not available or not applied pursuant to point 6.6.2. 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 6.10 Vulnerability handling and disclosure 6.10.1 The relevant entities shall obtain information about technical vulnerabilities in their network and information systems, evaluate their exposure to such vulnerabilities, and take appropriate measures to manage the vulnerabilities. 7.1 Documentation Govern Establish and Maintain a Vulnerability Management Process x x x Subset 6.10 Vulnerability handling and disclosure 6.10.4 The relevant entities shall review and, where appropriate, update at planned intervals the channels they use for monitoring vulnerability information. 7.2 Documentation Govern Establish and Maintain a Remediation Process x x x Subset 6.10 Vulnerability handling and disclosure 6.10.3 When justified by the potential impact of the vulnerability, the relevant entities shall create and implement a plan to mitigate the vulnerability. In other cases, the relevant entities shall document and substantiate the reason why the vulnerability does not require remediation. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 24 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 7.3 Software Protect Perform Automated Operating System Patch Management x x x 7.4 Software Protect Perform Automated Application Patch Management x x x 7.5 Software Identify Perform Automated Vulnerability Scans of Internal Enterprise Assets x x Subset 6.10 Vulnerability handling and disclosure 6.10.2 For the purpose of point 6.10.1, the relevant entities shall: (a) monitor information about vulnerabilities through appropriate channels, such as announcements of CSIRTs, competent authorities or information provided by suppliers or service providers. (b) perform, where appropriate, vulnerability scans, and record evidence of the results of the scans, at planned intervals; (c) address, without undue delay, vulnerabilities identified by the relevant entities as critical to their operations; (d) ensure that their vulnerability handling is compatible with their change management and incident management procedures; (e) lay down a procedure for disclosing vulnerabilities in accordance with the applicable national coordinated vulnerability disclosure policy. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 25 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 7.6 Software Identify Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets x x Subset 6.10 Vulnerability handling and disclosure 6.10.2 For the purpose of point 6.10.1, the relevant entities shall: (a) monitor information about vulnerabilities through appropriate channels, such as announcements of CSIRTs, competent authorities or information provided by suppliers or service providers; (b) perform, where appropriate, vulnerability scans, and record evidence of the results of the scans, at planned intervals; (c) address, without undue delay, vulnerabilities identified by the relevant entities as critical to their operations; (d) ensure that their vulnerability handling is compatible with their change management and incident management procedures; (e) lay down a procedure for disclosing vulnerabilities in accordance with the applicable national coordinated vulnerability disclosure policy. 7.7 Software Respond Remediate Detected Vulnerabilities x x Superset 6.10 Vulnerability handling and disclosure 6.10.3 When justified by the potential impact of the vulnerability, the relevant entities shall create and implement a plan to mitigate the vulnerability. In other cases, the relevant entities shall document and substantiate the reason why the vulnerability does not require remediation. 8 Audit Log Management 8.1 Documentation Govern Establish and Maintain an Audit Log Management Process x x x Equivalent 3.2 Monitoring and logging 3.2.1 The relevant entities shall lay down procedures and use tools to monitor and log activities on their network and information systems to detect events that could be considered as incidents and respond accordingly to mitigate the impact. 8.1 Documentation Govern Establish and Maintain an Audit Log Management Process x x x Superset 3.2 Monitoring and logging 3.2.2 To the extent feasible, monitoring shall be automated and carried out either continuously or in periodic intervals, subject to business capabilities. The relevant entities shall implement their monitoring activities in a way which minimizes false positives and false negatives. 8.1 Documentation Govern Establish and Maintain an Audit Log Management Process x x x Superset 3.2 Monitoring and logging 3.2.7 The procedures as well as the list of assets that are being logged shall be reviewed and, where appropriate, updated at regular intervals and after significant incidents. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 26 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 8.2 Data Detect Collect Audit Logs x x x Subset 3.2 Monitoring and logging 3.2.1 The relevant entities shall lay down procedures and use tools to monitor and log activities on their network and information systems to detect events that could be considered as incidents and respond accordingly to mitigate the impact. 8.3 Data Protect Ensure Adequate Audit Log Storage x x x 8.4 Network Protect Standardize Time Synchronization x x Equivalent 3.2 Monitoring and logging 3.2.6 The relevant entities shall ensure that all systems have synchronized time sources to be able to correlate logs between systems for event assessment. The relevant entities shall establish and keep a list of all assets that are being logged and ensure that monitoring and logging systems are redundant. The availability of the monitoring and logging systems shall be monitored independently. 8.5 Data Detect Collect Detailed Audit Logs x x Subset 3.2 Monitoring and logging 3.2.3 The relevant entities shall maintain, document, and review logs. Logs shall include: (a) outbound and inbound network traffic; (b) creation, modification or deletion of users of the relevant entities' network and information systems and extension of the permissions; (c) access to systems and applications; (d) authentication-related events; (e) all privileged access to systems and applications, and activities performed by administrative accounts; (f) access or changes to critical configuration and backup files; (g) event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls; (h) use of system resources, as well as their performance; (i) physical access to facilities, where appropriate; (j) access to and use of their network equipment and devices; (k) activation, stopping and pausing of the various logs; (l) environmental events, such as flooding alarms, where appropriate. 8.6 Data Detect Collect DNS Query Audit Logs x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 27 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 8.7 Data Detect Collect URL Request Audit Logs x x 8.8 Data Detect Collect Command-Line Audit Logs x x 8.9 Data Detect Centralize Audit Logs x x Subset 3.2 Monitoring and logging 3.2.5 The relevant entities shall maintain and back up logs for a predefined period and shall store the logs at a central location and protect them from unauthorized access or changes. 8.10 Data Protect Retain Audit Logs x x Subset 3.2 Monitoring and logging 3.2.5 The relevant entities shall maintain and back up logs for a predefined period and shall store the logs at a central location and protect them from unauthorized access or changes. 8.11 Data Detect Conduct Audit Log Reviews x x Subset 3.2 Monitoring and logging 3.2.3 The relevant entities shall maintain, document, and review logs. Logs shall include: (a) outbound and inbound network traffic; (b) creation, modification or deletion of users of the relevant entities' network and information systems and extension of the permissions; (c) access to systems and applications; (d) authentication-related events; (e) all privileged access to systems and applications, and activities performed by administrative accounts; (f) access or changes to critical configuration and backup files; (g) event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls; (h) use of system resources, as well as their performance; (i) physical access to facilities, where appropriate; (j) access to and use of their network equipment and devices; (k) activation, stopping and pausing of the various logs; (l) environmental events, such as flooding alarms, where appropriate. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 28 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 8.11 Data Detect Conduct Audit Log Reviews x x Subset 3.2 Monitoring and logging 3.2.4 The logs shall be reviewed for any unusual or unwanted trends. The relevant entities shall lay down appropriate values for alarm thresholds. If the laid down values for alarm threshold are exceeded, an alarm shall be triggered, where appropriate, automatically. The responsible employee shall ensure that, in case of an alarm, a qualified and appropriate response is initiated. 8.12 Data Detect Collect Service Provider Logs x 9 Email and Web Browser Protections 9.1 Software Protect Ensure Use of Only Fully Supported Browsers and Email Clients x x x 9.2 Devices Protect Use DNS Filtering Services x x x Subset 6.7 Network security 6.7.2 For the purpose of point 6.7.1, the relevant entities shall: (a) document the architecture of the network in a comprehensible and up to date manner; (b) determine and apply controls to protect the relevant entities' internal network domains from unauthorized access; (c) configure controls to prevent accesses not required for the operation of the relevant entities; (d) determine and apply controls for remote access to network and information systems, including access by service providers; (e) not use systems used for administration of the security policy implementation for other purposes; (f) explicitly forbid or deactivate unneeded connections and services; (g) where appropriate, exclusively allow access to the relevant entities' network and information systems by devices authorized by those entities; (h) allow connections of service providers only after an authorization request and for a set time period, such as the duration of a maintenance operation; ETSI ETSI TR 104 168 V1.1.1 (2025-09) 29 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description (i) establish communication between distinct systems only through trusted channels that are isolated using logical, cryptographic or physical separation from other communication channels and provide assured identification of their end points and protection of the channel data from modification or disclosure; (j) adopt an implementation plan for the secure and full transition towards latest generation network layer communication protocols to reduce the attack surface of the networks and establish measures to accelerate such transition; (k) adopt an implementation plan for the deployment of internationally agreed and interoperable modern e-mail communications standards to secure e-mail communications to mitigate vulnerabilities linked to e- mail-related threats and establish measures to accelerate such deployment; (l) apply best practices for Internet routing security and routing hygiene of traffic originating from and destined to the network. 9.3 Network Protect Maintain and Enforce Network-Based URL Filters x x 9.4 Software Protect Restrict Unnecessary or Unauthorized Browser and Email Client Extensions x x 9.5 Network Protect Implement DMARC x x Subset 6.7 Network security 6.7.2 For the purpose of point 6.7.1, the relevant entities shall: (a) document the architecture of the network in a comprehensible and up to date manner; (b) determine and apply controls to protect the relevant entities' internal network domains from unauthorized access; (c) configure controls to prevent accesses not required for the operation of the relevant entities; (d) determine and apply controls for remote access to network and information systems, including access by service providers; ETSI ETSI TR 104 168 V1.1.1 (2025-09) 30 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description (e) not use systems used for administration of the security policy implementation for other purposes; (f) explicitly forbid or deactivate unneeded connections and services; (g) where appropriate, exclusively allow access to the relevant entities' network and information systems by devices authorized by those entities; (h) allow connections of service providers only after an authorization request and for a set time period, such as the duration of a maintenance operation; (i) establish communication between distinct systems only through trusted channels that are isolated using logical, cryptographic or physical separation from other communication channels and provide assured identification of their end points and protection of the channel data from modification or disclosure; (j) adopt an implementation plan for the secure and full transition towards latest generation network layer communication protocols to reduce the attack surface of the networks and establish measures to accelerate such transition; (k) adopt an implementation plan for the deployment of internationally agreed and interoperable modern e-mail communications standards to secure e-mail communications to mitigate vulnerabilities linked to e- mail-related threats and establish measures to accelerate such deployment; (l) apply best practices for Internet routing security and routing hygiene of traffic originating from and destined to the network. 9.6 Network Protect Block Unnecessary File Types x x 9.7 Network Protect Deploy and Maintain Email Server Anti-Malware Protections x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 31 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 10 Malware Defences 10.1 Devices Detect Deploy and Maintain Anti- Malware Software x x x Subset 6.9 Protection against malicious and unauthorized software 6.9.1 The relevant entities shall protect their network and information systems against malicious and unauthorized software. 10.1 Devices Detect Deploy and Maintain Anti- Malware Software x x x Subset 6.9 Protection against malicious and unauthorized software 6.9.2 For that purpose, the relevant entities shall in particular ensure that their network and information systems are equipped with malware detection and repair software, which is updated regularly in accordance with the with the risk assessment and the contractual agreements with the providers. 10.2 Devices Protect Configure Automatic Anti- Malware Signature Updates x x x 10.3 Devices Protect Disable Autorun and Autoplay for Removable Media x x x Subset 12.3 Removable media policy 12.3.1 The relevant entities shall establish, implement and apply a policy on the management of removable storage media and communicate it to their employees and third parties who handle removable storage media at the relevant entities' premises or other locations where the removable media is connected to the relevant entities' network and information systems. 10.3 Devices Protect Disable Autorun and Autoplay for Removable Media x x x Subset 12.3 Removable media policy 12.3.2 The policy shall: (a) provide for a technical prohibition of the connection of removable media unless there is an organizational reason for their use; (b) provide for disabling self-execution from such media and scanning the media for malicious code before they are used on the entities' systems; (c) provide measures for controlling and protecting portable storage devices containing data while in transit and in storage; (d) where appropriate, provide measures for the use of cryptographic techniques to protect information on removable storage media. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 32 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 10.4 Devices Detect Configure Automatic Anti-Malware Scanning of Removable Media x x Subset 12.3 Removable media policy 12.3.1 The relevant entities shall establish, implement and apply a policy on the management of removable storage media and communicate it to their employees and third parties who handle removable storage media at the relevant entities' premises or other locations where the removable media is connected to the relevant entities' network and information systems. 10.5 Devices Protect Enable Anti-Exploitation Features x x 10.6 Devices Protect Centrally Manage Anti-Malware Software x x 10.7 Devices Detect Use Behaviour-Based Anti-Malware Software x x 11 Data Recovery 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 4.2 Backup management 4.2.1 The relevant entities shall maintain backup copies of information and provide sufficient available resources, including facilities, network and information systems and staff. 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 4.2 Backup management 4.2.2 Based on the results of the risk assessment and the business continuity plan, the relevant entities shall lay down backup plans which include the following: (a) recovery times; (b) assurance that backup copies are complete and accurate, including configuration data and information stored in cloud computing service environment; (c) storing backup copies (online or offline) in a safe location or locations, which are not in the same network as the system, and are at sufficient distance to escape any damage from a disaster at the main site; EN 8 EN (d) appropriate physical and logical access controls to backup copies, in accordance with the information classification level; (e) restoring information from backup copies, including approval processes; (f) retention periods based on business and regulatory requirements. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 33 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 11.1 Documentation Govern Establish and Maintain a Data Recovery Process x x x Superset 4.2 Backup management 4.2.4 The relevant entities shall ensure sufficient availability of resources by at least partial redundancy of the following: (a) network and information systems; (b) assets, including facilities, equipment and supplies; (c) personnel with the necessary responsibility, authority and competence; (d) appropriate communication channels. 11.2 Data Recover Perform Automated Backups x x x 11.3 Data Protect Protect Recovery Data x x x Subset 4.2 Backup management 4.2.2 Based on the results of the risk assessment and the business continuity plan, the relevant entities shall lay down backup plans which include the following: (a) recovery times; (b) assurance that backup copies are complete and accurate, including configuration data and information stored in cloud computing service environment; (c) storing backup copies (online or offline) in a safe location or locations, which are not in the same network as the system, and are at sufficient distance to escape any damage from a disaster at the main site; EN 8 EN (d) appropriate physical and logical access controls to backup copies, in accordance with the information classification level; (e) restoring information from backup copies, including approval processes; (f) retention periods based on business and regulatory requirements. 11.3 Data Protect Protect Recovery Data x x x Superset 4.2 Backup management 4.2.3 The relevant entities shall perform regular integrity checks on the backup copies. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 34 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 11.4 Data Recover Establish and Maintain an Isolated Instance of Recovery Data x x x Subset 4.2 Backup management 4.2.2 Based on the results of the risk assessment and the business continuity plan, the relevant entities shall lay down backup plans which include the following: (a) recovery times; (b) assurance that backup copies are complete and accurate, including configuration data and information stored in cloud computing service environment; (c) storing backup copies (online or offline) in a safe location or locations, which are not in the same network as the system, and are at sufficient distance to escape any damage from a disaster at the main site; EN 8 EN (d) appropriate physical and logical access controls to backup copies, in accordance with the information classification level; (e) restoring information from backup copies, including approval processes; (f) retention periods based on business and regulatory requirements. 11.5 Data Recover Test Data Recovery x x Equivalent 4.2 Backup management 4.2.6 The relevant entities shall carry out regular testing of the recovery of backup copies and redundancies to ensure that, in recovery conditions, they can be relied upon and cover the copies, processes and knowledge to perform an effective recovery. The relevant entities shall document the results of the tests and, where needed, take corrective action. 12 Network Infrastructure Management 12.1 Network Protect Ensure Network Infrastructure is Up-to- Date x x x Subset 6.6 Security patch management 6.6.1 The relevant entities shall specify and apply procedures for ensuring that: (a) security patches are applied within a reasonable time after they become available; (b) security patches are tested before being applied in production systems; (c) security patches come from trusted sources and are checked for integrity; (d) additional measures are implemented and residual risks are accepted in cases where a patch is not available or not applied pursuant to point 6.6.2. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 35 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 12.2 Network Protect Establish and Maintain a Secure Network Architecture x x Subset 6.7 Network security 6.7.2 For the purpose of point 6.7.1, the relevant entities shall: (a) document the architecture of the network in a comprehensible and up to date manner; (b) determine and apply controls to protect the relevant entities' internal network domains from unauthorized access; (c) configure controls to prevent accesses not required for the operation of the relevant entities; (d) determine and apply controls for remote access to network and information systems, including access by service providers; (e) not use systems used for administration of the security policy implementation for other purposes; (f) explicitly forbid or deactivate unneeded connections and services; (g) where appropriate, exclusively allow access to the relevant entities' network and information systems by devices authorized by those entities; (h) allow connections of service providers only after an authorization request and for a set time period, such as the duration of a maintenance operation; (i) establish communication between distinct systems only through trusted channels that are isolated using logical, cryptographic or physical separation from other communication channels and provide assured identification of their end points and protection of the channel data from modification or disclosure; (j) adopt an implementation plan for the secure and full transition towards latest generation network layer communication protocols to reduce the attack surface of the networks and establish measures to accelerate such transition; (k) adopt an implementation plan for the deployment of internationally agreed and interoperable modern e-mail communications standards to secure e-mail communications to mitigate vulnerabilities linked to e- mail-related threats and establish measures to accelerate such deployment; ETSI ETSI TR 104 168 V1.1.1 (2025-09) 36 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description (l) apply best practices for Internet routing security and routing hygiene of traffic originating from and destined to the network. 12.2 Network Protect Establish and Maintain a Secure Network Architecture x x Superset 6.8 Network segmentation 6.8.1 The relevant entities shall segment systems into networks or zones in accordance with the results of the risk assessment referred to in point 2.1. They shall segment their systems and networks from third parties' systems and networks. 12.2 Network Protect Establish and Maintain a Secure Network Architecture x x Superset 6.8 Network segmentation 6.8.2 For that purpose, the relevant entities shall: (a) consider the functional, logical and physical relationship, including location, between trustworthy systems and services; (b) apply the same security measures to all network and information systems in the same zone; (c) grant access to a network or zone based on an assessment of its security requirements; (d) keep all systems that are critical to the relevant entities operation or to safety in one or more secured zones; (e) restrict access and communications between and within zones to those necessary for the operation of the relevant entities or for safety; (f) separate the dedicated network for administration of network and information systems from the relevant entities' operational network; (g) segregate network administration channels from other network traffic; (h) separate the production systems for the entities' services from systems used in development and testing, including backups. 12.3 Network Protect Securely Manage Network Infrastructure x x 12.4 Documentation Govern Establish and Maintain Architecture Diagram(s) x x Subset 6.7 Network security 6.7.2 For the purpose of point 6.7.1, the relevant entities shall: (a) document the architecture of the network in a comprehensible and up to date manner; (b) determine and apply controls to protect the relevant entities' internal network domains from unauthorized access; ETSI ETSI TR 104 168 V1.1.1 (2025-09) 37 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description (c) configure controls to prevent accesses not required for the operation of the relevant entities; (d) determine and apply controls for remote access to network and information systems, including access by service providers; (e) not use systems used for administration of the security policy implementation for other purposes; (f) explicitly forbid or deactivate unneeded connections and services; (g) where appropriate, exclusively allow access to the relevant entities' network and information systems by devices authorized by those entities; (h) allow connections of service providers only after an authorization request and for a set time period, such as the duration of a maintenance operation; (i) establish communication between distinct systems only through trusted channels that are isolated using logical, cryptographic or physical separation from other communication channels and provide assured identification of their end points and protection of the channel data from modification or disclosure; (j) adopt an implementation plan for the secure and full transition towards latest generation network layer communication protocols to reduce the attack surface of the networks and establish measures to accelerate such transition; (k) adopt an implementation plan for the deployment of internationally agreed and interoperable modern e-mail communications standards to secure e-mail communications to mitigate vulnerabilities linked to e- mail-related threats and establish measures to accelerate such deployment; (l) apply best practices for Internet routing security and routing hygiene of traffic originating from and destined to the network. 12.4 Documentation Govern Establish and Maintain Architecture Diagram(s) x x Subset 6.7 Network security 6.7.3 The relevant entities shall review and, where appropriate, update these measures at planned intervals and when significant incidents or significant changes to operations or risks occur. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 38 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 12.5 Network Protect Centralize Network Authentication, Authorization, and Auditing (AAA) x x 12.6 Network Protect Use of Secure Network Management and Communication Protocols x x Subset 6.7 Network security 6.7.2 For the purpose of point 6.7.1, the relevant entities shall: (a) document the architecture of the network in a comprehensible and up to date manner; (b) determine and apply controls to protect the relevant entities' internal network domains from unauthorized access; (c) configure controls to prevent accesses not required for the operation of the relevant entities; (d) determine and apply controls for remote access to network and information systems, including access by service providers; EN 14 EN (e) not use systems used for administration of the security policy implementation for other purposes; (f) explicitly forbid or deactivate unneeded connections and services; (g) where appropriate, exclusively allow access to the relevant entities' network and information systems by devices authorized by those entities; (h) allow connections of service providers only after an authorization request and for a set time period, such as the duration of a maintenance operation; (i) establish communication between distinct systems only through trusted channels that are isolated using logical, cryptographic or physical separation from other communication channels and provide assured identification of their end points and protection of the channel data from modification or disclosure; (j) adopt an implementation plan for the secure and full transition towards latest generation network layer communication protocols to reduce the attack surface of the networks and establish measures to accelerate such transition; ETSI ETSI TR 104 168 V1.1.1 (2025-09) 39 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description (k) adopt an implementation plan for the deployment of internationally agreed and interoperable modern e-mail communications standards to secure e-mail communications to mitigate vulnerabilities linked to e- mail-related threats and establish measures to accelerate such deployment; (l) apply best practices for Internet routing security and routing hygiene of traffic originating from and destined to the network. 12.7 Devices Protect Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure x x 12.8 Devices Protect Establish and Maintain Dedicated Computing Resources for All Administrative Work x Subset 6.8 Network segmentation 6.8.2 For that purpose, the relevant entities shall: (a) consider the functional, logical and physical relationship, including location, between trustworthy systems and services; (b) apply the same security measures to all network and information systems in the same zone; (c) grant access to a network or zone based on an assessment of its security requirements; (d) keep all systems that are critical to the relevant entities operation or to safety in one or more secured zones; (e) restrict access and communications between and within zones to those necessary for the operation of the relevant entities or for safety; (f) separate the dedicated network for administration of network and information systems from the relevant entities' operational network; (g) segregate network administration channels from other network traffic; EN 15 EN (h) separate the production systems for the entities' services from systems used in development and testing, including backups. 13 Network Monitoring and Defence 13.1 Network Detect Centralize Security Event Alerting x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 40 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 13.2 Devices Detect Deploy a Host-Based Intrusion Detection Solution x x 13.3 Network Detect Deploy a Network Intrusion Detection Solution x x Subset 6.7 Network security 6.7.1 The relevant entities shall take the appropriate measures to protect their network and information systems from cyber threats. 13.4 Network Protect Perform Traffic Filtering Between Network Segments x x 13.5 Devices Protect Manage Access Control for Remote Assets x x 13.6 Network Detect Collect Network Traffic Flow Logs x x 13.7 Devices Protect Deploy a Host-Based Intrusion Prevention Solution x 13.8 Network Protect Deploy a Network Intrusion Prevention Solution x 13.9 Network Protect Deploy Port-Level Access Control x 13.10 Network Protect Perform Application Layer Filtering x 13.11 Network Detect Tune Security Event Alerting Thresholds x Subset 3.4 Event assessment and classification 3.4.1 The relevant entities shall assess suspicious events to determine whether they constitute incidents and, if so, determine their nature and severity. 14 Security Awareness and Skills Training 14.1 Documentation Govern Establish and Maintain a Security Awareness Program x x x Superset 8.1 Awareness raising and basic cyber hygiene practices 8.1.1 For the purpose of Article 21(2), point (g) of Directive (EU) 2022/2555, the relevant entities shall ensure that their employees are aware of risks, are informed of the importance of cybersecurity and apply cyber hygiene practices. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 41 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 14.1 Documentation Govern Establish and Maintain a Security Awareness Program x x x Subset 8.1 Awareness raising and basic cyber hygiene practices 8.1.2 The relevant entities shall offer to all employees, including members of management bodies, an awareness raising programme, which shall: (a) be scheduled over time, so that the activities are repeated and cover new employees; (b) be established in line with the network and information security policy, topic specific policies and relevant procedures on network and information security; (c) cover cybersecurity risk-management measures in place, contact points and resources for additional information and advice on cybersecurity matters, as well as cyber hygiene practices for users. 14.1 Documentation Govern Establish and Maintain a Security Awareness Program x x x Subset 8.1 Awareness raising and basic cyber hygiene practices 8.1.3 The awareness raising program shall be tested in terms of effectiveness, updated and offered at planned intervals taking into account changes in cyber hygiene practices, and the current threat landscape and risks posed to the relevant entities. 14.1 Documentation Govern Establish and Maintain a Security Awareness Program x x x Superset 8.2 Security training 8.2.5 The program shall be updated and run periodically taking into account applicable policies and rules, assigned roles, responsibilities, as well as known cyber threats and technological developments. 14.2 Users Protect Train Workforce Members to Recognize Social Engineering Attacks x x x 14.3 Users Protect Train Workforce Members on Authentication Best Practices x x x 14.4 Users Protect Train Workforce on Data Handling Best Practices x x x 14.5 Users Protect Train Workforce Members on Causes of Unintentional Data Exposure x x x 14.6 Users Protect Train Workforce Members on Recognizing and Reporting Security Incidents x x x Subset 3.3 Event reporting 3.3.1 The relevant entities shall put in place a simple mechanism allowing their employees, suppliers, and customers to report suspicious events. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 42 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 14.6 Users Protect Train Workforce Members on Recognizing and Reporting Security Incidents x x x Subset 3.3 Event reporting 3.3.2 The relevant entities shall communicate the event reporting mechanism to their suppliers and customers and shall regularly train their employees how to use the mechanism. 14.7 Users Protect Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates x x x 14.8 Users Protect Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks x x x 14.9 Users Protect Conduct Role-Specific Security Awareness and Skills Training x x Superset 8.2 Security training 8.2.1 The relevant entities shall ensure that employees, whose roles require security relevant skill sets and expertise, receive training on network and information system security. 14.9 Users Protect Conduct Role-Specific Security Awareness and Skills Training x x Superset 8.2 Security training 8.2.2 The relevant entities shall establish, implement and apply a training program in line with the network and information security policy, topic-specific policies and other relevant procedures on network and information security which lays down the training needs for certain roles and positions based on criteria. 14.9 Users Protect Conduct Role-Specific Security Awareness and Skills Training x x Superset 8.2 Security training 8.2.3 The training referred to in point 8.2.1 shall be relevant to the job function of the employee and its effectiveness shall be assessed. Training shall take into consideration security measures in place and cover the following: (a) regular and documented instructions regarding the secure configuration and operation of the network and information systems, including mobile devices; (b) regular and documented briefing on known cyber threats; (c) regular and documented training of the behaviour when security-relevant events occur. 14.9 Users Protect Conduct Role-Specific Security Awareness and Skills Training x x Superset 8.2 Security training 8.2.4 The relevant entities shall apply training to staff members who transfer to new positions or roles which require security relevant skill sets and expertise. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 43 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15 Service Provider Management 15.1 Users Identify Establish and Maintain an Inventory of Service Providers x x x Subset 5.2 Directory of suppliers and service providers 5.2.1 The relevant entities shall maintain and keep up to date a registry of their direct suppliers and service providers, including: (a) contact points for each direct supplier and service provider; (b) a list of ICT products, ICT services, and ICT processes provided by the direct supplier or service provider to the entities. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 5.1 Supply chain security policy 5.1.1 For the purpose of Article 21(2), point (d) of Directive (EU) 2022/2555, the relevant entities shall establish, implement and apply a supply chain security policy which governs the relations with their direct suppliers and service providers in order to mitigate the identified risks to the security of network and information systems. In the supply chain security policy, the relevant entities shall identify their role in the supply chain and communicate it to their direct suppliers and service providers. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 5.1 Supply chain security policy 5.1.6 The relevant entities shall review the supply chain security policy, and monitor, evaluate and, where necessary, act upon changes in the cybersecurity practices of suppliers and service providers, at planned intervals and when significant changes to operations or risks or significant incidents related to the provision of ICT services or having impact on the security of the ICT product from suppliers and service providers occur. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 6.1 Security in acquisition of ICT services or ICT products 6.1.1 For the purpose of Article 21(2), point (e) of Directive (EU) 2022/2555, the relevant entities shall set and implement processes and procedures to manage risks stemming from the acquisition of ICT services or ICT products for components that are critical for the relevant entities' security of network and information systems, based on the risk assessment, from suppliers or service providers throughout their life cycle. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 44 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Subset 6.1 Security in acquisition of ICT services or ICT products 6.1.2 For the purpose of point 6.1.1, the processes and procedures referred to in point 6.1.1 shall include: (a) security requirements to apply to the ICT services or ICT products to be acquired; (b) requirements regarding security updates throughout the entire lifetime of the ICT services or ICT products, or replacement after the end of the support period; (c) information describing the hardware and software components used in the ICT services or ICT products; (d) information describing the implemented cybersecurity functions of the ICT services or ICT products and the configuration required for their secure operation; (e) assurance that the ICT services or ICT products comply with the security requirements according to point (a); (f) appropriate methods for validating that the delivered ICT services or ICT products are compliant to the stated security requirements, as well as documentation of the results of the validation. 15.2 Documentation Govern Establish and Maintain a Service Provider Management Policy x x Superset 6.1 Security in acquisition of ICT services or ICT products 6.1.3 The relevant entities shall review and, where appropriate, update the processes and procedures at planned intervals and when significant incidents occur. 15.3 Users Govern Classify Service Providers x x 15.4 Documentation Govern Ensure Service Provider Contracts Include Security Requirements x x Subset 1.2 Roles, responsibilities and authorities 1.2.2 The relevant entities shall require all personnel and third parties to apply network and information system security in accordance with the established network and information security policy, topic-specific policies and procedures of the relevant entities. 15.4 Documentation Govern Ensure Service Provider Contracts Include Security Requirements x x Subset 3.3 Event reporting 3.3.2 The relevant entities shall communicate the event reporting mechanism to their suppliers and customers and shall regularly train their employees how to use the mechanism. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 45 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.4 Documentation Govern Ensure Service Provider Contracts Include Security Requirements x x Subset 5.1 Supply chain security policy 5.1.4 Based on the supply chain security policy and taking into account the results of the risk assessment carried out in accordance with point 2.1 of this Annex, the relevant entities shall ensure that their contracts with the suppliers and service providers specify, where appropriate through service level agreements, specify the following, where appropriate: (a) cybersecurity requirements for the suppliers or service providers, including requirements as regards the security in acquisition of ICT services or ICT products set out in point 6.1; (b) requirements regarding skills and training, and where appropriate certifications, required from the suppliers' or service providers' employees; (c) requirements regarding background checks of the suppliers' and service providers' employees pursuant to point 10.2; (d) an obligation on suppliers and service providers to notify, without undue delay, the relevant entities of incidents that present a risk to the security of the network and information systems of those entities; (e) provisions on repair times; (f) the right to audit or right to receive audit reports; EN 10 EN (g) an obligation on suppliers and service providers to handle vulnerabilities that present a risk to the security of the network and information systems of the relevant entities; (h) requirements regarding subcontracting and, where the relevant entities allow subcontracting, cybersecurity requirements for subcontractors in accordance with the cybersecurity requirements referred to in point (a); (i) obligations on the suppliers and service providers at the termination of the contract, such as retrieval and disposal of the information obtained by the suppliers and service providers in the exercise of their tasks. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 46 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.5 Users Govern Assess Service Providers x Subset 5.1 Supply chain security policy 5.1.2 As part of the supply chain security policy referred to in point 5.1.1, the relevant entities shall lay down criteria to select and contract suppliers and service providers. Those criteria shall include the following: (a) the cybersecurity practices of the suppliers and service providers, including their secure development procedures; (b) the ability of the suppliers and service providers to meet cybersecurity specifications set by the entities; (c) the overall quality and resilience of ICT products and ICT services and the cybersecurity risk- management measures embedded in them, including the risks and classification level of the ICT products and ICT services; (d) the ability of the relevant entities to diversify sources of supply and limit vendor lock-in. 15.5 Users Govern Assess Service Providers x Subset 5.1 Supply chain security policy 5.1.5 The relevant entities shall take into account the elements referred to in points 5.1.2 and 5.1.3 as part of the selection process of new suppliers and service providers, as well as part of the procurement process referred to in point 6.1. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 47 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.6 Data Govern Monitor Service Providers x Subset 5.1 Supply chain security policy 5.1.4 Based on the supply chain security policy and taking into account the results of the risk assessment carried out in accordance with point 2.1 of this Annex, the relevant entities shall ensure that their contracts with the suppliers and service providers specify, where appropriate through service level agreements, specify the following, where appropriate: (a) cybersecurity requirements for the suppliers or service providers, including requirements as regards the security in acquisition of ICT services or ICT products set out in point 6.1; (b) requirements regarding skills and training, and where appropriate certifications, required from the suppliers' or service providers' employees; (c) requirements regarding background checks of the suppliers' and service providers' employees pursuant to point 10.2; (d) an obligation on suppliers and service providers to notify, without undue delay, the relevant entities of incidents that present a risk to the security of the network and information systems of those entities; (e) provisions on repair times; (f) the right to audit or right to receive audit reports; EN 10 EN (g) an obligation on suppliers and service providers to handle vulnerabilities that present a risk to the security of the network and information systems of the relevant entities; (h) requirements regarding subcontracting and, where the relevant entities allow subcontracting, cybersecurity requirements for subcontractors in accordance with the cybersecurity requirements referred to in point (a); (i) obligations on the suppliers and service providers at the termination of the contract, such as retrieval and disposal of the information obtained by the suppliers and service providers in the exercise of their tasks. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 48 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.6 Data Govern Monitor Service Providers x Subset 5.1 Supply chain security policy 5.1.6 The relevant entities shall review the supply chain security policy, and monitor, evaluate and, where necessary, act upon changes in the cybersecurity practices of suppliers and service providers, at planned intervals and when significant changes to operations or risks or significant incidents related to the provision of ICT services or having impact on the security of the ICT product from suppliers and service providers occur. 15.6 Data Govern Monitor Service Providers x Subset 5.1 Supply chain security policy 5.1.7 For the purpose of point 5.1.5, the relevant entities shall: (a) regularly monitor reports on the implementation of the service level agreements, where applicable; (b) review incidents related to ICT products and ICT services from suppliers and service providers; (c) assess the need for unscheduled reviews and document the findings in a comprehensible manner; (d) analyse the risks presented by changes related to ICT products and ICT services from suppliers and service providers and, where appropriate, take mitigating measures in a timely manner. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 49 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 15.7 Data Protect Securely Decommission Service Providers x Subset 5.1 Supply chain security policy 5.1.4 Based on the supply chain security policy and taking into account the results of the risk assessment carried out in accordance with point 2.1. of this Annex, the relevant entities shall ensure that their contracts with the suppliers and service providers specify, where appropriate through service level agreements, specify the following, where appropriate: (a) cybersecurity requirements for the suppliers or service providers, including requirements as regards the security in acquisition of ICT services or ICT products set out in point 6.1; (b) requirements regarding skills and training, and where appropriate certifications, required from the suppliers' or service providers' employees; (c) requirements regarding background checks of the suppliers' and service providers' employees pursuant to point 10.2; (d) an obligation on suppliers and service providers to notify, without undue delay, the relevant entities of incidents that present a risk to the security of the network and information systems of those entities; (e) provisions on repair times; (f) the right to audit or right to receive audit reports; EN 10 EN (g) an obligation on suppliers and service providers to handle vulnerabilities that present a risk to the security of the network and information systems of the relevant entities; (h) requirements regarding subcontracting and, where the relevant entities allow subcontracting, cybersecurity requirements for subcontractors in accordance with the cybersecurity requirements referred to in point (a); (i) obligations on the suppliers and service providers at the termination of the contract, such as retrieval and disposal of the information obtained by the suppliers and service providers in the exercise of their tasks. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 50 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 16 Application Software Security 16.1 Documentation Govern Establish and Maintain a Secure Application Development Process x x Subset 6.2 Secure development life cycle 6.2.1 The relevant entities shall lay down, implement and apply rules for the secure development of network and information systems, including software, and apply them when acquiring or developing network and information systems. The rules shall cover all development phases, including specification, design, development, implementation and testing. 16.1 Documentation Govern Establish and Maintain a Secure Application Development Process x x Subset 6.2 Secure development life cycle 6.2.2 The relevant entities shall: (a) carry out an analysis of security requirements at the specification and design phases of any development or acquisition project undertaken by the relevant entities or on behalf of those entities; (b) apply principles for engineering secure systems and secure coding principles to any information system development activities such as promoting cybersecurity-by-design, zero trust architectures; (c) lay down security requirements regarding development environments; (d) establish and implement security testing processes in the development life cycle; (e) appropriately select, protect and manage security test information; EN 12 EN (f) sanitise and anonymize testing data according to the risk assessment. 16.1 Documentation Govern Establish and Maintain a Secure Application Development Process x x Subset 6.2 Secure development life cycle 6.2.3 For outsourced development and procurement of network and information systems, the relevant entities shall apply the policies and procedures referred to in points 5 and 6.1. 16.1 Documentation Govern Establish and Maintain a Secure Application Development Process x x Subset 6.2 Secure development life cycle 6.2.4 The relevant entities shall review and, where appropriate, update their secure development rules at planned intervals. 16.2 Documentation Govern Establish and Maintain a Process to Accept and Address Software Vulnerabilities x x 16.3 Software Protect Perform Root Cause Analysis on Security Vulnerabilities x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 51 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 16.4 Software Identify Establish and Manage an Inventory of Third-Party Software Components x x 16.5 Software Protect Use Up-to-Date and Trusted Third-Party Software Components x x 16.6 Documentation Govern Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities x x 16.7 Software Protect Use Standard Hardening Configuration Templates for Application Infrastructure x x 16.8 Network Protect Separate Production and Non-Production Systems x x 16.9 Users Protect Train Developers in Application Security Concepts and Secure Coding x x 16.10 Software Protect Apply Secure Design Principles in Application Architectures x x Subset 6.2 Secure development life cycle 6.2.2 The relevant entities shall: (a) carry out an analysis of security requirements at the specification and design phases of any development or acquisition project undertaken by the relevant entities or on behalf of those entities; (b) apply principles for engineering secure systems and secure coding principles to any information system development activities such as promoting cybersecurity-by-design, zero trust architectures; (c) lay down security requirements regarding development environments; (d) establish and implement security testing processes in the development life cycle; (e) appropriately select, protect and manage security test information; (f) sanitise and anonymize testing data according to the risk assessment. 16.11 Software Protect Leverage Vetted Modules or Services for Application Security Components x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 52 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 16.12 Software Protect Implement Code-Level Security Checks x 16.13 Software Detect Conduct Application Penetration Testing x 16.14 Software Protect Conduct Threat Modelling x 17 Incident Response Management 17.1 Users Respond Designate Personnel to Manage Incident Handling x x x 17.2 Documentation Govern Establish and Maintain Contact Information for Reporting Security Incidents x x x Subset 3.5 Incident response 3.5.3 The relevant entities shall establish communication plans and procedures: (a) with the Computer Security Incident Response Teams (CSIRTs) or, where applicable, the competent authorities, related to incident notification; (b) with relevant internal and external stakeholders. 17.3 Documentation Govern Establish and Maintain an Enterprise Process for Reporting Incidents x x x Subset 3.3 Event reporting 3.3.1 The relevant entities shall put in place a simple mechanism allowing their employees, suppliers, and customers to report suspicious events. 17.3 Documentation Govern Establish and Maintain an Enterprise Process for Reporting Incidents x x x Subset 3.5 Incident response 3.5.3 The relevant entities shall establish communication plans and procedures: (a) with the Computer Security Incident Response Teams (CSIRTs) or, where applicable, the competent authorities, related to incident notification; (b) with relevant internal and external stakeholders. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 3.5 Incident response 3.5.1 The relevant entities shall respond to incidents in accordance with documented procedures and in a timely manner. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 3.5 Incident response 3.5.2 The incident response procedures shall include the following stages: (a) incident containment, to prevent the consequences of the incident from spreading; (b) eradication, to prevent the incident from continuing or reappearing, (c) recovery from the incident, where necessary. 17.4 Documentation Govern Establish and Maintain an Incident Response Process x x Subset 3.5 Incident response 3.5.4 The relevant entities shall log incident response activities, and record evidence. 17.5 Users Respond Assign Key Roles and Responsibilities x x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 53 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 17.6 Users Respond Define Mechanisms for Communicating During Incident Response x x Subset 3.5 Incident response 3.5.3 The relevant entities shall establish communication plans and procedures: (a) with the Computer Security Incident Response Teams (CSIRTs) or, where applicable, the competent authorities, related to incident notification; (b) with relevant internal and external stakeholders. 17.7 Users Recover Conduct Routine Incident Response Exercises x x Equivalent 3.5 Incident response 3.5.5 The relevant entities shall test at planned intervals their incident response procedures. 17.8 Users Recover Conduct Post-Incident Reviews x x Equivalent 3.6 Post-incident reviews 3.6.1 The relevant entities shall carry out post-incident reviews that shall identify the root cause of the incident and result in lessons learned to reduce the occurrence and consequences of future incidents. 17.8 Users Recover Conduct Post-Incident Reviews x x Superset 3.6 Post-incident reviews 3.6.2 The relevant entities shall ensure that post-incident reviews contribute to improving their approach to network and information security, to risk treatment measures, and to incident handling, detection and response procedures. 17.8 Users Recover Conduct Post-Incident Reviews x x Superset 3.6 Post-incident reviews 3.6.3 The relevant entities shall review at planned intervals if significant incidents led to post-incident reviews. 17.9 Documentation Recover Establish and Maintain Security Incident Thresholds x Subset 3.4 Event assessment and classifica- tion 3.4.1 The relevant entities shall assess suspicious events to determine whether they constitute incidents and, if so, determine their nature and severity. 17.9 Documentation Recover Establish and Maintain Security Incident Thresholds x Subset 3.4 Event assessment and classification 3.4.2 For the purpose of point 3.4.1, the relevant entities shall act in the following manner: (a) carry out the assessment based on predefined criteria laid down in advance, and on a triage to determine prioritization of incident containment and eradication; (b) assess the existence of recurring incidents as referred to in Article 4 of this Regulation on a quarterly basis; (c) review the appropriate logs for the purposes of event assessment and classification; (d) put in place a process for log correlation and analysis, and (e) reassess and reclassify events in case of new information becoming available or after analysis of previously available information. ETSI ETSI TR 104 168 V1.1.1 (2025-09) 54 Control Safeguard Control Asset Type Safeguard Security Function Control / Safeguard Title IG1 IG2 IG3 NIS2 Relationship NIS 2 Provision NIS 2 Requirement Category NIS2 Requirement # NIS 2 Requirement Description 18 Penetration Testing 18.1 Documentation Govern Establish and Maintain a Penetration Testing Program x x Subset 6.5 Security testing 6.5.1 The relevant entities shall establish, implement and apply a policy and procedures for security testing. 18.1 Documentation Govern Establish and Maintain a Penetration Testing Program x x Subset 6.5 Security testing 6.5.2 The relevant entities shall: (a) establish, based on the risk assessment, the need, scope, frequency and type of security tests; (b) carry out security tests according to a documented test methodology, covering the components identified as relevant for secure operation in a risk analysis; (c) document the type, scope, time and results of the tests, including assessment of criticality and mitigating actions for each finding; (d) apply mitigating actions in case of critical findings. 18.2 Network Detect Perform Periodic External Penetration Tests x x 18.3 Network Protect Remediate Penetration Test Findings x x 18.4 Network Protect Validate Security Measures x 18.5 Network Detect Perform Periodic Internal Penetration Tests x ETSI ETSI TR 104 168 V1.1.1 (2025-09) 55 Annex A: Unmapped NIS2 Provisions The following NIS2 Directive provisions NOT mapped to the Critical Security Controls Safeguards. Table A.1 Directive Requirement# Directive Provision 1.1.1 Policy on the security of network and information systems 1.1.2 Policy on the security of network and information systems 1.2.1 Roles, responsibilities and authorities 1.2.3 Roles, responsibilities and authorities 1.2.4 Roles, responsibilities and authorities 1.2.5 Roles, responsibilities and authorities 2.1.1 Risk management framework 2.1.2 Risk management framework 2.1.3 Risk management framework 2.2.1 Compliance monitoring 2.2.2 Compliance monitoring 2.2.3 Compliance monitoring 2.3.1 Independent review of information and network security 2.3.2 Independent review of information and network security 2.3.3 Independent review of information and network security 2.3.4 Independent review of information and network security 3.1.1 Incident handling policy 3.1.2 Incident handling policy 3.1.3 Incident handling policy 4.1.1 Business continuity and disaster recovery plans 4.1.2 Business continuity and disaster recovery plans 4.1.3 Business continuity and disaster recovery plans 4.1.4 Business continuity and disaster recovery plans 4.2.5 Backup management 4.3.1 Crisis management 4.3.2 Crisis management 4.3.3 Crisis management 4.3.4 Crisis management 5.1.3 Supply chain security policy 6.4.1 Change management, repairs and maintenance 6.4.2 Change management, repairs and maintenance 6.4.3 Change management, repairs and maintenance 6.4.4 Change management, repairs and maintenance 6.5.3 Security testing 6.8.3 Network segmentation 7.1.1 Policies and procedures 7.1.2 Policies and procedures 7.1.3 Policies and procedures 9.1.2 Cryptography 9.1.3 Cryptography 10.1.1 Human resources security 10.1.2 Human resources security 10.1.3 Human resources security 10.2.1 Background checks 10.2.2 Background checks 10.2.3 Background checks 10.3.1 Termination or change of employment procedures 10.4.1 Termination or change of employment procedures 10.4.2 Termination or change of employment procedures 11.1.2 Access control policy 11.1.3 Access control policy 11.3.1 Privileged accounts and system administration accounts 11.5.2 Identification ETSI ETSI TR 104 168 V1.1.1 (2025-09) 56 Directive Requirement# Directive Provision 11.5.3 Identification 12.3.3 Removable media policy 12.5.1 Return or deletion of assets upon termination of employment 13.1.1 Supporting utilities 13.1.2 Supporting utilities 13.1.3 Supporting utilities 13.2.1 Protection against physical and environmental threats 13.2.2 Protection against physical and environmental threats 13.2.3 Protection against physical and environmental threats 13.3.1 Perimeter and physical access control 13.3.2 Perimeter and physical access control 13.3.3 Perimeter and physical access control ETSI ETSI TR 104 168 V1.1.1 (2025-09) 57 Annex B: Unmapped Critical Security Control Safeguards The following Critical Security Controls Safeguards are NOT mapped to the NIS2 Directive provisions Table B.1 Safeguard Safeguard Name 1.2 Address Unauthorized Assets 1.3 Utilize an Active Discovery Tool 1.4 Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory 1.5 Use a Passive Asset Discovery Tool 2.1 Establish and Maintain a Software Inventory 2.3 Address Unauthorized Software 2.4 Utilize Automated Software Inventory Tools 2.5 Allowlist Authorized Software 2.6 Allowlist Authorized Libraries 2.7 Allowlist Authorized Scripts 3.2 Establish and Maintain a Data Inventory 3.4 Enforce Data Retention 3.8 Document Data Flows 3.1 Encrypt Sensitive Data in Transit 3.1 Encrypt Sensitive Data at Rest 3.1 Deploy a Data Loss Prevention Solution 4.4 Implement and Manage a Firewall on Servers 4.5 Implement and Manage a Firewall on End-User Devices 4.6 Securely Manage Enterprise Assets and Software 4.7 Manage Default Accounts on Enterprise Assets and Software 4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software 4.9 Configure Trusted DNS Servers on Enterprise Assets 4.1 Enforce Remote Wipe Capability on Portable End-User Devices 4.1 Separate Enterprise Workspaces on Mobile End-User Devices 5.2 Use Unique Passwords 5.3 Disable Dormant Accounts 5.5 Establish and Maintain an Inventory of Service Accounts 5.6 Centralize Account Management 7.3 Perform Automated Operating System Patch Management 7.4 Perform Automated Application Patch Management 8.3 Ensure Adequate Audit Log Storage 8.6 Collect DNS Query Audit Logs 8.7 Collect URL Request Audit Logs 8.8 Collect Command-Line Audit Logs 8.1 Collect Service Provider Logs 9.1 Ensure Use of Only Fully Supported Browsers and Email Clients 9.3 Maintain and Enforce Network-Based URL Filters 9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions 9.6 Block Unnecessary File Types 9.7 Deploy and Maintain Email Server Anti-Malware Protections 10 Configure Automatic Anti-Malware Signature Updates 11 Enable Anti-Exploitation Features 11 Centrally Manage Anti-Malware Software 11 Use Behaviour-Based Anti-Malware Software 11 Perform Automated Backups 12 Securely Manage Network Infrastructure 13 Centralize Network Authentication, Authorization, and Auditing (AAA) 13 Ensure Remote Devices Utilize a VPN and are Connecting to an Enterprise's AAA Infrastructure 13 Centralize Security Event Alerting 13 Deploy a Host-Based Intrusion Detection Solution 13 Perform Traffic Filtering Between Network Segments 14 Manage Access Control for Remote Assets 14 Collect Network Traffic Flow Logs 14 Deploy a Host-Based Intrusion Prevention Solution 14 Deploy a Network Intrusion Prevention Solution ETSI ETSI TR 104 168 V1.1.1 (2025-09) 58 Safeguard Safeguard Name 14 Deploy Port-Level Access Control 13 Perform Application Layer Filtering 14 Train Workforce Members to Recognize Social Engineering Attacks 14 Train Workforce Members on Authentication Best Practices 14 Train Workforce on Data Handling Best Practices 15 Train Workforce Members on Causes of Unintentional Data Exposure 15 Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates 15 Train Workforce on the Dangers of Connecting to and Transmitting Enterprise Data Over Insecure Networks 15 Classify Service Providers 16 Establish and Maintain a Process to Accept and Address Software Vulnerabilities 16 Perform Root Cause Analysis on Security Vulnerabilities 16 Establish and Manage an Inventory of Third-Party Software Components 17 Use Up-to-Date and Trusted Third-Party Software Components 17 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities 17 Use Standard Hardening Configuration Templates for Application Infrastructure 17 Separate Production and Non-Production Systems 17 Train Developers in Application Security Concepts and Secure Coding 16 Leverage Vetted Modules or Services for Application Security Components 16 Implement Code-Level Security Checks 16 Conduct Application Penetration Testing 16 Conduct Threat Modelling 17 Designate Personnel to Manage Incident Handling 18 Assign Key Roles and Responsibilities 18 Perform Periodic External Penetration Tests 18 Remediate Penetration Test Findings 18 Validate Security Measures 19 Perform Periodic Internal Penetration Tests ETSI ETSI TR 104 168 V1.1.1 (2025-09) 59 History Document history V1.1.1 September 2025 Publication |
2ba1876e0259e748d226a329803049d9 | 104 160 | 1 Scope | The present document will focus on presenting the results, observations and lessons learnt from the ERATOSTHENES and CERTIFY projects that tackle the complex security challenges of the Internet of Things (IoT) with a focus on managing the entire lifecycle of these networks, with a specific focus on distributed trust management and digital identity solutions, and the certification process. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 2 References | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 2.1 Normative references | Normative references are not applicable in the present document. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive). [i.2] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). [i.3] Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act). [i.4] ETSI TS 103 097 (V2.1.1): "Intelligent Transport Systems (ITS); Security; Security header and certificate formats; Release 2". [i.5] Common Criteria for Information Technology Security Evaluation. [i.6] IETF RFC 9019 (2021): "A Firmware Update Architecture for Internet of Things". [i.7] IETF RFC 8520 (2019): "Manufacturer Usage Description Specification", E. Lear, D. Romascanu, and R. Droms. [i.8] IETF RFC 7950 (2016): "The YANG 1.1 Data Modeling Language", M. Bjorklund. [i.9] IETF RFC 8259 (2017): "The JavaScript Object Notation (JSON) Data Interchange Format", T. Bray. [i.10] "CVE vulnerabilities by date", May 2022, [Online]. [i.11] NIST SP 1800-15: "Securing Small-Business and Home Internet of Things Devices", Gaithersburg, MD, USA, 2019. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 7 [i.12] S. N. Matheu-García and A. Skarmeta: "Defining the Threat Manufacturer Usage Description Model for Sharing Mitigation Actions", 2022 1st International Conference on 6G Networking (6GNet), Paris, France, 2022, pp. 1-4, doi: 10.1109/6GNet54646.2022.9830415. [i.13] S. N. M. García, A. M. Zarca, J. L. Hernández-Ramos, J. B. Bernabé, and A. S. Gómez: "Enforcing behavioral profiles through software-defined networks in the industrial Internet of Things", Appl. Sci., vol. 9, no. 21, p. 4576, October 2019. [i.14] Elliot, Mark & Domingo-Ferrer, Josep (2018): "The future of statistical disclosure control". [i.15] UN Regulation No. 155: "Uniform provisions concerning the approval of vehicles with regards to cyber security and cyber security management system". [i.16] UN Regulation No. 156: "Uniform provisions concerning the approval of vehicles with regards to software update and software updates management system". [i.17] AC 20-168: "Certification Guidance for Installation of Non-Essential, Non-Required Aircraft Cabin Systems & Equipment (CS&E)", 2010, Federal Aviation Administration. [i.18] RTCA DO-313: "Certification Guidance for Installation of Non-Essential, Non-Required Aircraft Cabin Systems and Equipment", 2008, Radio Technical Commission for Aeronautics. [i.19] ETSI EN 303 645 (V3.1.3): "CYBER; Cyber Security for Consumer Internet of Things: Baseline Requirements". [i.20] Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements and amending Regulations (EU) No 168/2013 and (EU) 2019/1020 and Directive (EU) 2020/1828 (Cyber Resilience Act). [i.21] ENISA: "EUCS - Cloud Services Scheme EUCS, a candidate cybersecurity certification scheme for cloud services", 2020. [i.22] Directive 2014/53/EU of the European Parliament and of the Council of 16 April 2014 on the harmonisation of the laws of the Member States relating to the making available on the market of radio equipment and repealing Directive 1999/5/EC (Radio Equipment Directive (RED)). [i.23] ENISA: "Good practices for security of IOT; Secure Software Development Lifecycle", 2019. [i.24] "Product Security and Telecommunications Infrastructure (PSTI) Act", 2024, United Kingdom. [i.25] IETF RFC 3748 (2004): "Extensible Authentication Protocol (EAP)", B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson and H. Levkowetz. [i.26] NIST: "NISTIR 8259 Series". [i.27] IETF: "A summary of security-enabling technologies for IoT devices", 2024. [i.28] Global Platform: "Security Evaluation Standard for IoT Platforms (SESIP)". [i.29] ETSI TS 103 645 (V3.1.1): "CYBER; Cyber Security for Consumer Internet of Things: Baseline Requirements". [i.30] ETSI TS 103 701 (V2.1.1) (2025-05): "Cyber Security (CYBER); Cyber Security for Consumer Internet of Things: Conformance Assessment of Baseline Requirements". [i.31] IoT Security Foundation: "IoTSF Security Assurance Framework", Release 3.0, 2021. [i.32] H. Kaur, and K. Kaur: "Secure elements for IoT devices: A survey", vol. 176, no. 102918, 2021. [i.33] S. P. and N. Santos: "Demystifying Arm TrustZone: A Comprehensive Survey", ACM Comput Surv., vol. 51, no. 6, pp. 1-36, 2019. [i.34] S. N. Matheu, J. L. Hernández-Ramos, A. F. Skarmeta, and G. Baldini: "A Survey of Cybersecurity Certification for the Internet of Things", ACM Comput. Surv. CSUR, vol. 53, no. 6, pp. 1-36, 2. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 8 [i.35] S. N. Matheu, A. Robles Enciso, A. Molina Zarca, D. Garcia-Carrillo, J. L. Hernández-Ramos, J. Bernal Bernabe, and A. Skarmeta: "Security Architecture for Defining and Enforcing Security Profiles in DLT/SDN-Based IoT Systems", Sensors, vol. 20, no. 7, p. 1882, January 2020. [i.36] S. N. Matheu, J. L. Hernandez-Ramos, S. Perez, and A. F. Skarmeta: "Extending MUD profiles through an Automated IoT Security Testing Methodology", IEEE Access, pp. 1-20, 2019. [i.37] H. Cavusoglu, H. Cavusoglu, and S. Raghunathan: "Efficiency of Vulnerability Disclosure Mechanisms to Disseminate Vulnerability Knowledge", IEEE Trans. Softw. Eng., vol. 33, no. 3, pp. 171-185, March 2007. [i.38] S. E. Jaouhari and E. Bouvet: "Secure firmware Over-The-Air updates for IoT: Survey, challenges, and discussions, Internet of Things", Internet Things, vol. 18, 2022. [i.39] "ENISA Baseline Security Recommendations for IoT | OWASP IoT Top 10 2018 Mapping Project". [i.40] TÜV SÜD: "ETSI EN 303 645 Cybersecurity for Consumer Internet Of Things: What It Is and Why It"s Important". [i.41] EUROCAE. [i.42] Federal Aviation Administration (FAA). [i.43] European Union Aviation Safety Agency (EASA). [i.44] Australian Government- Australian Cyber Security Centre: "IoT Code of Practice - Guidance for Manufacturers". [i.45] ENISA: "Cyber Resilience Act Requirements Standards Mapping - Joint Research Centre & ENISA Joint Analysis", 2024. [i.46] CISA: "Shifting the Balance of Cybersecurity Risk: Principles and Approaches for Security-by- Design and -Default", 2023. [i.47] CISA: "Shifting the Balance of Cybersecurity Risk: Principles and Approaches for Secure by Design Software", 2023. [i.48] Commission Implementing Regulation (EU) 2024/482 of 31 January 2024 laying down rules for the application of Regulation (EU) 2019/881 of the European Parliament and of the Council as regards the adoption of the European Common Criteria-based cybersecurity certification scheme (EUCC). [i.49] ISO/IEC 15408-1:2022: " Information security, cybersecurity and privacy protection — Evaluation criteria for IT security — Part 1: Introduction and general model". [i.50] J. L. Hernández-Ramos et al.: "Defining the Behavior of IoT Devices Through the MUD Standard: Review, Challenges, and Research Directions", in IEEE™ Access, vol. 9, pp. 126265-126285, 2021, doi: 10.1109/ACCESS.2021.3111477. [i.51] IEEE 802.11™: "IEEE Standard for Information Technology--Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks--Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 7: Enhanced Broadcast Services", in IEEE Std 802.11bc™-2023 (Amendment to IEEE Std 802.11™-2020 as amended by IEEE 802.11ax™-2021, IEEE 802.11ay™-2021, IEEE 802.11ba™-2021, IEEE 802.11az™-2022, IEEE 802.11™-2020/Cor 1-2022, IEEE 802.11bd™-2022, IEEE 802.11bb™-2023, and IEEE 802.11™-2020/Cor 2-2024), pp.1-117, 28 February 2024, doi: 10.1109/IEEESTD.2024.10456575. [i.52] ECMA-368: "High Rate Ultra Wideband PHY and MAC Standard", 2007. [i.53] IEEE 802.15.3™: "IEEE Standard for Wireless Multimedia Networks", in IEEE Std 802.15.3™-2023 (Revision of IEEE Std 802.15.3™-2016) , vol., no., pp.1-684, 22 February 2024, doi: 10.1109/IEEESTD.2024.10443750. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 9 [i.54] ETSI EN 304 632: "CYBER; CRA; Essential cybersecurity requirements for smart home products with security functionalities; Including smart door locks, security cameras, baby monitoring systems and alarm systems". [i.55] ETSI EN 304 633: "CYBER; CRA; Essential cybersecurity requirements for Internet connected toys covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or filming) or that have location tracking features". [i.56] Directive 2009/48/EC of the European Parliament and of the Council of 18 June 2009 on the safety of toys. [i.57] ETSI EN 304 634: "CYBER; CRA; Essential cybersecurity requirements for personal wearable products to be worn or placed on a human body that have a health monitoring (such as tracking) purpose and to which Regulation (EU) 2017/745 or Regulation (EU) 2017/746 do not apply; Or personal wearable products that are intended for the use by and for children". [i.58] Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, amending Directive 2001/83/EC, Regulation (EC) No 178/2002 and Regulation (EC) No 1223/2009 and repealing Council Directives 90/385/EEC and 93/42/EEC. [i.59] Regulation (EU) 2017/746 of the European Parliament and of the Council of 5 April 2017 on in vitro diagnostic medical devices and repealing Directive 98/79/EC and Commission Decision 2010/227/EU. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 3 Definition of terms, symbols and abbreviations | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 3.1 Terms | For the purposes of the present document, the following terms apply: commissioning: process in which the device boots and connects to the target security context, establishing the necessary security verifications and materials for operating within the context cyber intelligence: information gathering and analysis activity aimed at identifying, tracking/predicting capabilities and intentions/activities of hostile actors in the cybersecurity domain Cyber Threat Intelligence (CTI): evidence-based knowledge (including context, mechanisms, indicators, implications, and actionable advice) about an existing or emerging threat that can be used to make decisions regarding similar threats pre-provisioning: process in which the device undergoes initial configuration and security material installation during its first boot at the manufacturer's premises security lifecycle: continuous process that encompasses identifying, protecting, detecting, responding to, and recovering from cybersecurity threats zero-trust: approach that avoids inherent trust assumptions, but instead relies on the continuous evaluation and consideration of the entities' trustworthiness, e.g. for authorization processes |
2ba1876e0259e748d226a329803049d9 | 104 160 | 3.2 Symbols | Void. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization and Accounting ACL Access Control Lists ETSI ETSI TR 104 160 V1.1.1 (2025-10) 10 API Application Programming Interface ARM Advanced RISC Machines CA Certification Authority CAV Connected and Automated Vehicle CC Common Criteria CCS Connected Cabin System CERT Computer Emergency Response Team CERTIFY aCtive sEcurity foR connecTed devIces liFecYcles COPD Chronic Obstructive Pulmonary Disease COTS Commercial Off the Shelf CP-ABE Ciphertext Policy Attribute-Based Encryption CRA Cyber Resilience Act CSIRT Computer Security Incident Response Team CTI Cyber Threat Intelligence CVSS Common Vulnerability Scoring System DAA Direct Anonymous Attestation DID Decentralized IDentifiers DLT Distributed Ledger Technologies EAP Extensible Authentication Protocol ECU Engine Control Unit ENISA European Union Agency for Cybersecurity ERATOSTHENES sEcuRe manAgemenT of iOt deviceS lifecycle THrough idENtities, trust, and distributEd ledgerS EUCS European Cybersecurity Certification Scheme for Cloud Service GB Gigabytes GDPR General Data Protection Regulation GLOSA Green Light Optimized Speed Advisory HW HardWare IdM Identity Management IDS Intrusion Detection System IoC Indicator of Compromise IoT Internet of Things IoTSF IoT Security Foundation ISACs Information Sharing and Analysis Centers low-SWaP-C Size, Weight, Power and Cost MSPL Medium-level Security Policy Language MUD Manufacturer Usage Description NIS Network and Information Systems NIST National Institute for Standards and Technology OBU On-Board Unit OTA Over-The-Air PDP Policy Decision Point PEP Policy Enforcement Point PHG Personal Health Gateway PKI Public Key Infrastructure PP-CTI Privacy-Preserving Cyber Threat Intelligence PSTI Product Security and Telecommunications Infrastructure PUF Physical Unclonable Function RED Radio Equipment Directive SaaS Software as a Service SDC Statistical Disclosure Control SE Secure Element SESIP Security Evaluation Standard for IoT Platforms SIEM Security Information and Event Management SOAR Security Orchestration, Automation, and Response SOCs Security Operations Centres SSI Self-Sovereign Identity SW SoftWare TB Terabytes TEE Trusted Execution Environment TMB Trust Management and Broker TMRA Threat Modelling and Risk Assessment ETSI ETSI TR 104 160 V1.1.1 (2025-10) 11 UN United Nations URL Uniform Resource Locator V2I Vehicle-to-Infrastructure V2V Vehicle-to-Vehicle V2X Vehicle-to-Everything VC Verifiable Credentials VM Virtual Machine VP Verifiable Presentations W3C World Wide Web Consortium YANG Yet Another Next Generation |
2ba1876e0259e748d226a329803049d9 | 104 160 | 4 Introduction | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 4.1 Key IoT Security Challenges | The widespread adoption of Internet of Things (IoT) devices has introduced a complex security landscape. With a vast number of interconnected devices, the attack surface expands significantly, demanding robust security on both individual devices and the entire network. However, many IoT devices have limited processing power and memory, hindering the implementation of strong security measures. Additionally, the lack of built-in security features and outdated firmware make them susceptible to unauthorized access, data breaches, and manipulation. The heterogeneity of devices, protocols, and platforms interweaved in IoT scenarios leads to interoperability challenges and makes it difficult to establish consistent security processes. Weak regulations and the tendency of some manufacturers to prioritize functionality over security exacerbate these issues. Beyond these foundational challenges, securing IoT networks and devices requires addressing several critical areas, such as: • Security visibility: Security gaps are extremely hard to be detected, to remediate, and to address on time. This is especially true in IoT ecosystems as the large variety of devices, specifications, and vendors makes it difficult to gain clear views into their security posture. • Effective information sharing: The effectiveness of information sharing with incident response teams (CERTs/CSIRTs) falls short, hindering collective efforts to address threats. This compounds with other security challenges, as the complexity of the systems make the building of collective defences critical to achieve meaningful security levels. • Lifecycle management: IoT devices present specific challenges in terms of their lifecycle management (shown in Figure 1). A comprehensive solution should cover the distinct phases, from initial pre-provisioning of security mechanisms during device manufacturing, to its secure deployment, operation, and decommission in target systems. • Common trust enforcement mechanisms: Trust relies on the different expected behaviours of people, data, information, or processes. However, establishing trust is not easy in autonomous systems like IoT, and it becomes critical to be able to model, monitor and quantify trust and its related events in a way that can be understood by artificial agents becomes critical. • Identity and privacy framework: managing the identities of IoT devices presents challenges due to their hardware characteristics, autonomous functioning, and complex lifecycles. Current practices often lack information in terms of how device and user privacy is protected, and how this interacts with the security of the system through fine-grained access control. • Firmware updates: Firmware and security updates are infrequent, difficult, or even impossible in large IoT networks. The outdated firmware and exploitable vulnerabilities that attackers may leverage exacerbates the difficulty of addressing other security challenges. • Training and automated protocol adoption: Humans are the weakest point in the lifecycle chain, as they build, test, deploy and use IoT. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 12 Figure 1: Lifecycle phases |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5 ERATOSTHENES | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5.1 Overview | The ERATOSTHENES project tackles the complex security challenges of the IoT with a focus on managing the entire lifecycle of these networks through distributed trust management and digital identity solutions. The focal point is the development of a Trust and Identity Management Framework for IoT devices, distributed and operating across the entire network, addressing different steps of the lifecycle of the participant devices. Additionally, the framework is auditable, enabling transparent tracking and verification of actions. Finally, it is privacy-respectful, prioritizing user data privacy and control. By effectively managing the lifecycle of IoT devices, this framework aims to strengthen trust, identities, and overall resilience within the IoT ecosystem. Importantly, the framework is aligned with relevant regulations such as the NIS2 Directive [i.1], the GDPR [i.2], and the Cybersecurity Act [i.3], addressing topics such as CTI sharing for improved cyber-threat handling, privacy-aware identity management and data processing, or device cybersecurity profiles. Overall, the objectives of the project can be summarized as follows: • Design a reference architecture, components, and protocols for IoT lifecycle management, through the pillars of identity and trust in security domains, suited for resource-restricted environments, critical and industrial applications. • Design of a decentralized, scalable, efficient and privacy-preserving IoT identity management to conciliate the requirements of self-sovereignty and privacy preservation in a distributed, interoperable, and transparent trust model. • Design and development of a lightweight, distributed, and dynamic Trust Management solution to enhance the trust in large-scale distributed networks of heterogeneous IoT devices, covering each layer and cross-layer of the network. • Support the solution and build the overall governance layer of the trust network on novel Distributed Ledger Technologies, enabling decentralization of the solution within domains along with trustworthy information sharing (such as CTI data) in the whole ecosystem. • Integrate and validate the approach through real-world pilots relevant to the tackled challenges, namely intelligent transport systems, e-health scenarios, and Industry 4.0. • Deliver knowledge via dissemination and capacity building, supporting the enforcement of the Cybersecurity Act and standardization activities. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 13 5.2 ERATOSTHENES Architecture for IoT lifecycle management |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5.2.0 Introduction | Figure 2: ERATOSTHENES architecture The ERATOSTHENES architecture and concept have been carefully developed to be adaptable across multiple industrial domains. The architecture is designed to accommodate different use cases, specific requirements, and unique characteristics of each application environment. This flexibility enables its implementation in various scenarios, including transport infrastructures and vehicles, smart devices, personalized health devices, and more. The architecture envisions an environment with multiple independent (but potentially collaborating through information exchange) domains, serving to group operations depending on physical or logical criteria. The components related to the architecture will act within the device, pertain to a specific domain, or operate across multiple ones to enable global functionalities. ERATOSTHENES establishes identity management based on self-sovereign principles, with SSI Agents in devices managing credentials to enable security and privacy and supporting infrastructural components like SSI Management. Physical Unclonable Function (PUF) based authentication is considered to further enhance the security of identification and cryptographic fingerprinting. The Trust Management & Broker (TMB) groups key components for achieving a trust framework based on zero-trust principles. Devices will interact with the trust framework through Trust Agents and the TEE will be an anchor of trust for devices along with their identity. The TMB's components for IDS, monitoring, threat modelling, and risk assessment will perform the necessary monitoring and evaluation tasks for maintaining an updated trust network for devices. The use of services will require continuous authorization both through identity and trust policies, with the PDP and PEP serving to delegate the process to the domain infrastructure when necessary. Along with the identity and trust, the architecture also tackles the management of devices' lifecycles through supporting tools like those for backup, recovery, secure data storage, and management (actuation tools, management and recovery, data protector) and the use of MUD files and CTI sharing both for device's security configurations and coordinated responses to cyber-threats. The whole ecosystem is enabled by Distributed Ledger Technologies (DLTs) acting as verifiable data registries enriched with smart contracts. Particularly, specific information (such as related to CTI, identity, etc.) can be carried out across domains through inter-DLT to allow collaboration that helps achieve a global ecosystem with enhanced security. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 14 With this series of components, the architecture tackles challenges in the pre-provisioning, commissioning (or enrolment), and operational phases. In the former, providing a root of trust for the identification of the device, i.e. a root identity, and additional identity and security configuration data. Then, during commissioning these artifacts will be used to enrol a device in the security context of operation. The enrolment process enables privacy-preserving authentication and authorization processes, monitoring, and trust evaluation of devices during their operational phase. This is expanded in the following subsections. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5.2.1 Pre-provisioning | The device undergoes initial configuration and security material installation during its first boot at the manufacturer's premises. This process has three key outcomes. First, the device receives and securely stores its root identity material, which serves as a foundation for authentication. This material can range from a simple pre-shared key (e.g. as used in EAP AAA) to a hardware-based root of trust for Trusted Execution Environments or advanced techniques like Physical Unclonable Function (PUF)-based fingerprints. Second, the device is provisioned with security-related configurations, including supported technologies and potential security profiles. Finally, device certificates are generated and installed, providing attributes that define the device's characteristics and identity. These certificates can be linked to the device's root identity, ensuring a secure and verifiable authentication process. Figure 3: Schematic view of fist pre-provisioning process In ERATOSTHENES, the Identity Management (IdM) solution uses Physical Unclonable Functions (PUFs) as the primary mechanism for device identification, acting as a root of trust for cryptographic fingerprinting. Figure 3 illustrates the initial pre-provisioning process. During this phase, the device undergoes PUF-based authentication enrolment, which involves installing a PUF authentication client and generating the corresponding cryptographic fingerprint. The device is then registered with the manufacturer's PUF authentication servers, establishing its root identity. Additionally, the device's security configurations are set up by creating an extended Manufacturer Usage Description (MUD) file. This file is stored on the manufacturer's MUD file server, and the device receives a URL linked to its identity through the PUF key material. Traditional identity certificates from PKI certification services are also installed, serving as an attribute source. The specific details of these certificates will vary based on the use case. For example, in scenarios like Intelligent Transport Systems, one of the project's pilots, the certificates may adhere to ETSI TS 103 097 [i.4]. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 15 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5.2.2 Commissioning | The next phase begins when the device first boots and connects to the target security context. To interact with the domain infrastructure, the device should perform a bootstrapping process that authenticates its root identity. The domain should have a trust relationship with the manufacturer, either directly through its identity service or implicitly, such as by trusting a public signing key. During this step, a domain identification key may be generated, acting as a root identity for use exclusively within the security context. Another important aspect of Identity Management (IdM) is enabling privacy-preserving authentication and authorization. In many use cases, authorization does not only require identification, but also the proof of certain identity attributes. Access control typically depends on conditions tied to these attributes. The framework follows self-sovereign identity principles, where subjects retain control of their identity. Therefore, the device's enrolment includes the issuance of credentials for attribute verification in the security context. This is done through identity proofs, typically in the form of certificates obtained during the initial manufacturer pre-provisioning. The final steps to be carried out during enrolment depart from the field of identity but are crucial for collaborative IoT scenarios and data spaces. Devices may publish their planned behaviour within the security context, such as offering services, data, or associated policies. This enables interactions during the operational phase and may influence how the authorization process is conducted. The result will be the full integration of the device into the trust management framework in the domain, enabling its monitoring and trustworthiness evaluation. Figure 4: Commissioning, enrolment in a security domain In ERATOSTHENES, the initial boot in the security domain (see Figure 4) is performed through the PUF authentication process. In this case, the process requires active involvement of the PUF authentication servers in the manufacturer's premises. As a result of this process, the device, through its SSI Agent, generates an identity for use within the domain and registers a Decentralized Identifier (DID) for identification. The SSI Agent interacts with issuers in the SSI Management infrastructure to facilitate the issuance process. This includes the identity proofing of the device, which may use the PKI certificates obtained by the device. After this, the device will have Verifiable Credentials (VCs) stored in its wallet. These VCs can be generated using a p-ABC scheme, that provides the opportunity for devices to later present them through the derivation of zero-knowledge proofs that reveal only the specific data necessary for an authentication process, improving the privacy achieved by the solution. To ensure secure usage and storage, the device's Trusted Execution Environment (TEE), particularly the Data Protector component, is used (note that sensitive material such as VCs or secret keys will be stored within the Data Protector, which is omitted from the diagram to avoid cluttering). At this point, the device has completed the identity enrolment process, but it may be necessary depending on the use case to link the device identity with the identity of its owner or manager within the domain (e.g. the security manager of a shop floor). ETSI ETSI TR 104 160 V1.1.1 (2025-10) 16 However, there is an additional process to complete the full enrolment within the ERATOSTHENES domain, involving the trust framework and particularly the Trust Manager & Broker. First, the security configurations are retrieved, analysed, and applied within the trust management component. This step initiates trust score calculations, risk assessment, monitoring, and other processes within the component. Note that the component is comprised of multiple subcomponents that will carry out the complex processes, such as Intrusion Detection Systems for monitoring, Risk Assessment and Threat Modelling engines, and a MUD Management module. The results, such as the initial trust score calculations and their rationale, are published on the DLT, which serves as the project's verifiable data registry. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 5.2.3 Operational Phase | Once the enrolment has been completed, devices are ready to interact with other entities in the security context. The framework defined in ERATOSTHENES follows the principles of self-sovereignty. That is, devices are in control of their identity materials, and no other parties should play an active role during an authentication process. As for the actual authorization, the project considers two scenarios that are common in practice. In both cases, the authentication check is equivalent: the device generates a Verifiable Presentation containing the information requested by the attribute-based policy. Outside the policy check, the process varies depending on who oversees verifying the result. On the one hand, the project envisions a fully decentralized approach, where the service provider is the one that assesses the requesting device. On the other hand, the service provider may delegate the authorization check to the infrastructure with the traditional roles of Policy Decision Point (PDP) and Policy Enforcement Point (PEP). Slight variations, like the service provider acting as its own PEP, are easily adapted from the framework. The main advantage of the centralized approach is that the more resource-intensive authorization process is carried out less frequently, with the verifier delegating the task to the infrastructure. This enables service providers with limited resources, or those that prefer to rely fully on the infrastructure, to integrate seamlessly into the framework. Additionally, it maintains backward compatibility with many existing IoT scenarios that already use a PDP/PEP infrastructure. However, this approach places a greater burden on the server-side and diverges from decentralization, as it requires stronger trust assumptions in the infrastructure. Despite this, both approaches can typically coexist, offering a range of viable options. Figure 5: Service usage authorization check ETSI ETSI TR 104 160 V1.1.1 (2025-10) 17 Figure 6: Service usage decentralized authorization alternative schematic view Thus, in ERATOSTHENES (see Figure 5) devices can perform authentication/authorization processes using the VCs retrieved during enrolment. Participants can retrieve policies from the DLT and generate Verifiable Presentations (VP) that include the necessary information to fulfil the policy through their SSI Agent. Additionally, they may check the current trust evaluation of the target service to inform the decision on continuing with the process or not. Due to the p-ABC scheme, the authentication process can be done in a zero-knowledge fashion, ensuring minimal disclosure and non-link-ability of the revealed data. By generalizing the process by enabling the PDP to generate authorization tokens that are valid for the mid to long term, reducing the frequency of complete authorization processes. These tokens are then checked by the PEP when accessing a service. Alternatively, the use of a direct communication flow is also supported by the solution, as shown in Figure 6. In both cases, according to the zero-trust approach of the framework, the current trust score of the involved parties is checked as an additional source of information for authorization decisions. The DLT plays the role of a verifiable data registry for identity and trust information, serving as a decentralized enabler for the trustworthiness in the process. Note on flexibility of the presented flows: The previous subsections present a solution covering the steps identified in the ERATOSTHENES framework up to device's actively participating in the domain. Throughout the discussion, it has established specific solutions, but it is worth noting that there exist alternatives with trade-offs. For instance, the adoption of a full-fledged p-ABC scheme brings remarkable privacy advantages but also introduces limitations e.g. in terms of efficiency. In some scenarios, selective disclosure might be enough to cover the privacy requirements. In other cases, it might not be possible to rely on schemes more complex than plain forwarding of credentials because of limiting resource constraints of the involved devices. Similarly, PUF-based authentication gives high guarantees against forgery or attacks on devices but imposes strict requirements on hardware that simpler solutions like pre-shared keys or plain certificates avoid. This need for flexibility is not only important for instantiations of the framework in different use cases. The vast heterogeneity within IoT environments in terms of conditions or device types makes the flexible application of technologies a key requirement in every deployment. Otherwise, solutions will achieve poor security or privacy results or become impractical as many devices will not be able to participate. This means the ideas of protection profiles enforced for specific targets (ISO/IEC 15408-1 [i.49]) are a compelling avenue for comprehensive solutions. It enables the creation of "flavours'' of security/privacy, which will be applied depending on the characteristics or needs of each device and domain of use. Accordingly, while the flows presented are the main solution in the ERATOSTHENES architecture, some variations are foreseen and planned. Precisely, the application of specifications such as the W3C VCs allows organizations to achieve transparent interchangeability between different solutions that offer trade-offs on security, privacy, and efficiency during an attribute-based authorization process without changes to flows, implementations, or models. Similarly, not all devices will be PUF-enabled, so alternative approaches for the root identity like pre-shared keys may be considered as an alternative. In this sense, the zero-trust approach of the framework helps to accommodate such changes more smoothly. The device's trustworthiness will be continuously evaluated and considered for authorization. Particularly, during enrolment, their characteristics and supported technologies will be considered to assign trust scores. A key tool for moving towards the security profile paradigm and aligning with Cyber Resilience Act (CRA) [i.20] is the extended MUD files, which can be assigned to each device to establish some security configurations that will be considered during enrolment and operation (see clause 9 for more information). ETSI ETSI TR 104 160 V1.1.1 (2025-10) 18 Particularly, the recovery processes in ERATOSTHENES cover multiple scenarios related to a device's lifecycle such as partial compromise or malfunction, actuations against potential threats even before they are realized, or substitution for a new device. The process may be triggered internally by the monitoring tools, or coming from the threat and mitigation sharing framework of the project as expanded in clause 7. Then, depending on the specifics of the issue, a multi-stage recovery process will be carried out. First, if necessary, new software will be securely deployed on the device (e.g. an upgraded version of a firmware that patches a known vulnerability). Then, recovery of identity material will be carried out, protected through the use of Data Protector and advanced cryptographic techniques such as proxy re-encryption. Lastly, the trust context of the device within the security domain will be updated and configured in the device to ensure its readiness to participate in the domain as part of its operation. The DLT is used as a verifiable registry to support these processes in a decentralized way. Figure 7: Generic device recovery process |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6 CERTIFY | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.1 Overview | The Horizon Europe project CERTIFY (active security for connected device lifecycles) aims to provide a methodological, technological, and organizational framework that ensures security throughout the lifecycle of connected devices. These efforts align with current EU regulations, particularly the CRA, positioning the project to not only demonstrate compliance but also to address real-world security challenges. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 19 CERTIFY's goal is to provide to IoT stakeholders (e.g. auditors, manufacturers, users, Information Sharing and Analysis Centers (ISACs), with tools and strategies that foster a high level of security. The project takes a collaborative and decentralized approach, helping stakeholders identify, assess, and respond to security threats throughout the lifecycle of connected devices. A key point of the CERTIFY approach is the sharing of security information and evidence among relevant parties, allowing for continuous risk assessments and faster responses to new vulnerabilities. CERTIFY's methodology addresses the full lifecycle of connected devices - from initial design and risk assessment to secure decommissioning or repurposing. Rooted in the principle of security by design [i.46], [i.47], the approach integrates security protocols and cryptographic controls from the beginning. By embedding these measures early in the design and development phases, CERTIFY ensures that devices are equipped to resist threats before they are deployed. After deployment, the framework supports secure commissioning, continuous monitoring, and adaptive reconfiguration to preserve device integrity and resilience against emerging vulnerabilities. This proactive strategy reduces real-time risks and limits the need for costly, reactive fixes. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2 CERTIFY Framework | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.0 Introduction | The CERTIFY architecture, as depicted in Figure 8, is organized into six "domains" or "planes" with dedicated functionalities. The embedded device plane provides security services built on top of hardware functionalities to instantiate and maintain a secure environment. It characterizes the IoT platform through the CERTIFY API and services, including for instance support for operations such as configuration, bootstrapping, upgrading, and monitoring. These high-level services are offered by the low-level security enablers for the IoT device, the Secure Element (SE) [i.32] and the Trusted Execution Environment (TEE) [i.33]. The access to such enablers is abstracted and made accessible through a low-level API. Figure 8: CERTIFY Architecture ETSI ETSI TR 104 160 V1.1.1 (2025-10) 20 The Domain enforcement plane includes services for the secure deployment of the device within the domain and the application of updates on the device. One core component of this plane is the Secure Enrolment module, responsible for the registration of the devices in the domain and the issuance of cryptographic material as the basis for domain identities. The secure update and upgrade agent provides a graphical user interface where security administrators can visualize registered software and devices, upload the software to the repository, and trigger the secure Over-The-Air (OTA) software update process. The Domain orchestration plane provides coordination functionalities within the domain, and its main component is the Device and Domain Manager, that provides high-level management IoT devices within a security domain. In particular, it coordinates the enforcement and reconfiguration of IoT devices. All the configurations (e.g. policies applied, version of updates) are stored in the Inventorying and Registry, which provides trustworthy data storage e.g. through DLTs. The Domain runtime sensors and monitoring plane offers software-based solutions for monitoring, detection, and decision functionalities based on the information received from the device and other domain components. The Network Bootstrapping Monitor and the Intrusion Detection System (IDS) receive data from the CERTIFY API in the IoT device regarding the network activity in different phases of the lifecycle (bootstrapping and operation). Alerts are sent to the SIEM-SOAR (Security Information and Event Management - Security Orchestration, Automation and Response), which aggregates data and carries out complex analysis. The Cyber Threat Intelligence (CTI) plane provides services for ensuring privacy-preserving sharing of security information, such as vulnerabilities, mitigations or recommended configurations. The Privacy-Preserving CTI (PP-CTI) system is a central tool here, anonymizing sensitive data and attributes in cyber threat reports. For responding to identified threats, the CTI plane combines the MUD [i.7] with the Threat MUD server [i.11] respectively as default secure configuration, and threat and mitigation signalling mechanisms. Finally, the external plane integrates all the manufacturer services that, even if not strictly part of the framework, are exploited by CERTIFY. In particular, it includes services for security assessment and certification, CTI sharing, device authentication, and MUD generation and storage. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.1 Pre-provisioning | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.1.1 Design Phase | In this phase, the device is designed, developed, programmed, and tested, establishing its initial security posture. All actors in the supply chain - component designers, integrators, and software developers - are involved, while the manufacturer conducts the initial security evaluation. However, as new threats and vulnerabilities continue to emerge, defining a fixed, standardized cybersecurity evaluation and certification process becomes increasingly difficult. This evolving threat landscape demands agile and dynamic approaches to maintain product security throughout its lifecycle. As a result, continuous assessment and the use of dynamic labels that reflect a device's current security status in real time are essential. While current certification schemes [i.48] acknowledge this need for adaptability, frameworks like Common Criteria (CC) [i.5] still require full recertification for any security change, leading to significant time and financial costs [i.34]. To support security by design and enable dynamic certification, CERTIFY proposes a model-based evaluation and certification approach. This method allows security to be tested from the early design stages and supports automation of the evaluation process by integrating security testing with risk assessment. The approach is implemented through the Cyberpass tool (https://www.cyber-pass.eu/) - a cloud-based platform that interprets security requirements and guides the evaluation process. It begins with a self-declaration or self-assessment step, enabling manufacturers to respond to a tailored questionnaire based on relevant security criteria. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 21 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.1.2 Pre-provisioning of security material | While security assessment results are typically used only for device certification, CERTIFY leverages this information to enhance device deployment and operation. Specifically, the evaluation results are embedded into a behavioural profile that maps different security levels to recommended operational policies. This profile limits the device's behaviour to a defined set of actions, thereby reducing its attack surface and enabling the detection of anomalous activity during runtime. CERTIFY's behavioural profile extends the Manufacturer Usage Description (MUD) standard [i.35] and [i.36]. The extended MUD profile is digitally signed by the Certification Authority (CA) and hosted on a MUD server, making it accessible to clients that buy and deploy the device. The MUD URL and root cryptographic identity material are stored in the device to facilitate secure deployment. To support this process, CERTIFY utilizes strong isolation mechanisms - such as Secure Elements (SE) and Trusted Execution Environments (TEE) - enabled by open hardware architectures and trusted computing standards. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.2 Commissioning | The commissioning phase starts when the device is installed and configured in a certain context. This usually consists of a set of procedures in which a device joins a network in a certain security domain. During the process, the cryptographic material installed during the previous phase is used to derive dynamic credentials and keys to be used during its operation. Extended MUD files were integrated into CERTIFY's enhanced commissioning to enable the safe deployment of configurations prior to the device joining the domain. Therefore, the device will not be allowed to interact with other components or to access network resources until it is not properly identified, configured, and authenticated, ensuring that the network will not be compromised once the device will access to it. In the first stages, the device requests to start the bootstrapping in the domain. CERTIFY leverages the Extensible Authentication Protocol (EAP) [i.25] to authenticate the device and generate domain keys. Moreover, CERTIFY relies on the extended MUD of the device, which is securely retrieved and translated in the MUD manager during the authentication process, to securely configure the device. The results are used during the security configuration of the device. Additionally, CERTIFY also checks that the device type is authorized based on its fingerprint. While attempting to join an IoT network, each device type exhibits a characteristic fingerprint. The network bootstrapping monitor exploits such a behavioural feature of the device to build a monitor that can pose constraints on the devices that can join the network, as well as request the enforcement of specific rules. This behavioural fingerprint can be created by the manufacturer and included as part of the extended MUD file designed in CERTIFY. For completing the enrolment in the domain, high-end devices need to verify their correct state based on the policies defined in the MUD. CERTIFY leverages the DAA (Direct Anonymous Attestation) protocol to authenticate the high-end device and generate appropriate policies for attestation. The DAA allows verifying the correct state of the device based on this verifiable evidence and helps to decide whether the network should allow or not the device to join. Once deployed, the device can generate dynamic credentials based on its identity for securely communicating with the entities inside the domain. All the information about authorized network devices, configurations, identity certificates and upgrades are stored in the Device Inventory and Registry. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.3 Operational Phase | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.3.0 General | In the operational phase, continuous monitoring of the device is essential due to evolving security threats and vulnerabilities that were not anticipated at design time. As a device's security posture evolves, it may require reassessment and even recertification. Within the CERTIFY framework, monitoring components collect data from IoT devices to detect vulnerabilities and trigger appropriate mitigation actions. Runtime attestation and the Integrity Monitor verify that certified security properties are maintained, while an IDS analyses network traffic in real time to identify potential threats. Detection rules are regularly updated with new signatures and can be tailored to specific user or customer needs. More complex analysis is handled by the Security Information and Event Management (SIEM) - Security Orchestration, Automation, and Response (SOAR) component, which processes events from both the network and the device, correlating them to detect sophisticated threats. The Device and Domain Manager then coordinates enforcement of mitigations and updates, linking runtime detection to recommended actions from manufacturers, threat databases, or certification authorities. CERTIFY uses an extended Threat MUD to support this process, enabling the system to block network access or reconfigure the device in response to critical risks. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 22 CERTIFY fosters continuous information sharing among stakeholders. It integrates external intelligence on vulnerabilities, patches, and zero-day threats with domain-specific insights. This is done through the Privacy-Preserving CTI (PP-CTI) component [i.37], which securely shares data with manufacturers and Cyber Threat Intelligence (CTI) providers, enabling bidirectional exchange of alerts, threat information and even mitigation actions. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.3.1 Updating | Over-The-Air (OTA) software updates are vital for maintaining the long-term security of IoT devices. This need is underscored by standards and recommendations from organizations such as the European Union Agency for Cybersecurity (ENISA), which highlights regular updates as key to improving the security and reliability of connected systems [i.38], [i.39] and [i.40]. CERTIFY aligns with these recommendations by incorporating OTA components based on the IETF RFC 9019 [i.6] framework. To strengthen security and trust, CERTIFY integrates DLTs to log every event related to firmware updates and device metadata. This provides transparency, immutability, and a continuous chain of trust across the OTA process. Secure cryptographic algorithms are used to verify firmware integrity and sign updates, ensuring authenticity and protection against tampering. The update phase in CERTIFY includes both the deployment of software patches from manufacturers and configuration adjustments needed to counter emerging threats. These tasks are carried out by a coordinated set of components - such as the enforcement and reconfiguration agent, secure update and upgrade agent, and the device and domain manager - and may be initiated manually by administrators or automatically in response to detected threats or anomalies. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 6.2.3.2 Decommissioning & Repurposing | The decommissioning phase in the CERTIFY lifecycle marks the final stage of a connected device's life, where it is either retired from operations or repurposed. This phase is crucial to ensuring that devices no longer in service do not pose residual security risks. Proper decommissioning protects the network by securely managing all sensitive data and configurations, preventing potential vulnerabilities that could arise from improper disposal. The process begins with an assessment to determine whether the device can be safely repurposed for a less security-sensitive role or should be fully retired. For devices being decommissioned, CERTIFY prioritizes secure data erasure - permanently deleting cryptographic keys, certificates, logs, and configurations. To ensure transparency and policy compliance, the framework uses DLT to create a verifiable, immutable record of the decommissioning process. If a device is deemed suitable for repurposing, CERTIFY provides a secure reconfiguration framework. This may involve assigning the device to a lower-security domain or adjusting its functionality to handle less sensitive tasks. While repurposing can extend device lifespan and reduce costs, it should be done in a way that maintains appropriate security standards for the device's new role. 7 Design of the continuous cybersecurity posture management and relation to CRA and certification |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.1 Introduction | In both projects, two technologies rise as a key cornerstone for achieving the continuous cybersecurity posture and certification goals. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 23 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2 Manufacturer Usage Description (MUD) | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.0 General | To achieve effective detection and mitigation of security threats in specific IoT environments, it is useful and sometimes necessary to know the expected behaviour of devices beforehand. However, the heterogeneity of IoT environments (from critical infrastructures to home) and of devices themselves, based on various technologies and communication protocols, and the restrictions inherent to certain IoT devices (e.g. the lack of a user interface) make the management of IoT devices cumbersome for non-expert users. To cope with these challenges, one key aspect is to standardize the identification and management of device behaviour. The Manufacturer Usage Description (MUD) standard was published in 2019 by the Internet Engineering Task Force (IETF) [i.7]. The MUD specification's major goal is to limit the threat and attack surface of a certain IoT device by allowing manufacturers to establish network behaviour profiles for their devices. Each profile is specified through Access Control Lists (ACLs), which establish policies for communication endpoints. They are defined using Yet Another Next Generation (YANG) [i.8] to model network restrictions, and JavaScript Object Notation (JSON) [i.9] as the serialization format. Since its adoption, MUD has been the object of interest both from researchers and standardization bodies. In particular, the National Institute of Standards and Technology (NIST) and the European Union Agency for Cybersecurity (ENISA) consider the use of MUD as part of future IoT security good practices to increase security against cyberattacks in IoT domains. The protection of security in environments with IoT devices does not end with the initial device installation. Many vulnerabilities and attacks can, and indeed are, discovered during the operational phase. For instance, only in 2022, more than 25,000 vulnerabilities were detected [i.10]. Manufacturers cannot always deal with vulnerabilities quickly enough through updates, which follow a complex process, and in many cases the relationship with third-party services makes this even harder. While MUD files can be updated, this process does not cover most vulnerable scenarios. In this sense, security-information-sharing systems enable fast and collaborative sharing, and analysis and mitigation of vulnerabilities or attacks, which may also be applied before a patch is released. The sharing of cyber-threat information for building cybersecurity capabilities has also been a big focus of the NIS2 Directive of the ENISA [i.1]. In this direction, the NIST proposed a threat Manufacturer Usage Description (threat MUD) [i.11], to share vulnerability information and its mitigations. It is based on the MUD standard for device behaviour specification and follows a similar structure. However, despite the close relationship, the threat MUD is conceived as a mitigation mechanism. However, the NIST only gives some indications about the threat MUD model and its functioning, leaving some details undefined but framed in the guidelines. In the following clause, the present document overviews the threat MUD model as presented in [i.12], which the present document uses as a basis, though with differences on how the flows are integrated into the architecture (e.g. receiving threat identifiers for which to search associated files through the TMB). The present document takes NIST guidelines and the MUD standard as a starting point. A key element to have in mind for the threat MUD is that, even if its structure and operation are similar that of the regular MUD, its purpose is to serve as a mitigation method against a specific threat, particularly through network communication rules for sites that have been associated to a threat. Therefore, a threat MUD does not need to be strictly related to a specific device, nor specify expected behaviour. As a result, rather than being developed by the manufacturer, the threat MUD might be created by a threat intelligence provider. As with the standard MUD, the threat MUD model has two modules. The first module reflects information about the threat MUD itself. It contains equivalent fields to the MUD standard, such as version, URL, cache-validity, signature, etc. However, some fields have to be modified (manufacturer name is changed to intelligence provider, and device model name is changed to threat name), removed (information about device to which the MUD is associated like system or firmware is no longer needed), or added (CVSS and documentation fields for additional information about the threat) to fulfil the new mitigation goal. The second module is again related to the ACLs that specify the conditions and restrictions. In this case, as the file is tied to a threat and its mitigation and not to a specific device, the configuration to apply should be as generic as possible. Thus, unnecessary fields like "same-manufacturer", "local-networks", "controller", and "my-controller" (which established conditions specific to the device) are removed. MUD is integrated into ERATOSTHENES and CERTIFY as a source of behavioural information of the devices that enrol in a domain. The MUD file servers are outside of the end user domains, e.g. on the manufacturer premises. MUD components from all domains may communicate with them to retrieve MUD files. The main functional components of the MUD standard and threat MUD proposal will be active in each domain, as part of the Trust Manager & Broker component. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 24 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.1 Key Components of MUD | • MUD File: This file, created by the manufacturer, contains a detailed set of instructions that define the anticipated network behaviour of the device. It serves as a blueprint for the device's network interactions and security posture. • MUD Manager: This component acts as the network administrator. It is responsible for retrieving MUD Files using MUD URLs provided by the devices. The MUD Manager ensures that the network policies are updated according to the latest MUD specifications. • MUD URL: Embedded within the device by the manufacturer, this URL points to the location where the MUD file is stored. It allows the MUD Manager to fetch the necessary files for policy implementation. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.2 Extended MUD | The MUD standard [i.50] presents a few limitations to its capabilities and applicability in practice, such as reduced expressivity focused only on networking, insufficient security in the MUD retrieval process, or supporting efficient updates for security information. Both ERATOSTHENES and CERTIFY go beyond the standard and provide "extended MUD", addressing such gaps for an improved impact of the solution in the lifecycle management process. CERTIFY extends the MUD model to accommodate finer-grained security aspects and diverse security policies. These encompass extended network access control, channel protection, data protection, and authorization policies [i.36]. In this regard, while a standard MUD server offers guidelines for allowed or restricted network activities for each device, a Threat MUD server would allow to incorporate real-time or near real-time threat information as provided by the PP-CTI. Additionally, the extended MUD file is taking advantage of to include behavioural profiles and device fingerprints that can be later used for attestation and monitoring of the device during the initial phases and throughout its operation in a security domain. One of the key innovations in ERATOSTHENES over the standardized MUD obtaining process comes from the integration of the MUD processing into a full-fledged trust framework. Now, using the ERATOSTHENES domain enrolment phase to get the MUD URL from the device, through the publish/subscribe approach used for communication between TMB components. The integration in such a flow, and within the ERATOSTHENES ecosystem, also allows the exploration of further improvements for the MUD flow. For instance, while the communication with the MUD fileservers can be easily secured in any usual way for webservers (e.g. HTTPS), there is a glaring gap in the standard regarding the possible spoofing of a MUD URL by the device. This authentication of the URL during MUD file obtention can be tackled through the ERATOSTHENES identity framework. Specifically, the manufacturer (at pre-provisioning time, along with PUF and MUD URL installation) will associate the PUF of a device (as a root of trust for identity) to the respective URL. Alternative approaches can be explored in the case of not having PUF available as a root of trust, following the project's general approach for tackling this case, e.g. by taking it into account when threat models, risk and trust for the device are evaluated. This is addressed, for instance, in CERTIFY with the securitization of the process through the secure element of the device during the bootstrapping phase. Of course, network elements will still have to be considered in specific instantiations, but this will be partly solved by the own MUD mechanism: MUD files will be associated to devices that are relevant to the application domain, which will make the rules included in them relevant to the deployment domain by default. What is more, the advantages of the extension of the MUD model with higher-level concepts, like software updates or cryptographic parameters restrictions, will be even more relevant through this abstraction. Lastly, both projects tackle the issue of efficient and scalable MUD updates and the dynamicity of security contexts, with the inclusion of update flows, threat MUDs and other means for sharing threat information. The approach taken in the projects for lifecycle management through MUD files thus innovates by providing comprehensive mechanisms at multiple levels (e.g. not only network level, or one-time configurations) that tackle multiple challenges identified in the MUD standard and other recent works and ensure the continuous management throughout the lifecycle including collaboration through sharing of cybersecurity information from many sources. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 25 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.3 MUD management in ERATOSTHENES | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.3.0 General | Figure 9: Instantiation of MUD components in ERATOSTHENES As a detailed example of the described tools and processes, Figure 9 shows the instantiation of the MUD components in the ERATOSTHENES architecture. Note that the MUD management module in ERATOSTHENES is an aggregation of subcomponents, including the functionalities of both standard MUD and threat MUD managers, plus a translation module for the interaction with other ERATOSTHENES components, e.g. by transforming MUD files into corresponding security policies. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.3.1 MUD Manager / Threat MUD Manager | The central components of the MUD Management Module architecture. The MUD Manager oversees the retrieval of MUD files associated to devices that enrol in an ERATOSTHENES domain. The threat MUD manager carries out the equivalent functionality for threat MUD files. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.3.2 Policy Translator | For inter-component communications, ERATOSTHENES introduces a service to translate MUD files into intermediate security policies. ERATOSTHENES currently utilizes Medium-level Security Policy Language (MSPL) [i.13], a security policy language with medium level of abstraction, that provides a set of actions suitable by the most common applicable security settings. The MSPL's structure is defined in a YANG model, which allows using XML or JSON as encoding format. This allows flexibility when applying the information contained in MUD files. Other components will take the medium-level policy from the topic and take advantage of it for their purposes, potentially with another translation into their own structures. For instance, the TMRA may use the policy directly to increase its knowledge base for building models, while the IDS may translate policies into rules that detect related events and further enforcement policies may be derived by PDPs. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.2.3.3 MUD File Servers | The source for all MUD/Threat MUD files. MUD file servers are located outside the ERATOSTHENES deployment, belonging instead to the device manufacturers. MUD components from all domains may communicate with them to retrieve MUD files. Threat MUD file servers, on the other hand, are controlled by threat intelligence actors (which may not necessarily be manufacturers). ETSI ETSI TR 104 160 V1.1.1 (2025-10) 26 |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.3 Continuous Assessment | In today's interconnected digital landscape, cybersecurity is no longer an afterthought; it is a strategic imperative. Organizations should proactively defend against cyber threats, adapt to evolving attack vectors, and ensure the resilience of their systems. This is critical to achieving cybersecurity resilience in the face of constant risks and threats. Referring to the cybersecurity environment, an organization's continuous efforts to monitor, assess, and improve its security measures are necessary. Unlike a static approach, where security is treated as a one-off event, the continuous posture recognizes that threats are dynamic and require constant vigilance. The following key components are recognized: • Threat Intelligence: Organizations collect and analyse threat intelligence to stay informed about emerging risks. This includes monitoring vulnerabilities, tracking threat actors, and understanding attack patterns. • Security Monitoring: Real-time monitoring of network traffic, system logs, and user behaviour helps detect anomalies and potential breaches. Security Operations Centres (SOCs) play a crucial role in this process. • Incident Response: Having a well-defined incident response plan ensures that the organization can swiftly address security incidents. Timely detection, containment, eradication, and recovery are essential steps. • Patch Management: Regularly and consistently applying security patches and updates is fundamental. Unpatched vulnerabilities are often exploited by attackers. • Employee Training: Educating employees about security best practices reduces the risk of insider threats and social engineering attacks. The European Union's Cyber Resilience Act (CRA) aims to protect consumers and businesses that buy or use products or software with a digital component. This law establishes mandatory cybersecurity requirements for manufacturers and retailers of such products, ensuring that inadequate security features become outdated. The CRA addresses two key issues: • Inadequate level of cybersecurity: Many products have an insufficient level of inherent cybersecurity or poor security updates. The CRA establishes harmonised standards when placing products or software with a digital component on the market. • Inability to determine secure products: Consumers and businesses are often unable to determine which products are secure from a cyber perspective. The CRA introduces a framework of cybersecurity requirements that governs the planning, design, development, and maintenance of such products. More descriptions on these regulations and needs, and how ERATOSTHENES and CERTIFY technologies may be envisaged as a tool to address them can be found in clause 9 of the present document. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.4 Cyber Threat Intelligence (CTI) | |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.4.1 General | Cyber intelligence is an information gathering and analysis activity aimed at identifying, tracking/predicting capabilities, and intentions/activities of hostile actors in the cybersecurity domain. Cyber-Threat Intelligence (CTI) can be defined as evidence-based knowledge (including context, mechanisms, indicators, implications, and actionable advice) about an existing or emerging threat that can be used to make decisions regarding similar threats. CTI is a compound of attributes that give overall meaning to such a report, e.g. malicious IP addresses or hashes alone are not considered CTI but grouped in context along with other information to form part of a CTI report. One of the most crucial elements of Cyber Threat Intelligence are Indicators of Compromise (IoCs). They are the most easily actionable attributes and the ones that most tools working with this information focus on: IoCs are widely used in applications such as Intrusion Detection Systems, web blockers, identification of compromised hosts or malware. In addition, these indicators can be easily related to other indicators that have occurred previously, taking advantage of big data analysis techniques on stored indicators. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 27 There are some risks involved in sharing CTI. Organizations are reluctant to share information on such platforms because they feel that revealing information about intrusions could damage their reputation. Moreover, this information sometimes carries identifying data, IP addresses, email accounts, names, which in the hands of attackers can be used against the organization that shared it, if they have not fixed the breaches in their system yet. This information, also, can fall into the hands of a dishonest partner, who can make fraudulent use of the data. For the anonymization of these identifiers values, there exist privacy-preserving and data transformation techniques, such as suppression, generalization, sampling, k-anonymity, l-diversity, t-closeness, d-presence, etc., derived from Statistical Disclosure Control (SDC) [i.14]. SDC, also known as Disclosure Avoidance, is the discipline that manages the balance between the privacy of respondent data and the usefulness of this data for research purposes. These techniques attempt to minimize data risks related to identity disclosure, (i.e. when an adversary can correctly associate an individual within a dataset), attribute disclosure, (i.e. when an attacker is able to infer the value of an attribute due to the distribution of attribute values in the table) and membership disclosure, (i.e. the ability of an attacker to be able to determine at very high probability whether or not a particular individual is in the dataset). |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.4.2 CTI in ERATOSTHENES | One of the key business challenges for IoT scenarios is the need for increased cybersecurity, as security events incur in many direct and indirect losses. The components developed in ERATOSTHENES and CERTIFY aim to provide a platform for inter-domain Cyber-Threat Intelligence (CTI) sharing, compliant with the guidelines of the NIS directive. The main outcome is the collaboration of the tools developed for a comprehensive scenario that covers the needs for CTI sharing in heterogeneous and large IoT scenarios. To showcase these concepts, this clause provides a detailed description of the CTI sharing components in ERATOSTHENES. ERATOSTHENES supports a comprehensive, resource-efficient, and flexible security analysis of threats based on cyber intelligence sharing across the different domains. The objective is to maintain an update status about vulnerabilities and threats that appears through the architecture elements including the lifecycle management and the trust governance layer. To this end, CTI reports will be generated by monitoring entities and shared through the domains with the support of the inter-DLT infrastructure. The exchange of security and threat information between the various stakeholders is implemented through CTI integration into DLT and inter-DLT platforms. The CTI Sharing Agent is a key component in the process of communication and threat information sharing between domains, specifically CTI and IDS systems. Besides, its anonymization techniques and along with the MISP platform ensure privacy and reliability, and flexible encryption approaches such as CP-ABE, in addition to privacy-enhancing techniques like k-anonymity or t-closeness provide confidentiality, trust, and privacy enhancement. This approach should provide the necessary confidentiality and flexibility for the tracking and exchange of cyber threat information. Figure 10 shows the detailed description of the CTI Sharing Agent as part of a Trust Manager and Broker, as well as the main communication flows between the subcomponents, and with other ERATOSTHENES components. ETSI ETSI TR 104 160 V1.1.1 (2025-10) 28 Figure 10: CTI Sharing Agent structure and flows The information shared through the CTI agent is integrated into the ERATOSTHENES ecosystem through the Trust Manager and Broker. A specific topic is setup so that components interested in threat information will receive the relevant events. One component of particularly close relationship with the CTI sharing tool is the Intrusion Detection System (IDS). The events generated by the IDS after detection of security events are shared with the CTI sharing agent through the MQTT broker. This is received by the CTI Agent Connector, which parses and prepares it and sends it to the next step in the pipeline, the Anonymizer, from which the events processed according to privacy policies are published. From the other direction, events received in the CTI agent from other agents will be prepared and published to the MQTT broker by the CTI Agent Connector. The IDS will be able to use that information to improve its detection capabilities, for instance by including rules in its detection engine that cover the newly discovered events. Another component whose interaction with the CTI Agent brings important security gains is the MUD Management module. One key element that may be shared through CTI are events that convey the publication of new mitigations, particularly new Threat MUD files, by manufacturers or security teams. Thus, the MUD Management module can retrieve them, translate them into a Medium-Level Security Policy Language (MSPL) object that is shared through the MQTT broker so that mitigations can be applied by the ERATOSTHENES components. |
2ba1876e0259e748d226a329803049d9 | 104 160 | 7.4.3 CTI Sharing Agent Components |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.