The origin of the Cube goes back to the first time we took on criminal liability for the use of machine tools in a FabLab, in 2015. You no doubt face the same doubts, and they cannot be settled with a “Trust me”. Here are the four questions that cost dearly:
“Who started the press at 3 a.m.?”
The situation: a restricted-use machine on a shared site, an incident occurs, with no witness.
Today: the access badge proves an entry into the building, and is very easily bypassed. It does not tell you who started the machine.
With Trust-Buster, start-up requires presence, hardware-proven identity, and a scheduled intervention. All three, or nothing. The log entry is signed: who, which equipment, when, under which rule, authorised or refused. The departure or absence of an authorised user is also detected, and an alarm indicates that the machine can still be activated, or the machine is even electrically protected against being restarted.
“Was this person authorised?”
The situation: co-activity, with cascading interventions by outside contractors, and an authorisation that expired three weeks ago.
Today: the answer is in a binder, reconstructed after the fact, and it will not stand up in front of an auditor.
With Trust-Buster: the authorisation is a rule, not a document. Once expired, it no longer authorises anything. A refusal is traced just like an approval. You obtain an enforceable list of granted and refused accesses, per contractor and per piece of equipment.
“The equipment was rewired live over the weekend.”
The situation: a power socket is moved, a power strip is added, or a control unit is reset.
Today: software supervision sees nothing. The tampering is discovered at the next incident.
With Trust-Buster: every unplugging, rewiring, reset and abnormal consumption is a security event. The perimeter locks down, the incident is logged. The timestamp of the bypass is directly accessible, and you can define a response rule requiring that you be contacted before the equipment is put back into service, even after the original wiring has been repaired.
“The site has been cut off from the world for three days. Is security still holding?”
The situation: your site is isolated, with no conventional IT link any more.
Today: IT security is adapted to work with OT equipment but depends heavily on the network, or even ends up relying on the cloud. In practice, it gets disarmed and work carries on, because production comes before IT.
With Trust-Buster, this is normal operation. The Cube decides on its own. Rules come in and logs go out via the phones of authorised and authenticated carriers.
The complete log for the isolation period is available, signed, with no gaps.