hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.1.3 Security Controls | 5.2.5.1.3.1 Authentication and Authorization of network elements supporting the C-Plane This clause addresses requirements REQ-SEC-OFCP-1 based on the use of IEEE 802.1X-2020 Port-based Network Access Control [12] for authentication and subsequent authorization of nodes that exchange C-Plane messages. Clause 5.2.5.5 of... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.2 U-plane | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.2.1 Requirements | Open Fronthaul U-plane transports 5G System Control Plane and User Plane messages between O-CU-CP and UE, and O-CU-UP and UE. The Packet Data Convergence Protocol (PDCP) [32] is an optional feature that may provide confidentiality and integrity protection of 5G System Control Plane and User Plane between O-CU-CP and UE... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.2.2 Security Controls | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.3 S-plane | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.3.1 Introduction | The Precision Time Protocol (PTP) is a protocol used to synchronize clocks within a PTP network. Within a PTP domain [27], the grandmaster clock is the source of time to which all other PTP clocks in the domain are synchronized. The IEEE 1588 standard specifies the Best Master Clock Algorithm (BMCA) for electing the be... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.3.2 Requirements | REQ-SEC-OFSP-1: The S-Plane shall support authentication and authorization of PTP nodes that communicate with other PTP nodes within Configuration LLS-C1, Configuration LLS-C2, or Configuration LLS-C3. NOTE 1: This ensures least privilege access to the S-Plane where authenticated and authorized PTP nodes communicate ov... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.3.3 Security Controls | 5.2.5.3.3.1 Synchronization Architecture Redundancy This clause addresses requirement REQ-SEC-OFSP-3 by providing an architectural recommendation to S-plane security based on redundancy in the Open Fronthaul Synchronization architecture. The following architectural recommendations for security controls build S-Plane re... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.4 M-plane | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.4.1 Requirements | The security requirements for M-Plane are defined in [14]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.4.2 Security Controls | The security controls for M-plane are defined in [14]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.5 Open Fronthaul Point-to-Point LAN Segment | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.5.0 Introduction | The Open Fronthaul Ethernet L1 physical interface comprises one or more coaxial cables, twisted pairs, or optical fibers. These are also known as point-to-point LAN segments [12]. Each end of the Open Fronthaul point-to-point LAN segment comprises a physical connection (colloquially known as an Ethernet Port) to physic... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.5.1 Requirements | REQ-SEC-OFHPLS-1: The Open Fronthaul shall provide a means to authenticate and authorize point-to-point LAN segments between Open Fronthaul network elements. REQ-SEC-OFHPLS-2: The Open Fronthaul shall provide a means to detect and report when an authorized point-to-point LAN segment is made or broken. REQ-SEC-OFHPLS-3:... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.5.5.2 Security Controls | 5.2.5.5.2.1 Solution #1: Authentication and Authorization based on 802.1x Port based Network Access Control IEEE 802.1X-2020 is optional to support. NOTE 1: Further security requirements for IEEE 802.1X-2020 [12] will continue to be studied. It is intended to evolve IEEE 802.1X-2020 [12] to a mandatory requirement for ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.6 R1 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.6.0 Introduction | R1 is the interface between rApps and Non-RT RIC Framework via which R1 Services can be produced and consumed. See R1 specification [39]. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.6.1 Requirements | REQ-SEC-R1-1: R1 interface shall support confidentiality, integrity, and replay protection. REQ-SEC-R1-2: R1 interface shall support mutual authentication and authorization. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.6.2 Security Controls | Figure 5.2.6.2-1: mTLS on R1 interface SEC-CTL-R1-1: For the security protection at the transport layer on R1 interface, TLS shall be supported as specified in O-RAN Security Protocols Specifications [3], clause 4.2. SEC-CTL-R1-2: For the mutual authentication of the Non-RT RIC Framework and rApps, the R1 interface sha... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.7 Y1 Interface | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.7.1 Introduction | The Near-RT RIC provides RAN analytics information services via Y1 service interface. These services can be consumed by Y1 consumers by subscribing to or requesting the RAN analytics information via the Y1 service interface. Y1 consumers may be Application Functions (AFs). The Near-RT RIC serves as Y1 provider. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.2.7.2 Requirements | REQ-SEC-Y1-1: The Y1 provider shall provide mechanisms to authenticate the Y1 consumer and allow for the Y1 consumer to authenticate the Y1 provider (mutual authentication). REQ-SEC-Y1-2: The Y1 provider shall authorize the Y1 consumer before allowing access to any service over the Y1 interface. REQ-SEC-Y1-3: The Y1 in... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3 Transversal requirements | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.1 Software Bill of Materials | Void. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.1.1 Requirements | Void. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2 Common Application Lifecycle Management | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.1 Package Protection | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.1.1 Requirements | REQ-SEC-ALM-FUN2-1: VOID. REQ-SEC-ALM-FUN3-1: VOID. REQ-SEC-ALM-PKG-1: The Application package shall be certified by the Application Provider. EXAMPLE 1: Software testing suites for certification include vulnerability scanning, static and dynamic testing, and penetration testing. Refer to clause C.2.1 for additional in... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.1.2 Security Controls | SEC-CTL-ALM-PKG-1: Application package shall be signed and verified for integrity and authenticity protection. To provide the authenticity and integrity protection for the Application package, one of the two following options shall be followed as defined in ETSI GS NFV-SEC 021 [41] and ETSI GS NFV-SOL 004 [42]: • Optio... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.2 Secure Update | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.2.1 Requirements | REQ-SEC-ALM-SU-1: Application updates shall follow the same security requirements as Application packages. REQ-SEC-ALM-SU-2: Applications should be updated with their latest security updates. REQ-SEC-ALM-SU-3: Applications should be protected from downgrade attacks to older, possibly vulnerable, software versions. REQ-... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.3 Security Descriptor | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.3.1 Requirements | REQ-SEC-LCM-SD-1: The Application descriptor shall support a description of the security group rules. Those rules shall be associated to the relevant Application interfaces. EXAMPLE: Security group rules include permissions, access control and filtering rules REQ-SEC-LCM-SD-2: The Application descriptor shall support a... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.4 Secure Deletion of Sensitive Data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.4.1 Introduction | Support for secure deletion of data owned by the Application is included in clause 5.1.8.6 for O-Cloud secure storage requirements and controls. NIST SP 800-88 [75] can provide additional guidance for data sanitization. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.4.2 Requirements | REQ-SEC-DEL-1: VOID. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 54 |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.4.3 Security Controls | SEC-CTL-DEL-1: VOID. SEC-CTL-DEL-2: VOID. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.5 Decommissioning of Applications | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.5.0 Introduction | NOTE: When an application is decommissioned, it is important to document the entire process. Another crucial task is to archive the legacy data and software for historical purposes. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.2.5.1 Requirements | REQ-SEC-ALM-DECOM-1: A complete post-decommission report documenting the performed tasks shall be generated. REQ-SEC-ALM-DECOM-2: Legacy data and software should be archived. REQ-SEC-ALM-DECOM-3: All trust artifacts associated with an application shall be revoked at the time of decommissioning. EXAMPLE: Trust artifacts... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.3 Network Protocols and Services | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.3.0 Introduction | Each O-RAN component serves important network function(s) based on a list of its necessary network protocols and services supported through its network interface(s). Proper, transparent, and secure network protocols and services enabled on each O-RAN component is essential for its overall security posture with the redu... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.3.1 Requirements | REQ-SEC-NET-1: A list of network protocols and services supported on the O-RAN component shall be clearly documented by its vendor. Unused protocols shall be disabled. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.4 Robustness of Common Transport Protocols | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.4.0 Introduction | IP, UDP, TCP, SCTP, SSH, HTTP and HTTP2 are the common transport protocols widely used by any O-RAN components for network communications and services. Robust implementation of those common transport protocols can significantly improve the security of each O-RAN component and system overall. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.4.1 Requirements | REQ-SEC-TRAN-1: Common transport protocols (IP, UDP, TCP, SCTP, SSH, HTTP and HTTP2) used in O-RAN system should be able to handle unexpected inputs (not in-line with protocol specification) without functional compromise. The unexpected inputs include random mutations of the protocol headers and payloads, as well as ta... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.5 Robustness against Volumetric DDoS Attack | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.5.0 Introduction | Distributed Denial of Service (DDoS) attack is one of the most common security risks for any O-RAN component. DDoS attack often results in service interruption and even worse system crash and prolonged network outage. A volumetric DDoS attack can come from a bad actor or adversary, or a misconfiguration by the operator... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.5.1 Requirements | REQ-SEC-DOS-1: An O-RAN element with external network interface shall be able to withstand network transport protocol based volumetric DDoS attack without system crash and returning to its normal service level after the attack subsides. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.5.2 Security Controls | SEC-CTL-DOS-1: An O-RAN element should be designed to incorporate redundant elements to achieve High Availability (HA). NOTE: The redundant High Availability (HA) elements play a crucial role in scalability of the O-RAN element to address the requirements of legitimate users when facing a volumetric Distributed Denial ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.6 Robustness of OS and Applications | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.6.0 Introduction | The robustness of the O-RAN component in the OS and application(s) installed is fundamental to the overall security posture of the O-RAN system. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.6.1 Requirements | REQ-SEC-SYS-1: Known vulnerabilities in the OS and applications of an O-RAN component shall be clearly identified. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.7 Password-Based Authentication | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.7.0 Introduction | Weak, stolen, and mis-used passwords are some of the common and leading causes of data breaches and methods of gaining access to systems, services, and applications. Password policy and management are applicable to both remote and Web UI login interfaces for user and automated machine password-based authentication on O... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.7.1 Requirements | REQ-SEC-PASS-1: If password is used as an authentication attribute, O-RAN component vendors should follow security best practices to mitigate risks resulting from different password-based authentication attacks such as brute-forcing, unauthorized password resets, man-in-the-middle, and dictionary attacks. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.7.2 Security Controls | SEC-CTL-PASS-1: Default passwords should be changed upon installation. Configured passwords should follow the organization's policies for strong passwords. SEC-CTL-PASS-2: O-RAN components shall support account lock-out for repeated failed login attempts. The number of failed login attempts shall be configurable. The n... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8 Security Log Management | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.1 Introduction | Security log management is "the process for generating, transmitting, storing, analyzing, and disposing of computer security log data. Log management is essential to ensuring that computer security records are stored in sufficient detail for an appropriate period of time. Routine log analysis is beneficial for identify... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.2 Generic Requirements | REQ-SEC-SLM-1: An O-RAN component shall support the generation and transmission of security log data. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.3 Micro Perimeter for Cluster Node | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.3.1 Requirements on Security Log Data Storage | REQ-SEC-SLM-TESS-1: The Security Log data which have been created within a micro perimeter shall be persistently stored in a non-volatile memory. This refers to Security Log data at rest. This applies to back-up Security Log data as well. REQ-SEC-SLM-TESS-2: Any anomalies detected in log settings, configurations, and p... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.3.2 Requirements on Security Log-data in Motion | REQ-SEC-SLM-TESM-1: The Security Log data in motion shall be protected with the help of the micro perimeter. REQ-SEC-SLM-TESM-2: The Security Log data in motion shall be confidentiality, integrity and replay protected if this is going to leave the micro perimeter. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 57 REQ-SEC-SLM-TE... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.3.3 Requirements for Setup of a Micro Perimeter | REQ-SEC-SLM-TE-1: The Micro Perimeter shall support the secure storage of sensitive data. REQ-SEC-SLM-TE-2: The Micro Perimeter shall support the execution of Security Log data sensitive functions, which are hosting the Log-Agent(s) and the Log-Collector. REQ-SEC-SLM-TE-3: The Micro Perimeter shall support the executio... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.4 Micro Perimeter for Log data Repository | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.4.1 Requirements on Storage in Log data Repository | REQ-SEC-TESR-1: The Security Log data stored in the repository shall be protected with the help of the micro perimeter. REQ-SEC-TESR-2: The Security Log data which have been created inside the trusted environment of the repository shall be persistently stored in a non-volatile memory. This refers to Log data at rest. T... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.5 Secure storage of security log data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.5.1 Introduction | Security log data storage involves the safekeeping and retention of security log data for a certain period of time. Security log data storage should ensure that all data of security events is retained reliably for a certain time so that no data is lost or altered, and access to the data is restricted to authorized pers... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.5.2 Requirements | REQ-SEC-SLM-SST-1: Security log data shall be stored in a centralized location for easy management and analysis. REQ-SEC-SLM-SST-2: Security log data shall be stored in a tamper-proof manner to ensure their integrity and authenticity. REQ-SEC-SLM-SST-3: Retention policies for security log data shall be established to d... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.5.3 Security Controls | SEC-CTL-SLM-SST-1: Centralized storage for security log data should be realized using centralized logging servers or cloud-based services. SEC-CTL-SLM-SST-2: Tamper-proof storage of security log data may be achieved through digital signature, encryption, and hashing techniques. SEC-CTL-SLM-SST-3: The retention period s... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.6 Secure Transfer of security log data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.6.1 Introduction | Security log transfer involves the movement of security log data from one location to another, such as from a local device to a centralized logging server. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.6.2 Requirements | REQ-SEC-SLM-STR-1: Security log data shall be confidentiality- and integrity- protected during transfer to protect them from unauthorized access or tampering. REQ-SEC-SLM-STR-2: The parties involved in the security log transfer shall mutually authenticate each other to ensure that the logs are coming from a trusted sou... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.6.3 Security Controls | SEC-CTL-SLM-STR-1: Digital signatures or Hash-based Message Authentication Codes (HMACs) may be used to provide integrity protection of security log data. SEC-CTL-SLM-STR-2: An O-RAN component may support the transport of Syslog as defined in IETF RFC 5424 [64] over TLS as defined in IETF RFC 5425 [65] for log streamin... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.7 Log Format | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.7.1 Introduction | Each O-RAN component produces logs in various formats. The logs are collected at a central and trusted location where the logs are unified. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.7.2 Requirements | REQ-SEC-SLM-FMT-1: Security logs shall be formatted in a consistent, standard, and machine-readable format that maintains backward compatibility with previous log format versions. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.8 Log Fields | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.8.1 Introduction | To enable effective security analytics, it is important to include additional details in the security logs of the security event. These details help to identify adversarial operations within the O-RAN environment. A typical security log entry consists of two main parts: the log fields and the log message. The log field... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.8.2 Requirements | REQ-SEC-SLM-FLD-1: Security logs shall include the date and time of the security event for each log entry, using a consistent and standardized format that logs time to at least the second. REQ-SEC-SLM-FLD-2: Security logs shall record the location of the security event for each log entry. For network transactions, the ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.8.3 Security Controls | SEC-CTL-SLM-FLD-1: Security logs should use the ISO 8601 [62] date and time format. SEC-CTL-SLM-FLD-2: Security logs shall use IP addresses for the location field. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.9 Authenticated Time Stamping and Missing Time Source | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.9.1 Requirements | REQ-SEC-SLM-ATS-1: All network functions shall be synchronised to a common and authenticated time source. REQ-SEC-SLM-ATS-2: Any successful as well as the unsuccessful synchronization to the common time source shall be logged. REQ-SEC-SLM-ATS-3: The Security Log-data shall be time-stamped with the system time in case o... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.9.2 Security Controls | 5.3.8.9.2.1 Authenticated Time Stamping SEC-CTL-SLM-ATS-1: The Network Time Protocol (NTP) version 4 should be supported as specified by IETF RFC 5905 [60] for the support of authenticated time stamping. SEC-CTL-SLM-ATS-2: If NTPv4 authentication is in use, then AES-CMAC as specified by IETF RFC 4493 [78] shall be supp... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.10 Security Log Management Due Diligence and Auditing | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.10.1 Requirements | REQ-SEC-SLM-DDA-1: The organization should define a policy and procedure for security logging. The security log management policy shall define periodic audits to confirm that logging standards and guidelines are being followed throughout the organization. REQ-SEC-SLM-DDA-2: The organization should ensure that the polic... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.10.2 Security Controls | SEC-CTL-SLM-DDA-1: Testing and validation should be used to ensure that the policies and procedures in the log management process are being performed properly. ETSI ETSI TS 104 104 V9.1.0 (2025-06) 61 SEC-CTL-SLM-DDA-2: While defining the log management scheme, organizations should ensure that they provide the necessar... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11 Security Events to be Logged | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.1 Introduction | During O-RAN operations, components generate many events. Some of these events have security utility and are thus termed security events. Logging these security events is critical to maintaining a secure O-RAN environment. For convenience, security event log requirements are organized by high-level categories. These ca... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.2 Network Security Event Log Requirements | REQ-SEC-SLM-NET-EVT-1: O-Cloud shall log all physical and virtual network events related to creating and modifying network configurations, enabling, and disabling ports, network connections, and packets over limit from the firewalls from all host operating systems, hypervisors, and container engines. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.3 System Security Event Log Requirements | 5.3.8.11.3.1 General O-Cloud Security Events 5.3.8.11.3.1.1 Requirements REQ-SEC-SLM-GEN-EVT-1: O-Cloud shall log the following resource-related events: shortages, system crashes, reboots, shutdowns, resource creation, and deletion from all host operating systems, hypervisors, and container engines. REQ-SEC-SLM-GEN-EVT... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.4 Application Security Event Log Requirements | REQ-SEC-SLM-APP-EVT-1: O-RAN Network Functions shall log any errors or exceptions generated. REQ-SEC-SLM-APP-EVT-2: O-RAN Network Functions shall log the use of any dynamically loaded libraries, including the name and version information of the library being loaded. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.5 Data Access Security Event Log Requirements | REQ-SEC-SLM-DAT-EVT-1: O-RAN components shall log successful file additions, deletions, and unsuccessful attempts due to errors and authorization issues. REQ-SEC-SLM-DAT-EVT-2: O-RAN components should log successful file reads and writes. REQ-SEC-SLM-DAT-EVT-3: O-RAN components shall log unsuccessful attempts of file r... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.6 Account and Identity Security Event Log Requirements | REQ-SEC-SLM-AAI-EVT-1: O-RAN components shall log account creation, modification, deletion, and unsuccessful attempts. REQ-SEC-SLM-AAI-EVT-2: O-RAN components shall log changes to account privilege levels and unsuccessful attempts. REQ-SEC-SLM-AAI-EVT-3: O-RAN components shall log successful group membership changes fo... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.11.7 General Security Event Log Requirements | REQ-SEC-SLM-GSE-1: O-RAN components shall log the activation and deactivation of security software related to security logging, firewalls, malware protection, Data Loss Prevention (DLP), and Intrusion Detection Systems (IDS). REQ-SEC-SLM-GSE-2: O-RAN components shall log the use of administrative privileges. REQ-SEC-SL... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.12 Log data Lifecycle Management | REQ-SEC-LCSS-2: The Security Log data process shall support Log data rotation. Log data rotation in this context refers to a closing of a Log-storage and opening a new Log-storage when the first Log-storage is complete. REQ-SEC-LCSS-3: The Security Log data rotation process shall be configurable at regular time interva... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.13 Requirements on Security Log data Policy | REQ-SEC-POL-5: The archived Security Log data and their storage media shall be checked periodically to determine whether the Security Log data is accessible. REQ-SEC-POL-6: The archived Log data and their media shall be physically protected. REQ-SEC-POL-7: The Personally Identifiable Information (PII) shall be removed ... |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.14 Preventing (D)DoS to Security Log Data | |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.14.1 General | The Requirements below are applicable to the vendors of the log management infrastructure. |
bdb2368fe245f24f55528d6ee26c2023 | 104 104 | 5.3.8.14.2 Requirements | REQ-SEC-SLM-DoS-1: The log management infrastructure should be designed to support typical and peak volume of log data to be processed per hour and day [58]. REQ-SEC-SLM-DoS-2: The log management infrastructure should support the handling of peak situations for extreme situations. Extreme situations in this context ref... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.