SBN

Inner Circle Podcast: Episode 004

My guest on the Inner Circle podcast this week is Cesar Cerrudo, CTO of IOActive. Our topic revolves around ransomware–but with a twist that involves robots.

I think we can all agree that ransomware is annoying. When it comes to the standard ransomware business model of encrypting data and holding it hostage, though, there’s a simple solution. As long as you have current backups of your data, you can simply ignore the ransomware demand and restore your unencrypted data from backup.

IOActive

Researchers from IOActive have uncovered a potential twist on ransomware, however, that would make it much harder to ignore or recover from without paying the ransom. If attackers use malware to exploit vulnerabilities in robots and take them offline or make them dysfunctional, that could have a significant financial impact on companies that rely on robot automation for manufacturing, production, and logistics.

A blog post from IOActive explains, “Businesses and factories lose money every second one of their robots is non-operational. It stands to reason, then, that service and/or production disruption is another strategy for attackers. Instead of encrypting data, an attacker could target key robot software components to make the robot non-operational until the ransom is paid.”

The robot ransomware angle has two significant and insidious advantages over the standard ransomware model. First, as mentioned above, recovery is more complex and can’t be achieved by simply restoring data from backup. Second, the companies that rely on robots will suffer huge financial losses while the robots remain dysfunctional–providing a massive incentive to simply pay the ransom and get back to business.

The IOActive blog post points out that many robots don’t provide any simple way to perform a factory reset or update the operating system or software. “Having a technician fix a robot problem could take weeks depending on availability. Ironically, during our research, our robot started to malfunction. The only option to repair it was to send it back to the vendor. We had to ship it from our country to the US and wait a couple weeks for its return. We also had to cover the associated shipping costs, including customs handling.”

As promised in the podcast, here are the links to the resources from IOActive:

Check out the podcast to learn more. Share your thoughts or ask questions in the comments below.

*** This is a Security Bloggers Network syndicated blog from Security – TechSpective authored by Tony Bradley. Read the original post at: http://techspective.net/2018/03/09/inner-circle-podcast-episode-004/

Tony Bradley

I have a passion for technology and gadgets--with a focus on Microsoft and security--and a desire to help others understand how technology can affect or improve their lives. I also love spending time with my wife, 7 kids, 2 dogs, 4 cats, 3 rabbits, 2 ferrets, pot-bellied pig and sulcata tortoise, and I like to think I enjoy reading and golf even though I never find time for either. You can contact me directly at [email protected]. For more from me, you can follow me on Twitter and Facebook.

tony-bradley has 191 posts and counting.See all posts by tony-bradley