Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Roaming and GRX security protects the private interconnect that carries mobile traffic between operators abroad, a network whose members trust each other far more than they should.

What Is Roaming and GRX Security?
When a British phone connects to a network in another country, the data session does not run over the public internet. It travels back to the home operator across a private interconnect, historically called the GPRS Roaming Exchange and now generally the IP Exchange, operated by a small number of carriers that peer with hundreds of mobile operators worldwide. Roaming and GRX security is the protection of that interconnect and of the signalling that rides on it.
The central problem is the trust model. The interconnect was built as a closed club between licensed operators, so membership was treated as proof of good intent. There are now well over a thousand mobile networks globally, together with virtual operators, hub providers, and testing partners, and a breach at any one of them puts an attacker inside a network that treats its members as peers.
The industry answer is to stop treating peers as trusted and start filtering.
Public telecoms providers in the UK operate under the Telecommunications (Security) Act 2021, the Electronic Communications (Security Measures) Regulations 2022, and the telecommunications security code of practice issued at the end of 2022. The measures speak directly to this area: providers must protect signalling, control access from third parties and interconnects, separate management functions, and monitor for compromise. Ofcom enforces, with the NCSC providing technical guidance, and providers are tiered so that the largest were expected to implement the most significant measures first.
The code of practice is unusually explicit that other networks are not to be trusted by default, which gives a UK operator a regulatory basis for filtering interconnect traffic even where a roaming partner objects commercially. For enterprises, the practical implication is narrower but real: if your staff roam, their traffic crosses networks you have no relationship with, which is an argument for treating mobile connectivity as untrusted transport and putting your own encryption on top of it.
Our network security services assess operator interconnect boundaries, including signalling and GTP filtering, against the measures the code of practice expects.
No. It is a private IP interconnect used only by mobile operators and the carriers that serve them, with its own addressing and no general public access. That isolation is a genuine control, but it is not a security boundary in itself, because every member network and every hub provider is a potential entry point, and an attacker inside the interconnect is treated as a peer.
It improves it substantially where it is deployed in standalone mode. Roaming traffic passes between security edge protection proxies over a protected interface with authentication and integrity protection, replacing the implicit trust of earlier generations. The benefit disappears when a session falls back to 4G or 2G roaming, which remains common, so legacy filtering stays necessary for years yet.
Near real-time roaming data exchange is the industry process by which a visited network sends usage records to the home network quickly, so that abnormal roaming usage is visible within hours rather than days. It exists because roaming fraud depends on the billing delay. Where partners fail to meet the timescales, that delay reopens, and large losses accumulate before anyone notices.
Treat mobile connectivity as untrusted transport and the concern becomes manageable. You cannot audit the networks your staff roam onto, so rely on your own controls: encrypted applications, a corporate virtual private network or zero trust access, no reliance on text messages as an authentication factor, and awareness among travelling staff about sudden loss of service.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Authentication and Authorisation?
Read MoreWe 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.