4 ms·
IoT device manufacturers should be sued for negligence.
by 2OEH8eoCRo0 5y ago
IoT device manufacturers should be sued for negligence.
- gruez 5y agoYou mean the manufacturers based in china that have little in the way of assets, and might disappear before the issues become apparent?
- east2west 5y agoIf it is Chinese companies, then presumably a lot of those devices are in China as well. Wondering whether they might be used to bring down the Great FireWall of China. At least any attempt might force the Chinese government to crack down on the manufacturers to improve device security.
- sam_lowry_ 5y agoAFAICS, this attack is running on Microtik routers. Mikrotik is a Latvian company. They are successfully competing with Cisco and Juniper in feature-set and performance at a fraction of a price. The thing is, they provided a large, under-educated user base with powerful, complex and utterly sophisticated tools. That the attacker targeted those and not less numerous and better guarded mainstream manufacturers only pays tribute to the success of Mikrotik.
- Y_Y 5y agoYou forgot to include your affiliate link.
- sam_lowry_ 5y agoI am unaffiliated irregular customer They have great hardware, but I prefer rinning OpenWRT on their hardware.
- donmcronald 5y ago> The thing is, they provided a large, under-educated user base with powerful, complex and utterly sophisticated tools. Do you think the expensive manufacturers don’t do that? I’ve seen un-configured, un-updated, EoL Cisco equipment. Small businesses get sold it because it’s “the best”, but they don’t actually need anything nearly that complicated and don’t want to pay the ongoing costs so you end up with things like managed switches being used like you’d use a dumb switch that’s 1/10th of the price.
- yelling_cat 5y ago>I’ve seen un-configured, un-updated, EoL Cisco equipment. I was in a server room a couple of years ago that looked like a Cisco museum, with some of the kit dating back to the early 2000s. When I mentioned that running a business on gear that had been EoL'd for a decade+ wasn't quite up to security best practices my contact shrugged and said they wouldn't be updating any of it in any case since they'd long since lost all of their access passwords.
- j_walter 5y agoI trashed my Microtik router as soon as I started seeing my bandwidth jump and a lot of traffic from Isreal a few years ago. There was no mitigation of whatever was going on and clearly there were issues...turns out Microtik's RouterOS had multiple vulnerabilities. Ubiquiti on the other hand has been more than adequate for my needs and is even easier to setup than Microtik. https://www.cvedetails.com/product/23641/Mikrotik-Routeros.html?vendor_id=12508 https://www.cvedetails.com/product/23641/Mikrotik-Routeros.h...
- sam_lowry_ 5y agoUbiquity tarnished its image with the leak of client credentials from its Cloud offering.
- j_walter 5y agoNo doubt that was concerning. That hack (not really a leak) sounds like it was due to an AWS issue and probably someone with intricate knowledge of their systems. Eventually they responded, but not until a whistleblower called them out first (thanks to their legal team holding them back from disclosing the event).
- jszymborski 5y agoStep 1: Require commercial IoT to meet software compliance Step 2: Ban IoT that doesn't meet software compliance Step 3: Pray that the compliance standard makes any sense and that the NSA don't require backdoors or suspect CRNG.
- jl6 5y agoOr, mandatory 3rd party liability insurance for anyone operating an internet connection. Insurance premium discounts for running only security-audited devices.
- gizdan 5y agoUsers shouldn't be punished by the negligence of manufacturers. Sure the majority of HN will know to ensure they run secure products or something, but you can't expected nana to know that. She just wants to talk to some device to help her a little.
- jl6 5y agoA good way to teach people to run secure products is to charge them more for running insecure products. The general public can’t distinguish between secure and insecure products, but they can read a list of products that are covered by the $0.99/month insurance plan, and anything not on that list you need the $1.99/month plan. DDoS victims can then make a claim against the insurance companies (who own the liability arising from each IP address; ISPs can de-NAT), a court can evaluate the evidence if necessary, and the insurance providers pay out. N.B. It’s actually experts who would be penalized most by this scheme, because if you do something like run a customized FreeBSD box, it’s unlikely to appear on the audited-device list.
- Nextgrid 5y ago> N.B. It’s actually experts who would be penalized most by this scheme, because if you do something like run a customized FreeBSD box, it’s unlikely to appear on the audited-device list. The "audit" can be as simple as the insurance company running automated pentests trying published exploits and passwords. That would still achieve the desired goal (the majority of botnets spread via well-known vulnerabilities and/or bruteforced credentials, custom equipment where manual effort is needed on the attacker's part are a minority) while allowing enthusiasts to run custom hardware.
- briffle 5y agoHow can a home user protect themselves from this, when most manufactures only release a very, shockingly small number of firmware updates, and don't notify users of the updates?