Long-lived IoT devices put lifecycle security and quantum readiness in focus
Internet-connected devices can remain in factories, warehouses and critical infrastructure for 15 or 20 years. That operating life creates a security challenge beyond protecting products at launch: manufacturers and operators need to retain visibility, manage vulnerabilities and determine how devices can be updated long after deployment.
Christian Schwalbe, CEO of Deutsche Telekom IoT, identified neglected devices as a particular concern. A small sensor that continues to function may attract less attention than a critical industrial controller, even though it can still create an entry point or exposure for a wider environment. The operational risk, he said, is not determined by a device’s purchase price, but by the weaknesses and opportunities it presents.
For enterprise teams, that makes asset visibility and ongoing ownership central to IoT security. A device that is still transmitting data is not necessarily being monitored or maintained. Security responsibilities need to continue after installation, with organizations able to identify what is connected, understand its expected behavior and know who is accountable when a vulnerability is found.
The Cyber Resilience Act puts product support in focus
The EU Cyber Resilience Act reinforces the need to address cybersecurity and vulnerability handling during a product’s support period. Schwalbe described the regulation as an important step, while noting practical questions for manufacturers of long-lived products: how support periods should reflect expected use, how updates can be managed, and how vulnerabilities should be handled across devices already deployed around the world.
Those questions matter where thousands of devices may be in service for years. Manufacturers need to consider whether software can be updated and who will take responsibility for that work. Schwalbe said that while some companies have invested in product security for a long time, others are now examining more closely what it means to protect connected products throughout their lifetimes. He also pointed to a partnership with Exein and the importance of security measures that can help protect devices during operation.
The shift is from treating security as a final pre-release check to incorporating it into product design, deployment and maintenance. For buyers, support commitments and vulnerability-response processes therefore deserve attention alongside a device’s features and cost. A product’s expected service life should be matched by a realistic plan for handling security issues over that period.
Traffic patterns can help without inspecting payloads
Monitoring network behavior can provide one way to spot possible problems while limiting the need to inspect communications’ contents. Schwalbe gave unexpected destinations and changes from a device’s normal communication behavior as examples of signals that may indicate an anomaly. This approach can be useful where privacy expectations or encryption make payload inspection inappropriate or unavailable.
It is not a complete substitute for other controls. Schwalbe cautioned that not every threat is visible in network traffic, particularly when communications are encrypted. He advocated layered security, in which network-level measures may be complemented by protections on the device, depending on the system’s architecture. He also stressed that metadata requires responsible handling, including clarity about what is collected, why it is processed and who can access it.
Organizations can apply these points by defining expected communications for device classes, investigating meaningful deviations and pairing network monitoring with device-level capabilities where appropriate. The aim is not to assume that an unusual connection proves compromise, but to use behavior as a source of evidence within a broader security process.
Planning for post-quantum protection
Long-lived devices also raise questions about the future confidentiality of data. Schwalbe highlighted the “Harvest Now, Decrypt Later” risk: encrypted information collected today could potentially be decrypted in the future if sufficiently capable quantum computers become available. He said post-quantum cryptography is relevant now for use cases where information must remain confidential for many years, including some critical-infrastructure and sensitive industrial applications. Not every sensor, however, needs the same level of protection; requirements depend on the data and how long it must remain confidential.
Resource-constrained devices complicate adoption. Limited processing power, memory, energy and data rates can affect which cryptographic approaches are practical. Deutsche Telekom IoT, its T-Labs colleagues and research partners are exploring ways to establish trust using post-quantum cryptography and secret sharing across multiple terrestrial and satellite communication paths. The approach is intended to distribute security-critical information rather than rely on a single connectivity path.
Schwalbe said the team had developed a proof of concept and presented the research at European Wireless 2026. He described the results as demonstrating technical feasibility, while noting that further optimization and validation are needed before broader deployment. For enterprises, the work is not evidence that a production-ready solution is available, but it underscores the value of designing systems that can adapt as cryptographic requirements change.
Sovereignty means understanding dependencies
Schwalbe also framed digital sovereignty as a question of control and understanding, not simply the location of a data center. An IoT deployment may combine devices, communication modules, firmware, software, connectivity and cloud platforms from different providers and countries. Knowing where data is hosted remains relevant, but so does understanding what runs on devices, where dependencies lie and whether vulnerabilities can be identified and addressed.
For security leaders, the practical takeaway is to treat IoT as a lifecycle and supply-chain responsibility. Maintain an inventory, establish who supports each component, assess update and vulnerability processes, and set monitoring appropriate to the privacy and operational context. Those measures help organizations retain meaningful control over devices that may otherwise remain in service long after the teams that deployed them have moved on.