hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1 Network Functions and Applications maintained by O-RAN | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1 Service Management and Orchestration (SMO) | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1 Security Requirements | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1.1 SMO | REQ-SEC-SMO-1: SMO shall support authentication of SMO functions. REQ-SEC-SMO-2: SMO shall support authentication of External Systems. REQ-SEC-SMO-3: SMO functions shall support authorization as a resource owner/server and client for internal requests. REQ-SEC-SMO-4: SMO shall support authorization of the service reque... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1.2 SMO Internal Communications | REQ-SEC-SMO-Internal-1: SMO Internal Communications shall support confidentiality, integrity, and replay protection between SMO functions. REQ-SEC-SMO-Internal-2: SMO Internal Communications shall support mutual authentication between SMO functions. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1.3 SMO External Interfaces | External Interfaces not specified by O-RAN that provide services to SMO, acting in a consumer role, shall meet security requirements specified in this clause. REQ-SEC-SMO-External-1: SMO External Interfaces shall support confidentiality, integrity, and replay protection. REQ-SEC-SMO-External-2: SMO External Interfaces ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1.4 SMO Logging | The below mentioned requirements are referring to securing the event logs in SMO. REQ-SEC-SMO-Log-1: SMO shall support forwarding of event logs to a mutually authenticated remote location. REQ-SEC-SMO-Log-2: SMO shall provide confidentiality and integrity protection for event logs transferred to a remote server. REQ-SE... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.1.5 NFO and FOCOM | The below mentioned requirements are referring to securing the NFO and FOCOM in SMO. REQ-SEC-NFO-FOCOM-1: NFO and FOCOM shall support confidentiality, integrity, and replay protection. REQ-SEC-NFO-FOCOM-2: VOID. REQ-SEC-NFO-FOCOM-3: NFO shall support mutual authentication with the O-Cloud on the O2dms interface. REQ-SE... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2 Security Controls | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2.1 SMO | SEC-CTL-SMO-1: SMO may support OAuth 2.0 authorization server and provide a token end-point, as specified in O-RAN Security Protocols Specifications [3], clause 4.7. SEC-CTL-SMO-3: SMO shall support OAuth 2.0 resource owner/server, as specified in O-RAN Security Protocols Specifications [3], clause 4.7, for service req... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2.2 SMO Internal Communications | Figure 5.1.1.2.2-1: mTLS or TLS for SMO Internal Communications SEC-CTL-SMO-Internal-1: For security protection at the transport layer, SMO Internal Communications shall support TLS as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-SMO-Internal-2: For mutual authentication between SMO fun... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2.3 SMO External Interfaces | External Interfaces not specified by O-RAN that provide services to SMO, acting in a consumer role, shall meet security controls specified in this clause. Figure 5.1.1.2.3-1: mTLS on SMO External interfaces SEC-CTL-SMO-External-1: For confidentiality and integrity protection of data in transit, SMO External Interfaces ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2.4 SMO Logging | SEC-CTL-SMO-Log-1: A SMO External Interface used for SMO log export shall support TLS as specified in O-RAN Security Protocols Specifications [3], clause 4.2, and FTPES. SEC-CTL-SMO-Log-2: SMO log export may support SSH as specified in O-RAN Security Protocols Specifications [3], clause 4.1, and SFTP. mTLS or TLS-PSK S... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.1.2.5 NFO and FOCOM | SEC-CTL-NFO-FOCOM-1: NFO shall support mutual authentication with O-Cloud DMS using mTLS with PKI X.509v3 certificates, as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-NFO-FOCOM-2: FOCOM shall support mutual authentication with O-Cloud IMS using mTLS with PKI X.509v3 certificates, as sp... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.2.1 Requirements | rApp packages shall follow the security requirements and controls in the Common App LCM clause 5.3.2.1 in the present document. REQ-SEC-NonRTRIC-1: The Non-RT RIC shall support authorization as a resource owner/server and client. REQ-SEC-NonRTRIC-2: The Non-RT RIC Framework, as a resource owner/server, shall provide au... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.2.2 Security Controls | SEC-CTL-NonRTRIC-1: For A1-EI, Non-RT RIC shall support OAuth 2.0 resource owner/server, as specified in O-RAN Security Protocols Specifications [3], clause 4.7, for service requests received from one or more Near-RT RICs. SEC-CTL-NonRTRIC-2: For A1-P, Non-RT RIC shall support OAuth 2.0 client, as specified in O-RAN Se... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.3.1 Requirements | xApp packages shall follow the security requirements and controls in the Common App LCM clause 5.3.2.1 in the present document. REQ-SEC-XAPP-1: VOID REQ-SEC-XAPP-2: VOID REQ-SEC-XAPP-3: During the xApp registration procedure the xApp identifier (xApp ID) shall be associated with xApp credentials used for authentication... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.3.2 Security Controls | API Security - Authentication SEC-CTL-NEAR-RT-1: Transactional APIs (REST and gRPC) shall support mutual TLS (mTLS) authentication via X.509v3 certificates as specified in the O-RAN Security Protocols Specification [3], clause 4.2. SEC-CTL-NEAR-RT-2: Time critical APIs, not supported by TLS protocol, shall support IPse... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.4 O-CU-CP/UP | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.4.1 Requirements | REQ-SEC-OCU-1: O-CU-CP and O-CU-UP shall meet the security requirements for gNB-CU-CP and gNB-CU-UP respectively, as specified in ETSI TS 133 501 [55]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.4.2 Security Controls | SEC-CTL-OCU-1: O-CU-CP and O-CU-UP shall support the security controls for gNB-CU-CP and gNB-CU-UP respectively, as specified in ETSI TS 133 501 [55]. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 29 |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.5 O-DU | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.5.1 Requirements | REQ-SEC-ODU-1: O-DU shall meet the security requirements for gNB-DU as specified in ETSI TS 133 501 [55]. The security requirements for the Open Fronthaul Interface are specified in clause 5.2.5 of the present document. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.5.2 Security Controls | SEC-CTL-ODU-1: O-DU shall support the security controls for gNB-DU as specified in ETSI TS 133 501 [55]. The security controls for the Open Fronthaul Interface are specified in clause 5.2.5 of the present document. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.6 O-RU | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.6.1 Requirements | REQ-SEC-ORU-1: O-RU shall meet the security requirements for gNB setup and configuration as specified in ETSI TS 133 501 [55]. REQ-SEC-ORU-2: O-RU shall meet the security requirements for gNB secure environment as specified in ETSI TS 133 501 [55]. The security requirements for the Open Fronthaul Interface are specifie... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.6.2 Security Controls | The security controls for the Open Fronthaul Interface are specified in clause 5.2.5 of the present document. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.7 O-eNB | 5.1.7.1 Requirements REQ-SEC-OeNB-1: O-eNB shall meet the security requirements for eNB as specified in ETSI TS 133 401 [56]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.7.2 Security Controls | SEC-CTL-OeNB-1: O-eNB shall support the security controls for eNB as specified in ETSI TS 133 401 [56]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8 O-Cloud | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.0 Introduction | NOTE 1: In the following requirements and controls, 'App' is intended to include both xApp and rApp. NOTE 2: In the following requirements and controls, the actor 'Service Provider' is used to refer to the Telco Operator and/or the O-Cloud Provider since the Application package verification may be performed by both or ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.1 Generic requirements | Generic requirements for Cloud Platform Management are specified in [8]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.1.1 User Management Requirements for Cloud Platform Management | REQ-SEC-OCLOUD-1: Users shall be authenticated. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 30 REQ-SEC-OCLOUD-2: Users shall be authorized. O-Cloud platform shall use an authorization mechanism to control the access rights of users. REQ-SEC-OCLOUD-3: Means of isolation of control and resources among different users shall be ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.1.2 Security Controls | SEC-CTL-OCLOUD-1: O-Cloud platform should support access management to O-Cloud resources based on RBAC (Role-based access control) policies. SEC-CTL-OCLOUD-2: O-Cloud platform shall support Multi-Factor Authentication (MFA) [46] to ensure secure access. 5.1.8.2 Software Package Protection at the O-Cloud Network Functio... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.2.1 Requirements | REQ-SEC-OCLOUD-IMG-1 to 18: VOID. REQ-SEC-OCLOUD-PKG-1: The Application package shall be successfully authenticated and verified by the O-Cloud Platform during instantiation from the trust images repository using signatures from both Application Provider and Service Provider. REQ-SEC-OCLOUD-PKG-2: O-Cloud Platform shal... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.2.2 Security Controls | SEC-CTL-OCLOUD-IMG-1 to 4: VOID. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.3 O-Cloud Software Images Protection | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.3.0 Introduction | The identified requirements and controls in this clause are enforcing the protection of O-Cloud software images during both initial deployment and subsequent updates. EXAMPLE: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor/Container Engine. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.3.1 Requirements | REQ-SEC-OCLOUD-SW-1: All O-Cloud software images shall be protected to ensure their integrity and authenticity. REQ-SEC-OCLOUD-SW-2: The O-Cloud shall support the capability to perform vulnerability scanning on O-Cloud software images. The activation and enforcement of this vulnerability scanning prior to the deploymen... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.3.2 Security Controls | SEC-CTL-OCLOUD-SW-1: For all deployments and updates, the O-Cloud shall verify the digital signature associated with the new O-Cloud software image before installing the software package. The algorithms, key sizes, and standards used for signature generation and verification shall adhere to the 'O-RAN Security Protocol... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.4 O-Cloud Virtualization and Isolation | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.4.1 Introduction | This clause contains security requirements and controls to mitigate threats to O-Cloud Virtualization layer (Host OS-Hypervisor/Container engine/Cloud platform software components) and provide isolation to the Applications hosted on the O-Cloud. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.4.2 Requirements | REQ-SEC-OCLOUD-ISO-1: O-Cloud shall implement means of preventing privilege escalation by Applications. REQ-SEC-OCLOUD-ISO-2: The communication between the different Applications shall be mutually authenticated and authorized. REQ-SEC-OCLOUD-ISO-3: The O-Cloud consumer and provider shall together ensure that the Applic... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.4.3 Security Controls | SEC-CTL-O-CLOUD-ISO-1: For mutual authentication between O-Cloud platform software components, mTLS shall be supported as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-O-CLOUD-ISO-2: For confidentiality and integrity protection of data in transit, O-Cloud platform software components sha... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.5 Secure update | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.5.0 Introduction | The identified requirements and controls in this clause are enforcing the secure update of O-Cloud software. EXAMPLE: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor/Container Engine. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.5.1 Requirements | REQ-SEC-OCLOUD-SU-1: All software within the O-Cloud platform shall be kept up to date with the last security updates for adding additional security protections and correcting vulnerabilities [i.1]. REQ-SEC-OCLOUD-SU-2: VOID. REQ-SEC-OCLOUD-SU-3: VOID. REQ-SEC-OCLOUD-SU-4: VOID. REQ-SEC-OCLOUD-SU-5: In case of an incom... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.5.2 Security Controls | SEC-CTL-OCLOUD-SU-1: VOID. SEC-CTL-OCLOUD-SU-2: VOID. SEC-CTL-OCLOUD-SU-3: VOID. SEC-CTL-OCLOUD-SU-4: The O-Cloud shall possess the capability to detect and retrieve the latest security updates of the O-Cloud software images. NOTE: This ensures that all O-Cloud software components can be consistently updated with the l... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.6 Secure Protection of cryptographic keys and sensitive data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.6.1 Requirements | REQ-SEC-OCLOUD-SS-1: Sensitive data within the O-Cloud platform shall be protected in terms of integrity and confidentiality at rest, in use and in transit. REQ-SEC-OCLOUD-SS-2: The O-Cloud platform shall support a secure deletion method from both active and backup storage medias. REQ-SEC-OCLOUD-SS-3: The O-Cloud platf... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.6.2 Security Controls | SEC-CTL-OCLOUD-SS-1: The O-Cloud shall support the capability for encryption of all sensitive data, including cryptographic keys, credentials, tokens, and configuration data. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 33 SEC-CTL-OCLOUD-SS-2: The O-Cloud shall support the capability for secure deletion of data in addressable... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.7 Chain of Trust | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.7.1 Requirements | REQ-SEC-OCLOUD-COT-1: The O-Cloud platform shall support a root of trust that verifies the integrity of every relevant component in the O-Cloud platform [i.1], [i.2]. REQ-SEC-OCLOUD-COT-2: It shall be possible to attest an O-RAN Application through the full attestation chain from the hardware layer through the virtuali... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.7.2 Security Controls | SEC-CTL-OCLOUD-COT-1: The chain of trust shall be built from measurements stored in a hardware root of trust. SEC-CTL-OCLOUD-COT-2: The chain of trust shall be built from measurements stored in a software root of trust for scenarios where a hardware root of trust is not feasible or available. SEC-CTL-OCLOUD-COT-3: A re... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.8 AAL | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.8.0 Introduction | There are two different scenarios of deployment of the hardware accelerator manager: • Scenario 1: the hardware accelerator manager is a SW component part of the O-Cloud platform and outside the hardware accelerator device. It is linked to the hardware accelerator device via a vendor specific interface. • Scenario 2: T... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.8.1 Requirements and Security Controls on AAL interfaces | 5.1.8.8.1.1 AALI-C-Mgmt 5.1.8.8.1.1.1 Requirements REQ-SEC-AALI-C-Mgmt-1: The hardware accelerator manager shall authenticate O-Cloud IMS/DMS when O-Cloud IMS/DMS initiates a communication to the hardware accelerator manager over AALI-C-Mgmt interface. REQ-SEC-AALI-C-Mgmt-2: The hardware accelerator manager shall check... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.8.2 Specific Requirements and Security Controls on AAL components | 5.1.8.8.2.1 Requirements REQ-SEC-AAL-1: The hardware accelerator device shall provide the capability for memory to be cleared securely prior to allocation or when indicated by the AAL Application on returning the memory. REQ-SEC-AAL-2: The AAL Implementation shall clear memory prior to allocation or when indicated by t... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.9 O2dms/O2ims/O-Cloud Notification APIs | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.9.1 Requirements | 5.1.8.9.1.1 O2dms REQ-SEC-OCLOUD-O2dms-1: O-Cloud DMS shall authenticate SMO (NFO or any other entity using O2dms) when SMO initiates a communication to O-Cloud for the deployment and management of Applications over O2dms interface. REQ-SEC-OCLOUD-O2dms-2: O-Cloud DMS shall be able to establish securely protected conne... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.9.2 Security Controls | SEC-CTL-O-CLOUD-INTERFACE-1: For the security protection at the transport layer on O2 interface, TLS shall be supported as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-O-CLOUD-INTERFACE-2: For the authorization of O2 RESTful and O-Cloud Notification APIs requests and notifications, OAut... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.10 O-Cloud hardware | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.10.1 Introduction | This clause contains security requirements and controls on the O-Cloud hardware to protect sensitive data. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.10.2 Requirements | REQ-SEC-O-CLOUD-HW-1: O-Cloud hardware deployment shall be protected against unauthorized extraction or inference of sensitive information using physical methods. NOTE: O-Cloud hardware deployment refers to the hardware used to build the operator's O-Cloud infrastructure. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.10.3 Security Controls | SEC-CTL-O-CLOUD-HW-1: O-Cloud hardware deployment should implement physical access restrictions to deny unauthorized access. NOTE: O-Cloud hardware deployment refers to the hardware used to build the operator's O-Cloud infrastructure. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 37 |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.11 O-Cloud instance ID | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.11.0 Introduction | The following set of requirements and controls outlines the essential criteria concerning the O-Cloud instance ID. This ID is a cornerstone for uniquely identifying and managing various components, including VMs, pods, containers, nodes, and compute pools within the O-Cloud platform. Safeguarding its global uniqueness,... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.11.1 Requirements | REQ-SEC-OCLOUD-INST-ID-1: The O-Cloud instance ID shall be unique within the O-Cloud platform to prevent conflicts and ensure accurate identification. REQ-SEC-OCLOUD-INST-ID-2: The O-Cloud instance ID shall not be exposed in public-facing interfaces, APIs, or logs without proper authentication and authorization mechani... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.11.2 Security Controls | SEC-CTL-OCLOUD-INST-ID-1: O-Cloud instance IDs shall be generated using strong randomization methods to ensure a high degree of uniqueness and minimize the likelihood of collisions. EXAMPLE: Implementation (Kubernetes-specific): - Kubernetes generates unique instance IDs, called Pod names, by combining factors like pse... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.12 Time Synchronization and Consistency Requirements for O-Cloud | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.12.0 Introduction | The requirements listed below highlight the O-Cloud's focus on creating a secure time synchronization framework with NTP as the focus. The requirement and security controls below in this clause are not applicable to PTP. By ensuring each node of the O-Cloud connects to a trusted and authenticated time source, O-Cloud a... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.12.1 Requirements | REQ-SEC-OCLOUD-TS-1: All O-Cloud nodes shall be configured to connect to a secure and authenticated time synchronization server for ToD synchronization. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 38 REQ-SEC-OCLOUD-TS-2: The O-Cloud shall be configured such that ToD synchronization is maintained across all nodes in an O-Clou... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.8.12.2 Security Controls | SEC-CTL-OCLOUD-TS-1: The O-Cloud shall ensure that all nodes are configured to exclusively connect to a secure and authenticated time synchronization server for Time of Day (ToD) synchronization. EXAMPLE 1: • NTP Usage: The O-Cloud should primarily use the Network Time Protocol (NTP) for general time synchronization ne... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.9 Shared O-RU | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.9.1 Security Requirements | REQ-SEC-SharedORU-1: The Shared O-RU shall mutually authenticate with an O-RU Controller. REQ-SEC-SharedORU-2: The Shared O-RU shall provide least privilege access to each SRO based upon its sro-id. REQ-SEC-SharedORU-3: The Shared O-RU shall provide separate confidentiality and integrity protection of data-at-rest for ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.1.9.2 Security Controls | SEC-CTL-SharedORU-1: The Shared O-RU shall support mTLS 1.2, or higher, as specified in O-RAN Security Protocols Specifications [3], clause 4.2 for mutual authentication on the M-Plane interface with an O-RU Controller. SEC-CTL-SharedORU-2: The Shared O-RU should not use password-based authentication with an O-RU Contr... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2 Interfaces maintained by O-RAN | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.1 A1 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.1.0 Introduction | The A1 Interface is defined in the A1 specifications [5]. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 40 |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.1.1 Requirements | REQ-SEC-A1-1: A1 interface shall support confidentiality, integrity, replay protection. REQ-SEC-A1-2: A1 interface shall support mutual authentication and authorization. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.1.2 Security Controls | Figure 5.2.1.2-1: mTLS on A1 interface SEC-CTL-A1-1: For the security protection at the transport layer on A1 interface, TLS shall be supported as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-A1-2: For the mutual authentication of the Non-RT RIC and one or more Near-RT RICs, the A1 inte... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2 O1 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.0 Introduction | O1 Interface connecting the SMO to the Near-RT RIC, may have one or more O-CU-CPs, one or more O-CU-UPs, and one or more O-DUs. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.1 Requirements | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.1.1 Summary | This clause specifies the requirements for O1 NACM support post function initialization when the function is in operation. NACM requirements related to network function initialization and when repairing broken access control configuration will be addressed in a future release of the present document. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.1.2 Confidentiality, Integrity and Authenticity | REQ-TLS-FUN-1: O1 interface implementations that support TLS for confidentiality and integrity protection shall support TLS as specified in O-RAN Security Protocols Specification [3], clause 4.2. REQ-TLS-FUN-2: O1 interface implementations that support mTLS for mutual authentication shall support mTLS 1.2, or higher, a... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.1.3 Least Privilege Access Control | REQ-NAC-FUN-1: Management Service providers and consumers that use NETCONF shall support the Network Configuration Access Control Model (NACM) as specified in IETF RFC 8341 [10] to restrict NETCONF protocol access for users to a preconfigured subset of available NETCONF protocol operations and content. REQ-NAC-FUN-2: T... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.2.2 Security Controls | As defined in the previous clause 5.2.2.1.2, the O1 will use TLS 1.2 or higher to enforce confidentiality, integrity, and authenticity; and will use NACM [10] to enforce least privileged access. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.3 O2 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.3.0 Introduction | General Aspects and Principles of O2 Interface between the SMO and the O-Cloud are defined in [6]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.3.1 Requirements | REQ-SEC-O2-1: O2 interface shall support confidentiality, integrity, replay protection and data origin authentication. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.3.2 Security Controls | SEC-CTL-O2-1: Management Service providers and consumers that use TLS shall support TLS as specified in O-RAN Security Protocols Specifications [3], clause 4.2. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.4 E2 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.4.0 Introduction | General Aspects and Principles of E2 Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs are defined in [7]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.4.1 Requirements | REQ-SEC-E2-1: E2 interface shall support confidentiality, integrity, replay protection and data origin authentication. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.4.2 Security Controls | SEC-CTL-E2-1: For the security protection at the IP layer on E2 interface, IPsec shall be supported as specified in O-RAN Security Protocols Specifications [3], clause 4.5. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5 Open Fronthaul Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.1 C-plane | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.1.1 Introduction | The O-DU sends UL C-plane messages and DL C-plane messages to O-RU to trigger transmission and reception of RF signals. The DL C-plane message describing multiple symbols must arrive at O-RU within a certain time window for the O-RU to successfully receive DL I/Q data in U-plane messages from O-DU. Likewise, the UL C-p... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.1.2 Requirements | REQ-SEC-OFCP-1: The C-Plane shall support authentication and authorization of O-DUs that exchange C-plane messages with O-RUs. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 43 REQ-SEC-OFCP-2: The O-DU shall be able to detect and defend against application level attacks across the C-Plane messages with O-RUs, due to misbehavior... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.