Articles · Infrastructure & Cities
Give yours a name at birth
Devices with no identity become other people’s armies. PlugCheck gives every connected product a birth identity, checks its updates, and writes the evidence file as it goes.
By Lucian · Lux Automations
The problem
The connected product in a home — the television, the router, the camera, the recorder — usually arrives with no real identity of its own. It may carry a default credential, shared across every unit the maker ever shipped. Whoever learns that one secret holds a key to all of them, and the devices cannot tell their maker’s voice from a stranger’s.
The scale of what follows is in the product page’s figures. Record attacks driven by hijacked consumer devices have reached 29.7 terabits per second, by Cloudflare’s reporting — an estimated 1 to 4 million Android TVs, routers, DVRs and cameras, mostly taken through default credentials. Google’s 2025 lawsuit described 10 million or more uncertified Android devices infected before they were even sold. Devices with no identity become other people’s armies, sometimes before they reach a shelf.
For makers selling into Europe, this is now a legal matter as well as a practical one. The Cyber Resilience Act asks makers to identify their products, secure their update paths, and keep the evidence. A device born nameless cannot produce that evidence, however honest its maker is.
The technology
PlugCheck begins at manufacture, with a birth identity per device. Every device is born with an issued identity, in the device’s own name — not a model’s shared secret, but this unit’s identity, issued at birth and carried for its life. Crossings to and from the device can then be tied to the device itself.
Updates must prove themselves. An update command crosses only when it carries the maker’s signed instruction, checked at the crossing. The device, and the systems speaking to it, can distinguish the maker’s genuine instruction from any other voice claiming the maker’s authority. Underneath, it is the house engine: Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt.
When a device is compromised, it can be revoked: a hijacked device loses its name and its welcome, rather than remaining a trusted member of the fleet it was taken from. And the receipts accumulate into the maker’s Cyber Resilience Act evidence file, written by the crossings themselves. The clock is published: full obligations land December 11, 2027.
What it changes
For a maker, the compliance file stops being a document assembled under pressure and becomes a record the products wrote as they lived. Identity issued at birth, updates checked as they crossed, revocations recorded when they happened — that is the shape of evidence the Act expects, produced in the ordinary course of the device’s life.
For the people who buy the products, the change is quieter. A device with its own name can be told apart from every other device, welcomed when it proves itself, and cut off when it is taken. The home’s small machines stop being anonymous footholds that anyone holding a default password can gather into an army.
PlugCheck does not make a cheap device into a fine one, and it does not claim a named device cannot be attacked. It gives the device a name at birth, checks the instructions it obeys, and keeps the receipts — the three things a nameless device can never do.
See it
PlugCheck checks connected products for Europe’s Cyber Resilience Act, one birth identity at a time. PlugCheck — the product page · All the house articles · Lux Automations — ailux.ca