TRACED
Get your Assessment
© TRACED 2022

TRACEDTRACED

  • Solutions
    • DevSecOps
    • Open Source
    • Software Supply Chain
    • M&A Due Diligence
  • Services
    • Assess & Review
    • Train & Enable
    • Policy & Governance
    • Managed Service
    • SBOM
  • Company
  • Insights
  • Contact
Get Your Assessment

Telecom Cloud and its Open Source Risks

Traced
Thursday, 09 March 2023 / Published in Open Source Security

Telecom Cloud and its Open Source Risks

According to federal cyber authorities, some new and emerging technologies that are taking over the telecoms space are presenting inherent security risks to users and providers. These open-source options provide companies with simpler tools whilst using vulnerable code that can leave spaces for third parties and hackers to breach systems. Open source interfaces and components are a growing part of plenty of other networks aside from telecoms, with the security risks to the telecoms industry and infrastructure having potentially catastrophic security implications for organisations.

What is Open RAN?

Open RAN stands for Open Radio Access Network and refers to a series of interconnected standards-based parts that any user can contribute to. There are a few key principles of Open RAN, including an open disaggregation of parts, standards-based compliance, proof that different parts can work together with one another, and neutrality in the way that people implement the system.

Risks of Open RAN

There are a few security risks that using Open RAN poses to users in a range of settings. One of the main causes of this risk is the increase in “threat surface area”, or the proportion of the network that is vulnerable to outside parties. The larger the surface area, the more space and potential there is for a hacker to find a vulnerability in the system and steal information or destroy the functionality of the network.

A lack of future compatibility is another threat that Open RAN poses. If there is a vulnerability and one vendor patches it, the multi-vendor nature of the system means that some parts of the system are vulnerable whilst others aren’t. The more platforms you introduce, the more parties need to add their own safety and security features.

Why use Open RAN?

In spite of these risks, people keep using Open RAN for a few reasons. The first is the greater level of flexibility. As different vendors all provide parts for the system, a single company going out of operation doesn’t mean that the system becomes obsolete. Companies using Open RAN access a more flexible system with a lower risk of harm to systems in the future.

Low barriers to entry are another significant benefit. As providers and companies access information interchanges and radio networks more often, Open RAN is a more flexible way of building an organisation from the bottom.

Government Guidance

Thanks to these issues, the National Security Agency and Cybersecurity and Infrastructure Security Agency have guidance for providers. This includes everything from making sure of security provisions to network virtualisation, all with the goal of a more secure network in the future that people can use reliably. Any guidance is focusing on security in telecoms for different applications, with a bespoke and unique approach necessary for different apps with a series of unique security requirements. Open RAN is a useful tool for the telecoms industry and, with guidance from relevant government agencies, these systems are looking more and more likely to eliminate the risks and leave only the upside.

 

Our range of OSS services help businesses to build trust in their software supply chain.

Assess & Review – Request a full review of your software security and gain visibility across the supply chains and to any Open Source exposure.

Open Source Training – Build your team’s knowledge and skills with our training courses. Designed to help everyone in your team – no matter what their role in the organisation.

Managed Services – Build continuous compliance into your business process to help you manage OSS risk on an on-going basis.

Open Source Software Policy – Define clear OSS policies to help decision-making and to manage risk from supply chain attacks, and implement a continuous compliance programme.

SBOM Services – Use SBOMs to help manage your vulnerabilities, and risk (financial, reputational, and legal).

Start the process of securing your software supply chain, get in touch with us to find out how we can help.

  • Tweet
Tagged under: open source software, software security

What you can read next

Why it’s important to not ignore Log4j
Software Security Checkpoints in the SDLC
Know your ingredients! How SBOMs protect code

Recent Posts

  • Telecom Cloud and its Open Source Risks

    According to federal cyber authorities, some ne...
  • Avoid Surprises: Don’t Let Open Source Issues Impact a Transaction

    Open source software (OSS) is becoming increasi...
  • Software Security Checkpoints in the SDLC

    How Widespread Are Software Security Checkpoint...
  • The Balance Between Open Source Software and Monetisation

    Can OSS Be Commercially Viable? It is commonly ...
  • Why it’s important to not ignore Log4j

    Open-source software is becoming more popular, ...

Archives

  • March 2023
  • February 2023
  • December 2022
  • November 2022
  • October 2022

Categories

  • Insight
  • Open Source Development
  • Open Source Risk
  • Open Source Security
  • SBOMs
  • Software Supply Chain

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Solutions
  • Software Supply Chain
  • Open Source
  • DevSecOps
  • M&A Due Diligence
Services
  • Assess & Review
  • Policy & Governance
  • Managed Service
  • SBOM
Company
  • Quick Assessment
  • Company
  • Contact us

[email protected]

© 2022 All rights Reserved @Traced

TOP