9 ms·
I hope we start to see some pretty strong regulation around what type of computer can be put inside of non-standard computing device, and guidance and regulatio
by neom 10y ago
I hope we start to see some pretty strong regulation around what type of computer can be put inside of non-standard computing device, and guidance and regulation on how it must be secured and updated. I work in city tech specifically around IoT and I'm incredibly worried about where all of this is going, cities DDoSing themselves in critical infrastructure points sounds pretty annoying.
- proaralyst 10y ago> annoying More likely fatal, or at least very costly. To expand: there was the recent[0] attack on Dallas' tornado alarm. Imagine that was a disabling attack ahead of a tornado instead. [0]: https://www.theregister.co.uk/2017/04/13/dtmf_replay_phreaked_out_the_dallas_tornado_alarm_say_researchers/ https://www.theregister.co.uk/2017/04/13/dtmf_replay_phreake...
- pjmlp 10y agoIncluding programming language restrictions and who to sue, like in other areas where human life is at risk.
- weberc2 10y ago> around what type of computer can be put inside of non-standard computing device What does "type of computer" mean? And why would this need regulation (are some "types of computers" less secure than others)?
- neom 10y agoThis: https://news.ycombinator.com/item?id=14247715 https://news.ycombinator.com/item?id=14247715 -- But also, there is no need to put a computer with a huge amount of resource in say, a baby bottle that can tell an app what temperature the milk is. In theory you could do a lot more (or at least different) damage with a P5 than a 486. The IoT stuff is usually cobbled together components, so we'll see things like a 500gig HD on a device (such as an environmental sensor for a city intersection) that passes off data and at most needs a couple gigs for OS and cache stuff. It's harder to start installing stuff on devices that are at the minimum specs for what they are designed to do. I'm not sure if that makes sense but I'm pretty sure there is some logic in there somewhere. Correct me if I'm wrong. it was just a thought. :)
- runeks 10y agoI think we should forget about regulating the implementation details for IoT devices, and instead mandate insurance, such that manufacturers become financially responsible for attacks committed using their hardware. I'm almost certain that an excise tax on IoT devices proportional to how much damage they can do, combined with giving white hats legal immunity to hack devices as well as being paid a part of the device-tax, will be both more effective and cheaper than having politicians write detailed laws on software security. If a company wants to drill into the ground looking for oil, and we know that this company can't pay the bill if things go wrong, we force them to pay an insurance premium/excise tax that covers the potential cleanup work. Of course we should do the same for devices that can be weaponized in this manner. For example: a tax of 1 cent/mbit/s of network throughput, where 10% goes to administration costs, and 90% is paid out to white hats who are able to penetrate the device and display a "defective device; return to <local device-drop-off office>" message on the screen.
- zild3d 10y agoSome devil's advocate thoughts - Proportional to how much damage they can do doesn't seem like a possible/reasonable measure. Should every car manufacturer now be responsible for insuring the cost of every car on the road causing a synchronized collision around the world? Should airplane manufacturers have to be insured for every airplane being in the sky, full of VIPs, and dropping onto the X most expensive buildings on earth, also full of prized possessions and more VIPs? About giving white hats legal immunity to hack devices and be paid. How do you determine who is a white hat? Why wouldn't every black hat attempt to play the part of a white hat, gaining free range to play around with a system without any legal concerns. And if they find a crippling vulnerability, being able to sell it in a black market / partner with other black hats, and pretend they found nothing?
- groby_b 10y agoYes, they should. Those of us that worked in regulated industries (health, nuclear, etc.) had to do that for a long time now, at least based on my experience in Germany. If your system has the potential to bring down the entire airfleet you sold, yes, you're on the hook for that event. Try building systems that are resilient in the face of failure, make that case to the insurer, premiums will go down. I'm tired of the argument "well, we can break A LOT of shit in one go, so we shouldn't be held liable for our sloppiness". It's "too big to fail" in disguise.
- zild3d 10y agoCan you clarify what you mean by "type of computer"? I hope you don't mean we should see regulation that say ARM 32 bit devices are fine for IoT, but TI 8 bit devices cannot be used. This vulnerability doesn't seem dependent on any particular type of computer. It's mostly due to default router passwords and open ports, which I agree points to the need for guidance and regulation on how systems are secured and updated
- kijin 10y agoI think GP is talking more about software than hardware. Most of today's IoT devices are intentionally crippled general-purpose computers. The only thing that's preventing them from doing everything a general-purpose computer can do, like running a different OS or attacking random websites, is the pre-installed software (often called firmware). In this case, we might say that the manufacturer has a much stronger responsibility to keep their devices under control than in the case of, say, a typical PC where the user assumes more of that responsibility. The less freedom you give your users, the more power you reserve for yourself. That power should come with corresponding responsibilities. For example: - Mandatory security auditing of all pre-installed software - Mandatory security updates for X years - Mandatory insurance for damages caused by vulnerabilities in your products Allow some of these requirements to be met by reusing previously audited and/or independently maintained software, giving manufacturers an incentive to stick with well-tested standard components. Waive some or all of the requirements if the device is allowed to be used as a general-purpose computer and/or all the software is freely available. Best case scenario: we get routers and TVs labeled "Red Hat Embedded Linux inside: security updates guaranteed for 10 years."
- noobiemcfoob 10y ago> Best case scenario: we get routers and TVs labeled "Red Hat Embedded Linux inside: security updates guaranteed for 10 years." As long as the industry is allowed to come to these SLA-like stamps on their own, on a per product basis, without government regulation breathing down their neck, this is exactly the way to go. IoT is so wide, there is no such thing as a "one size fits all". Any talk about across the board rules stinks of missing this obvious reality.
- dplgk 10y agoThe problem is that gov't is extremely bad at regulating computers/Internet because half of them never used email and the other half if is paid by big interest groups.