Articles · Infrastructure & Cities
Your building obeys anyone who asks
Most building systems take orders without asking who is speaking. TowerCheck makes sure the orders come from someone allowed to give them, and receipts every vendor session.
By Lucian · Lux Automations
The problem
Your building takes orders all day. Heating and cooling adjust, doors lock and unlock, lights follow their schedules, lifts answer their calls. Behind each of those ordinary acts, a controller obeyed an instruction that crossed to it from somewhere on the building’s network. The quiet fact is that most of those controllers never asked who sent it.
The product page cites Armis Labs vendor research: 91% of building automation systems communicate over protocols with no authentication at all. BACnet, KNX and Modbus never ask who is speaking, so any device on the network can issue commands the controllers will obey. The same research found 73% of organizations run at least one such system carrying a known exploited vulnerability.
This is not a flaw anyone chose. These protocols were designed for closed rooms and trusted wires, and buildings outgrew both. Vendor clouds, property-manager networks and tenant systems now cross to the same controllers, through the same unauthenticated conversation, and a vendor’s service visit leaves little record of what was touched while they were in.
The technology
TowerCheck begins at the network door, with identity. Controllers and vendor service tools carry issued identities, so the parties at a crossing are known rather than assumed. A device that cannot present its issued identity is not simply another voice on the wire to be obeyed.
Commands crossing between systems are then mandate-checked. What may instruct what is a mandate, not an accident of wiring: a lighting controller has no business instructing an access panel, in the product page’s example, and under TowerCheck that instruction does not cross. Each system’s mandate describes the orders it may give and receive, and the check enforces the description at the join.
Every vendor session leaves a signed receipt: who came in, what they touched, when they left. Underneath, it is the house engine at work: Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt. When a tool or a vendor relationship ends, precisely that one can be revoked — the building runs on.
What it changes
For building owners and operators, the change is that the building’s obedience becomes deliberate. Orders still flow all day, as they must. The difference is that each order crossed from a known party, inside a checked mandate, and the crossing was written down. A strange instruction can be traced to its source instead of dissolving into the network’s general hum.
Vendor work changes in the same way. A service session is named, scoped and receipted, which serves the building and the vendor alike: the building can show what was done on its systems, and the vendor can show that what was done was exactly the work they came to do. When tenants or insurers ask how the building’s systems are accessed, the answer is a record, not an assurance.
The building does not become a fortress, and nothing here claims it cannot be troubled. It becomes a place where controllers are known, commands are checked, and sessions are receipted — a building that asks who is speaking before it obeys.
See it
TowerCheck checks a building’s lifts, doors and controllers at the network door. TowerCheck — the product page · All the house articles · Lux Automations — ailux.ca