Law enforcement interest in IoT data is growing as connected devices proliferate across networks. The Internet of Things (IoT) is transforming industries from logistics and agriculture to healthcare and smart cities. Billions of connected devices now communicate over cellular and non-cellular networks, generating vast quantities of machine-to-machine (M2M) data. For telecommunications operators — particularly those providing Low Power Wide Area Network (LPWAN) connectivity and M2M services — this growth brings not only commercial opportunity but also expanding regulatory obligations, including lawful interception.
The application of lawful interception obligations to IoT and M2M communications is a developing area of regulation, but the direction of travel is clear: as IoT traffic grows and becomes more relevant to criminal investigations, law enforcement interest in IoT data is growing, and operators should expect more requests for data, mainly for subscriber, location and traffic data rather than live content. This article examines the current state of LI obligations for IoT operators, the technical challenges involved, and the steps operators should take to prepare.
Por qué es importante la interceptación legal en el ámbito del IoT
The question of whether IoT and M2M communications fall within the scope of lawful interception obligations is primarily a legal one, and the answer varies by jurisdiction. In the European Union, the obligation to support lawful interception generally applies to providers of electronic communications services that are available to the public. Under the EU Electronic Communications Code, transmission services used for machine-to-machine communication are electronic communications services (Art. 2(4)(c) EECC). Whether they carry LI obligations depends on whether they are offered to the public and on national law, which sets the LI conditions and any exemptions.
In Germany, § 170 TKG and the TKÜV (Telekommunikations-Überwachungsverordnung) require operators of networks used for publicly available telecommunications services to provide interception capability, and M2M transmission services count as telecommunications services (§ 3 No. 61(c) TKG). The TKÜV exempts some systems from having to install interception facilities, for example systems used only to transmit measurement data (§ 3(2) No. 4 TKÜV) or systems with no more than 10,000 users (§ 3(2) No. 5). Whether an IoT offering is exempt therefore depends on what it carries, not on the label ‘IoT’. In other EU member states the details differ.
Even an operator that is exempt from installing interception facilities must cooperate with an individual order (in Germany, § 100a(4) StPO). It should therefore know how it would carry out an order on its IoT platform, even where no permanent LI system is required.
Por qué los datos del IoT son importantes para las fuerzas del orden
Los dispositivos del IoT generan datos que pueden resultar muy relevantes para las investigaciones penales. Los vehículos conectados generan datos de ubicación, patrones de conducción y registros de comunicaciones. Los dispositivos domésticos inteligentes registran datos ambientales, patrones de uso y, en algunos casos, audio o vídeo. Los dispositivos de salud portátiles recogen datos biométricos y patrones de movimiento. Los sensores industriales del IoT pueden revelar actividades operativas, movimientos de la cadena de suministro y condiciones ambientales. Incluso los dispositivos M2M más sencillos, como las máquinas expendedoras o los contadores de servicios públicos, generan datos de ubicación y uso que pueden resultar relevantes en determinadas investigaciones.
Como fuerzas del orden A medida que se van concienciando más sobre el potencial de investigación de los datos del IoT, es cada vez más probable que soliciten a los operadores de IoT la interceptación o la divulgación de datos. Los operadores que no puedan responder a estas solicitudes se enfrentan no solo a consecuencias normativas, sino también al riesgo de que las autoridades policiales los consideren poco cooperativos, lo que puede tener implicaciones más amplias para la relación del operador con los organismos reguladores.
Retos técnicos del IoT LI
La implementación de la interceptación legal de las comunicaciones de IoT y M2M plantea varios retos técnicos que difieren significativamente de la interceptación tradicional de voz y datos. El primero es la diversidad de protocolos de comunicación. Los dispositivos del IoT se comunican mediante una amplia gama de protocolos —MQTT, CoAP, LwM2M, HTTP y protocolos propios— a través de diversas tecnologías de red, entre las que se incluyen LTE-M, NB-IoT, LoRaWAN, Sigfox y satélite. Cada protocolo y tecnología de red presenta características diferentes que influyen en la forma en que se puede llevar a cabo la interceptación.
The second challenge is the volume and pattern of communications. Unlike voice calls or web browsing sessions, IoT communications are typically short, infrequent, and low-bandwidth. A sensor may transmit a few bytes of data every hour. This pattern matters less for capture, because interception points copy every packet or non-IP message of the target, however small, but it means many sessions stay idle for long periods and each transmission is reported separately.
The third challenge is target identification. IoT devices may be identified by IMSI, IMEI, IP address, or device-specific identifiers that do not correspond to traditional subscriber identities. Mapping these identifiers to a specific target — particularly when the device is owned by an organisation rather than an individual — can be complex. The administration function and the interception points must support the identifier types used for IoT devices (for example IMSI/SUPI, IMEI/PEI, external identifiers and IP addresses), and the operator must be able to map a device serial number to one of them before the task is provisioned.
The fourth challenge relates to encryption and security. Many IoT protocols implement application-layer encryption, which means that the operator may be able to capture the encrypted traffic but not access the content. The DTLS and TLS implementations used by CoAP and MQTT, for example, may encrypt the application payload in a way that the operator cannot decrypt. This limitation must be communicated transparently to law enforcement when responding to interception requests. Operators must remove encryption they apply in the network or whose keys they help generate or exchange (in Germany, § 8(3) TKÜV); application-layer encryption between device and customer platform that the operator holds no key for is delivered as captured.
A fifth challenge is the sheer scale of IoT deployments. An operator may have millions of IoT devices on its network, and large device populations matter mainly for identifying the right device (for example mapping a device serial number to IMSI/IMEI) and for making sure all IoT core functions are covered. The number of simultaneous intercepts remains driven by the number of orders.
Consideraciones específicas sobre LPWAN
LPWAN technologies — including NB-IoT, LTE-M, LoRaWAN, and Sigfox — have specific characteristics that affect LI implementation. NB-IoT and LTE-M operate within the 3GPP ecosystem and are served by the cellular core network. 3GPP TS 33.127/33.128 already cover their IoT-specific paths: data sent over the signalling plane (Data over NAS) and Non-IP Data Delivery via the SCEF (4G) or NEF (5G). Operators must make sure these functions, not just the user-plane gateways, have interception points.
LoRaWAN and Sigfox operate outside the 3GPP ecosystem and use proprietary or open-standard network architectures. The application of LI to these technologies is less well-defined in terms of standards, and operators may need to develop custom interception solutions. The network architecture of LoRaWAN, for example, includes gateways, network servers, and application servers, and the network server sees device identifiers, timing and gateway (location) metadata, but the application payload is encrypted end-to-end with a key held by the application server. Interception at the network server gives readable content only where the operator also runs the application or join server.
IRI y CC para las comunicaciones del IoT
Standard IRI covers what the network knows: identities (IMSI/SUPI, IMEI/PEI, external identifiers), sessions, location. Sensor readings travel as content (CC). Any additional metadata must come from the national handover specification, not from operator-specific extensions.
CC for IoT communications is typically much smaller in volume than for voice or data sessions, but may be more diverse in format. The content of an IoT transmission might be a JSON payload, a binary sensor reading, a protocol buffer message, or a proprietary data format. CC is delivered as an unaltered copy of what was transmitted (for example IP packets or non-IP data), together with the IRI. Interpreting proprietary payload formats is the job of law enforcement’s analysis tools.
Preparación para las obligaciones relacionadas con el IoT LI
Los operadores que prestan servicios de IoT y M2M deben adoptar medidas proactivas para prepararse para las obligaciones en materia de LI, incluso cuando los requisitos normativos aún no estén plenamente definidos. En primer lugar, evalúen la situación normativa en cada mercado en el que operen, consultando con asesores jurídicos y con la autoridad reguladora nacional pertinente. En segundo lugar, evalúe sus capacidades actuales en materia de LI en relación con los requisitos específicos de la interceptación de datos del IoT, identificando las deficiencias en la identificación de objetivos, la captura de tráfico, la generación de IRI y la entrega de CC.
En tercer lugar, elabora una hoja de ruta técnica para mejorar tus capacidades de LI con el fin de facilitar la interceptación del IoT. Esta hoja de ruta debería abordar la integración de los elementos de red del IoT con el LI función de mediación, the extension of target identification to support IoT device identifiers, and coverage of the IoT-specific data paths (Data over NAS, NIDD via SCEF/NEF). Fourth, engage with your Solución LI proveedor para conocer su plan de desarrollo en materia de compatibilidad con IoT LI e influir en sus prioridades de desarrollo en función de tus necesidades.
Por último, documenta tu enfoque respecto al IoT Cumplimiento de la normativa LI, including any limitations in your current capabilities and the steps you are taking to address them. This documentation shows the regulator why your service is exempt or how your interception capability is implemented. Where an obligation applies, it does not replace the capability: in Germany the facilities must be in place when the service starts (§ 170(1) TKG).
Conclusión
The growth of IoT and M2M communications is bringing more law enforcement requests to operators, because IoT data is increasingly relevant to investigations. While the technical challenges of IoT LI are significant — spanning protocol diversity, traffic patterns, target identification, encryption, and scale — they are not insurmountable. Operators that assess their regulatory exposure, evaluate their technical capabilities, and invest in IoT-capable LI solutions will be well positioned to meet their obligations and to maintain compliance as the IoT ecosystem continues to grow.
La intersección entre el IoT y la interceptación legal también plantea cuestiones más amplias sobre el alcance de la vigilancia en un mundo cada vez más conectado. A medida que los objetos cotidianos se conectan a la red y generan flujos de datos, la frontera entre la interceptación de comunicaciones y la recopilación de datos en general se vuelve menos clara. Los operadores deberían colaborar de forma proactiva con los organismos reguladores y los organismos del sector para ayudar a dar forma al marco emergente de la interceptación legal en el IoT, aportando conocimientos técnicos prácticos para garantizar que los requisitos resultantes sean eficaces para las fuerzas del orden y aplicables por parte de los operadores.
El alcance de las obligaciones en materia de interceptación legal en el ámbito del IoT varía según la jurisdicción y el tipo de servicio. Los operadores deben identificar los requisitos de interceptación legal en el ámbito del IoT en una fase temprana de la planificación de su despliegue.
Artículos relacionados
Si desea leer más sobre temas relacionados, consulte estos artículos:
- El «network slicing» en 5G SA: cómo complica (y puede simplificar) la selección de objetivos de LI
- eSIM e interceptación legal: Qué significa la arquitectura RSP para el cumplimiento de la normativa
- OMV vs. OMR: ¿Quién es legalmente responsable de la interceptación legal?
Recursos externos
Los siguientes recursos externos proporcionan contexto adicional y documentación oficial:
