“We were able to make the device completely inoperable by preventing a local operator from controlling the drill through the onboard display and disabling the trigger button."
Why doesn’t the wrench then only have the ability to talk to a local server and that server have internet then? If that were the case the wrench would have no reason to download anything from the Internet, just speak to the local server. Probably wont fix every vulnerability but it can’t be more vulnerable.
The wrench has a web UI to program it or monitor it. It also talks a few “standardised” car-manufacturer protocols for recieving and sending instructions/measurements/certifications. And it can send also send stuff to a local history server.
The majority of the CVEs seem to exist in its onboard webUI system, with a few in the manufacturing protocols.
But yes, IoT devices should be on an isolated vlan or on pvlans. That should be standard practice.
Access from wrench->server should be via a firewall that logs connections. And access from management->wrench should be via firewall with logging.
There is no reason for unauthorized people to have access to the wrenches network, and there is no need for the wrench to communicate with anything other than the local history server.
This feels like one of those things that’ll go exactly opposite of what I expect. Ten years from now I’m be explaining to my grandkids how much harder live was before wrenches were Internet connected.
I can’t imagine a single valid reason to have an Internet connected wrench. But life is weird, so I’m guessing I’ll keep one synced to my fax machine someday.
I am not a fan of making everything part of ‘the internet of things’
Nearly all IoT items are developed for idiots, which is interesting because most of them are also made by idiots.
Iot wrenches are built for blue collar workers to ensure proper tooling of complex parts on production lines
And to then certify it’s tightened to spec and send that cert to a logging server, for things like aviation
Why doesn’t the wrench then only have the ability to talk to a local server and that server have internet then? If that were the case the wrench would have no reason to download anything from the Internet, just speak to the local server. Probably wont fix every vulnerability but it can’t be more vulnerable.
Yup, that would be sensible security practices.
The wrench has a web UI to program it or monitor it. It also talks a few “standardised” car-manufacturer protocols for recieving and sending instructions/measurements/certifications. And it can send also send stuff to a local history server.
The majority of the CVEs seem to exist in its onboard webUI system, with a few in the manufacturing protocols.
But yes, IoT devices should be on an isolated vlan or on pvlans. That should be standard practice.
Access from wrench->server should be via a firewall that logs connections. And access from management->wrench should be via firewall with logging.
There is no reason for unauthorized people to have access to the wrenches network, and there is no need for the wrench to communicate with anything other than the local history server.
except in this case, where it looks like there are more than valid reasons
This feels like one of those things that’ll go exactly opposite of what I expect. Ten years from now I’m be explaining to my grandkids how much harder live was before wrenches were Internet connected.
I can’t imagine a single valid reason to have an Internet connected wrench. But life is weird, so I’m guessing I’ll keep one synced to my fax machine someday.
Ok cool