hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.1 DoS Attack against a Master Clock | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.1.0 Overview | The tests outlined in this clause evaluate the system's defence capabilities against DoS attacks targeting the master clock, especially in different LLS configurations. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.1.1 DOS Master Clock LLS C1 C2 C3 | Requirement Name: S-Plane DoS protection Requirement Reference & Description: 'REQ-SEC-DOS-1' clause 5.3.5 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-SPLANE-01' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: O-RU, O-DU Test Name: TC_DOS_MASTER_C... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.1.2 DOS Master Clock LLS C4 | Requirement Name: S-Plane DoS protection Requirement Reference & Description: 'REQ-SEC-DOS-1' clause 5.3.5 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-SPLANE-01' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: O-RU, O-DU Test Name: TC_DOS_MASTER_C... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.2 Spoofing of Master Clocks in the S-Plane | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.2.0 Overview | The tests presented in this clause focus on assessing the system's defences against potential spoofing attacks on master clocks. Specifically, these tests examine scenarios where attackers may try to impersonate or manipulate the master clock's communications to disrupt accurate time synchronization. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.2.1 Impersonation Master Clock | Requirement Name: Spoofing Prevention for Master Clocks in the S-Plane Requirement Reference & Description: 'REQ-SEC-OFSP-2' clause 5.2.5.3.2 in O-RAN Security and Controls Requirements Specifications [5] Threat References: 'T-SPLANE-02, T-SPLANE-03' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.2.2 Rogue PTP Instance | Requirement Name: Spoofing Prevention for Master Clocks in the S-Plane Requirement Reference & Description: 'REQ-SEC-OFSP-2' clause 5.2.5.3.2 in O-RAN Security and Controls Requirements Specifications [5] Threat References: 'T-SPLANE-02, T-SPLANE-03' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.3 Clock Accuracy Protection Against MITM Attacks | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.3.0 Overview | This clause delves into tests specifically designed to gauge the system's robustness when facing MITM attacks targeting clock synchronization. Such MITM attacks could manifest as the selective interception and removal of crucial PTP timing packets or the deliberate introduction of delays to these packets. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.3.1 Selective Interception and Removal of PTP Timing Packets | Requirement Name: Clock Accuracy Protection Against MITM Attacks Requirement Reference & Description: 'REQ-SEC-OFSP-3' clause 5.2.5.3.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-SPLANE-04, T-SPLANE-05' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment [3] DU... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.1.5.3.2 Delay Attack on PTP Timing Packets | Requirement Name: Clock Accuracy Protection Against MITM Attacks Requirement Reference & Description: 'REQ-SEC-OFSP-3' clause 5.2.5.3.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-SPLANE-04, T-SPLANE-05' clause 5.4.1.2 in O-RAN Security Threat Modeling and Risk Assessment [3] DU... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2 Y1 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.0 Overview | This clause delineates a series of test cases aimed at validating the security of the Y1 interface within the O-RAN architecture. The tests focus on five critical security facets: confidentiality, integrity, anti-replay, authenticity, and authorization. These are paramount in ensuring a robust and secure communication ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.1 Y1 Authenticity | Requirement Name: Y1 protection in terms of authenticity ETSI ETSI TS 104 105 V7.0.0 (2025-06) 126 Requirement Reference & Description: 'REQ-SEC-Y1-1', 'REQ-SEC-Y1-5', 'REQ-SEC-Y1-6' clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-Y1-01', T-Y1-02', T-Y1-03' clause 7.4... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.2 Y1 Confidentiality, integrity, and replay | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.2.1 Y1 Confidentiality | Requirement Name: Y1 protection in terms of confidentiality Requirement Reference & Description: 'REQ-SEC-Y1-3', 'REQ-SEC-Y1-4' clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-Y1-01', T-Y1-02', T-Y1-03' clause 7.4.1.13 in O-RAN Security Threat Modeling and Risk Assess... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.2.2 Y1 Integrity | Requirement Name: Y1 protection in terms of integrity Requirement Reference & Description: 'REQ-SEC-Y1-3', 'REQ-SEC-Y1-4' clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-Y1-01', T-Y1-02', T-Y1-03' clause 7.4.1.13 in O-RAN Security Threat Modeling and Risk Assessment [... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.2.3 Y1 Replay | Requirement Name: Y1 protection in terms of replay Requirement Reference & Description: 'REQ-SEC-Y1-3', 'REQ-SEC-Y1-4' clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-Y1-01', T-Y1-02', T-Y1-03' clause 7.4.1.13 in O-RAN Security Threat Modeling and Risk Assessment [3] ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.2.3 Y1 Authorization | Requirement Name: Y1 protection in terms of mutual Authorization Requirement Reference & Description: 'REQ-SEC-Y1-2', 'REQ-SEC-Y1-6' clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-Y1-01', T-Y1-02', T-Y1-03' clause 7.4.1.13 in O-RAN Security Threat Modeling and Risk A... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3 O1 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.0 Overview | This clause delineates a series of test cases aimed at validating the security of the O1 interface within the O-RAN architecture. The tests focus on five critical security facets: confidentiality, integrity, anti-replay, authenticity, and authorization. These are paramount in ensuring a robust and secure communication ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.1 O1 Authenticity | Requirement Name: O1 protection in terms of authenticity Requirement Reference & Description: 'REQ-TLS-FUN-1' clause 5.2.2.1 in O-RAN Security Requirements and Controls Specifications [5] ETSI ETSI TS 104 105 V7.0.0 (2025-06) 133 Threat References: 'T-MPLANE-01' clause 5.4.1.2, clause 5.4.1.1 'T-O-RAN-05' in O-RAN Secu... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.2 O1 Confidentiality, integrity and replay | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.2.1 O1 Confidentiality | Requirement Name: O1 protection in terms of confidentiality Requirement Reference & Description: 'REQ-TLS-FUN-1' clause 5.2.2.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-MPLANE-01' clause 5.4.1.2, 'T-O-RAN-05' clause 5.4.1.1 in O-RAN Security Threat Modeling and Risk Assessmen... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.2.2 O1 Integrity | Requirement Name: O1 protection in terms of integrity Requirement Reference & Description: 'REQ-TLS-FUN-1' clause 5.2.2.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-MPLANE-01' clause 5.4.1.2, 'T-O-RAN-05' clause 5.4.1.1 in O-RAN Security Threat Modeling and Risk Assessment [3] ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.3.0 Overview | Following zero trust principles, O-RAN O1 interface shall enforce confidentiality, integrity and authenticity through an encrypted transport, and shall support least privilege access control using the network configuration access control model. The network configuration access control model (NACM) [14] provides the mea... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.3.3.1 O1 Interface NACM Validation | Requirement Name: O1 Interface security requirements Requirement Reference: 'REQ-NAC-FUN-1 to REQ-NAC-FUN-10', clause 5.2.2.1 in O-RAN Security Requirements and Controls Specifications [5] Requirement Description: Requirements of O1 Interface Confidentiality, Integrity & Authenticity protection and Least Privilege Acce... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4 O2 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.0 Overview | This clause delineates a series of test cases aimed at validating the security of the O2 interface within the O-RAN architecture. The tests focus on five critical security facets: confidentiality, integrity, anti-replay, authenticity, and authorization. These are paramount in ensuring a robust and secure communication ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.1 O2 Authenticity | Requirement Name: O2 protection in terms of authenticity Requirement Reference: 'REQ-SEC-OCLOUD-O2dms-1, REQ-SEC-OCLOUD-O2ims-1', clause 5.1.7.9 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O2-01' clause 5.4.2.5.1 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: S... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.2 O2 Confidentiality | Requirement Name: O2 protection in terms of confidentiality Requirement Reference: 'REQ-SEC-OCLOUD-O2dms-2, REQ-SEC-OCLOUD-O2ims-2' clause 5.1.7.9 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O2-01' clause 5.4.2.5.1 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s:... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.3 O2 Integrity | Requirement Name: O2 protection in terms of integrity Requirement Reference: 'REQ-SEC-OCLOUD-O2dms-2, REQ-SEC-OCLOUD-O2ims-2' clause 5.1.7.9 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O2-01' clause 5.4.2.5.1 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: SMO, ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.4 O2 Replay | Requirement Name: O2 protection in terms of anti-replay Requirement Reference: 'REQ-SEC-OCLOUD-O2dms-2, REQ-SEC-OCLOUD-O2ims-2' clause 5.1.7.9 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O2-01' clause 5.4.2.5.1 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: SMO... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.4.5 O2 Authorization | Requirement Name: O2 protection in terms of authorization Requirement Reference: 'REQ-SEC-OCLOUD-O2dms-3, REQ-SEC-OCLOUD-O2ims-3' clause 5.1.7.9 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O2-01' clause 5.4.2.5.1 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: S... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5 E2 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.0 Overview | This clause focuses on verifying the confidentiality, integrity, replay protection, and authenticity of data over the E2 interface. Through a series of meticulously designed tests, the E2 interface's robustness against potential threats is ascertained. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.1 E2 Confidentiality | Requirement Name: Data confidentiality protection over E2 interface Requirement Reference & Description: 'REQ-SEC-E2-1, SEC-CTL-E2, SEC-CTL-NEAR-RT-2, SEC-CTL-NEAR- RT-7' clause 5.2.4 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O-RAN-05' clause 5.4.1, 'T-NEAR-RT-01, 02, 03 & 04'... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.2 E2 Integrity | Requirement Name: Data integrity protection over E2 interface Requirement Reference & Description: 'REQ-SEC-E2-1' clause 5.2.4 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O-RAN-05' clause 5.4.1, 'T-NEAR-RT-01, 02, 03, 04' clause 5.4.1.4 in O-RAN Security Threat Modeling and Risk... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.3 E2 Replay | Requirement Name: Data replay protection over E2 interface Requirement Reference & Description: 'REQ-SEC-E2-1' clause 5.2.4 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O-RAN-05' clause 5.4.1, 'T-NEAR-RT-01, 02, 03 & 04' clause 5.4.1.4, 'T-xAPP-01' clause 5.4.1.6 in O-RAN Securit... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.4 E2 Authenticity | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.4.1 E2 Authenticity with certificate | Requirement Name: Data Authentication over E2 interface Requirement Reference & Description: 'REQ-SEC-E2-1' clause 5.2.4 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O-RAN-05' clause 5.4.1, 'T-NEAR-RT-01, 02, 03 & 04' clause 5.4.1.4 in O-RAN Security Threat Modeling and Risk Asse... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.4.2 E2 Authenticity with PSK | Requirement Name: Data Authentication over E2 interface Requirement Reference & Description: 'REQ-SEC-E2-1' clause 5.2.4 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-O-RAN-05' clause 5.4.1, 'T-NEAR-RT-01, 02, 03 & 04' clause 5.4.1.4 in O-RAN Security Threat Modeling and Risk Asse... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.5.4.3 E2 Interface data validation by Near-RT RIC | Requirement Name: Validation of the data received via E2 interface by Near-RT RIC Requirement Reference: - SEC-CTL-NEAR-RT-17 - clause 5.1.3.2, Security Controls, Near-RT RIC and xApps, O- RAN Security Requirements and Controls Specification [5] Requirement Description:- The Near-RT RIC shall verify data received throu... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.6 A1 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.6.1 A1 Authenticity | Requirement Name: A1 protection in terms of authenticity Requirement Reference & Description: 'REQ-SEC-A1-2, SEC-CTL-A1-2' clause 5.2.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-A1-01' clause 7.4.1.10 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: Non-RT RIC,... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.6.2 A1 Confidentiality, integrity and replay | Requirement Name: A1 protection in terms of confidentiality, integrity, and replay ETSI ETSI TS 104 105 V7.0.0 (2025-06) 157 Requirement Reference & Description: 'REQ-SEC-A1-1', 'SEC-CTL-A1' clause 5.2.1.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-A1-02', T-A1-03' clause 7.4.1... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.6.3 A1 Authorization | Requirement Name: A1 protection in terms of authorization Requirement Reference & Description: 'REQ-SEC-A1-2', 'SEC-CTL-A3' clause 5.2.1.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-A1-01' clause 7.4.1.10 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: Non-RT R... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.7 R1 | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.7.1 R1 Authenticity | Requirement Name: R1 protection in terms of authenticity Requirement Reference & Description: 'REQ-SEC-R1-2' clause 5.2.6.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-R1-03' clause 7.4.1.9 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: Non-RT RIC, rApps Test N... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.7.2 R1 Confidentiality, integrity and replay | Requirement Name: R1 protection in terms of confidentiality, integrity and replay Requirement Reference & Description: 'REQ-SEC-R1-1' clause 5.2.6.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-R1-06, T-R1-07' clause 7.4.1.9 in O-RAN Security Threat Modeling and Risk Assessment [... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 11.7.3 R1 Authorization | Requirement Name: R1 protection in terms of authorization Requirement Reference & Description: 'REQ-SEC-R1-2' clause 5.2.6.1 in O-RAN Security Requirements and Controls Specifications [5] Threat References: 'T-R1-01, T-R1-04, T-R1-05' clause 7.4.1.9 in O-RAN Security Threat Modeling and Risk Assessment [3] DUT/s: Non-R... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 12 Security test of O-RU | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 12.1 Overview | This clause contains security tests to validate the security protection mechanism specific to O-RU. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 12.2 SSH on M-Plane interface | Requirement Name: Network Security Protocol - SSH Requirement Reference: clause 5.4, O-RAN Fronthaul Management Plane Specification [21] Requirement Description: Robust protocol implementation with adequately strong cipher suites is being required for SSH Threat References: T-O-RAN-05 ETSI ETSI TS 104 105 V7.0.0 (2025-... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 12.3 TLS on M-Plane interface | Requirement Name: Network Security Protocol - TLS Requirement Reference: clause 5.4, O-RAN Fronthaul Management Plane Specification [21] Requirement Description: Support TLS v1.2 and/or TLS v1.3 with protocol profiles Threat References: T-O-RAN-05 DUT/s: O-RU Test name: TC_TLS_MPlane Test Description Purpose: To verify... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 12.4 Security functional requirements and test cases | The 802.1X Supplicant Validation test cases in clause 11.2.2 of the present document apply to O-RU. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13 Security test of Near-RT RIC | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.1 Overview | This clause contains security tests to validate the security protection mechanism specific to Near-RT RIC. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.2 Void | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.3 Transactional APIs | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.3.1 Introduction | Transactional APIs in the Near-RT RIC are APIs that are based on HTTP/TLS, i.e. APIs based on REST or gRPC. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.3.2 TLS for transactional APIs | Requirement Name: TLS for transactional APIs Requirement Reference: SEC-CTL-NEAR-RT-6, clause 5.1.3.2, O-RAN Security Requirements and Controls Specification [5]. Requirement Description: "Transactional APIs (REST and gRPC) shall support TLS to provide message confidentiality and integrity." Threat References: T-NEAR-R... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.3.3 mTLS for transactional APIs | Requirement Name: mTLS for transactional APIs ETSI ETSI TS 104 105 V7.0.0 (2025-06) 165 Requirement Reference: REQ-SEC-NEAR-RT-3, clause 5.1.3.2, O-RAN Security Requirements and Controls Specification [5]. Requirement Description: "The communication between xApps and Near-RT RIC platform APIs shall be mutually authenti... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.3.4 OAuth 2.0 for transactional APIs | Requirement Name: OAuth 2.0 for transactional APIs Requirement Reference: REQ-SEC-NEAR-RT-4, REQ-SEC-NEAR-RT-5, clause 5.1.3.1, O-RAN Security Requirements and Controls Specification [5]. Requirement Description: Near-RT RIC architecture provides an authorization framework. Threat References: T-NEAR-RT-01, T-NEAR-RT-02... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.4.1 Overview | This clause contains security tests to verify OAuth2.0 implementation on Near-RT RIC as resource owner/server for A1-P. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.4.2 Near-RT RIC OAuth 2.0 Resource Owner/Server | Requirement Name: Near-RT RIC support as OAuth2.0 resource owner/server Requirement Reference: Clause 5.1.3.2, Security Controls, Near-RT RIC and xApps, O -RAN Security Requirements and Controls Specification [5] Requirement Description: OAuth 2.0 security controls for Near-RT RIC authorization of service requests Thre... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.5 Security test of Near-RT RIC OAuth 2.0 client | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.5.1 Overview | This clause contains security tests to verify the implementation on Near-RT RIC as OAuth2.0 client for A1-EI. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 13.5.2 Near-RT RIC OAuth 2.0 client | Requirement Name: Near-RT RIC support as OAuth2.0 client for A1-EI Requirement Reference: Clause 5.1.3.2, Security Controls, Near-RT RIC and xApps, O-RAN Security Requirements and Controls Specification [5] Requirement Description: OAuth 2.0 security controls for Near-RT RIC authorization of service requests ETSI ETSI ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14 Security test of xApps | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.1 Overview | This clause contains security tests to validate the security protection mechanism specific to xApps deployed on Near- RT RIC. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.2 xApp Signing and Verification | Security test cases "TC_SW_Img_Pkg_Signing" and "TC_SW_Img_Pkg_Verification" shall be performed. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.3 xAppID | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.3.0 Overview | This clause contains security tests to validate the xApp ID which is a string that uniquely identifies the xApp instance. The format of this string is a Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 4122 [6]). |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.3.1 xApp ID format check | Requirement Name: xApp ID uniqueness check for the xApp instance Requirement Reference: - SEC-CTL-NEAR-RT-13- clause 5.1.3.2, Security Controls, Near-RT RIC and xApps, O-RAN.WG11.Security Requirements and Controls Specification [5] Requirement Description: To validate the format of xApp ID string and the uniqueness of ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 14.3.2 xApp ID in xApp instance Certificate | Requirement Name: xApp ID presence in "Subject Alternative Name" field of the xApp instance certificate. Requirement Reference: - SEC-CTL-NEAR-RT-14 - clause 5.1.3.2, Security Controls, Near-RT RIC and xApps, O-RAN.WG11.Security Requirements and Controls Specification [5]. Requirement Description: "Subject Alternative ... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15 Security test of Non-RT RIC | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.1 Overview | This clause contains security tests to validate the security protection mechanism specific to Non-RT RIC and the R1 and A1 interfaces. Security test cases for rApps are covered in a separate sub-clause. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.2 Non-RT RIC | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.2.0 Overview | Following zero trust principles, O-RAN Non-RT RIC shall enforce authorization using OAuth 2.0 |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.2.1 Non-RT RIC OAuth 2.0 Resource Owner/Server | Requirement Name: Server authorization support Requirement Reference: REQ-SEC-NonRTRIC-1, clause 5.1.2.1, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: Non-RT RIC supports OAuth 2.0 as a Server Threat References: T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 DUT/s: Non-RT RIC Test N... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.2.2 Non-RT RIC OAuth 2.0 Client | Requirement Name: Client authorization support Requirement Reference: REQ-SEC-NonRTRIC-1, clause 5.1.2.1, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: Non-RT RIC supports OAuth 2.0 as a Client Threat References: T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 DUT/s: Non-RT RIC Test N... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.2.3 Non-RT RIC Framework OAuth 2.0 | Requirement Name: Framework Server authorization support Requirement Reference: REQ-SEC-NonRTRIC-2, clause 5.1.2.1, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: Non-RT RIC Framework supports OAuth 2.0 as a Server Threat References: T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 DUT/... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.3 R1 interface | Void. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 15.4 A1 interface | Void. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 16 Security test of rApps | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 16.1 Overview | This clause contains security tests to validate the security protection mechanism specific to rApps deployed on Non-RT RIC. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 16.2 rApp Signing and Verification | Security test cases "TC_SW_Img_Pkg_Signing" and "TC_SW_Img_Pkg_Verification" shall be performed. |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 16.3 rApp Authorization | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 16.3.1 rApp OAuth 2.0 Client | Requirement Name: rApp OAuth2.0 Client support Requirement Reference: REQ-SEC-NonRTRIC-3, clause 5.1.2.1, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: "rApps shall provide client authorization requests to the Non-RT RIC Framework." Threat References: T-rAPP-04 DUT/s: rApps Test N... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17 Security test of SMO | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.1 Overview | This clause contains security tests to validate security protection mechanisms related to the SMO. The test cases validate the security of SMO termination of O1 interfaces, SMO, SMO Services (SMOS) Communications, SMO External Interfaces, and SMO Logging are secured to zero trust principles for confidentiality, integri... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.2 Void | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.3 SMO | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.3.1 SMO OAuth 2.0 Resource Owner/Server | Requirement Name: SEC-CTL-SMO-3 Requirement Reference: Clause 5.2.1.2.1, Security Controls, SMO, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: OAuth 2.0 security controls for SMO to authorize service requests from SMO Functions. Threat References: T-SMO-02, T-SMO-05 DUT/s: SMO, SM... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.3.2 SMO OAuth 2.0 Client | Requirement Name: SEC-CTL-SMO-4 Requirement Reference: Clause 5.2.1.2.1, Security Controls, SMO, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: OAuth 2.0 security controls for SMO to support client functionality for service requests to other SMO Functions Threat References: T-SMO-0... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.3.3 SMO mTLS for mutual authentication | Requirement Name: SEC-CTL-SMO-5 Requirement Reference: Clause 5.2.1.2.1, Security Controls, SMO, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: SMO support mTLS for mutual authentication with SMO Functions. Threat References: T-SMO-01, T-SMO-04 DUT/s: SMO Test Name: TC_SMO_mTLS Tes... |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.4 SMO Internal Communications | |
0ce77be9f03a15fedfc038153382bd6a | 104 105 | 17.4.1 TLS for SMO Internal Communications | Requirement Name: SEC-CTL-SMO-Internal-1 Requirement Reference: Clause 5.2.1.2.2, Security Controls, SMO Internal Communications, O-RAN Security Requirements and Controls Specifications [5] Requirement Description: Data in transit protection with TLS for SMO Internal Communications Threat References: T-SMO-09 DUT/s: SM... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.