You own and operate the core on your own infrastructure, on premise, with a RAN you run yourself or take through a carrier arrangement. Cellular networks were built for carriers, not enterprise IT/OT teams. OneLayer bridges that gap, bringing the coverage and control you expect from every other part of your network.
Supported Local cores
The Challenge
Cellular networks were designed for carriers, not enterprise IT/OT teams. Manufacturing plants, mines, ports, and oil and gas sites deploy a private local core for dedicated capacity, data sovereignty, and full operational control on premise. But cellular is the one conduit your security and IT frameworks weren't built to see: it breaks the Purdue model's zone boundaries, because the core authenticates by SIM, not device, with no record of type, ownership, or whether it belongs on the network. As AGVs, cobots, and sensors multiply on the floor, that gap gets harder to close by hand.
Your core confirms the subscription is valid. It can't tell you the device type, manufacturer, or whether it was swapped on the floor overnight.
Every new AGV, camera, or sensor added to the network means another manual provisioning step, another gap between when it connects and when your ITSM or CMDB knows about it.
Your NGFW and SIEM act on IP addresses, not IMEI or IMSI. Without device identity, policy enforcement and anomaly detection stop at the cellular network's edge.
The Solution
How OneLayer Fits: A Security and
Management Layer for the Core You
Already Operate
OneLayer Bridge connects to your private core's management interface, across Nokia, Ericsson, Celona, Druid, Athonet, Cisco, and GE Vernova alike, adding the device visibility, automated onboarding, and security context the core was never designed to provide. Read-only, no agents, no cellular expertise required, with a single pane of glass across every site and vendor you run.
Onboard
Automated SIM provisioning and activation at fleet scale, triggered from your ITSM or CMDB. Every new device gets the same security policy automatically, managed from one interface with no per-site setup.
Observe
Automatic fingerprinting classifies make, model, vendor, and protocol, extending discovery to assets behind edge and cellular routers your NGFW and SIEM can’t see today. Out-of-policy tethering and unauthorized device types get flagged in real time, alongside behavioral anomalies.
Protect
OneLayer feeds verified device identity to the firewalls you already run, like Palo Alto, Fortinet, and Check Point, revoking access automatically the moment behavior changes. A flagged device gets blocked at the firewall instead of just logged.
What Our Customers Are Saying
“We initiated a program called ‘No Asset Left Behind’ because we realized we needed to know about and manage all assets, not just network traffic. We needed this to apply to our private cellular networks in worldwide manufacturing sites. OneLayer seamlessly provided us with that visibility, including to non-cellular devices connected to the LTE/5G networks.”
No. OneLayer extends your existing Zero Trust architecture to cover private cellular networks, which most ZTNA tools were never designed to reach. Your current stack (NAC, MDM, ISE, SIEM) continues to operate as-is. OneLayer integrates with it, surfacing cellular connection events and policy decisions into the same workflows your security team already uses.
For unmanaged IoT and OT devices, OneLayer uses signature-based fingerprinting. A device identity is constructed from stable, device-specific attributes: IMEI, radio behavior, connection patterns, and other observable characteristics. This signature becomes the identity assertion at connection time. Certificate-based validation is used for managed endpoints that can support it.
The staging APN is an isolated network environment that new devices are routed to before they can reach your operational network — a DMZ for cellular traffic. No production data or systems are accessible from it. Once a device passes identity and posture checks in the staging APN, it is moved to the production APN with a minimal-privilege profile applied. Devices that fail checks remain in the staging APN and trigger alerts.
No changes to existing SIMs, devices, or network hardware are required. OneLayer integrates at the mobile core level, intercepting and validating connection requests as part of the authentication flow. Your devices, SIMs, and physical network infrastructure remain untouched.
Policies are defined based on device identity attributes: type, operational role, location, or business unit. Groups can be created directly in OneLayer or pulled from existing systems such as your CMDB, MDM, or NAC. Enforcement happens at the cellular connection layer and is passed to your existing firewall or enforcement infrastructure. Any communication attempt that violates a policy is blocked and an alert is generated.