Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Blade Runner Redux: Do Embedded Systems Need A Time To Die?

chicksdaddy (814965) writes | about 3 months ago

1

chicksdaddy (814965) writes "In a not-so-strange case of life imitating Blade Runner, Dan Geer, the CISO of In-Q-Tel, has proposed making embedded devices such as industrial control and SCADA systems more 'human' (http://geer.tinho.net/geer.secot.7v14.txt) in order to manage a future in which hundreds of billions of them will populate every corner of our personal, professional and lived environments. (http://www.gartner.com/newsroom/id/2636073)

Geer was speaking at The Security of Things Forum (http://www.securityofthings.com), a conference focused on securing The Internet of Things last Wednesday. He struck a wary tone, saying that "we are at the knee of the curve for deployment of a different model of computation," as the world shifts from an Internet of 'computers' to one of embedded systems that is many times larger.

Individually, these devices may not be particularly valuable. But, together, IoT systems are tremendously powerful and capable of causing tremendous social disruption. Geer noted the way that embedded systems, many outfitted with remote sensors, now help manage everything from transportation to food production in the U.S. and other developed nations.

“Is all the technologic dependency, and the data that fuels it, making us more resilient or more fragile?" he wondered. Geer noted the appearance of malware like TheMoon (https://isc.sans.edu/forums/diary/Linksys+Worm+TheMoon+Summary+What+we+know+so+far/17633), which spreads between vulnerable home routers, as one example of how a population of vulnerable, unpatchable embedded devices might be cobbled into a force of mass disruption.

Taking a page out of Philip Dick's book (http://www.goodreads.com/book/show/7082.Do_Androids_Dream_of_Electric_Sheep_) or at least Ridley Scott's movie (http://www.imdb.com/name/nm0000631/) Geer proposes a novel solution: “Perhaps what is needed is for embedded systems to be more like humans.”

By "human," Geer means that embedded systems that do not have a means of being (securely) managed and updated remotely should be configured with some kind of "end of life" past which they will cease to operate. Allowing embedded systems to 'die' will remove a population of remote and insecure devices from the Internet ecosystem and prevent those devices from falling into the hands of cyber criminals or other malicious actors, Geer argued.

The idea has many parallels with Scott's 1982 classic, Blade Runner, in which a group of rebellious, human-like androids – or “replicants” – return to a ruined Earth to seek out their maker. Their objective: find a way to disable an programmed ‘end of life’ in each of them. In essence: the replicants want to become immortal."

Link to Original Source

cancel ×

1 comment

Sorry! There are no comments related to the filter you selected.

There's a term for this: Planned obsolescence. (1)

The Altruist (1448701) | about 3 months ago | (#46994429)

In some instances, and I can fathom just a few - mostly in regards to 32-bit time-stamp bugs, end of life is acceptable; this product should no longer be in service. Given enough time, a bug of convenience will throw the entire system out of whack. Said bugs of convenience are put in place by developers who cannot fathom the system being in use after the year 2106 (or 2038) or the entire flash memory module will fill up or the EEPROM will finally see 100,001 write operations.

But in others, I'm finding it hard to justify. There are many industries where "it's worked for years and we're not going to change it" is the modus operandi. In manufacturing operations, like a paper mill I worked in, many times the individual embedded systems don't have to be complicated; they have one job and they just have to do it right. In fact, they'll often employ the same out-dated desktop and servers on isolated networks for over 15 years simply because it's still working and there's no pressing need to change.

So, in some instances yes, sure, let's give the poor chips a dignified rest. But I'd really rather not find out that a when the warranty on a pace-maker goes ou...

(User expired during the writing of this post.)

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>