hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 3 Definition of terms, symbols and abbreviations | |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 104 050 [1] and ISO/IEC 22989 [2] and the following apply: AI system: engineered system that generates outputs such as content, forecasts, recommendations or decisions for a given set of human-defined objectives NOTE: Definition from ISO/IEC 22989 [2]... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 3.2 Symbols | Void. ETSI ETSI TS 104 224 V1.1.1 (2025-03) 7 |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence BTT Build-Train-Test DARPA Defence Advanced Research Projects Agency LRP Layer-wise Relevance Propagation ML Machine Learning OECD Organization for Economic Cooperation and Development RTE Run Time Explicability TA T... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 4 Explicability and transparency | The SAI problem statement, ETSI TR 104 221 [i.1], identifies explicability as being a contributor in establishing trust in AI systems as one element of achieving transparency. However, in computer science the concept of transparency is somewhat at odds with explicability and can be interpreted as "functioning without t... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 5 Static explicability analysis | |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 5.1 Summary of the role of static explicability analysis | The role of static explicability is closely related to giving detailed system documentation. The purpose of explicability is to allow a lay person (i.e. not a professional programmer or system analyst) to gain a reasonable understanding of the main data flows and processing steps in the program. EXAMPLE: A data set of ... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 5.4 Identifying who is the liable party | In undertaking analysis and in providing the necessary documentation it should be made clear who is responsible for the AI system, and the system of which it forms a component. This should be consistent with any other obligations when placing products on the market. NOTE: This is addressed in part in the AI Act [i.5] a... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6 Run time explicability | |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.1 Summary of service | When an AI system is running it applies its AI to data to achieve its purpose. The goal of run time explicability is to ensure that the system developer, and other stakeholders in the supply chain, can identify the role of active processes, and data, in achieving the system purpose. Static explicability is a pre-requis... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.2 Abstraction of AI system | An abstract model of an AI processing system is given in ETSI TR 104 221 [i.1] from which figure 1 is taken to represent stages in the ML lifecycle. Figure 1: Typical machine learning lifecycle (Source: ETSI TR 104 221 [i.1]) Explicability applies to the Build-Train-Test (BTT) cycle during model design, and to the role... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.3 Evidence requirements for explicability | The requirements for static explicability, outlined in clause 5, apply as a pre-requisite to providing evidence for run-time explicability. ETSI ETSI TS 104 224 V1.1.1 (2025-03) 12 As indicated above, explicability (and transparency as a pre-requisite) aims to prevent the AI components of a system from denying that the... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.4 Performance considerations | |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.4.1 General requirement | An AI/ML system can make decisions at a rate that, if a detailed evidential record was to be created, and retained securely, has potential to overload the system. Rather than take a detailed evidential record for every decision the goal of explicability and transparency is to ensure that the rationale for a decision is... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.4.2 Precision and recall metrics | In addition to issues related to performance from audit and logging as above, the designer shall define and publish the expected accuracy of the system. This should be achieved by explicitly identifying the measure of precision and of recall against both static data and live data. • Precision, the measure of positive p... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 6.5 Application of XAI approaches | Complementing the approaches presented above, academic research on more complex technical methods for gaining insights into the behaviour and decisions of AI models is performed in the field of eXplainable AI (XAI). Depending on the use case, different methods can be used. An overview of the different approaches is giv... |
1a78e9090133dfd7ab8c19db79ccb9ca | 104 224 | 7 Data transparency | ETSI TR 104 048 [i.2] identifies the role of understanding the data supply chain as a link in integrity and availability assurance. As stated in clause 4 transparency when applied to AI is related to being "open to examination". The value of integrity checks, e.g. using cryptographic hashes, in transparency is that the... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 1 Scope | The present document describes an ensemble of cyber security specifications and other materials, especially the ETSI Critical Security Controls in ETSI TR 103 305-1 [i.9] that can be applied to support NIS2 Directive [i.1] requirements by EU Member States and affected essential and important entities. The present docum... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 2 References | |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 2.1 Normative 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. Referenced documents which a... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 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 1: While any hyperlinks... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 3 Definition of terms, symbols and abbreviations | |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 3.1 Terms | For the purposes of the present document, the terms given in the NIS2 Directive [i.1] and the following apply: NOTE: It should be noted that the NIS2 created definitions of terms that are nuanced and may vary with those used elsewhere. Because the present document concerns the implementation of the NIS2 Directive, it b... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 3.2 Symbols | Void. |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence ANSSI Agence Nationale de la Sécurité des Systèmes d'Information (National Agency for the Security of Information Systems) (France) Art. Article ATT&CK Adversarial Tactics, Techniques, and Common Knowledge BSI Bundes... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4 Measures common to Directive requirements | |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.1 Description | The NIS2 Directive [i.1] requires the implementation of cybersecurity measures by different types of stakeholders that are articulated in different contexts in the individual articles and annexes that are identified in clause 5, below. It should be noted that the entities included in the annexes are subject to change u... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.3 Addressing cyber threats | The treatment of cyber threats in the NIS2 Directive [i.1] can be found in the following articles: - Scope (Art. 2); - national strategies (Art. 7); - CSIRT tasking (Arts. 10, 11); - national cooperation (Art. 13); - Cooperation Group (Art. 14); - CSIRTs network (Art. 15); - CyCLONE (Art. 16); - Risk Management (Art. 2... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.4 Addressing incidents and near misses | The treatment of incidents and near misses in the NIS2 Directive [i.1] can be found in the following articles: - Scope (Art. 2); - national strategies (Art. 7); - national cooperation (Art. 3); - Cooperation Group (Art. 14); - CSIRTs network (Art. 15); - reporting obligations (Art. 23); and - voluntary notification (Ar... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.5 Addressing vulnerabilities | The treatment of vulnerabilities in the NIS2 Directive [i.1] can be found in the following articles: - national strategies (Art. 7); - coordinated vulnerability disclosure (Art. 6); - CSIRT tasking (Arts. 9, 10); - Cooperation Group (Art. 14); - CSIRT's network (Art. 15); - risk management (Art. 21); - critical supply ... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.6 Instituting risk management measures | Risk management in the NIS2 directive [i.1] encompasses a broad array of subjects that include: - risk analysis; - incident handling; - business continuity; - supply chain security; - systems acquisition, development, and maintenance security; - certification, testing and auditing; - cyber hygiene and training; - use o... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.8 Standards and technical specifications | The treatment of standards and technical specifications in the NIS2 Directive [i.1] can be found in the following articles: - Cooperation Group (Art. 14); - CSIRT's network (Art. 15); - risk management (Art. 21); - critical supply chains (Art. 22); and - standardization (Art. 25). Standards and technical specifications... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.9 Trust Services measures | The treatment of Trust Services and their provision in the NIS2 Directive [i.1] can be found in the following articles: - Scope (Art. 2); - Definitions (Art. 4); - risk management (Art. 21); - reporting (Art. 23); - certification schemes (Art. 21); and - Digital Infrastructure sectors of high criticality (Annex I, Sect... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 4.10 Encryption measures | The NIS2 Directive [i.1] includes an array of new actions and requirements related to encryption that is consonant with [i.46]. ETSI's ISG on Encrypted Traffic Integration (ETI) has published ETSI GR ETI 006 [i.22] specifically relating to matters relating to the [i.46] and the NIS2 Directive [i.1]. ETSI ISG ETI has al... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5 Implementation of NIS2 Directive | |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.1 Description | The present clause suggests how requirements of the NIS2 Directive [i.1] can be effectively met using ETSI Critical Control Safeguards [i.9], [i.10], [i.11] and [i.12] together with associated facilitation mechanism, privacy enhancements, and sector guides. NOTE: Articles of the NIS2 Directive that treat legislative pr... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.2 National cybersecurity strategy (Art. 7) | Article 7 of the NIS2 Directive [i.1] requires each EU Member State to adopt a national cybersecurity strategy defining the strategic objectives and appropriate policy and regulatory measures, with a view to achieving and maintaining a high level of cybersecurity. |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.3 Coordinated vulnerability disclosure (Art. 12) | Article 6 of the NIS2 Directive [i.1] requires each EU Member State to designate one of its CSIRTs as a coordinator for the purpose of Coordinated Vulnerability Disclosure (CVD). It additionally requires ENISA to develop and maintain a European vulnerability database, in consultation with the Cooperation Group. Impleme... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.6 European cybersecurity certification scheme (Art. 24) | Art. 24 of the NIS2 Directive [i.1] states that Member States may require essential and important entities to use particular ICT products, services and processes certified under specific European cybersecurity certification schemes. It further notes that the Commission may adopt implementing acts specifying which categ... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.7 Standardization (Art. 25) | Art. 25 of the NIS2 Directive [i.1] requires, with respect to risk management measures, that Member States encourage the use of European or internationally accepted standards and specifications relevant to the security of network and information systems. Furthermore, that ENISA, in collaboration with Member States, dra... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 5.8 Reporting and information-sharing (Arts. 23, 29, 30) | Art. 23 of the NIS2 Directive [i.1] requires Member States establish an extensive array of reporting and sharing obligations concerning any incident having a significant impact on the provision of services and mitigation measures. Art. 29 requires Member States ensure that essential and important entities may exchange ... |
e9ad103446e7301c9322c48d5ddebb4b | 103 992 | 6 Recommendations | The Critical Security Control Safeguards profiled to be part of Implementation Group 1 as defined in ETSI TR 103 305- 1 [i.9] shall be implemented by entities. All other Critical Security Control safeguards from ETSI TR 103 305-1 [i.9] and privacy enhancements specified in ETSI TR 103 305-5 [i.12], as detailed in the s... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 1 Scope | The present document specifies security protocols as to be used for O-RAN compliant implementation. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 2 References | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 2.1 Normative 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. Referenced documents which a... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 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 i... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 3 Definition of terms, symbols and abbreviations | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 3.1 Terms | Void. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 3.2 Symbols | Void. ETSI ETSI TS 104 107 V9.0.0 (2025-05) 10 |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] and the following apply. NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1]. CA Certification Authority CMP Certificate Management... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1 SSH | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.1 General requirements | O-RAN and 3GPP interfaces that implement authentication, confidentiality and integrity using SSH shall: • Support SSHv2 [1] and [70]. • Disable by default cryptographically insecure ciphers as specified in clauses 4.1.2.1, 4.1.2.3 and 4.1.2.4 of the present document. • Enable an O-RAN deployer to configure SSH to offer... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2 Required ciphers | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2.0 Introduction | O-RAN requires the following ciphers when using SSH. For more information see [2], [5], [11], [12], [13], [14] and [15]. See the Security chapter of the O-RAN Working Group 4 Management Plane Specification for the M-plane mandated SSH ciphers [6]. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2.1 Key agreement | Note that the present document uses the IANA cipher naming convention [5]. • Required a. ecdsa-sha2-nistp256 b. ecdsa-sha2-nistp384 c. ecdsa-sha2-nistp521 d. ssh-ed25519 • Optional a. ssh-ed448 • Shall not be implemented a. ssh-rsa b. ssh-dss |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2.2 Symmetric algorithms for encrypting transferred data | • Required a. aes256-gcm b. aes128-gcm c. aes256-ctr d. aes192-ctr e. aes128-ctr |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2.3 Key exchange algorithms (KexAlgorithms) | • Required a. ecdh-sha2-nistp521 b. ecdh-sha2-nistp384 c. ecdh-sha2-nistp256 d. diffie-hellman-group-exchange-sha256 e. curve25519-sha256 • Shall not be implemented a. Diffie-hellman-group1-sha1 ETSI ETSI TS 104 107 V9.0.0 (2025-05) 12 |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.1.2.4 Message Authentication Codes (MACs) | • Required a. hmac-sha2-512-etm b. hmac-sha2-512 c. hmac-sha2-256-etm d. hmac-sha2-256 e. umac-128 • Shall not be implemented a. hmac-sha1 |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2 TLS | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2.1 General requirements | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2.1.0 Introduction | O-RAN interfaces that implement authentication, confidentiality and integrity using Transport Layer Security (TLS) shall: • Support TLS 1.2 [18]. • Configure the TLS 1.2 Intermediate server ciphers as specified in [i.2] and [8]. • Support TLS 1.3 [18] and [i.4]. • Enable an O-RAN deployer to configure TLS 1.2 to offer ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2.1.1 Specific requirements | In addition, one-way TLS authentication may be supported with server certificate exchanged as specified in [18] clause 7.4.2 (TLS 1.2) or [18] clause 4.4.2 (TLS 1.3). ETSI ETSI TS 104 107 V9.0.0 (2025-05) 13 |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2.2 TLS Protocol profiles specifications | TLS 1.2 used on all interfaces except the Open Fronthaul interfaces shall support the TLS 1.2 profiles as defined by ETSI TS 133 210 [20] clause 6.2.3. See Chapter 5.4 Security in [6] for the M-plane mandated TLS ciphers [6]. TLS 1.3 used on all interfaces except the Open Fronthaul interfaces shall support the TLS 1.3 ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.2.3 Certificate Profile for TLS Entity | The present clause addresses the certificate profile requirements for the TLS entities that may behave either as client, server, or both. The structure of the TLS certificate profile described in this clause under Table 4-1 provides requirements based on the ETSI TS 133 310 [26], CA-browser forum [56] and NIST Special ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.3 Support NETCONF over secure Transport | TLS requirements for use with NETCONF on the O1 interface [10] are specified in clause 4.2. TLS requirements for use with NETCONF on the Open Fronthaul M-plane are specified in clause 5.4 of the O-RAN WG4 Management Plane Specification [6]. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.4 DTLS | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.4.1 General requirements | O-RAN and 3GPP interfaces that implement mutual authentication, integrity protection, replay protection and confidentiality protection using DatagramTransport Layer Security (DTLS) shall: • Support DTLS 1.2 [23]; • Support DTLS for Stream Control Transmission Protocol [24]; and should support DTLS 1.3 [23]. DTLS 1.0 sh... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.4.2 DTLS 1.2 profiling | DTLS 1.2 is based on TLS 1.2, so all requirements defined in clause 4.2 in the present document for TLS 1.2 shall apply to DTLS as well. 3GPP control plane interfaces in O-RAN system implementing DTLS 1.2 shall support all requirements defined in the profiling for TLS 1.2 specified in ETSI TS 133 210 [20], clause 6.2.3... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.4.3 Certificate profiling | Certificate requirements defined in clause 4.2 in the present document for TLS 1.2 shall apply to DTLS as well. ETSI ETSI TS 104 107 V9.0.0 (2025-05) 16 3GPP control plane interfaces in O-RAN system implementing DTLS 1.2 shall support certificate profiling as given in clause 6.1.3a of ETSI TS 133 310 [26]. DTLS client ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5 IPSec | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5.1 Overview | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5.1.0 Supported IPsec capabilities | O-RAN and 3GPP interfaces that implement authentication, confidentiality and integrity using IPsec shall support IPsec according to [27]. The supported IPsec capabilities in this clause follow [20] for interworking purposes and further apply requirements given in [26], [28], [29] and [i.5]. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5.1.1 Supported IPsec capabilities | Services that SHALL be supported (see also [29], section 9.8.2): • Confidentiality, can be enabled/disabled (via ENCR_NULL) • Integrity protection, always enabled • Data origin authentication, always enabled • Anti-replay protection, can be enabled/disabled • Extended sequence numbers, can be enabled/disabled Protocol ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5.2 Parallel usage of IPsec and other secure transport protocols | Implementations SHALL support IPSec configuration with one or more dedicated connections in parallel with other secure transport protocols. EXAMPLE: It should be possible to run SSH or TLS connections within an IPsec tunnel or in parallel to IPsec tunnel(s). |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.5.3 Responder mode and Initiator/Responder mode support | Implementations SHALL support a configurable option per IKE Security Association to use "Responder mode" instead of "Responder/Initiator mode". Responder mode is applied to IKE SA establishment only. The introduction of "Responder mode" does not change the IKE SA rekeying behaviour: Each node shall be able to operate a... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.6 CMPv2 | Certificate Management Protocol version 2 (CMPv2) is based on Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP) specified in IETF RFC 4210 [38] and IETF RFC 4211 [39]. ETSI TS 133 310 [26] specifies the use of CMPv2 used by base stations to obtain an operator-signed certificate using ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7 OAuth 2.0 | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.1 Overview | The authorization framework described in clause 4.7 of the present document uses the OAuth 2.0 framework as specified in IETF RFC 6749 [35]. It allows the service producers to authorize the requests from service consumers, and the service consumers to obtain authorization credentials ("token endpoint"). Interfaces requ... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2 Basic Parameterization | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.1 General | Client access token authorization grants shall be supported with type Client Credentials Grant, as described in clause 4.4 of IETF RFC 6749 [35]. Mutual TLS authentication, as specified in the present document (clause 4.2.1), is the mechanism selected by O-RAN for this security procedure. In addition, still aligned wit... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.2 Registration process | OAuth 2.0 resource servers (API service producers) shall be registered with the OAuth 2.0 Authorization server. Service producers may include additional scope information related to specific allowed service operations and resources per client type. Before initiating the authorization protocol, OAuth 2.0 clients shall b... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.3 Access Token request process | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.3.0 Server requirements | After TLS mutual authentication procedure between the OAuth 2.0 client and OAuth 2.0 Authorization server, or one- way TLS authentication with server certificate and client authentication based on Client Id and Client Secret has been executed, the Authorization server exposes a 'Token Endpoint' where the Access Token r... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.3.1 Server requirements | • The OAuth 2.0 Authorization server shall verify that the input parameters in the access token (e.g. client type) match with the corresponding ones in the public certificate of the client, or those in the client profile previously registered. • If the client is authorized, the Authorization server shall generate an ac... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 4.7.2.4 Service access request based on token verification | Once the client is in possession of a valid access token, it may proceed with the request of service access towards the service producer (OAuth 2.0 resource owner/server). ETSI ETSI TS 104 107 V9.0.0 (2025-05) 20 OAuth 2.0 Client OAuth 2.0 Resource Owner/Server 1.Service request (access token) 3. Service response 2. Ve... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 5 Cryptographic operations | Table 5-1 outlines the main cryptographic operations involved in the protection of (1) App/VNF/CNF packages for ensuring their integrity, authenticity and confidentiality (for sensitive artifacts) during delivery, onboarding, and instantiation phases, (2) the communication channel over O-RAN interfaces in terms of auth... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6 Secure File Transfer protocols | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.1 General | File Transfer management is required in several O-RAN use cases, e.g. for export of log files. An O-RAN architectural element that implements file management shall support at least one of these secure file transfer protocols: SFTP, FTPES, HTTPS. This is aligned with, for example, how 3GPP specifies File Management in [... |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.2 SFTP | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.2.1 General Requirements | O-RAN architectural elements that implement secure file transfer using SFTP shall: • Support secure connection and authentication using SSHv2 Authentication Protocol [2] with all O-RAN specific requirements from clause 4.1 in the present document. • Support SFTPv3 as the SFTP Industry Best Practice [65]. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.3 FTPES | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.3.1 General Requirements | O-RAN architectural elements that implement secure file transfer using FTPES shall: • Support secure connection and authentication using TLS with all O-RAN specific requirements from clause 4.2 in the present document. • Support FTPES as defined in [66]. |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.4 HTTPS | |
5f9c441dec96cf3060075b9f996af316 | 104 107 | 6.4.1 General Requirements | O-RAN architectural elements that implement secure file transfer using HTTPS shall: • Support secure connection and authentication using TLS with all O-RAN specific requirements from clause 4.2 in the present document. • Support HTTPS as defined in [69]. ETSI ETSI TS 104 107 V9.0.0 (2025-05) 23 Annex A (informative): C... |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 1 Scope | The present document describes the requirements for consumer receivers designed to be used with an Emergency Warning System (EWS) based on DAB, and the necessary test methods that lead to compliance with the requirements. It may be used as the technical basis for an EWS Certification Mark scheme. An EWS Certification M... |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 2 References | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 2.1 Normative 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. Referenced documents which a... |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 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 i... |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3 Definition of terms, symbols and abbreviations | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3.1 Terms | For the purposes of the present document, the following terms apply: band scan: function to scan the whole of the tuning range to update the stored service list when required EWS ensemble: DAB ensemble with FIG 0/7 and FIG 0/15 receiver: any device designed to receive digital radio signals tuning memory: stored informa... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.