BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
DTSTART:20240310T030000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20241103T010000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20240327T120106Z
UID:7DE3F4DC-D2B3-45A5-BC33-5820F3E3280D
DTSTART;TZID=America/New_York:20240320T110000
DTEND;TZID=America/New_York:20240320T120000
DESCRIPTION:The security challenges confronting Open RAN are like those fac
 ed by contemporary RAN systems and other virtualized architectures. The di
 vision of functions in Open RAN expands the potential threat landscape. Wh
 en implementing security measures\, such as encryption\, on the Open Front
 haul Interface\, it is essential to consider the stringent latency require
 ments of the RAN. The growing reliance on open-source software in modern t
 elecommunications platforms underscores the importance of secure developme
 nt practices within open-source communities for Open RAN. In addition\, th
 e integration of AI in the RAN introduces the possibility of unforeseen co
 nsequences\, as observed in other domains (e.g.\, racially biased facial r
 ecognition). Additionally\, the substantial increase in IoT devices necess
 itates that all RAN deployments guard against the rising risk of attacks b
 y compromised devices. Acknowledging these potential security challenges a
 nd recognizing the paramount importance of a secure RAN\, this presentatio
 n will outline security requirements and solutions that empower the O-RAN 
 architecture to deliver the expected level of security for both the indust
 ry and 5G users. The discussion will also spotlight the efforts of the O-R
 AN ALLIANCE Security Task Group (STG) and O-RAN ALLIANCE Working Groups (W
 Gs) in addressing security challenges across all O-RAN interfaces and comp
 onents\, specifying\, and recommending modern\, practical security solutio
 ns.\n\n*This event is being recorded\n\nCo-sponsored by: IEEE Future Netwo
 rks\n\nSpeaker(s): Taha Sajid\n\nVirtual: https://events.vtools.ieee.org/m
 /403461
LOCATION:Virtual: https://events.vtools.ieee.org/m/403461
ORGANIZER:c.polk@comsoc.org
SEQUENCE:6
SUMMARY:Optimizing ORAN Security Design and Considerations
URL;VALUE=URI:https://events.vtools.ieee.org/m/403461
X-ALT-DESC:Description: &lt;br /&gt;&lt;p&gt;The security challenges confronting Open R
 AN are like those faced by contemporary RAN systems and other virtualized 
 architectures. The division of functions in Open RAN expands the potential
  threat landscape. When implementing security measures\, such as encryptio
 n\, on the Open Fronthaul Interface\, it is essential to consider the stri
 ngent latency requirements of the RAN. The growing reliance on open-source
  software in modern telecommunications platforms underscores the importanc
 e of secure development practices within open-source communities for Open 
 RAN. In addition\, the integration of AI in the RAN introduces the possibi
 lity of unforeseen consequences\, as observed in other domains (e.g.\, rac
 ially biased facial recognition). Additionally\, the substantial increase 
 in IoT devices necessitates that all RAN deployments guard against the ris
 ing risk of attacks by compromised devices. Acknowledging these potential 
 security challenges and recognizing the paramount importance of a secure R
 AN\, this presentation will outline security requirements and solutions th
 at empower the O-RAN architecture to deliver the expected level of securit
 y for both the industry and 5G users. The discussion will also spotlight t
 he efforts of the O-RAN ALLIANCE Security Task Group (STG) and O-RAN ALLIA
 NCE Working Groups (WGs) in addressing security challenges across all O-RA
 N interfaces and components\, specifying\, and recommending modern\, pract
 ical security solutions.&lt;/p&gt;\n&lt;p&gt;*This event is being recorded&lt;/p&gt;
END:VEVENT
END:VCALENDAR

