Articles · Infrastructure & Cities
The attacks arrive at the crossings
Connected vehicles are reached remotely, through telematics, clouds and service tools. FleetDoor checks every arrival, and keeps a signed record across the vehicle’s whole life.
By Lucian · Lux Automations
The problem
A connected vehicle is never alone. It crosses to manufacturer telematics clouds, it receives dealer and service tools at the workshop, and fleet systems cross both ways around it. The car itself is heavily engineered. The crossings around it — remote, frequent, and spread across makers, dealers and platforms — are where it is most often reached.
Upstream Security’s 2026 report, cited on the product page as vendor research, counted 494 publicly reported automotive cybersecurity incidents in 2025, up 21% year over year. Of those, 92% were carried out remotely, and 67% involved telematics or cloud vectors. The pattern matches the product page’s opening line: the attacks arrive at the crossings, not at the car.
Each crossing involves a different party holding a different kind of access. A cloud service, a dealer tool and the vehicle itself may all take part in one service story, yet no single signed record follows the vehicle from build to sale to service to resale. When something is questioned years later, the story must be rebuilt from separate systems that were never designed to agree.
The technology
FleetDoor gives every party at the crossing an issued identity: vehicles, dealer tools and cloud services each hold an identity of their own, so every arrival at the vehicle — and every departure from it — is made by a known party, in its own name.
What a service session may do is then mandate-checked. A dealer tool may do its job — and nothing past it. The mandate describes the session’s proper work, and the check holds the session inside that description at the crossing, whether the tool is in the workshop or reaching the vehicle remotely.
Signed receipts follow the vehicle across its whole life: build, sale, service, resale — one signed story rather than a shelf of partial ones. That is the audit trail UNECE R155 expects, in the product page’s words. Underneath, it is the house engine: Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt. One tool or one vehicle can be revoked precisely, the moment it should be, without disturbing the rest.
What it changes
For makers and suppliers, who must run a certified cybersecurity management system under UNECE R155 to sell into adopting markets, the change is evidence that travels with the product. The vehicle’s crossings are not reconstructed for an audit; they are read from the receipts the crossings left, across the same life the regulation follows.
For dealers, fleets and owners, the same record works at human scale. A service session that stayed inside its mandate is provable. A tool that should no longer touch vehicles can be cut off on its own. And a vehicle changing hands carries its signed story with it, so the next keeper inherits a record rather than a mystery.
FleetDoor is about connected vehicles, car by car — their clouds, their service tools, their crossings. It does not claim the car cannot be attacked. It checks every arrival, and it keeps the record of a vehicle’s life in one signed hand.
See it
FleetDoor checks connected vehicles, car by car, from build to resale. FleetDoor — the product page · All the house articles · Lux Automations — ailux.ca