O-RAN E2 Node & O1 Management Interface Audit

O-RANNear-RT RICLab Ready

Overview & Audit Objective

The O-RAN Alliance specifies open, disaggregated interfaces across the Radio Access Network. This playbook demonstrates how to audit O-RAN architectures by simulating E2 Nodes (E2-DU / E2-CU), testing E2AP v2/v3 SCTP connections to Near-RT RICs, auditing E2SM-KPM telemetry streams, and scanning O1 NETCONF/YANG servers.

Execution Steps

1
Inspect O-RAN Subsystem Status:
Verify that O-RAN emulation tools and SCTP network sockets are operational:
Terminal — O-RAN Status Check
```
telcosec oran status
```
2
Scan O1 NETCONF Management Interface:
Audit target O1 management nodes for open ports, TLS certificate strength, and YANG model exposures:
Terminal — O1 NETCONF Audit
```
telcosec oran o1-scan 192.168.1.50
```
3
Launch E2 Node Simulation & xApp Telemetry:
Emulate an E2 Node streaming E2SM-KPM metrics to the Near-RT RIC:
Terminal — E2 Node Simulator
```
sudo oran-e2sim-install
telcosec oran e2-sim 127.0.0.1
```
4
Capture E2AP SCTP Packets in Wireshark:
Decode O-RAN E2 Application Protocol packets (PPID 70 over SCTP port 36421):
Terminal — Wireshark E2AP Capture
```
wireshark -k -i any -f "sctp port 36421" &
```

Evidence & Artifact Archiving

Export all E2AP PCAP traces and O1 scan logs into a signed audit bundle:

Terminal — Bundle Evidence

telcosec bundle-evidence oran-audit