Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
5G network security covers the controls that protect a service-based 5G core, its virtualised radio access network, network slices, and roaming interconnect against attack and misuse.

What Is 5G Network Security?
5G is not a faster version of 4G with the same plumbing. The core network moved from bespoke telecoms signalling to a service-based architecture where network functions talk to each other over HTTP/2 and JSON, authenticate with OAuth 2.0 tokens, and run as containers on commodity infrastructure. That shift hands mobile operators an IT security problem wearing a telecoms badge, and it is the reason 5G security work looks more like cloud security than the signalling hardening that came before it.
Four architectural changes drive most of the risk.
Most commercial 5G began as non-standalone: a 5G radio bolted onto a 4G Evolved Packet Core. That deployment inherits every weakness of the previous generation, including Diameter signalling abuse and, where interworking remains, legacy SS7 exposure. Operators running non-standalone networks should be clear with regulators and customers that the security claims made for 5G standalone do not yet apply to them.
In standalone roaming, the Security Edge Protection Proxy sits at the network edge and protects the N32 interface between operators, using application-layer protection so that intermediaries can perform the modifications roaming requires without reading everything. A SEPP that is deployed without proper peer validation or that falls back to transport protection alone reopens the interconnect problem 5G was meant to close.
UK telecoms security stopped being voluntary with the Telecommunications (Security) Act 2021. The Electronic Communications (Security Measures) Regulations 2022 and the accompanying Telecommunications Security Code of Practice set specific duties: separating management planes from the signalling and user planes, protecting the virtualisation layer, controlling privileged access with multi-factor authentication, retaining security-critical logs, and assessing supplier risk formally. Ofcom is the enforcement body, with powers to direct and to fine, and providers are tiered by size with staged compliance dates. NCSC’s Telecoms Security Requirements underpin the technical detail, and high-risk vendor directions require the removal of designated equipment from 5G networks on a published timetable.
Turkey regulates the same ground through BTK, the Information and Communication Technologies Authority, whose network and information security rules for the electronic communications sector impose security measures, incident reporting, and audit obligations on operators, with BTK electronic communications security covering the detail. Two differences matter if you operate in both markets. Turkish rules put more weight on domestic supply and on data remaining in country, while the UK regime is built around tiered duties, a statutory code of practice, and an economic regulator with enforcement powers. Incident reporting routes also differ: BTK and the national computer emergency response structure in Turkey, Ofcom and NCSC in the UK.
Useful assurance work goes beyond scanning the core. It covers authorisation between network functions, slice isolation under load, SEPP configuration against a hostile peer, management plane segregation, the container platform underneath, and the operations support systems that usually hold the real crown jewels. GSMA’s NESAS scheme and 3GPP’s security assurance specifications give a baseline for equipment, but they say nothing about how your particular deployment was configured. At Privia Security, our infrastructure security testing services examine the mobile core and its supporting platforms as one connected estate rather than as a list of boxes.
In standalone deployments the protocol design is stronger: subscriber identifiers are encrypted, roaming interconnect has dedicated protection at the edge, and mutual authentication between network functions is specified. In practice the benefit depends on configuration, and non-standalone networks still rely on a 4G core with its existing signalling exposure. The attack surface is also wider because the core is now software on general-purpose infrastructure.
Slice isolation is enforced by configuration and by shared network functions, not by physical separation, so cross-slice risk is real. Research has shown paths where a function serving several slices can be used to reach data or capacity belonging to another. Treat slice boundaries like tenant boundaries in a cloud platform: test them, monitor them, and avoid putting incompatible trust levels on shared functions.
It places legal duties on UK public telecoms providers to identify and reduce the risk of security compromises, with detail set out in the Electronic Communications (Security Measures) Regulations 2022 and a statutory code of practice. Duties cover management plane separation, virtualisation security, privileged access, logging, supplier risk, and testing. Ofcom monitors and enforces, and compliance dates are staged by provider tier.
Against a correctly configured standalone 5G network, passive capture of the permanent subscriber identifier does not work, because the device sends an encrypted SUCI instead. Devices still fall back to 4G and 2G where coverage requires it, and some operators configure the null protection scheme, so the practical answer depends on the network. Downgrade behaviour remains the most reliable route for an attacker.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.