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 que razão a interceção legal na Internet das Coisas (IoT) é importante
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 que razão os dados da IoT são importantes para as forças policiais
Os dispositivos IoT geram dados que podem ser extremamente relevantes para investigações criminais. Os veículos conectados geram dados de localização, padrões de condução e registos de comunicação. Os dispositivos domésticos inteligentes registam dados ambientais, padrões de utilização e, em alguns casos, áudio ou vídeo. Os dispositivos de saúde vestíveis captam dados biométricos e padrões de movimento. Os sensores industriais da IoT podem revelar atividades operacionais, movimentos na cadeia de abastecimento e condições ambientais. Mesmo dispositivos M2M simples, como máquinas de venda automática ou contadores de serviços públicos, geram dados de localização e utilização que podem ser relevantes em determinadas investigações.
Como organismos responsáveis pela aplicação da lei À medida que se tornam mais conscientes do potencial investigativo dos dados da IoT, é cada vez mais provável que solicitem a interceção ou a divulgação de dados aos operadores de IoT. Os operadores que não consigam responder a estes pedidos enfrentam não só consequências regulamentares, mas também o risco de serem considerados pouco cooperantes pelas autoridades responsáveis pela aplicação da lei, o que pode ter implicações mais amplas na relação do operador com as entidades reguladoras.
Desafios técnicos da IoT LI
A implementação da interceção legal das comunicações de IoT e M2M apresenta vários desafios técnicos que diferem significativamente da interceção tradicional de voz e dados. O primeiro é a diversidade de protocolos de comunicação. Os dispositivos IoT comunicam utilizando uma vasta gama de protocolos — MQTT, CoAP, LwM2M, HTTP e protocolos proprietários — através de várias tecnologias de rede, incluindo LTE-M, NB-IoT, LoRaWAN, Sigfox e satélite. Cada protocolo e tecnologia de rede possui características diferentes que afetam a forma como a interceção pode ser realizada.
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.
Considerações 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 e CC para comunicações na Internet das Coisas (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.
Preparação para as obrigações relacionadas com a IoT LI
Os operadores que prestam serviços de IoT e M2M devem tomar medidas proativas para se prepararem para as obrigações em matéria de LI, mesmo nos casos em que os requisitos regulamentares ainda não estejam totalmente definidos. Em primeiro lugar, avalie a situação regulamentar em cada mercado em que opera, consultando um advogado e a autoridade reguladora nacional competente. Em segundo lugar, avalie as suas capacidades atuais em matéria de LI face aos requisitos específicos da interceção de dados da IoT, identificando lacunas na identificação de alvos, na captura de tráfego, na geração de IRI e na entrega de CC.
Em terceiro lugar, elabore um plano de ação técnico para melhorar as suas capacidades de LI, de modo a apoiar a interceção da IoT. Este plano de ação deve abordar a integração dos elementos da rede da IoT com a LI função de mediação, 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 Solução LI fornecedor, para compreender o seu plano de desenvolvimento para o suporte à IoT LI e para influenciar as suas prioridades de desenvolvimento com base nos seus requisitos.
Por fim, documente a sua abordagem à IoT Conformidade com a 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).
Conclusão
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.
A interseção entre a IoT e a interceção legal levanta também questões mais amplas sobre o âmbito da vigilância num mundo cada vez mais conectado. À medida que os objetos do quotidiano se tornam interligados e geram fluxos de dados, a fronteira entre a interceção de comunicações e a recolha de dados em geral torna-se menos nítida. Os operadores devem colaborar de forma proativa com as entidades reguladoras e os organismos do setor para ajudar a definir o quadro emergente para a interceção legal na IoT, contribuindo com conhecimentos técnicos práticos para garantir que os requisitos resultantes sejam eficazes para as autoridades responsáveis pela aplicação da lei e exequíveis pelos operadores.
O âmbito das obrigações relativas à interceção legal na IoT varia consoante a jurisdição e o tipo de serviço. As operadoras devem identificar os seus requisitos em matéria de interceção legal na IoT numa fase inicial do planeamento da sua implantação.
Artigos relacionados
Para mais informações sobre temas relacionados, consulte estes artigos:
- Network Slicing na rede 5G SA: como complica (e pode simplificar) a segmentação de LI
- eSIM e interceção legal: O que a arquitetura RSP significa para a conformidade
- MVNO vs MNO: Quem é legalmente responsável pela interceção legal?
Recursos externos
Os seguintes recursos externos fornecem contexto adicional e documentação oficial:
