{"id":2166,"date":"2026-07-29T08:00:00","date_gmt":"2026-07-29T07:00:00","guid":{"rendered":"https:\/\/ic-services.io\/?p=2166"},"modified":"2026-10-21T14:12:27","modified_gmt":"2026-10-21T13:12:27","slug":"iot-intercettazione-legale-lpwan-m2m","status":"publish","type":"post","link":"https:\/\/ic-services.io\/it\/resources\/blog\/iot-lawful-interception-lpwan-m2m\/","title":{"rendered":"IoT e intercettazione legale: L'obbligo crescente per gli operatori LPWAN e M2M"},"content":{"rendered":"

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 \u2014 particularly those providing Low Power Wide Area Network (LPWAN) connectivity and M2M services \u2014 this growth brings not only commercial opportunity but also expanding regulatory obligations, including lawful interception.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Perch\u00e9 l'intercettazione legale nell'ambito dell'IoT \u00e8 importante<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

In Germany, \u00a7 170 TKG and the TK\u00dcV (Telekommunikations-\u00dcberwachungsverordnung) require operators of networks used for publicly available telecommunications services to provide interception capability, and M2M transmission services count as telecommunications services (\u00a7 3 No. 61(c) TKG). The TK\u00dcV exempts some systems from having to install interception facilities, for example systems used only to transmit measurement data (\u00a7 3(2) No. 4 TK\u00dcV) or systems with no more than 10,000 users (\u00a7 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.<\/p>\n\n\n\n

Even an operator that is exempt from installing interception facilities must cooperate with an individual order (in Germany, \u00a7 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.<\/p>\n\n\n\n

Perch\u00e9 i dati dell'IoT sono importanti per le forze dell'ordine<\/h2>\n\n\n\n

I dispositivi IoT generano dati che possono essere di grande rilevanza per le indagini penali. I veicoli connessi generano dati di localizzazione, modelli di guida e registri delle comunicazioni. I dispositivi per la casa intelligente registrano dati ambientali, modelli di utilizzo e, in alcuni casi, audio o video. I dispositivi indossabili per la salute acquisiscono dati biometrici e modelli di movimento. I sensori IoT industriali possono rivelare attivit\u00e0 operative, movimenti della catena di approvvigionamento e condizioni ambientali. Anche semplici dispositivi M2M, come i distributori automatici o i contatori delle utenze, generano dati di localizzazione e di utilizzo che possono risultare rilevanti in determinate indagini.<\/p>\n\n\n\n

Come forze dell'ordine<\/a> Man mano che acquisiscono maggiore consapevolezza del potenziale investigativo dei dati IoT, \u00e8 sempre pi\u00f9 probabile che richiedano agli operatori IoT l\u2019intercettazione o la divulgazione dei dati. Gli operatori che non sono in grado di rispondere a tali richieste vanno incontro non solo a conseguenze normative, ma anche al rischio di essere considerati poco collaborativi dalle autorit\u00e0 di polizia, il che pu\u00f2 avere implicazioni pi\u00f9 ampie per il rapporto dell\u2019operatore con le autorit\u00e0 di regolamentazione.<\/p>\n\n\n\n

Sfide tecniche dell'IoT LI<\/h2>\n\n\n\n

L\u2019implementazione dell\u2019intercettazione legale delle comunicazioni IoT e M2M presenta diverse sfide tecniche che differiscono in modo significativo dall\u2019intercettazione tradizionale di voce e dati. La prima \u00e8 la diversit\u00e0 dei protocolli di comunicazione. I dispositivi IoT comunicano utilizzando un'ampia gamma di protocolli \u2014 MQTT, CoAP, LwM2M, HTTP e protocolli proprietari \u2014 su varie tecnologie di rete, tra cui LTE-M, NB-IoT, LoRaWAN, Sigfox e satellite. Ogni protocollo e tecnologia di rete presenta caratteristiche diverse che influenzano le modalit\u00e0 di esecuzione dell'intercettazione.<\/p>\n\n\n\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.<\/p>\n\n\n\n

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 \u2014 particularly when the device is owned by an organisation rather than an individual \u2014 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.<\/p>\n\n\n\n

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, \u00a7 8(3) TK\u00dcV); application-layer encryption between device and customer platform that the operator holds no key for is delivered as captured.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Considerazioni specifiche relative alle reti LPWAN<\/h2>\n\n\n\n

LPWAN technologies \u2014 including NB-IoT, LTE-M, LoRaWAN, and Sigfox \u2014 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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

IRI e CC per le comunicazioni IoT<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Prepararsi agli obblighi relativi all\u2019IoT LI<\/h2>\n\n\n\n

Gli operatori che forniscono servizi IoT e M2M dovrebbero adottare misure proattive per prepararsi agli obblighi relativi alla LI, anche laddove i requisiti normativi non siano ancora stati definiti in modo completo. In primo luogo, \u00e8 necessario valutare il quadro normativo in ciascun mercato in cui si opera, consultando un consulente legale e l\u2019autorit\u00e0 nazionale di regolamentazione competente. In secondo luogo, valutate le vostre attuali capacit\u00e0 in materia di LI alla luce dei requisiti specifici relativi all\u2019intercettazione IoT, individuando eventuali lacune nell\u2019identificazione degli obiettivi, nell\u2019acquisizione del traffico, nella generazione di IRI e nella consegna dei CC.<\/p>\n\n\n\n

In terzo luogo, elaborate una roadmap tecnica per potenziare le vostre capacit\u00e0 LI a supporto dell'intercettazione dell'IoT. Tale roadmap dovrebbe prevedere l'integrazione degli elementi di rete IoT con il LI funzione di mediazione<\/a>, 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 Soluzione LI<\/a> fornitore per comprendere la sua roadmap relativa al supporto dell\u2019IoT LI e per influenzare le sue priorit\u00e0 di sviluppo in base alle vostre esigenze.<\/p>\n\n\n\n

Infine, documenta il tuo approccio all'IoT Conformit\u00e0 alle norme LI<\/a>, 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 (\u00a7 170(1) TKG).<\/p>\n\n\n\n

Conclusione<\/h2>\n\n\n\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 \u2014 spanning protocol diversity, traffic patterns, target identification, encryption, and scale \u2014 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.<\/p>\n\n\n

L\u2019intersezione tra l\u2019IoT e l\u2019intercettazione legale solleva inoltre questioni pi\u00f9 ampie riguardo alla portata della sorveglianza in un mondo sempre pi\u00f9 connesso. Man mano che gli oggetti di uso quotidiano si connettono in rete e generano flussi di dati, il confine tra l\u2019intercettazione delle comunicazioni e la raccolta di dati in senso pi\u00f9 ampio diventa sempre meno netto. Gli operatori dovrebbero collaborare in modo proattivo con le autorit\u00e0 di regolamentazione e gli organismi di settore per contribuire a definire il quadro normativo emergente in materia di intercettazione legale nell\u2019ambito dell\u2019IoT, apportando competenze tecniche concrete per garantire che i requisiti che ne deriveranno siano sia efficaci ai fini dell\u2019applicazione della legge sia attuabili da parte degli operatori.<\/p>\n\n\n\n

L'ambito di applicazione degli obblighi relativi all'intercettazione legale nell'ambito dell'IoT varia a seconda della giurisdizione e del tipo di servizio. Gli operatori dovrebbero definire i propri requisiti in materia di intercettazione legale nell'ambito dell'IoT sin dalle prime fasi della pianificazione dell'implementazione.<\/p>\n\n\n\n

Articoli correlati<\/h2>\n\n\n\n

Per ulteriori letture su argomenti correlati, esplorate questi articoli:<\/p>\n\n\n\n